Inheritable options causes panic

Hi there,
func main() {
        parser := argparse.NewParser("q-scheduler", "", nil)

	startParser := parser.AddCommand("start", "Starts the scheduler", &argparse.ParserConfig{
		DisableHelp: true,
	})

	initParser := parser.AddCommand("init", "", &argparse.ParserConfig{
		DisableHelp: true,
	})

	configPath := parser.String("", "config-path", &argparse.Option{
		Default:     "/etc/q-scheduler/config.toml",
		Help:        "Path to the configuration file of q-scheduler.",
		Inheritable: true,
	})

	if err := parser.Parse(nil); err != nil {
		fmt.Println(err.Error())
		return
	}
}

This panics:
omikron@xps13 ~/g/q-scheduler (main) [1]> go run cmd/q-scheduler/main.go start --config-path abc
panic: runtime error: slice bounds out of range [1:0]

goroutine 1 [running]:
github.com/hellflame/argparse.min({0xe57678?, 0x84210842?, 0xc0001738c0?})
        /opt/go/pkg/mod/github.com/hellflame/argparse@v1.8.0/levenshtein.go:63 +0x7c
github.com/hellflame/argparse.decideMatch({0x7ffcaffd478c, 0xd}, {0x0, 0x0, 0xc0002da460?})
        /opt/go/pkg/mod/github.com/hellflame/argparse@v1.8.0/levenshtein.go:8 +0x87
github.com/hellflame/argparse.(*Parser).Parse(0xc0002da380, {0xc000132020?, 0x7ffcaffd4786?, 0x5?})
        /opt/go/pkg/mod/github.com/hellflame/argparse@v1.8.0/parse.go:502 +0x88d
github.com/hellflame/argparse.(*Parser).Parse(0xc0002da1c0, {0x0?, 0x0?, 0xa4849d?})
        /opt/go/pkg/mod/github.com/hellflame/argparse@v1.8.0/parse.go:432 +0x19b
main.main()
        /home/omikron/git/q-scheduler/cmd/q-scheduler/main.go:28 +0x145
exit status 2

May it be an option to change the behavior from Inheritable that it is possible to inherit the option on all parsers not just the ones defined after the option?

May it be an option to change the behavior from Inheritable that it is possible to inherit the option on all parsers not just the ones defined after the option?

Well, this is what I wanted to do first, but it may be too complex to use it. So I just took the simple way.
The panic can be fixed in no time.

I get the point, but I don't think, the way its implemented now, reduce the complexity.
I'd say if one is thinking about an option that is used in multiple, but not all parsers, the probability will be high, the user want to use the feature on multiple different parsers.
In my understanding this won't be possible right now

Well, in some cases like only one argument to inherit or arguments with the same hierarchy to inherit,  you can choose to inherit it or them in all parsers or some parsers. This way, I think it's easy to use the inherit here.
And here, one option is easy to control to be inherited by one or many parsers actually. This one option should be declared before that or those parsers.

an option that is used in multiple, but not all parsers

Or I just misunderstand the scenario =.=

Maybe with this code example, the problem will be clearer. bcArgs should be only usable by bParser and cParser, cdArgs only by cParser and dParser.
package main

import (
	"fmt"
	"github.com/hellflame/argparse"
)

func main() {
	parser := argparse.NewParser("", "", nil)
	aParser := parser.AddCommand("a", "", nil)
	bcArgs := parser.Strings("", "bc", &argparse.Option{Inheritable: true})
	bParser := parser.AddCommand("b", "", nil)
	cdArgs := parser.Strings("", "cd", &argparse.Option{Inheritable: true})
	cParser := parser.AddCommand("c", "", nil)
	dParser := parser.AddCommand("d", "", nil)

	err := parser.Parse(nil)
	if err != nil {
		fmt.Println(err.Error())
		return
	}

	fmt.Println(aParser, bcArgs, bParser, cdArgs, cParser, dParser)
}

Another topic would be, that options with Inheritable option should (in my opinion) not be registered on the main parser, which is by now the case.

I designed this Inheritable feature main to deal the scenario described in #15. In which the sub parsers need to inherit the  Inheritable option. I guess if the sub parsers don't inherit from the main parser, it can't be called inherit, right? Or some virtual option feature should be implemented? ......
I don't know what's your case would be like?  And that's right, this would be another topic to discuss.

Sorry for the problem.
Panic problem is fixed by version 1.8.1.
Closing this issue for the panic is fixed, raise another issue for more topic to discuss.


Development

Coverage decreased (-1.2%) to 47.561% when pulling f10d555a3cfab20e81f1e73465a6f374931aa16a on development into 76039ada34c2daabbe21864098d561a68b0af1f3 on master.


Use dotnet strong typed resource builder

PR Summary
Now .Net SDK brought back a strong typed resource support so we can switch from our ResGen tool.
For WPF projects (Microsoft.Management.UI.Internal) the  .Net SDK support does not work OOB so we have to implement a workaround in csproj file.
(Also I discovered that now all .Net dll-s is in ReadyToRun format and PowerShell distributive doubled in size. So we could turn on the feature too. It will add ~20Mb (10%). I removed this in last commit but could bring back.)
Docs https://docs.microsoft.com/en-us/dotnet/core/compatibility/msbuild#net-core-30
PR Context
Fix #2882
Related #666
Related #5777
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[x] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[ ] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:

Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host).
Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

Please add ready to run in a separate PR as it needs to be back ported.

@iSazonov master branch has moved to .NET 5 preview 3, do want to check if the workaround is still needed?

@adityapatwardhan Yes, we need. I do not see any progress in MSBuild repo. Tracking issue https://github.com/microsoft/msbuild/issues/4751

/cc @mklement0 The PR is one step to resolve #666

@daxian-dbw Could you please merge?

The files are generated in obj\ folder where *.resource are. If Start-PSBuild success you have the files.
VS Code works well for me too (after restart?).

Found the .cs files under obj\Debug\netcoreapp5.0, but opening in VS Code still doesn't work -- a lot errors due to the resource string references. @TravisEz13 do you see the same issue?

Currently we have to use Build.psm1 module to build PowerShell.
Additional benefits - now if we change any resx file it will be automatically compiled without needs to run Start-PSBuild -ResGen.

ResGen doesn't depend on PowerShell. Anyone wants to build without PowerShell can do it as described in our doc: https://github.com/PowerShell/PowerShell/blob/master/docs/building/internals.md#resgen
I agree that's a benefit, but personally, I don't think it's convincing ... I personally don't want to incorporate everything into msbuild, as I personally believe a script is more maintainable than black magic in msbuild 😄

@iSazonov Can you please address @JoeRobich's comment?
I notice this comment from the Ominisharp issue you opened: https://github.com/OmniSharp/omnisharp-vscode/issues/3781#issuecomment-630999837
Have you guys reached to a conclusion on the issue and how to fix it?

@daxian-dbw My current intention is to put generated files in custom gen folder. I will prepare the commit tomorrow.

As for OmniSharp behavior my understanding is:

.Net SDK targets explicitly define exclusions obj/**/*.cs from Compile.
OmniSharp follow this - it ignores the files at startup
Strong Typed Resource Generator add strong typed generated files to Compile list on the fly.
OnmiSharp follow this too - if we run dotnet build it discover the files.

I don't know there general fix should be done (in OmniSharp to follow modern .Net SDK behavior or in .Net SDK). I will simply put the files in gen folder.

@daxian-dbw Now VS Code works well.

I don't know where the general fix should be done (in OmniSharp to follow modern .Net SDK behavior or in .Net SDK).

Here are my thoughts on this. Generating the resource classes under a /gen folder to move them out of the /obj folder is the wrong fix.
The issue seems to be that you want design time intellisense for these resource files, which is understandable. The problem is that these backing files are only generated when the Build task is run in MSBuild. Design time builds do not run the Build task, instead they run the Compile task. Since these files aren't generated during when Compile is run, they are not considered part of the compilation and not added to the open Workspace.
You can add a short Target to run the resource generator before the Compile task (See https://github.com/OmniSharp/omnisharp-vscode/issues/3781#issuecomment-630999837). Now they will be part of the Compilation and will be part of the Workspace when working from an IDE. They will also be updated when they are changed within the IDE instead of requiring a full build. Since you likely do not want them to be regenerated constantly, defining the Inputs and Outputs for targets is the MSBuild mechanism so that targets are only run when changes have been made.

Generating the resource classes under a /gen folder to move them out of the /obj folder is the wrong fix.

We cannot create a "fix" in PowerShell repo. We can only create a "workaround".
Right place for the fix is either OmniSharp repo or .Net SDK repo.
As I mentioned .Net explicitly moved generating strong typed resources from design time to build time - it is new standard. I don't think they will change this. So expectation is that OmniSharp will follow the new behavior too.
As for workarounds, we have two ones:

put new files in custom gen directory
add new target

I don't like adding new target because this again changes standard .Net SDK behavior - it can have
side effects and later we can catch other issues.

@iSazonov @anmenaga @TravisEz13 @adityapatwardhan and I had a offline discussion on this PR, and we agreed the built-in resgen tool in MSBuild is what we should move forward with. Here are some but not all the benefits:

No need to run Start-ResGen before the build when there is any new resource files/strings added.
Other powershell projects can do the same in .csproj for their resource strings, without having to copy over the src\ResGen code and the related build script.

However, the built-in resgen tool is not ready yet for us to depend on, and hence your workaround in the Microsoft.PowerShell.GraphicalHost.csproj project.
The changes in Microsoft.PowerShell.GraphicalHost.csproj is what we felt most concerned. A proposal is to use a hybrid way moving toward our ultimate goal:

for this PR, remove the changes to Microsoft.PowerShell.GraphicalHost.csproj and keep the rest
keep src\Res and make it only to generate .cs files for the GraphicalHost.csproj
So only the resources for GraphicalHost.csproj are generated using our existing tool, and all rest resources are handled by the built-in tool in MSBuild.
Do you think that's feasible?

The changes in Microsoft.PowerShell.GraphicalHost.csproj is what we felt most concerned. A proposal is to use a hybrid way moving toward our ultimate goal

If it is not a priority in days I'd ask MSFT team internally communicate with SDK team (they have low public activity) - they could tell how they plan to work with WPF projects and strongly typed resources. If they have a solution or workaround we could implement this and simplify our build.


lnd update to v0.15.2

urgent bugfix update to be used by all new builds

Not familiar with the setup here, but doesn't the comment on line 6 say you should also update lnd.update.sh  at the same time?

Not familiar with the setup here, but doesn't the comment on line 6 say you should also update lnd.update.sh at the same time?

thanks for checking. That lndUpdateVersion is basically does add the option to apply the fix with PGP verification hen it someone patched scripts, but not the whole SDcard image yet (aka dirty update - not recommended)
When a new SDcard image will be released (which is the plan here) the setting si irrelevelant again as the image will contaimn the latest LND version.


feat(genesis): use OPCM for deployments

#176  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @jakim929 and the rest of your teammates on  Graphite


[nmstate-0.3] state: Don't merge state:down if not defined in desire state

When user include only interface name in desire state, we should
treat it as state:up instead of merging from current state:down.
Test case added.

@cathay4t It seems the RPM build for centos-stream is failing. But I think it is not related to this PR.


ui: fix import instance form root disk label

Description
Wrong key 'title' was used instead of 'label'

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[ ] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[x] Trivial

Screenshots (if appropriate):
Before:

.
.
.
.
After:

How Has This Been Tested?

@blueorangutan ui

@shwstppr a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: http://qa.cloudstack.cloud:8080/client/pr/5252 (SL-JID-445)


Crash in concatenating encoded term positions

Hi Doug, I've been getting a crash when building an index where there is lots of empty strings. I've isolated it down to this simple case:
from searcharray import SearchArray  # version: 0.0.69
SearchArray.index(["a", ""], batch_size=1)

Here's the stack:
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
Cell In[198], line 3
      1 # import pdb; pdb.pm()
      2 # SearchArray.index(foods["brand_name"].head(1_000).fillna(""), batch_size=100, tokenizer=tokenizer)
----> 3 SearchArray.index(["a", ""], batch_size=1)

File [~/.local/lib/python3.11/site-packages/searcharray/postings.py:284](http://<IP_ADDRESS>:8888/home/macro/.local/lib/python3.11/site-packages/searcharray/postings.py#line=283), in SearchArray.index(cls, array, tokenizer, truncate, batch_size, avoid_copies, workers, cache_gt_than, data_dir, autowarm)
    280 if not is_list_like(array):
    281     raise TypeError("Expected list-like object, got {}".format(type(array)))
    283 term_mat, posns, term_dict, avg_doc_length, doc_lens =\
--> 284     build_index_from_tokenizer(array, tokenizer, batch_size=batch_size,
    285                                truncate=truncate,
    286                                data_dir=data_dir,
    287                                cache_gt_than=cache_gt_than,
    288                                workers=workers)
    290 if autowarm:
    291     posns.warm()

File [~/.local/lib/python3.11/site-packages/searcharray/indexing.py:277](http://<IP_ADDRESS>:8888/home/macro/.local/lib/python3.11/site-packages/searcharray/indexing.py#line=276), in build_index_from_tokenizer(array, tokenizer, batch_size, data_dir, truncate, workers, cache_gt_than)
    275             futures = []
    276     if len(futures) > 0:
--> 277         bit_posns = _process_batches(term_doc, batch_size,
    278                                      futures,
    279                                      last_batch_beg_processed,
    280                                      bit_posns, doc_lens, truncate=truncate)
    282 doc_lens = np.concatenate(doc_lens)
    284 avg_doc_length = np.mean(doc_lens)

File [~/.local/lib/python3.11/site-packages/searcharray/indexing.py:193](http://<IP_ADDRESS>:8888/home/macro/.local/lib/python3.11/site-packages/searcharray/indexing.py#line=192), in _process_batches(term_doc, batch_size, futures, last_batch_beg_processed, bit_posns, doc_lens, truncate)
    191 else:
    192     logger.info("(main thread) Concatenating bit positions")
--> 193     bit_posns.concat(batch_bit_posns)
    194     logger.info("(main thread) Concatenated bit positions... Done")
    196 doc_lens.append(batch_doc_lens)

File [~/.local/lib/python3.11/site-packages/searcharray/phrase/middle_out.py:349](http://<IP_ADDRESS>:8888/home/macro/.local/lib/python3.11/site-packages/searcharray/phrase/middle_out.py#line=348), in PosnBitArray.concat(self, other)
    347     self.clear_cache()
    348     return self
--> 349 self.encoded_term_posns = ArrayDict.concat(self.encoded_term_posns, other.encoded_term_posns)
    350 self.max_doc_id = max(self.max_doc_id, other.max_doc_id)
    351 self.clear_cache()

File [~/.local/lib/python3.11/site-packages/searcharray/phrase/memmap_arrays.py:64](http://<IP_ADDRESS>:8888/home/macro/.local/lib/python3.11/site-packages/searcharray/phrase/memmap_arrays.py#line=63), in ArrayDict.concat(lhs, rhs, sort)
     62 all_for_key = [value]
     63 curr_offset += value.size
---> 64 if key in rhs.metadata:
     65     rhs_value = rhs[key]
     66     all_for_key.append(rhs_value)

AttributeError: 'dict' object has no attribute 'metadata'

It seems when combining batches, if other didn't have any encoded positions than it returns an empty dict and crashes (expects some other type). I noticed there is some relevant guard code for this in the case of self but not other.

Hey @JVillella thank you! For now you can try a workaround with an _ or something as a dummy term, but I'll try to add a test case and a fix.

Fixed in v0.0.70 :)

wow, you're fast! thank you :)


[PDI-12278]: MonetDB Bulk Loader error with MonetDB Jan 2014-SP2 bugfix  release

The problem was:
Starting from Jan 2014-SP2 bugfix release we should not use double write of empty line (see the sample http://dev.monetdb.org/hg/MonetDB/file/tip/java/example/SQLcopyinto.java).
At the same time for "old" versions of MonetDB (before Jan 2014-SP2) we are still need to do this one otherwise the error appears.
The fix consists of:
1)Getting current MonetDB version (via JDBC property) during execution the step
2)Defining if the current version is before boundary Jan 2014-SP2 version or not (so-called compatibility with old version db mode).
3)Addition condition for such case during writing buffer.
Also there are several unit tests.

@deinspanjer Hi, could you please review this one.

@deinspanjer
Hi,
I've fixed one of remark and commented another one.
Could you please review again.


Install plugin

Extract NuGet package content from folder for .NET Framework.
Also download dependencies.
TODO:

[ ] Pass in target framework monikers.
[x] Refactor repository creation.
[ ] Download required dependencies.
[ ] Handle errors.

Notes:

Dependencies in package as global tools?
Reading content from contained .xml?

PackagesConfigWriter

Lets simplify things for this release

No dependencies: All dependencies must be part of the package.
Install and update do through PackageConfigWriter.


Add preprocessRecord function

See https://github.com/senzing-garage/garage-roadmap/issues/22

Pull requests:

https://github.com/senzing-garage/sz-sdk-python-abstract/pull/76


upgrade to latest rollup and latest dependency versions

This just upgrades dependencies to the latest and updates tests to newer rollup config.
No functional changes to the plugin itself, I was just having some trouble with the version of rollup-pluginutils that it depended on.

@mnutt we've put together https://www.npmjs.com/package/@rollup/plugin-html that's maintained out of the official plugins repo.

Thanks! 👍

@mnutt we've put together https://www.npmjs.com/package/@rollup/plugin-html

But it is not the same.
@bdadam version does:
import htmlFile from 'example.html';

And converts that into:
const htmlFile = "this is the source of example.html";

Yours does not...


Add formatting/linting to project

Noticed there was no consistent formatting/linting included for this project and it will cause unnecessary merge conflicts. This should be enforced by the CI as well.

We seem to have a number of open PRs, let's try to keep this issue in mind and do it at a moment with very little opens. @volovyk-s .

Using ESLint and Prettier should be enforced. I have created an opinionated version of a ESLint config called eslint-config-near which could be used here. It is pretty strict, but IMO makes the code more readable and thus more maintainable. There is also a Prettier config called prettier-config-near by the NF engineering team. We could try to have consistent linting and formatting practices across our tooling

@petarvujovic98 I can see that your config is more advanced, but I do not think that we need to create "new standards". I like something that is as close to default as possible. And there is definitely no reason to create 2 standards in NEAR ecosystem, let's just contribute to the existing one, if we really want to have something custom.

@volovyks That is something that we worked on at NF Edu a few months ago, so it could change. But what is the current standard for linting rules?

There is no one standard at the moment. But if I would create one - it should be based on what we have in near-api-js. It is the biggest JS project. Also, with time we are planning to move other JS projects to that repo. The first steps are already made.

I even think that it can be a subproject in near-sdk-js repo.

So what repo is going to be the monorepo? near-sdk-js? near-api-js?

Sory, typo. It's near-api-js.
https://github.com/near/near-api-js

Being addressed in #213


programmatic smooth scrolling

🔎 Usage Questions
Is it possible to programmatically smooth scroll? I'm trying to get a "scroll to top" button working without jumping right back to the top all jittery and ugly -like.
My current code:
 $('.go-top').click(function(event) {
    event.preventDefault();
    let bodyscrollTop = simpleBar.getScrollElement()
    bodyscrollTop.scrollTop = 0
    // let bodyscrollTopTop = bodyscrollTop.scrollTop
    // $('html, body').animate({bodyscrollTopTop: 0}, 300);
})

That works, but jumps immediately back to the top, which isnt great UX..
The commented out portion is how I would expect to be able to do it smoothly, however that doesnt work at all. No Action. It does not generate any error messages either..
I've tried the scrollIntoView() method as well. That doesnt work either.
Is this simply not possible with simplebar or am I missing something?

No idea about your jQuery plugin but should works just fine with scrollIntoView() but you need to target the element you want to scroll to. Not the element that scrolls itself.
Something like:
$('#topOfThePageElement')[0].scrollIntoView({ behavior: 'smooth' })

@Grsmto when I tried it previously I had set the element as my header menu bar - that didnt work for whatever reason. I tried it now with the first H1 at the top of the page and that worked flawlessly!

Is there a way to programmatically smooth-scroll only the simplebar area without moving browser scrollbar, using Grsmto's method? If both are present they both get scolled.
`
(...)

(...)
Lorem ipsum...
(...)

(...)
`

@al1357 I don't think so.
However there are extra options, see: https://developer.mozilla.org/en-US/docs/Web/API/Element/scrollIntoView
Otherwise you'll have to use another tool to animate the scrollTop property.

You could also try
[data-simplebar]:not(.simplebar-dragging) .simplebar-content-wrapper {
	scroll-behavior: smooth;
}

You could also try
[data-simplebar]:not(.simplebar-dragging) .simplebar-content-wrapper {
	scroll-behavior: smooth;
}

this actually worked. ty

You could also try
[data-simplebar]:not(.simplebar-dragging) .simplebar-content-wrapper {
	scroll-behavior: smooth;
}

Thank you for responding. This truly worked. However, when there is a nested simplebar. It no longer works. It only works on the parent simplebar.

@darkmodeee should work all the same honestly, do you have a codepen or something to test it?

@darkmodeee should work all the same honestly, do you have a codepen or something to test it?

Hi @Rod911 I prepared a fiddle for you. Here's the link: https://jsfiddle.net/zorenkonte/vfb0gLun/42/. Thank you so much for your time.

@darkmodeee Codepen See, works like a charm, I find the link tag works better for nested scrollbars as it scrolls both parent and child to get the element into view


Speed up estimates loading

Speeds up estimates pipeline loader. WIP pending further improvements
Some timings
On this branch:
py.test tests/pipeline/test_quarters_estimates.py  42.86s user 1.74s system 98% cpu 45.408 total
On master:
py.test tests/pipeline/test_quarters_estimates.py  46.65s user 1.98s system 96% cpu 50.636 total

Not sure where we wanted this to end up but going to close it b/c stale activity.


deploy with apache

I got error messages by using apache to handle the http and ws request.
It runs with manage.py runserver.
If use apache, it will return error code 200.
Anyone did try this before?

@BitForceStudio I ran into the same problem. Did you managed to solve it?

Yes, but I forgot how I solve it in detail. I think what I did is change the server from apache to daphne and then use runwork.  the apache didn't support channel yet. You can find some useful work in here: http://stackoverflow.com/questions/37098504/how-to-configure-apache-to-run-asgi-in-django-channels-is-apache-even-required
or the twist version problem, have to be 16.2.0 as I remembered.  Try this first

Thanks a lot for the pointers.
My twisted version is exactly 16.2.0. If your link is not outdated yet it explains why it's not working... I am so surprised Apache doesn't support ASGI. The problem for me is I am using Elastic Beanstalk to deploy my application and Apache comes with default and there is no way for me to choose other web servers like daphne or nginx ...


[FEATURE] add cards to the game.

🚀 Feature
a card that will have a number (1-12) and a symbol (clubs, swords, cups and golden coins).
Motivation
You need cards to play the game and this issue is necessary for the development of the game board #2
Implementation
If the art design is not available yet, just use mock cards with a number and a letter (representing the symbol) on them

(edited), original issue:
🚀 Feature

(Write your description here)
a card that ll have a number(1-12) and a symbol (clubs, swords, cups and golden coins).
Motivation

(Outline your motivation here)
you need cards to play the game.
Implementation

Additional context
Add any other context or screenshots about the feature request here.


Skillmap Polish feature requests:

Different color for completed Tutorial tiles - there's too much competition for attention, completed tiles are done, so they should be a different (less attention-grabby) color from "open" tiles

Ability to anchor elements onto the background - we want to be able to have different themes/islands for different learning paths in a Skillmap, and even have text elements that describe the game they will be building.

Ability to have full image over the background (not just middle 2/3rds)

Side-bar improvements:

nice text wrapping for tags
remove unnecessary fields (https://github.com/microsoft/pxt-arcade/issues/3500)
add link to "Learning Outcomes" page for overall Skillmap
add labels to specify what each field is (i.e. Tutorials: 0/12 complete)

Double-click a tile to open the Tutorial

Pending things here:
nice text wrapping for tags
remove unnecessary fields (Remove fields from Skillmap Tutorial overview pane #3500)
@shakao can you open a bugs for the above.
Resolving the enhancement issue as done.


Holographic projectors can be put into respective belts

About the PR
Now you can put holofan projectors in the toolbelt, and more importantly, you can put both holosigns and normal signs in the janibelt.
H̶o̶p̶e̶f̶u̶l̶l̶y̶ ̶t̶h̶e̶r̶e̶ ̶a̶r̶e̶ ̶n̶o̶ ̶u̶n̶i̶n̶t̶e̶n̶d̶e̶d̶ ̶c̶o̶n̶s̶e̶q̶u̶e̶n̶c̶e̶s̶ ̶o̶f̶ ̶g̶i̶v̶i̶n̶g̶ ̶t̶h̶e̶ ̶h̶o̶l̶o̶s̶i̶g̶n̶ ̶p̶r̶o̶j̶e̶c̶t̶o̶r̶ ̶t̶h̶e̶ ̶W̶e̶t̶F̶l̶o̶o̶r̶S̶i̶g̶n̶ ̶t̶a̶g̶.̶.̶.̶
Edit: Gave Holosign Projector its own tag (the physical sign still fits in the belt though)
Screenshots

Changelog

:cl:

tweak: You can now put holofan projectors into the utility belt.
tweak: You can now put both holosign projectors and wet floor signs into the janibelt.

Give the projector it's own new tag instead of reusing one.

Gave the sign projector its own tag, but the physical wet floor sign will still be fitting in the janibelt.

i might resolve the conflict tomorrow

well it's done now, for real this time, i think.


Requires plugins that modify options to load before tool does

Similarly to the issue with cgit-wp-user-guide, a plugin that is added to amend the options the tweak tool uses must be named alphabetically previous to the tweak tool itself, otherwise the add_filter() call will fire too late.

Clarified in README.


Feature Request - Foundry Journal Entry conversion to Obsidian.MD file

Hiya! Love the module so far. I was wondering if it would be possible to support using this plugin in reverse: i.e. right clicking a folder containing multiple journal entries and exporting it into an Obsidian Vault in Markdown format.

This is kinda close: https://foundryvtt.com/packages/export-markdown
Although one thing it is missing is Obsidian-style links. I'll consider this for a future feature, but I worry about some limitations in foundry's journal system that might cause losses in your vault if you were to overwrite. E.g. you upload your vault, edit some journals, export the journals, and extract the zip over your vault.
But I do see the utility of having created a bunch of journals in Foundry and wanting to add them to your vault.


Timecode is no longer available

In version 2.1.4, there was a property for timecode that was available on the data stream. It is no longer available and is breaking our application, Can you please help resolve.

Was it part of the webm file? GetUserMedia, the current method of recording in this repository, dose not support timecodes. See https://stackoverflow.com/questions/63298137/screen-recordings-in-javascript-with-navigator-mediadevices-getdisplaymedia-aren

Try using https://github.com/buynao/webm-duration-fix
or if you want low level control over the webm stream https://www.npmjs.com/package/ts-ebml


login error

hello i think there is an error in login it only sent confirmation to an email address again and again it wont direct a user to a homepage. it was stack on login it only say email confirmation sent and when i confirm my email and login it say email confirmation again

@fadleyfrost
Just to summarize what you are saying, after clicking on the login link on the email, it opens the app's login page again?
What device are you using?

sir when i click on login on email it says local host refused to connect.

my internet connection is good. maybe im doing it wrong what did i miss


NPoco3  - PocoDataFactory.ForType(typeof(T)) throws exception.. An Item with the same key has already been added

I really don't understand why this does this and I really depend on being able to get the PocoData.  This worked great in v2; but something has definitely changed in v3.   I was able to work around it for getting the TableName by using TableInfoForType - but I still need the ForType method to work (or some equivalent).
Is there some other method that I can't find that will get back the PocoData for a type?

I would probably need more info about the exception

Here is some sample code that causes it:
Class:  CustomDatabase.cs
        public string GetColumnName<TType, TProperty>(Expression<Func<TType, TProperty>> property)
        {
            // Get the property name as a string
            var expression = (MemberExpression)property.Body;
            var propertyName = expression.Member.Name;

            // Get the corresponding query column name
            var column = PocoDataFactory
                .ForType(typeof(TType)).Columns.Values
                .Where(c => c.MemberInfo.Name == propertyName)
                .SingleOrDefault();
            var columnName = column.ColumnName;

            return columnName;
        }

...
        public string GetTableName<TType, TProperty>(Expression<Func<TType, TProperty>> property)
        {
            // Get the corresponding table information
            return GetTableName(typeof(TType));
        }

        public string GetTableName(Type type)
        {
            // Get the corresponding table information
            var tableInfo = PocoDataFactory
                .ForType(type)
                .TableInfo;
            return tableInfo.TableName;
        }

Then calling that function from a repository class:
...
Database = new CustomDatabase(connectionString);
...

                var sql = @"
                    SELECT DISTINCT rp." + Database.GetColumnName((ReportQualifiedStudent rp) => rp.ProgramYearId) + @"
                      FROM " + Database.GetTableName(typeof(ReportQualifiedStudent)) + " rp";

The PocoDataFactory.ForType(type) fails in both instances with the error metioned.  I found a work around for the Table name PocoDataFactory.TableInfoForType(type);  but couldn't find a work around for getting the column names; so I've had to revert back to NPoco 2.x

And the stack trace of the exception?

Stack Trace:
   at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
   at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
   at System.Linq.Enumerable.ToDictionary[TSource,TKey,TElement](IEnumerable`1 source, Func`2 keySelector, Func`2 elementSelector, IEqualityComparer`1 comparer)
   at NPoco.PocoDataBuilder.NPoco.InitializedPocoDataBuilder.Build()
   at NPoco.FluentPocoDataFactory.ForType(Type type)
   at Aemis.Data.Databases.CustomDatabase.GetColumnName[TType,TProperty](Expression`1 property) in C:\dev\projects\AemisCloud\Aemis\Aemis.Data\Databases\CustomDatabase.cs:line 48
   at Aemis.Data.Repositories.ManyToManyLoader`4..ctor(CustomDatabase database, Expression`1 primaryIdProperty, Expression`1 primaryListProperty, Expression`1 associationPrimaryIdProperty, Expression`1 associationRelatedIdProperty, Expression`1 relatedIdProperty) in C:\dev\projects\AemisCloud\Aemis\Aemis.Data\Repositories\ManyToManyLoader.cs:line 48
   at Aemis.Data.Repositories.RegionCountyLoader..ctor(CustomDatabase database) in C:\dev\projects\AemisCloud\Aemis\Aemis.Data\Repositories\RegionCountyLoader.cs:line 11
   at lambda_method(Closure , Object[] )
   at Autofac.Core.Activators.Reflection.ConstructorParameterBinding.Instantiate()

This is the same error just happening elsewhere in my app - but calling the same method of GetColumName which calls PocoDataFactory.ForType(type)
If you need any other info I have made a branch for this so I can beat it up to get it into whatever condition you need it in.

The code called to generate that stack was:
        public ManyToManyLoader(
            CustomDatabase database,
            // The property on the primary type related to the many to many table. Usually the primary key
            Expression<Func<TPrimary, int>> primaryIdProperty,
            // The property on the primary type that will store the related ids
            Expression<Func<TPrimary, List<TListType>>> primaryListProperty,
            // The property on the many to many type that references the primary type.
            Expression<Func<TManyToMany, int>> associationPrimaryIdProperty,
            // The property on the many to many type that references the related type.
            Expression<Func<TManyToMany, int>> associationRelatedIdProperty,
            // The property on the related type related to the many to many table. Usually the primary key
            Expression<Func<TRelated, int>> relatedIdProperty)
        {
...
            var associationPrimaryIdColumn = database.GetColumnName(associationPrimaryIdProperty);
....

You must have a class with duplicate property names by case on it

how would that be possible?
For instance the above code fails on the two following models:
using Aemis.Data.Models.Classes;
using NPoco;
using System.Collections.Generic;

namespace Aemis.Data.Models.Regions
{
    public class Region : BaseSecurableModel
    {
        public int RegionId { get; set; }

        public string Title { get; set; }
        public int SortSequence { get; set; }

        public string Url { get; set; }

        public bool IsActive { get; set; }
        public bool UsesDailyAttendance { get; set; }
        public bool UsesMonthlyAttendance { get; set; }

        public int RegionTypeId { get; set; }
        public bool SupportsEnrollmentPeriods { get; set; }
        public bool IsCorrectional { get; set; }

        [ResultColumn]
        public int? PrimaryAdminAccountId { get; set; }

		[ResultColumn]
		public List<int> CountyIds { get; set; }

        [ResultColumn]
        public List<ClassAlert> ClassAlerts { get; set; }

        [ResultColumn]
        public override string ModelTitle
        {
            get { return this.Title; }

        }
    }
}

and then when loading:
using NPoco;
namespace Aemis.Data.Models.RegionAdmins
{
    public class RegionAdmin : BaseSecurableModel
    {
        public int RegionAdminId { get; set; }
        public int RegionId { get; set; }
        public int AccountId { get; set; }
        public int SortSequence { get; set; }

        [ResultColumn]
        public override string ModelTitle
        {
            get { return ""; }

        }
    }
}

this is the standard pattern I've been using for my many to many relationship loading.  (A region can have many admins and the same person could admin many regions in this case).
There are no duplicate property names.  I'm not even sure how I could successfully define duplicate property names (maybe via an annotation?)
Anyway, I have just stayed on 3.9.4 because I couldn't figure out the problem and can't, currently, take the time to refactor how all of my database interactions go.  It's fine how it is I just had hoped at the time to stay at the latest version of npoco.

Here is base security model and base model

    public abstract class BaseSecurableModel : BaseModel
    {
        [ResultColumn]
        public bool HasReport { get; set; } // can generate reports on the model
        [ResultColumn]
        public bool HasRead { get; set; } // can see the model
        [ResultColumn]
        public bool HasWrite { get; set; } // can edit an existing model
        [ResultColumn]
        public bool HasDelete { get; set; } // can delete the model
        [ResultColumn]
        public bool HasAdmin { get; set; } // can edit meta things associated with the model
    }

    public abstract class BaseModel
    {
        public BaseModel()
        {
            DateAdded = DateTime.Now;
            DateModified = DateTime.Now;
        }

        public virtual string GetSummary()
        {
            return JsonConvert.SerializeObject(this);
        }

        public abstract string ModelTitle { get; }

        [ResultColumn]
        public string KeyCode { get; set; }

        public virtual DateTime DateAdded { get; set; }

        public virtual DateTime DateModified { get; set; }

        [ResultColumn]
        public string LogChildProperty { get; set; }

    }

This is about as minimum of an example as I have.  I shared this region model example because it was so basic of a model.  Basically all of my many-to-many classes are built exactly like RegionAdmins just with different names to represent the relationships.  Hopefully this is enough to illustrate the problem.
I have a huge deadline at work that is keeping me really busy through July 16 - but after that I can try to build a very simplified example app that illustrates the issue.

I'm sorry I haven't been back to build a simple example of this for you yet. I'm still planning on getting a simple example for you as soon as I can.

Closed as no sample received

sorry - I left the job where I had that code shortly after my last comment and was never able to revisit it.


error after closing tour

Hi,
always after closing the tour with X or after finishing I'm getting a 'Cannot read property 'getBoundingClientRect' of undefined' (or rather 'substr of undefined')  error in the browsers console. Did I miss something?
EDIT: it appears whenever I resize the window. I also tried that in another prototype, where enjoyhint is the only js I use. maybe you should remove the window.resize event handler after the tour is finished.
It seems as if the script is still looking for prev/forward buttons, doesn't find it and that causes the script to stop (?!). Anybody any idea how this is possible? As far as I can see (and possibly my basic understanding is'n enough), destroyEnjoy() should prevent that and it seems as if nobody else has a similar problem ... maybe.
:)

I am also experiencing this issue on print as well.

I also experience the same issue. Every time I close the tour. Any update on this?

Same here any fix ?

Hi, it happend, becuase you used browser, where getBoundingClientRect didn't supported.


Add An Unnecessarily High-Effort Clubstep Mashup by DEMON GIRLFRIEND

Song Name
An Unnecessarily High-Effort Clubstep Mashup
Artist Name
DEMON GIRLFRIEND
Source
Youtube
Youtube Link
_tMSmScMJu_rNCVQ
Direct File Link
No response
Song ID
13
Start Offset [ms]
0
Extra
Created from Auto Nong.
Created for level: 1777565

reject

invalid yt link
already exists


Merge some GN changes from master to next

merge https://github.com/crosswalk-project/chromium-crosswalk/pull/377, https://github.com/crosswalk-project/chromium-crosswalk/pull/378 and https://github.com/crosswalk-project/chromium-crosswalk/pull/381from master to next

lgtm. One thing I said in the original pull requests is that all commits except for the backports can be squashed into the gyp versions, which you should also consider doing.
And don't forget my comment about backporting an upstream change in #381.


operator skupper-operator (1.8.1)

Thanks for submitting your Operator. Please check the below list before you create your Pull Request.
Your submission should not

[x] Add more than one operator bundle per PR
[x] Modify any operator
[x] Rename an operator
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description of the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

/pipeline restart operator-hosted-pipeline


[BUG]: MySQL alter table fails where tablename is reserved word

What version of drizzle-orm are you using?
0.23.4
Describe the Bug
Using the db push feature with a planetscale database. If I push the following minimal schema then it creates the table.
export const key = mysqlTable(
  "key",
  {
    id: varchar("id", { length: 191 }).primaryKey().notNull(),
  }

If I then add a field to the table and push again, it fails with the following error.
export const key = mysqlTable(
  "key",
  {
    id: varchar("id", { length: 191 }).primaryKey().notNull(),
    primary: boolean("primary"),
  }

Error: syntax error at position 16 near 'key'
    at PromiseConnection.query (<myproject>/node_modules/drizzle-kit/index.js:43543:26)
    at Command2.<anonymous> (<myproject>/node_modules/drizzle-kit/index.js:50883:33)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  code: 'ER_UNKNOWN_ERROR',
  errno: 1105,
  sql: 'ALTER TABLE key ADD `primary` boolean;',
  sqlState: 'HY000',
  sqlMessage: "syntax error at position 16 near 'key'"

I believe this is because the table name is a MySQL keyword/reserved word, so drizzle should wrap the tablename in backticks. I verified that the backtick version of the generated sql does indeed work by taking the sql from the above error message and wrapping table name in backticks like so, and then executing it against the actual db in the planetscale web UI:
ALTER TABLE `key` ADD `primary` boolean;

Same occurs with postgres, for example:
export const user = pgTable('user', {
  id: serial('id').primaryKey(),
  fullName: varchar('full_name', { length: 256 }),
}, (user) => ({
  nameIdx: index('name_idx').on(user.fullName),
}));

will generate
CREATE TABLE IF NOT EXISTS user (
  'id' SERIAL PRIMARY KEY,
  'full_name' character varying(256)
);
CREATE INDEX IF NOT EXISTS user_full_name_index ON user (full_name);

which will fail with
syntax error at or near "user"

Fixed in<EMAIL_ADDRESS>

@AndriiSherman looks like some cases were missed. Seeing this sql in an error message:
sql: 'truncate table order;'


Shouldn't use NavController to push a new View

If you use NavController to push a new View, IONIC will treat this behavior like we change the View, the ionViewCanLeave will trigger.
It's not make sense for this case, we just open a dialog to choose some items and we don't want to push the new View.
When I need to check the Form is dirty or not I met this issues :
The event ionViewCanLeave will trigger every time this control opened.
My solution is : change from NavController to Modal dialog.

Hi, I see... It seems like it would be better to use Modal rather than Page. I'll try to find some time to implement it.

@GFoley83 thanks a lot for the PR, it saved me time 👍
Version 1.1.1 now has useModal parameter with true as default value:
https://github.com/eakoriakin/ionic-select-searchable/wiki/API-Documentation#usemodal


Extension Command Stopped Showing Up

Does this issue occur when all extensions are disabled?: Yes (tried Start Extension Bisect)

VS Code Version: 1.86.0
OS Version: MacOS Monterey 12.6.8

Steps to Reproduce:

Follow the "Your First Extension" tutorial verbatim. https://code.visualstudio.com/api/get-started/your-first-extension
Press f5 to open extension.
Press cmd+shift+P
Type "Hello"
Nothing comes up.

I was working on an extension a few weeks ago, and it was working fine. It stopped working as I continued to work on the frontend part of the app. I reverted to starting from the "Your First Extension" tutorial, and I can't even get that to work.
I was working on a webview. The tutorial for building a webview doesn't work either. I'm completely lost. There are no error messages I can use. The Start Extension Bisect doesn't yield any useful leads either.

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.87.0. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Wow, Microsoft disables extension development if I don't update VSCode too?
None of 1.87.0's features are necessary to develop this tutorial extension. 💀

Now it leads to command '[my-app-name].helloWorld' not found
Here's the error bubble message when calling the command
Activating extension 'undefined_publisher.[my-app-name]' failed: Cannot find module '/Users/jonhong/dev/vscode-extension-example/[my-app-name]/dist/extension.js' Require stack: - /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/loader.js - /Applications/Visual Studio Code.app/Contents/Resources/app/out/bootstrap-amd.js - /Applications/Visual Studio Code.app/Contents/Resources/app/out/bootstrap-fork.js - .

Works fine for me so marking this as a dev question
As a start, the compiled js should be in out instead of dist. Maybe you're using an outdated extension template?


tweaked the german language file

Thanks!

According to Duden (http://www.duden.de/rechtschreibung/E_Mail), E-Mail is the correct spelling.

@manuelgu Yeah, I just checked that now too :+1:  I guess I'll change everything to E-Mail then.


Upgrade directives name since we use angular-ui-bootstrap

Fixes https://github.com/containous/traefik/issues/577

This change is

Thanks a lot @micaelmbagira, tabs are fixed :)
LGTM! But needs a rebase :)

Rebased !

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

@micaelmbagira needs another rebase :sweat:


broken link

There's a broken link on the use.ink website.
At https://use.ink/examples/smart-contracts if we click on view example for Cross-contract calls we end up with 404

Seems to be fixed by now. Points to Delegator.


Don't hard code Audience for SAML.

Had to change this to get this working, and it does, thanks!

Thanks, mustve been a manual test I was running, and forgot to replace it back.  Thanks for the PR


api subresources singular support

went ahead an made account/transfer a custom call instead of a subresource in account since subresource doesn't support singular, but adding that would be great

It's not singular support that's lacking in general. It's a singular inside of another singular resource. Right now nested resources are only supported if the parent is plural.


Keysight operator upgrade

@alexmasi I have upgraded the keysight operator.

Thanks Anjan, we will do some work internally to validate release 0.0.1-4478 and then I'll get this merged

/gcbrun

/gcbrun

The presubmit failure is because the new operator adds resource requirements for CPU (~0.5 per ixia-c port) which pushes the requirements for the presubmit topology up over the 16 CPUs we currently provision. So I will make a change to the presubmit to increase the machine resources of the runner

@anjan-keysight Can you sync to the main branch?

@alexmasi I have synced with main

/gcbrun


Add BigQuery

Work in progress for BigQuery...
Datasets

[x] Create a dataset
[x] List datasets
[x] Get a dataset
[x] Update a dataset (name, description, expiration)
[x] Delete a dataset
[x] Represent extended attributes from get

Tables

[x] Create a table
[x] List tables
[x] Get a table
[x] Update a table (name, description, schema)
[x] Delete a table
[x] Create a view
[x] Update the query used by the view
[x] Represent extended attributes from get

Jobs

[x] Create a job
[x] List jobs
[x] List jobs with total count on list
[x] Get a job
[x] Knows the job's state (pending/running/done)
[x] Knows if there are errors (status/errorResult and status/errors)
[x] Represents a Copy job
[x] Represents an Export job (destinationUriFileCounts)
[x] Represents a Load job (inputFiles, inputFileBytes, outputRows, outputBytes)
[x] Represents a Query job (totalBytesProcessed)
[x] Represent Job status error data
[x] Represent Job statistics data
[x] Refresh a job

Insert Data

[x] Load records to a table directly (insertAll)
[x] Upload data to a table
[x] Import Storage file to a table

Query Data

[x] Create an query
[x] Create a Batch query
[x] Query with query cache disabled
[x] Query to a table
[x] Query with default dataset

Query Results

[x] Get query results from a job (pagination, etc.)

Export Data

[x] Export to single file
[x] Export to multiple files

Copy Data

[x] Copy data to new table
[x] Copy data to new dataset and table
[x] Copy data to new project and dataset and table

Other

[x] Have entities grab the full resource data when initially created by a list call (gcloud.bigquery.datasets.first.tables.first.description vs. gcloud.bigquery.dataset("test").table("test").description) (Look for creationTime in the google api object)
[x] Link Data?
[x] Regression tests
[x] Documentation
[x] README
[x] Documentation Left Nav

The main documentation page is not 100% complete, but the rest of the documentation is. We're accepting this PR so we can get the docs showing up on the gcloud-ruby site.


Question about VITS KL Loss Formula

Thank you for this fantasic work.
I think the kl loss in VITS might have missed one term. See: https://statproofbook.github.io/P/norm-kl.html#mjx-eqn-eq%3Anorm-KL

https://github.com/jaywalnut310/vits/issues/6#issuecomment-861903556


Type validation of instruction sets

I've pondered our options for the architecture of our program validator again, and one issue is that type correctness of an instruction set is generally undecidable without knowing its concrete instantiation.
Consider the following, very simple scenario:
A.core_desc
InstructionSet Base {
    architectural_state {
        int XLEN;
        unsigned<XLEN> x;
    }
}

B.core_desc
import "A.core_desc"

Core Derived provides Base {
    architectural_state {
        XLEN = -1;
    }
}

Obviously this results in a type error, because Base now contains a field of type unsigned<-1>, which is not a valid type.
This can however only be discovered during validation of Derived.
My question would be how errors of this kind should be handled. The closest real world counterpart to this kind of parametrization I can think of would be C++ templates, and those are notorious for their incomprehensible error reporting.

Are the errors reported at the correct position within the instruction set?
Are all errors reported on the "provides Base" clause? Maybe with a prefix like "Error during instantiation of Base"?
What happens if the instruction set is located in a different file?

Another question would be how to handle validation of individual instruction sets.

Should we simply never validate instruction sets, but only core definitions?
Should we partially validate instruction sets, but ignore everything involving unknown types?
Should we attempt to infer constraints on the type somehow?

Has anyone thought about any of this during the language design phase? 😅

My question would be how errors of this kind should be handled. The closest real world counterpart to this kind of parametrization I can think of would be C++ templates,

That is also my mental model.

and those are notorious for their incomprehensible error reporting.

Yup.

Are the errors reported at the correct position within the instruction set?
Are all errors reported on the "provides Base" clause? Maybe with a prefix like "Error during instantiation of Base"?

Maybe both, if that's possible? At some point, you're elaborating the CoreDefinition by traversing its provides clause, and trigger a full check of the referenced Instruction sets, during which you detected invalid types etc.

What happens if the instruction set is located in a different file?

Aren't import'ed definitions all parsed into the same object model?

Another question would be how to handle validation of individual instruction sets.

I'd say

partially validate instruction sets, but ignore everything involving unknown types

... plus having default values for implementation parameters, as you proposed yesterday, would be useful. For future reference, your point was, basically all types are parametrised on XLEN, so assuming XLEN=32 would make vastly more declarations and assignments type-checkable.

Closing this, AFAIK @AtomCrafty's latest version of the parameter elaboration and type checking phase does best-effort checking of instruction sets, and reports meaningfully-located errors.


add Maniaplanet

SteamDB app page links to a few games using this

ShootMania: Storm
Trackmania (2020)
TrackMania 2: Canyon
Trackmania 2: Lagoon
TrackMania 2: Stadium
TrackMania 2: Valley

Brief explanation of the change

need non matching test


Bom version parsing fix

Cherry picked fix: https://github.com/CycloneDX/cdxgen/commit/fbc5dc3d56cb817f22efb0fd0e264899426aeb84
Motivation:
https://shiftleftinc.atlassian.net/browse/SEN-533
https://shiftleftinc.atlassian.net/browse/SEN-572

This looks ok to me @yusefsaraby i added @prabhu as the local expert on the matter so he can give his blessing. @prabhu i am aware you are no longer maintaining this package so please do not feel forced here, ignore this if you prefer.

Got the following response from Prabhu:
There were more bugs with yarn parsing that were fixed in 8.1.0. Best to get the very latest Our enhancements in the fork were specifically around sbt support for angi. If those could be isolated and added back it would be great


Latest unicorn breaks x86_64 guest?

On ARM host at least, I'm seeing this, no matter the command:
invalid read: @0x0, 0x8 = 0x0
Example trace footer:
$ ./usercorn -etrace busybox-x86_64 cal

+ block @0x4aeda0
                              0x4aeda0:           4889fa mov rdx, rdi
                              0x4aeda3:       be681e4f00 mov esi, 0x4f1e68
                              0x4aeda8:     41ba08000000 mov r10d, 8
                              0x4aedae:       b80e000000 mov eax, 0xe
                              0x4aedb3:             31ff xor edi, edi
                              0x4aedb5:             0f05 syscall
                              rax 0x0000000000000000

                            + block @0x4aedb7
                              0x4aedb7:               c3 ret

                          + block @0x4b5ce8
                            0x4b5ce8: 488db4247c090000 lea rsi, qword ptr [rsp + 0x97c]
                            0x4b5cf0:       bf01000000 mov edi, 1
                            0x4b5cf5:       e85efeffff call 0x4b5b58

                            + block @0x4b5b58
                              0x4b5b58:           83ff02 cmp edi, 2
                              0x4b5b5b:       b816000000 mov eax, 0x16
                              0x4b5b60:             7718 ja 0x4b5b7a

                            + block @0x4b5b62
                              0x4b5b62: 64488b142500000000 mov rdx, qword ptr fs:[0]
invalid read: @0x0, 0x8 = 0x0
[memory map]
  0x400000-0x4f8000 r-x busybox-x86_64 [exe]
  0x6f6000-0x6fb000 rw- busybox-x86_64 [brk]
  0x60000000-0x60801000 rwx [stack]
[registers]
   fs 0x0000000000007ee0   rbx 0x00000000607fe760   rsi 0x00000000607fe89c   r11 0x0000000000000000
   gs 0x0000000000000000   rcx 0x0000000000000000    r8 0x00000000607fe760   r12 0x00000000607fed70
  rax 0x0000000000000016   rdi 0x0000000000000001    r9 0x0000000000000000   r13 0x00000000000003e9
  rbp 0x00000000607f0000   rdx 0x0000000000000000   r10 0x0000000000000008   r14 0x0000000000000002
                           r15 0x0000000000000014       0x0000000000000000       0x0000000000000000
[stacktrace]
  0x400194
  0x4a0566
  0x4a0706
  0x4007b0
  0x400aa8
  0x40048f
  0x400766
  0x40048f
  0x4004ac
  0x4002a9
  0x400454
  0x401bef
  0x4b8358
  0x4b5c7b
  0x4b5b62
panic: Invalid memory read (UC_ERR_READ_UNMAPPED)

Unicorn was compiled with no custom CFLAGS  and busybox-armv5 seems unaffected.

I believe they changed the way segments are handled (there's actually a GDT now), so I need to update for that

Hi again,
I haven't been following the developments for a while - what's the situation re unicorn?
And besides, any use revisiting some of my old glshim issues?
Thx

x86-64 guest support is almost fixed. If you look at the glshim commit history I've been working on texgen which is 100% for the foobillard issue.

x86_64 linux is fixed for me in the latest unstable. can you confirm?

Stale bindings?
# github.com/unicorn-engine/unicorn/bindings/go/unicorn
could not determine kind of name for C.uc_x86_mmr

Alright, I had some stale includes but this looks like 64-bit-only stuff:
# github.com/unicorn-engine/unicorn/bindings/go/unicorn
../go/src/github.com/unicorn-engine/unicorn/bindings/go/unicorn/unicorn.go:123: type [1073741824]C.struct_uc_mem_region larger than address space
../go/src/github.com/unicorn-engine/unicorn/bindings/go/unicorn/unicorn.go:123: type [1073741824]C.struct_uc_mem_region too large

Can you apply this commit and make sure it fixes the problem before I PR upstream? https://github.com/lunixbochs/unicorn/commit/2a9a794bffa30402819cd9873577ecc2f424288d

leads to some more errors:
# github.com/lunixbochs/usercorn/go/kernel/linux/unpack
../go/src/github.com/lunixbochs/usercorn/go/kernel/linux/unpack/mmap_linux.go:12: undefined: syscall.MAP_32BIT
../go/src/github.com/lunixbochs/usercorn/go/kernel/linux/unpack/mmap_linux.go:20: undefined: syscall.MAP_STACK
../go/src/github.com/lunixbochs/usercorn/go/kernel/linux/unpack/mmap_linux.go:21: undefined: syscall.MAP_HUGETLB

I'll fix that up tonight, looks like the Unicorn fix worked though.

It did - the funny thing is I'd already hit a problem like that before:
https://github.com/pijul/pijul/issues/2#issuecomment-180233469

What's your Go / Linux version? I don't have that error with Go 1.6 on a 32-bit Ubuntu 14.04 install.

It's go 1.5.3 on Arm Linux.

Try on latest unstable.

All's fine again, including x86_64 emulation.


DevTools position on page

How I can position DevTools in other view port location opposed to a right-top corner? for example DevTools container blocking navigation in my app. I wish I could set props on DevTools component for example: <DevTools className="Position-bottomRight" style={{bottom: '10px', right: '10px'}} />

You can pass a position prop. It's in the readme.
Or you can see the code: Panel position

<DevTools style={...} /> might be a good alternative for current <DevTools position={...} />

'position' prop will do work for me just fine.


[DEVOPS] Provison a private Docker Repo for the Paloma LightNode v2

Let's create private docker repo on current servers so that we are able to auth v2 purchases and downloads of the light client.

Deployed the registry in the bots-server. Left some instruction/information on Notion: https://www.notion.so/volumefi/Docker-Registry-10de002bb62180daa589ea40552ed270

Done.


order search towards lower arities first?

could result in some quicker early wins?

just favor expanding things that already have low arity i guess?

meh nah


Inherit or specify DNS configuration

Hi there,
Since we have a lot of internal services (Private gitlab, internal packages service, etc) that we need access to from our CI jobs we need the tart VM to be configured to use a specific DNS server, currently we have our own custom implementation to start tart VMs for gitlab CI but we'd like to switch to this package instead. In order to do that we need to configure the DNS server before cloning.
To do that we currently run networksetup -setdnsservers Ethernet $HOST_DNS in the prepare stage inside the tart VM where $HOST_DNS is the DNS server configured on the physical Mac read using HOST_DNS="$(scutil --dns | grep nameserver | head -n 1 | awk '{print $3}')".
I would suggest a --dns-server option to gitlab-tart-executor prepare allowing the value inherit to inherit the config from the host, or an IP address to allow for a custom value.

Hey @WarriorXK, do you happen to use a Tart VM that has DNS configured? For example, our images were setting up DNS which override the host settings.
In case networksetup -getdnsservers Ethernet returns something for your image, you can run sudo networksetup -setdnsservers Ethernet "Empty" to reset it in your pre_get_sources_script .

@fkorotkov
Is there some special thing we need to do in order to let the VM's use the host network?
We have a hosted mac which is connected to a VPN.
In the regular shell runner, there is no issue with connecting to the vpn but with the tart runner this doesn't work
Running with gitlab-runner 15.10.1 (dcfb4b66)
  on m2-tart2 h-KdyTkV, system ID: s_1543d887871b
  feature flags: FF_USE_FASTZIP:true, FF_RESOLVE_FULL_TLS_CHAIN:false
Resolving secrets 00:00
Preparing the "custom" executor 06:41
Using Custom executor...
2024/01/17 08:51:11 Pulling the latest version of ghcr.io/cirruslabs/macos-ventura-base:latest...
2024/01/17 08:57:39 Cloning and configuring a new VM...
2024/01/17 08:57:39 Waiting for the VM to boot and be SSH-able...
2024/01/17 08:57:51 Was able to SSH!
2024/01/17 08:57:51 VM is ready.
Preparing environment 00:01
Running on admins-Virtual-Machine.local...
Getting source from Git repository 01:15
Fetching changes with git depth set to 20...
Initialized empty Git repository in /private/tmp/builds/apps/.git/
Created fresh repository.
fatal: unable to access 'https:/redacted.com/apps.git/': Failed to connect to redacted.com port 443 after 75029 ms: Couldn't connect to server
2024/01/17 08:59:07 Process exited with status 128
Cleaning up project directory and file based variables 00:01
ERROR: Job failed: exit status 1

Hello @PaulWoitaschek,
Consider using a VPN solution with Network Extension support, for example, WireGuard. If you're using OpenVPN, macOS networking machinery won't be able to tell that it is a VPN and configure the proper packet filter rules.
See https://github.com/cirruslabs/tart/issues/278#issuecomment-1589048449 for more details.

I'm also not sure if Ventura images have this change https://github.com/cirruslabs/macos-image-templates/pull/87 which removes DNS override within the VM. You can also try the latest Sonoma images even if the host is still Ventura.

Thank you! Switching our companies VPN to WireGuard is unfortunatelly not in my power.
I don't understand the comments regarding orchard. Does this mean that running tart in an OpenVPN enviornment is not possible?

So the only option I have is to let each job install openvpn, and pass the credentials as env variables?

So the only option I have is to let each job install openvpn, and pass the credentials as env variables?

You might also have a luck toying with pfctl, see pfctl -s nat -a "com.apple.internet-sharing/shared_v4" when the VM is started. It adds NAT rules for the normal network interfaces and Network Extension-based VPNs, but not for utun*-based VPNs like OpenVPN.
We've considered doing this automatically in Tart, but running pfctl requires root and it is pretty hacky because it might break at any moment.

So I'd run pfctl -s nat -a "com.apple.internet-sharing/shared_v4" in a pre_get_sources_script?

@PaulWoitaschek unfortunately, this is a question beyond general support and the answer will be most likely specific to your use case. We'll need to specifically work with you, try to reproduce your use case and find a solution.  Due to resource limitation on our end we only do so for folks on Priority Support.
As @edigaryev mentioned, please take a look at pfctl -s nat -a "com.apple.internet-sharing/shared_v4 output before and after you run a Tart VM. Then you'll need to figure out your OpenVPN networking situation on the host and manually add rules for OpenVPN for proper routing.


chores: update outdated dingtak qr code

Ⅰ. Describe what this PR does

Ⅱ. Does this pull request fix one issue?

Ⅲ. Describe how to verify it
Ⅳ. Special notes for reviews
V. Checklist

[ ] I have written necessary docs and comments
[ ] I have added necessary unit tests and integration tests
[ ] All checks passed in make test

/lgtm
/approve


Swift 2.0

Sad :panda_face:

Please look at https://github.com/aschuch/AwesomeCache/pull/35. I am still waiting for feedback but will merge the change soon.


server

BTW i am looking to take your gmail clone flutter and get it working with Gmail API.
https://developers.google.com/gmail/api/quickstart/go#step_3_set_up_the_sample

its rest

And also pure golang email server that preserves privacy.
https://github.com/spilled-ink/spilld

its imap, smpt, pop.

I think the first thing is to get oAuth2 working.
https://github.com/codeing-io/FlutterOAuth

seems to be a very nice abstraction

very nice!


Using deprecated method new Buffer()

Describe the bug
After installed sqltools in vscode, got error in Output > Log(Window)
2023-04-20 20:18:52.477 [error] [Extension Host] (node:9330) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead. (Use node --trace-deprecation ... to show where the warning was created)
To Reproduce

Open a terminal, navigate to OUTPUT > Log(Window)
Install SQLTools & SQLTools MySQL/MariaDB Driver in VSCode.

Expected behavior
No error relates to the extension.
Screenshots

Desktop (please complete the following information):

SQLTools Version [0.27.1]
VS Code Version: [1.76.1]
OS: [Windows 10]
Driver:

[ ] PostgreSQL/Redshift
[0.5.1] MySQL/MariaDB
[ ] MSSQL/Azure
[ ] SQLite
[ ] Other? Which...

Database version: [e.g. MySQL v5.6, PostgreSQL vX...]

Additional context
Add any other context about the problem here.

I think this isn't specific to these extensions. See https://github.com/microsoft/vscode/issues/82524

The error is eliminated while disabling the extension.
And see code of the extension at branch dev (ce93cf99cc2355503954fe2879b8ce117e845150):
in file 'vscode-sqltools\packages\util\persistence\serializable-storage.ts'
... 30  private serializeContent(): Buffer { 31    return new Buffer(JSON.stringify(this.items, null, 2), 'utf8'); 32  } ...

You are right. I have submitted a PR to resolve this in the next release.


Umbraco issue

Hey,
I'm using with umbraco but I have following issue:
Server Error in '/' Application.
Value cannot be null.
Parameter name: routeData

Here is my controller
private IUserMailer _userMailer = new UserMailer();

_userMailer.Welcome(registerFormModel).Send();

And my Welcome method
public virtual MvcMailMessage Welcome(RegisterModel model)
{
   return Populate(x =>
            {
                x.Subject = "Welcome";
                x.ViewName = "Welcome";
                x.To.Add(model.Email);
            });
}

My web config:
<smtp deliveryMethod="Network">
   <network host="test.server.com" />
</smtp>

Glad I posted this for my future self as I just hit the problem again on an old site and uncovered this while looking for a solution! 😄

The responses in this issue led me to my solution:
        var data = new RouteData();
        data.DataTokens["playermailer"] = "PlayerMailer";
        this.ControllerContext = new ControllerContext(context, data, this);

context in this case is the HttpContext which is passed into the constructor. PlayerMailer is the directory containing the views.

Glad I posted this for my future self as I just stumbled across it again while looking for the solution in an old site 😄


plain-text code block incompatibility with Jekyll

Hi
Several days ago I tried notion-to-md (npm) and asked for fixing a problem  which is more relevant to Jekyll

Hi
plain text code parts converted to
```plain text

instead of
```text

not supported in jekyll
it is text

it is plain text

For instence, I created this blog post: https://adehghanzadeh.github.io/Jekyll_minimal-mistake/try-to-deploy-this-blog-to-cloudflare-pages/

I switched to jekyll-notion and this problem exists

Hey 👋
Thanks for reporting the issue.
I've had a look at markdown support for "Fenced Code Blocks" and it says nothing about text or plain text.
I guess it depends on the markdown processor to treat one, the other, or both formats for syntax highlighting.
I think this issue is more related to how Jekyll treats spaces in code block format.
I've tested what you mean on my blog and yes, the output is a you mention

Hey 👋
Thanks for reporting the issue.
I've had a look at markdown support for "Fenced Code Blocks" and there's no mention of text or plain text format.
I guess it depends on the markdown processor. Some will deal with one format or the other, or even both.
Anyway, I don't think this issue is related to the format but to how Jekyll treats spaces in code block format.
I've tested what you mean on my blog and yes, the output is as you mention.

After changing the format to text, the new output is OK:

Even using plaintext or whatever is still working OK.
To confirm my theory, I've used a random code format name with spaces (bla bla) and the result is a bad formatted code block as the first sample.
I don't think this is an issue related to notion_to_md but a Jekyll issue treating spaces in code formats.
Can you open an issue in jekyll-notion?

Well, after all as @souvikinator says, it does not matter plain text or text.
In the next release, the fix will be available.
Thanks again @adehghanzadeh.

Thanks for your response
Glad to help this project ❤


error in code

// Calls another Macro after using.
// Make sure the commented out section below
// 'Auto Bandage' exist as another macro
// named "Auto Bandage" for this to work
if @inrange 'enemy' '10'
// not
if @inranget 'enemy' '10'
in line 8

Nice find @leandrobtu! Fix for this in just a sec.

valeu Man ! estou jogando com o Baga fiquei muito feliz em saber que eram
Brazucas os desenvolvedores ! parabens !
On Thu, Feb 21, 2019 at 9:38 PM Melanie<EMAIL_ADDRESS>wrote:

Nice find @leandrobtu https://github.com/leandrobtu! Fix for this in
just a sec.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/her/uosteam/issues/8#issuecomment-466226648, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AQMaiJu_-swhInujyvWHny8qImKud8viks5vPzwegaJpZM4bB8WK
.

--
Leandro

Fixed in: https://github.com/her/uosteam/pull/9


shorten linear slide and counterweights to fit under stage door

not sure how viable this is. would probably mean adding at least one if not two stages to linear slide. one technique might be to lower the base of the linear slide so we can get more extension per stage (right now we are 3 inches off the ground, limiting total stage length to 9 inches, we could probably go to only 1 inch off the ground allowing 11 inches per stage)

related issues that might make this one moot: #48, #51, #52

we fit under truss now, and i think that's fine

Reopening for states, now a different purpose. Would involve shortening each extrusion so as to have the extended length be (roughly) equal to what it is now, as we don't really need to get much higher for the way we play the game and that would require having 3 stages. Here are the benefits of executing this:

Does #47 if we get it right. Our main issue with hang from the slide is we don't have enough travel to lift the robot because its one point and its all the way at the back. More stages=more travel.
Allows our arm to start reach on the board, would be really helpful for auto for reducing bounce. 50 Point autos will be the standard at states, no room for error.
Will maybe get us under 12 inches, allowing travel from both directions under the stage door. Expect large bots at states, flexible travel is super important.

Now that 20342's season is over, we can cannibalize the slide they had planned on using (the one we used last year for POWERPLAY for those who remember), the slide is much smoother with a smaller footprint that allows for a multistage design. It also has pulleys built in, meaning less custom prints that can fail.
https://www.servocity.com/cascading-x-rail-slide-kit/

Unfettered linear slide

another rigging option

Cad done, next is assembly steps for fab. Good luck!

[ ] Cut three X Rails, each to 140 mm. This should be as precise as possible, it is what determines whether or not we fit under the truss. Mr. Miller may have to do this, just mark on each where we want to cut it.
[ ] 3d print new mounts for the motor plates. These are the thick orange pieces in the cad model.
[ ] 3d print new motor spool. Spacing is updated, requires a reprint.
[ ] Assemble two gantry plates, each with four mini rollers. These may already be assembled, if not refer to cad for details.
[ ] Assemble three pulley mounts to go on linear slide. I believe two of three are assembled, one more is partially assembled but the main screw is stripped, will have to find a replacement. Use nylon lock nuts for the main screw (the one holding the pulley).
[ ] Assemble three pulley mounts to go on baseplate. These are slightly different from the old ones, so new mounts will have to be 3d printed. The old pulley bearing itself should work fine, just update the mount.
[ ] Find the black pieces that go on the ends of the slides. We should have them all in the lab around the linear slide area but if not, laser cutting should suffice. Pay careful attention to which ones go where and how many go on each end, be faithful to the CAD model, it is accurate.
[ ] Assemble full slide and ensure it has smooth motion.
[ ] Attach slide and external pulleys to the baseplate as per the cad model. Only 6-32 should be necessary.
[ ] Mount motor so that the grooves in the spool are planar with the pulleys. New mounting holes were added for the motor mount, refer to CAD.
[ ] Thread return and extensions strings. The above image explains how to do this with the addition of a pulley for the green return string. Use our standard kevlar string, and make sure all knots are secure. Knots can be tied to the black end pieces.


Projection modes

Last breaking change for #3831
RFC
Change List

Remove deprecated constants COORDINATE_SYSTEM.LNGLAT_DEPRECATED and COORDINATE_SYSTEM.METERS
Add COORDINATE_SYSTEM.CARTESION (same as old COORDINATE_SYSTEM.IDENTITY)
Layer prop coordinateSystem now defaults to COORDINATE_SYSTEM.DEFAULT (LNGLAT when used with geospatial viewport, CARTESION when used with non-geospatial viewport)
Update examples, tests and docs

Coverage increased (+0.008%) to 81.741% when pulling e64e2e7c62e5c5c137c45e5254c581455e52e661 on x/projection-mode into b73b81a569e0841e773001b35c339d79c09e4a4e on master.

it is valuable to emit reasonable error messages when removing things from the API, to avoid silent failures when upgrading existing apps to v8.

COORDINATE_SYSTEM.IDENTITY is not removed in this version. I can add a deprecation warning if it's accessed. Conceptually, I think of "identity" as a transform (i.e. projection mode) and "Cartesian" as a coordinate system.
According to the RFC we will call WGS84 Cartesian COORDINATE_SYSTEM.WGS84. It is technically a flavor of Cartesian, with specific definitions of the origin and units. However, it is also possible for us to treat the combination of COORDINATE_SYSTEM.CARTESIAN (defined by the layer prop coordinateSystem) and PROJECTION_MODE.WEB_MERCATOR (defined by the viewport) as projecting WGS84 coordinates.

According to the RFC we will call WGS84 Cartesian COORDINATE_SYSTEM.WGS84. It

OK. If ignore the CesiumJS usage, can certainly use a more specific name for fixed frame support. WGS84 is perhaps overly restrictive. As an example we could easily add fixed frame support for multiple ellipsoids as follows (not even a hard dependency on math.gl):
import {Ellipsoid} from<EMAIL_ADDRESS>
new Layer ({
  coordinateSystem: COORDINATE_SYSTEM.FIXED_FRAME,
  coordinateEllipsoid: Ellipsoid.WGS84
})

We should be able to support this with a few lines of code by prepending Ellipsoid.getENUTransformation() matrix to the layer's model matrix (modulo any remaining modelMatrix hacks).
At least this should work on local scales though I am not sure we can handle very low zoom levels.

However, it is also possible for us to treat the combination of COORDINATE_SYSTEM.CARTESIAN (defined by the layer prop coordinateSystem) and PROJECTION_MODE.WEB_MERCATOR (defined by the viewport) as projecting WGS84 coordinates.

I like that general idea of separating coordinates and projection, it could probably be valuable to develop that more.
That said, at first blush, interpreting CARTESIAN differently based on viewport/projection mode seems a little too arbitrary.
WGS84 cartesian has a specific origin (distance from ground is ~6 million meters) and also implies a distance scale (meters) as well as a specific ellipsoid for long lat conversion and height calculations, so it has a lot more associated information than IDENTITY had.
And I'd naively expect CARTESIAN coordinates to remain as small local coordinates in whatever system is convenient for the user - the actual numbers would be very different in the two use cases. So maybe we just stick with different enums for fixed frame and cartesian.


fix(deps): upgraded to latest big-integer

Codecov Report

Merging #35 (f85b4b6) into main (064489d) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #35   +/-   ##
=======================================
  Coverage   95.12%   95.12%
=======================================
  Files           7        7
  Lines         164      164
  Branches       21       21
=======================================
  Hits          156      156
  Misses          8        8

Continue to review full report at Codecov.

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


Please add Installation instruction for mac

Using Mac

Copy the code from the copy.xml file
Go to /Applications/MySQLWorkbench.app/Contents/Resources/data/code_editor.xml (to open the contents of the app right click on the workbench app and select 'Show Package Contents')
Open code_editor.xml
Paste the code you've selected before inside the tag <language name="SCLEX_MYSQL">, replacing all styles in that tag
Open your MySQL Workbench and be happy!

Thanks for contributting, here is the commit https://github.com/dracula/mysql-workbench/commit/0292a3ee2dfa2f7dc8397ef982c6d742e395de67


Update versions to 0.14.1

Versions are updated for all crates so that they're in sync (and so I can create a 0.14.1 tag now, and the next bugfix release will be 0.14.2 and things are not confusing).
I'm going to upload cairo, glib-macros and glib as those had actual bugfixes. The other crates had documentation fixes and clippy warning fixes, which seem not very relevant for crates.io.

I was about to ask why updating all crates' version but you answered it so all good for me, thanks!


Use WinPython as portable/relocatable base MicroDrop Python distribution (Trac #167)

#!md

It seems like [WinPython][1] is more actively maintained and has a larger following than [Portable Python][2], so we should switch to WinPython.

Other benefits include:

 - Easy to register WinPython as a standard Windows Python installation, if desired.  This adds explorer support, registry entries, etc., similar to installing the standard Python installation.
 - Easy drag-n-drop installation of `windist` Python `.exe` packages using the [WinPython Control Panel][3].
 - Large selection of bundled packages, including [numpy, scipy, sympy, matplotlib, pandas, Cython, etc.][4] *as well as* a compiler ([`MinGW32`][5]).

[1]: https://winpython.github.io/
[2]: http://portablepython.com/
[3]: https://github.com/winpython/winpython/wiki/Winpython-Control-Panel
[4]: https://github.com/winpython/winpython/wiki/PackageIndex_27
[5]: https://github.com/numpy/numpy/wiki/Mingw-static-toolchain

Migrated from http://microfluidics.utoronto.ca/microdrop/ticket/167
{
    "status": "new",
    "changetime": "2015-01-06T23:00:37",
    "description": "{{{\n#!md\n\nIt seems like [WinPython][1] is more actively maintained and has a larger following than [Portable Python][2], so we should switch to WinPython.\n\nOther benefits include:\n\n - Easy to register WinPython as a standard Windows Python installation, if desired.  This adds explorer support, registry entries, etc., similar to installing the standard Python installation.\n - Easy drag-n-drop installation of `windist` Python `.exe` packages using the [WinPython Control Panel][3].\n - Large selection of bundled packages, including [numpy, scipy, sympy, matplotlib, pandas, Cython, etc.][4] *as well as* a compiler ([`MinGW32`][5]).\n\n\n[1]: https://winpython.github.io/\n[2]: http://portablepython.com/\n[3]: https://github.com/winpython/winpython/wiki/Winpython-Control-Panel\n[4]: https://github.com/winpython/winpython/wiki/PackageIndex_27\n[5]: https://github.com/numpy/numpy/wiki/Mingw-static-toolchain\n}}}",
    "reporter": "cfobel",
    "cc": "",
    "resolution": "",
    "_ts": "1420585237753513",
    "component": "microdrop",
    "summary": "Use WinPython as portable/relocatable base MicroDrop Python distribution",
    "priority": "minor",
    "keywords": "",
    "version": "0.1",
    "time": "2015-01-06T22:33:54",
    "milestone": "",
    "owner": "cfobel",
    "type": "enhancement"
}

Trac update at 20150106T23:00:37:

ryan changed component from "dmf_control_board_plugin" to "microdrop"
ryan changed priority from "major" to "minor"

We've now switched to a custom Miniconda distribution using the conda constructor tool for building the MicroDrop installer.


Form field attributes are not applied if inline_editable: true

I wanted to apply a data-attribute="something" to some form fields on an Element but noticed these don't get added when the Element has inline_editable set to true.
Is this intentional?
It looks like the React component just isn't rendering the attributes. For now I have just set all my Elements to inline_editable: false but it would be great if data-attributes were applied on the inline forms.

duplicate https://github.com/silverstripe/silverstripe-elemental/issues/738
yeah this is the #one reason I keep roll-out elements with inline_editable: false

Thanks both! Will close as a duplicate of https://github.com/silverstripe/silverstripe-elemental/issues/738


WIP OPTICS clustering

Still working out how best to test it but it seems mostly there. Wiki for details https://en.wikipedia.org/wiki/OPTICS_algorithm there's also a paper I used as reference at the start I'll see if I can dig that out if anyone wants. Also I think I may have to change some of the neighbour stuff to be more correct. I'll figure it out 👀

Thank you! I will look into this at the end of the week.
Could you take a look at https://github.com/rust-ml/linfa/blob/fdf241127fe9058ae98c67a603a2bbb8eccc561c/CONTRIBUTE.md, I'm currently writing a small how-to-contribute document for the upcoming interface changes. If you find something unclear, please let me know so I can update the document. The interface is a bit different, to the original K-Means implementation because of the new traits. If you find some drawbacks in ergonomic, please let me know as well.

@bytesnake sure, I had a brief look and it looks fine but I'll see if I have any more concrete feedback after using it. I'll try and rebase and start updating it some point this week so you might want to save giving it too strong a look until that's done :sweat_smile:. Plus I still need to figure out adequate tests :thinking:
An interesting aside of OPTICS, is you can use the distance metrics it outputs to calculate an equivalent to the output of some clustering algorithms like DBSCAN. It's naturally slower to do OPTICS then from that get the DBSCAN clusters but it might be a nice demonstration of the correctness of both algorithms :thinking:

Yeah so far just done the rebase, gonna try to get onto moving to new traits etc this weekend or next week. Just have some tarpaulin stuff I need to do first :sweat_smile:

I've moved over to the transformer trait. One comment though I think potentially it should return a result type. Especially since existing code does tend to unwrap the l2_dist result and we all know how tricky floating point numbers can be. Either a result or decide for each algorithm if a floating point op fails what the appropriate value to replace it with so we can change them to unwrap_or.

Also just noticed when I ran cargo test on the root there's dependencies in tests for the main linfa crate that aren't in the Cargo.toml? I'm patching locally can open another PR, commit here or let someone else do it

I've moved over to the transformer trait. One comment though I think potentially it should return a result type. Especially since existing code does tend to unwrap the l2_dist result and we all know how tricky floating point numbers can be. Either a result or decide for each algorithm if a floating point op fails what the appropriate value to replace it with so we can change them to unwrap_or.

I think Transformer will most of the time return a Result<_> type, but I think it does not make much difference to have the type implicitly in the trait

Also just noticed when I ran cargo test on the root there's dependencies in tests for the main linfa crate that aren't in the Cargo.toml? I'm patching locally can open another PR, commit here or let someone else do it

wait are some dependencies missing in dev-dependencies? I haven't encountered any errors in travis and locally

Fair enough, I did some similar traits in a work project and explicitly did the Result and then had an infallible type which was automatically generated when the error type was std::convert::Infallible

Also just noticed when I ran cargo test on the root there's dependencies in tests for the main linfa crate that aren't in the Cargo.toml? I'm patching locally can open another PR, commit here or let someone else do it

wait are some dependencies missing in dev-dependencies? I haven't encountered any errors in travis and locally

hm looking at the diff it looks like it was removed between now and master, but I don't recall changing that Cargo.toml. What's the branch the traits are in so I can diff against that?

Also I think the only thing I need to do bar docs, tidy-up and any review comments is to actually do the tests properly. I'll look for an existing implementation work out the optics result then encode that in the test for similarity

Also just noticed when I ran cargo test on the root there's dependencies in tests for the main linfa crate that aren't in the Cargo.toml? I'm patching locally can open another PR, commit here or let someone else do it

wait are some dependencies missing in dev-dependencies? I haven't encountered any errors in travis and locally

hm looking at the diff it looks like it was removed between now and master, but I don't recall changing that Cargo.toml. What's the branch the traits are in so I can diff against that?

can you post the error you're encountering? The traits branch is already merged into master, perhaps the error goes away, when you rebase your PR to the newest commit?


Atlas one way collision is not working

Godot version:
v3.1.beta3.official
OS/device including version:
macOS Mojave 10.14.3
Issue description:
Atlas one way collision is not working (it just works in the first tile collision), single tiles are working well.
Atlas tiles look unsorted, single tiles are hard to sort.
Steps to reproduce:

Create a TileMap
Create a TileSet
-- Add an Atlas
-- Create collisions
-- Turn on "Shape One Way" property

Minimal reproduction project:
tileset_bug.zip

Likely related to #25610.

Ping @MarianoGnu

In fact, there's no way to enable one way collision at all. How did you setled it up @juancolacelli ?

This does the trick:
https://gyazo.com/2ae899c2bef23feaa1e16ee8e202b04a

Hi @MarianoGnu, I don't see that option (using beta 10):

I used the cell editor on TileMap inspector:

ah yes, changing it from there it will only change the first tile, the gift is from #26599 and is still not merged, so it's not included on Beta 10

I'm still having this issue, the first tile is one-way but the others are solid. This is in 3.5 RC2.


Feature request: Make it easier to wrap an arbitrary element/selector

Is your feature request related to a problem? Please describe.
When testing components that Teleport a node to somewhere else, I need to make a wrapper for that teleported HTML element. I can't use .findComponent, because the teleported node might not be a component, and finding by selector doesn't work because the teleported HTML is not in the DOM tree of my root mounted component.
Instead, I have to make the following utility:
export function getWrapper(selector) {
  const el = document.querySelector(selector);
  if (el) return new DOMWrapper(el);
  else return createWrapperError("DOMWrapper");
}

This works, but there's a major footgun here because if you don't know about createWrapperError, the intuitive thing is to just always return a DOMWrapper. But, DOMWrapper.exists() always returns true, regardless of whether element is nullish or not.
Describe the solution you'd like
DOMWrapper.exists returns false if its element doesn't exist.
OR export a function similar to the one I wrote above from vue-test-utils that includes this error handling.
Describe alternatives you've considered

Keep writing this wrapper function myself.
Additional context

If there's a better way of testing Teleport when it only teleports pure DOM nodes (not components), I'd love to see it added to https://test-utils.vuejs.org/guide/advanced/teleport.html.

But, DOMWrapper.exists() always returns true, regardless of whether element is nullish or not.

This seems like a bug - but according to our test suite, we have coverage for this. A DOM element that does not exists should return false for exists(). Here's the test: https://github.com/vuejs/test-utils/blob/main/tests/exists.spec.ts#L14
I could be missing something - can you reproduce this error in a minimal fashion?

import { DOMWrapper } from "@vue/test-utils";
expect(new DOMWrapper(null).exists()).toBe(false); // fails<EMAIL_ADDRESS>

It looks like BaseWrapper defines true as the default value: https://github.com/vuejs/test-utils/blob/52b25f4bcc3df90de1dbd0fcc3d2008837486f40/src/baseWrapper.ts#L265-L267 and that exists is not overwritten in DOMWrapper. As it extends BaseWrapper, exists always returns true.
This looks like a bug, even if it probably went unnoticed as people usually don't build DOMWrapper themselves, but get it via find or get.
I think that adding a proper exists in DOMWrapper may solve the issue? Do you want to give it a try @ascott18 and open a PR?


Change the bucket naming to include deployment

This is a necessary change to reflect a change in how buckets will be named in AWS deployments.   The previous naming scheme would have limited Nimbella to a single AWS deployment, since bucket names must be globally unique and each deployment is an independent scope for Nimbella namespace names.  There is no change to the GCS bucket naming: this change should only affect AWS.
@jthomas I called this a draft initially because (as we've discussed) I am having trouble getting a clean working version of python3 on my machine and have been unable to run the tests locally.   However, it appears the tests passed in the github workflow.
The timing of publication is unconstrained, assuming no regressions in GCS behavior, since we do not yet have hosted customers using AWS buckets.

LGTM! Tests all passing in the CI/CD so good to merge as far as I'm concerned.


Remove digital ocean marketplace image

Using the setup guide is a much better alternative as it's so easy to setup now.
@nathanpotter

Need to fix this ASAP to prevent user confusion.
e.g. see https://github.com/cdr/code-server/issues/1852

I assume this is referring to the code-server droplet on the DigitalOcean marketplace. I'll see if I can work with @nathanpotter to get this removed.

I just logged into the DO vendor portal and there doesn't appear to be a way to remove the listing through there. I've opened a support ticket to take the image down and will update here once I hear back.

I am one of those newbies that installed this droplet...doesn’t even seem to work, but maybe I know why then :P

DO support team has taken the image down :+1:


[ASCII-985][Component] Reduce the usage of aggregator package in favour of comp/aggregator/demultiplexer

What does this PR do?
Reduce the usage of aggregator package in favor of comp/aggregator/demultiplexer:

Use NewDefaultParams instead of DefaultAgentDemultiplexerOptions in cmd
Reduce the occurence of DefaultAgentDemultiplexerOptions in test
Use demultiplexer mock instead of InitTestAgentDemultiplexerWithFlush…:
The following code

log := fxutil.Test[log.Component](t, logimpl.MockModule())
	demux := aggregator.InitTestAgentDemultiplexerWithFlushInterval(log, time.Hour)

was replaced by
demux := createDemultiplexer(t)

where
func createDemultiplexer(t *testing.T) demultiplexer.FakeSamplerMock {
	return fxutil.Test[demultiplexer.FakeSamplerMock](t, logimpl.MockModule(), demultiplexerimpl.FakeSamplerMockModule())
}

Remove InitTestAgentDemultiplexer
Move TestAgentDemultiplexer to comp
Remove InitTestAgentDemultiplexerWithOpts

Motivation
Make it easier to move code from pkg/aggregator to comp

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided. Except if the qa/skip-qa label, with required either qa/done or qa/no-code-change labels, are applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

LGTM for container-integrations owned files

/merge


[KOGITO-4149] Kogito - Provide a way to access task details in boundary event

Jira https://issues.redhat.com/browse/KOGITO-4149

The Linux check has failed. Please check the logs.