experiment: UI search uses search endpoint for global search

Only V6 alpha
I'm experimenting for searching from a global source, so instead search only local packages it uses the power of the npm search endpoint to mix private packages and global search, so you can search even packages are not cached yet. Thoughts on this? @verdaccio/collaborators @verdaccio/kubernetes

At this point has as unique remote search on npmjs, but I'd like to use the proxy property of each package access to search on multiple endpoints based on the package pattern.

That's a pretty cool feature. Maybe we should be marking the results with a label somewhere that shows if it's a local private package or one from a remote registry? Also keep in mind dependency confusion here.

That's a pretty cool feature. Maybe we should be marking the results with a label somewhere that shows if it's a local private package or one from a remote registry? Also keep in mind dependency confusion here.

Not the best design but this is the idea

The field private would be defined by the plugin itself. I've added Remote but the idea would be find the way to identify from which remote is comming from, since remote are defined as uplinks we know whould be the remote used.
Does looks better?

Oh yes, that's really cool.

Ok, the status is like this:

Search in all uplinks, on this demo I do have Nexus3 and npmjs as proxies
Add label based on the origin, cached if is cache, remote if comes from the proxies and does not exist locally, private if is a private package.
It uses the same npm search endpont with some internal magic sauce to remove duplicates, apply scoring (by default 1 on private packages)
It's fairly fast, allows search any package, so if you click on any remote one, will became cached.
What's pending, error handling, probably I'll log errors on the terminal for proxies failires, but the enpoint only would fail if the backend is nor reachable, but if remote fails I won't include results and display cached and private
About remotes, at this point (due the design) I cannot figure out from which proxie the package is being search, maybe in the future can be improved.

More feedback is welcome.
https://user-images.githubusercontent.com/558752/159170421-9ce991b6-ca76-45c4-bfc7-de21c497d3c0.mp4

Thoughts on prioritizing private packages on the list over remote ones? So that private packages show up on top.

Thoughts on prioritizing private packages on the list over remote ones? So that private packages show up on top.

That make sense, thanks @sumanbh


Closing issues from commits comments

Gitea version (or commit ref): 1.7.3
Git version: 2.11.0
Operating system: Debian 9.6/Linux
Database (use [x]):

[ ] PostgreSQL
[x] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[x] No
[ ] Not relevant

Description
I am not being able to close some issues from commits messages such as fix #n, close #x, etc.
In the attached image you can see the issue must have been closed but it was not, I had to close it manually by pressing close button (check the seconds interval).
Update
We have test with other branch than master and the issue is not closed, but when using master the issue is closed. Is this default behaviour ? Can it be changed ?
Screenshots

https://github.com/go-gitea/gitea/blob/7780ea88907197abf6166bedc8b3021489444ea3/custom/conf/app.ini.sample#L40

Thanks @CL-Jeremy

I have enabled the option DEFAULT_CLOSE_ISSUES_VIA_COMMITS_IN_ANY_BRANCH but I think this is another problem. Our repository table in the mysql database doesn't have any column called close_issues_via_commit_in_any_branch.

This could be the reason why I can't change this option in the repository settings. I attach some images as evidence.

We have previously upgraded from version 1.7.2 to 1.7.3, then to version 1.7.4 but in no one the column is being created.
What could we be doing wrong ?

Apologies for my carelessness. This option is fairly new and has not yet been merged.
In fact, the change in behavior you have encountered only came with 1.7.0, after https://github.com/go-gitea/gitea/pull/5662 was merged.
The aforementioned option for reverting this change wasn't introduced until https://github.com/go-gitea/gitea/pull/5992, which was merged but not yet shipped with any of the current releases. I'm also pretty new here so I can't say if you have to wait for the next major update, or maybe the next maintenance update (milestone: 1.8.0, but even the shipping of https://github.com/go-gitea/gitea/pull/5662 with 1.7.0 was supposed to be a "backport").
Hopefully this could be resolved timely.

@CL-Jeremy option for closing issues on non-default branch will be supported only in 1.8.0

fixed by #5992


SIGSERV in binary built with GitHub Workflow

The binary built through release.yml crashes on startup with a segfault:
fish: Job 1, './LingueeOnAlfred hello' terminated by signal SIGSEGV (Address boundary error)

A suspect is that the linker fails to link libswift_Concurrency.dylib. Refs to https://www.zditect.com/code/ios/swift-552-xcode-132-beta-fails-to-link-libswiftconcurrencydylib--using-swift.html.

With the macos-12 change, the built binary runs successfully on Arm. Tested: runs/8113762957.


Remove public bets warning

Per discord conversation: https://discord.com/channels/915138780216823849/915138780653051910/987834037571837963

Rip, duplicate of #544


Remove bottlerocket in snow doc

Issue #, if available:
https://github.com/aws/eks-anywhere/issues/1111
Description of changes:
Testing (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/cherrypick release-0.14


WIP: Add forall a. Show (t a) superclass to GShow -- contains #20

As GShow is isomorphic to this constraint, it's nice to add this super
class. This reminds people that if they implement GShow they should
also implement forall a. Show (t a), as its both incredibly easy to do
so and never (in practice) an additional dependency.
Unforunately, this change doesn't yet type-check because the instances
in base for Sum and Product are overly conservative: they assume
there is a field with a type related to the GADT index. That should be
fixed, and this PR can be pointed to as an example of why the problem
isn't just theoretical.

So since this PR was written, I made https://github.com/haskell/core-libraries-committee/issues/10. If that is accepted, then this class will become identical to Show1.
GEq and GCompare are not the same as Eq1 and Ord1, and that is very intentional. GRead is also not the same as Read1. Perhaps at that point there should just be a breaking release of some where GShow is a reexport of Show1.

It's not identifical to Show1. GShow doesn't need Show a / a -> Int -> ShowS. GShow is unrestricted.

Yes. Let's reconsider this when i bump the lower bound to GHC-8.6. i don't see a need to do that.
(if that going to happen I'd probably just remove the class all-together).

I'll just turn this to a 8.6+ PR that does quantified constraints for all the classes.

Once GHC 9.6 comes out we can give this another look.


Added config.xml properties for maximum area size

Optimized MyAreaCommand.java code with a switch
Tweaked default config.xml to be consistent throughout
Updated README
Documented config.xml properties in README
Documented all commands and aliases in README
Added Bryan Burke to CONTRIBUTORS

NOTE: Because I alphabetized all the properties in config.xml, git gave up on providing a proper diff for that file, replacing it in whole instead.
I apologize for the mess last time, but now that I know how to base a branch properly, it won't happen again.

It looks much better now, the only thing still unacceptable is the switch in MyAreaCommand which would only work in Java 7. Using this version is not recommended as articles like this one pop up every week.

Should I convert the switch to use hashes for Java 6 or just go back to the if...else if...else statements in master?

I reverted back to the if...else if...else statements because using hashCode(), even String.hashCode(), may not be 100% reliable in all circumstances.

Good, it's almost ready now. Just one more question: Can I circumvent the restriction by executing start on (0,0), end on (5,5) and then again start on (1000,1000)?

Thank you for noticing that loophole. All is well once more.


API container sync:opendistro-security fails to create tenants

Description
Running yarn sync:opendistro-security in a running API container leads to a 400 bad request error when creating tenants:
2021-03-16T18:36:55.432Z - info: Syncing 3 groups
2021-03-16T18:36:55.433Z - debug: Processing lagoonadmin
debug: lagoonadmin: Created OpendistroSecurity role "lagoonadmin"
error: Opendistro-Security create tenant error: HTTPError: Response code 400 (Bad Request)
debug: lagoonadmin: Created index-pattern "application-logs-*"
...

This error is thrown here when opendistro-security api endpoints don't behave.
The reason this request is leading to a 400 is because it doesn't include the required description json body key, I can't find when this changed in opendistro-security but it seems like it's required now.
To Reproduce
Steps to reproduce the behavior:
Firstly make sure you have an up to date opendistro-es install

Exec into a running api container with k exec -n lagoon-core -it deployment/lagoon-core-api -- sh
Run yarn sync:opendistro-security in the continaer
See the error

Expected behavior
No error, expect the tenant to be created
Additional context
I've tested this with postman and can create the tenants successfully only when the description is included. So I've opened a PR that adds a generic description.

fixed in #2578


update dashboard (#2901)

// Describe your PR here; eg. Fixes #issueNo

Make sure that:

[x] You have read the contribution guidelines.
[x] You submit test cases (unit or integration tests) that back your changes.
[x] Your local test passed mvn clean install -Dmaven.javadoc.skip=true.

Codecov Report

Merging #2902 (85ecc73) into master (d4d52fd) will decrease coverage by 0.42%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #2902      +/-   ##
============================================
- Coverage     60.00%   59.57%   -0.43%
+ Complexity     4462     4423      -39
============================================
  Files           692      692
  Lines         19978    19975       -3
  Branches       1782     1781       -1
============================================
- Hits          11988    11901      -87
- Misses         6983     7069      +86
+ Partials       1007     1005       -2

Impacted Files
Coverage Δ

...ache/shenyu/plugin/grpc/cache/GrpcClientCache.java
68.75% <0.00%> (-31.25%)
:arrow_down:

...che/shenyu/sync/data/http/HttpSyncDataService.java
70.37% <0.00%> (-13.34%)
:arrow_down:

...yu/sync/data/http/refresh/AbstractDataRefresh.java
70.00% <0.00%> (-13.34%)
:arrow_down:

...henyu/admin/service/impl/UpstreamCheckService.java
42.85% <0.00%> (-12.70%)
:arrow_down:

...a/org/apache/shenyu/common/utils/VersionUtils.java
67.85% <0.00%> (-10.72%)
:arrow_down:

...henyu/plugin/grpc/resolver/ShenyuNameResolver.java
52.12% <0.00%> (-10.64%)
:arrow_down:

...apache/shenyu/admin/utils/ShenyuDictH2Trigger.java
63.63% <0.00%> (-9.10%)
:arrow_down:

...ache/shenyu/admin/utils/PluginHandleH2Trigger.java
63.63% <0.00%> (-9.10%)
:arrow_down:

.../apache/shenyu/admin/model/dto/BatchCommonDTO.java
50.00% <0.00%> (-7.15%)
:arrow_down:

...apache/shenyu/admin/model/dto/AuthPathWarpDTO.java
57.14% <0.00%> (-7.15%)
:arrow_down:

... and 27 more

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 d4d52fd...85ecc73. Read the comment docs.


Update spectator-view.md

HT loc

Docs Build status updates of commit 53b0ad2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/spectator-view.md
:white_check_mark:Succeeded
View

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


Angular v6 - CLI - Wiki - CI Stories - wrong commands

Bug Report or Feature Request (mark with an x)
- [X] bug report -> please search issues before submitting
- [ ] feature request

Area
- [x] Wiki

Repro steps
This wiki is out of date: https://github.com/angular/angular-cli/wiki/stories-continuous-integration
Now you can run the following commands to use the --no-sandbox flag:

ng test --single-run --no-progress --browser=ChromeNoSandbox <---THIS LINE
ng e2e --no-progress --config=protractor-ci.conf.js

Desired functionality
I think the command should be as follows:
Now you can run the following commands to use the --no-sandbox flag:

ng test --watch=false --no-progress --browsers=ChromeNoSandbox <---THIS LINE
ng e2e --no-progress --config=protractor-ci.conf.js

This is valid.
Tried to run the original command and got:
Unknown option: '--singleRun'

The command argument should be --single-run

the correct command in this case would be


Add timestamp to filename

To prevent accidental overwrites via PutObject you can (a) add a flag to prepend the filename with the timestamp or always do it even when the filename is specified and (b) when there is no filename specified prepend the timestamp with the remote_addr https://github.com/ThreatResponse/margaritashotgun/blob/master/margaritashotgun/remote_host.py#L55
In my opinion GMT time would be best so it wouldn't be effected by local time. I can implement b if I have your blessing for GMT time via
    from time import gmtime, strftime
    strftime("%Y-%m-%d-%H:%M:%S", gmtime())

I think modifying the default filename (b) is best for now.
I agree UTC/GMT is the way to go, I suggest one minor edit to the format string to match timestamps used in the log file.
https://github.com/ThreatResponse/margaritashotgun/blob/master/margaritashotgun/logger.py#L50
from time import gmtime, strftime
    strftime("%Y-%m-%dT%H:%M:%S", gmtime())

Done 👍  https://github.com/ThreatResponse/margaritashotgun/pull/6


Stricter callbacks?

I was checking out how the Verifier works and noticed this line in verify_first_party_caveat:
caveat_met = true if callback.call(caveat.caveat_id)

This is concerning since, because of Ruby's default-return semantics, it becomes very easy to write callbacks that will return a truthy value accidentally. It seems safer to:
caveat_met = true if callback.call(caveat.caveat_id) == true

This is a good suggestion - always better to make it harder to make mistakes.
I've made this change and update the library.
Thanks!


verifier: use json.loads(..) instead of ast.literal_eval(..)

The data sent via the API is JSON not Python dicts.
This failed once I build more complex policies for IMA or measured boot.
@maugustosilva can you confirm that you also expect it to be JSON and not Python dicts?

/packit test

/packit test

Yes, LGTM


⚠ Bofrost.be has degraded performance

In 4d5d17e, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 2061 ms

Resolved: Bofrost.be performance has improved in 22e6890.


Handle the case where the server reaches it's maximum content size

Currently, if the client asks for a file with a size superior to 200MB, it will relaunch the measure indefinitely.
What we need in the future:

The client doesn't make a complete measure with 150MB of data. Before it triggers the restart event it asks for 300MB of data to the server.
The server can return a maximum of 200MB, it can't fulfill the request so it returns an error (for example, a 409 HTTP code with an appropriate message).
The client cancels the restart event and emits the end event with the measures made with 150MB of data. Optionally, a warning could be thrown and a special event emitted.

Stale issue


add test to check that the checkboxes are within the form tag

Pre-Submission Checklist

[ ] Your pull request targets the staging branch of freeCodeCamp.
[x ] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[x ] You have only one commit (if not, squash them into one commit).
[ ] All new and existing tests pass the command npm test. Use git commit --amend to amend any fixes.

Type of Change

[ x] Small bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would change existing functionality)
[ ] Add new translation (feature adding new translations)

Checklist:

[ ] Tested changes locally.
[x ] Addressed currently open issue (replace XXXXX with an issue no in next line)

Closes #18210
Description
added a check to make sure the checkboxes are created within form tags.  This is the same functionality that radio buttons use

Hi @c-stu
This file has now moved to:
https://github.com/freeCodeCamp/freeCodeCamp/blob/next/curriculum/challenges/english/01-responsive-web-design/basic-html-and-html5/create-a-set-of-checkboxes.english.md
Can you please make a fresh PR on that file instead? Thanks for taking the time to prepare this.


Fix for symbolizing responses when yajl-ruby is used for JSON

This is to fix an issue with symbolizing the response keys when using the yajl-ruby gem to handle JSON.  The json and yajl gems are not 100% compatible in terms of API.  One main difference is on JSON.parse, the standard json gem takes a :symbolize_names option while yajl takes :symbolize_keys.  There already is a ticket on the yajl ruby gem to make it play nice with the json gem:
https://github.com/brianmario/yajl-ruby/issues/94
But it doesn't even have a comment yet.  Luckily, both params can be passed to either gem and have it function as desired:
string = '{"bla": "blub"}'

require 'json'
JSON.parse string, :symbolize_names => true # => {:bla=>"blub"}
JSON.parse string, :symbolize_keys => true  # => {"bla"=>"blub"}
JSON.parse string, :symbolize_keys => true, :symbolize_names => true  # => {:bla:=>"blub"}

require 'yajl/json_gem'
JSON.parse string, :symbolize_names => true # => {"bla"=>"blub"}
JSON.parse string, :symbolize_keys => true  # => {:bla=>"blub"}
JSON.parse string, :symbolize_keys => true, :symbolize_names => true  # => {:bla=>"blub"}

This patch ensures that both options are passed to JSON.parse.

Thanks Ken!


update to duros v3.2.1

Codecov Report

Merging #22 (668df4f) into master (eb0e30a) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@          Coverage Diff           @@
##           master     #22   +/-   ##
======================================
  Coverage    7.26%   7.26%
======================================
  Files           4       4
  Lines         234     234
======================================
  Hits           17      17
  Misses        216     216
  Partials        1       1

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


There is a problem with the Assets directory under the assets directory.

Information
Apktool Version 2.4.0
Operating System Windows
the problem didn't appear under the version 2.3.1，because you use the aapt command
there is a apk with the Assets directory under the assets directory,（一个apk里的assets目录下有Assets目录）
if I execute d command and then b command（执行反编译后再回编译）
The file was not correctly entered into the apk.（文件并没有正确打进包里）
three is the code I modified on the brut.directory.ZipUtils for now
private static void processFolder(final File folder, final ZipOutputStream zipOutputStream, final int prefixLength)
            throws BrutException, IOException {
        for (final File file : folder.listFiles()) {
            if (file.isFile()) {
                final String finalPath;
                String cleanedPath = BrutIO.sanitizeUnknownFile(folder, file.getPath().substring(prefixLength));
                if(cleanedPath.startsWith("Assets")) {
                    finalPath = cleanedPath.replace("Assets", "assets");
                }else{
                    finalPath = cleanedPath;
                }
                final ZipEntry zipEntry = new ZipEntry(BrutIO.normalizePath(finalPath));
                // aapt binary by default takes in parameters via -0 arsc to list extensions that shouldn't be
                // compressed. We will replicate that behavior
                final String extension = FilenameUtils.getExtension(file.getAbsolutePath());
                if (mDoNotCompress != null && (mDoNotCompress.contains(extension) || mDoNotCompress.contains(zipEntry.getName()))) {
                    zipEntry.setMethod(ZipEntry.STORED);
                    zipEntry.setSize(file.length());
                    BufferedInputStream unknownFile = new BufferedInputStream(new FileInputStream(file));
                    CRC32 crc = BrutIO.calculateCrc(unknownFile);
                    zipEntry.setCrc(crc.getValue());
                    unknownFile.close();
                } else {
                    zipEntry.setMethod(ZipEntry.DEFLATED);
                }

                zipOutputStream.putNextEntry(zipEntry);
                try (FileInputStream inputStream = new FileInputStream(file)) {
                    IOUtils.copy(inputStream, zipOutputStream);
                }
                zipOutputStream.closeEntry();
            } else if (file.isDirectory()) {
                processFolder(file, zipOutputStream, prefixLength);
            }
        }
    }

I have the same problem with
Apktool Version 2.4.0
Operating System mac

I have the same problem with
Apktool Version 2.4.0
Operating System win

Please do a pull request if you want to change something. I don't know what you are trying to fix or understand what the problem is with this style.

Please do a pull request if you want to change something. I don't know what you are trying to fix or understand what the problem is with this style.
I'm surprised to hear from you. It's not a big deal, the reason for this is that the windows system directory name is not case sensitive, modify the method sanitizeunknownfile in the brutio class, replace canonicalDirPath with getAbsolutePath, I solved the problem


Add payload v2 compatibility

Config changes:

change mongoUrl to databaseUri to match payload v2 config

Extra feature:

Allow custom express-session (optional), still defaults to previous version's value if not defined.
Added custom authorize path (optional), still defaults to previous version's value if not defined.

Awesome! Will release this as v2 (so it's clear that it supports payload v2)


Work around type checker ambiguity when generalized collection casts are enabled.

The type checker erroneously calls it ambiguous when both throws and nonthrowing functions can be used by collection conversion. To let id-as-Any land, temporarily work around this.

@swift-ci Please test and merge

No problem. There might be a few more, since it looks like it hits every XCTestManifest, though swift-ci stops on the first one. When I land our changes, generalized collection casting should allow you to get rid of the overload set altogether, since [() -> ()] will just be a subtype of [() throws -> ()].


Ukraine: optimizations

Make observed holidays calculation more universal and readable

Coverage remained the same at 100.0% when pulling 72c8beac54ec039c69d2dcab3a415ff0ae6d3964 on KJhellico:optim-ukraine into 4b83875321cff0778b58a9eada462d94ce46b3cd on dr-prodigy:beta.

👍 👍


PendingStateImpl tune-up and tx broadcast rate control adjustment

decrease the tx flooding number from cached layer to pool layer.
adjust tx broadcast rate control in p2p module 10/s -> 20/s base on the max buffer send in the pendingStateImpl.
refine log

LGTM


Startup System Checks

The system that runs checks to make sure the minimum requirements are met to startup the engine without issues.

Completed in https://github.com/rsbox/rsbox/pull/30


Ensure optional variants are loaded last.

This is a quick fix for #84841
There is an issue with our shader cache when there are disabled variants, it does not seem to deal with these properly (though this seems to be a recently introduced issue, possibly due to shader groups being added in 4.2).
For the most part this isn't a problem as the missing variants end up being recompiled and the cache fixes itself. The exception are our copy effects where a new copy type was added after the optional variants.
There is a more serious bug in the shader cache that causes all variants to be deleted (even the ones loaded properly) but in such a way that the Godot can no longer compile new versions.
This PR works around the problem by moving this new variant before the optional variants. This fixes the immediate problem.
We will need to fix the cache logic at some point but that will be a 4.3 fix.

Just for future reference, we'll need to investigate this further. But I think the problem is that disabled variants are simply not added to the cache at all. So now it's trying to load the COPY_TO_FB_SET_COLOR variant as if it's the COPY_TO_FB_MULTIVIEW.
We'll probably need to save something into the cache to indicate that slow contains a disabled variant, so that COPY_TO_FB_SET_COLOR is saved in the correct slot.

Thanks!


Rename Pod Security Policies to Pod Security Policy Templates in Cluster Mgmt -> Advanced

From @genexpr, under Cluster Management and Advanced, we should use Pod Security Policy Templates instead of Pod Security Policies

QA TEST PLAN
Scenarios

Scenario
Test Case

1
As a standard user, validate that in Cluster Management, Pod Security Policies is renamed to Pod Security Policy Templates

Validated that this is addressed in v2.7-head https://github.com/rancher/rancher/commit/6cca23fd75c3ccc447a6013c7a0a3482656515d6. See details below:
ENVIRONMENT DETAILS

Rancher install: Helm
Rancher version :v2.7-head https://github.com/rancher/rancher/commit/6cca23fd75c3ccc447a6013c7a0a3482656515d6
Browser: Chrome

TEST RESULT

Scenario
Test Case
Result

1
As a standard user, validate that in Cluster Management, Pod Security Policies is renamed to Pod Security Policy Templates
:white_check_mark:

VALIDATION STEPS
Scenario 1

As a standard user, navigated to Cluster Management > Advanced.
Validated that Pod Security Policy Templates is visible:


Refactor business logic to a service layer

I attended a talk at RailsConf that really got me thinking. Your Service Layer Needn't be Fancy, It Just Needs to Exist from David Copeland, author of Sustainable Web Development with Ruby on Rails.
The gist was that all of your business logic is scattered across your app. If you need to know what your app does you have to open models, controllers, jobs, and maybe even some views. Instead, he proposed moving all business-specific code to a service layer.
Note "layer" and not object. He doesn't care how you do it (POROs were recommended) just that it has to exist. And it doesn't need to be complicated.

Based on that I'm inspired to try and consolidate some business logic of railsdevs into services/. I kind of already started this with #387 but it could be extended further. Here are some high-level guidelines for what I'm planning.

Move non-database-related logic out of Active Record models

Exception: keep validations in the model
"Creating a user via the website is not the same adding a row to the database"

Move business-related logic into a PORO under services/

CreateDeveloper#create_developer(developer_params) is better than DeveloperService.create(params) - explicit about exactly what each class and method does

Service layer could be moved to a Ruby command line app

Return a state and the model, let the controller switch on that and generate the path
Return an error message, let the controller shove it in the flash

Roll our own authorization

Consolidate logic into specific services, but Pundit has proved too limiting

Have you seen u-case?

I haven't, no! I'm trying to stay as "boring" as possible right now but I will take a look for inspiration.
Do you use it in your projects?

Have you seen u-case?

I haven't, no! I'm trying to stay as "boring" as possible right now but I will take a look for inspiration.
Do you use it in your projects?

Yes. I started "boring" as well. Once a controller starts to be more complex than simple operations I eventually extract to a domain layer with usecases.

A usecase flow is made of "micro"cases or steps. It's very readable. I also like the functional style to unfold results (Success or Failure objects).

That's pretty slick, and I could see it working really well in super-large applications. That said, I wonder if it becomes a bit of an over-abstractions when you're just dealing with 5-10 people contributing at any given time.

This project

That's pretty slick, and I could see it working really well in super-large applications. That said, I wonder if it becomes a bit of an over-abstractions when you're just dealing with 5-10 people contributing at any given time.

I'm new to rails. Didn't build a lot of projects but I think it brings convention and good design to bigger teams.

For the 'create developer' task I know that a CreateDeveloper usecase exists somewhere.

You could consider interactor
It's nice to use very lightweight interactors that call helper modules or classes which in turn are super easy to test in isolation.
Several interactors can be called by an organizer  with each passing a context that will return the result and any relevant message.

What's very interesting to me is that I've enjoyed your approach of keeping the app as vanilla Rails as possible. There's a lot you can you within that app/models folder and I think that creating a separate app/services folder feels like a (small) step outside of the Rails way of doing things.

Thanks @andreimaxim, I needed to hear this.
The more service layer/objects I write the worse I feel about them. All I want to do is extract a DSL or parent object when I really want freedom to return whatever makes the most sense.
I also feel like I'm adding more and more code, and more and more indirection, to not accomplish much. Testing controllers via integration tests isn't hard these days. Yes, they are much slower than a unit level test. But I feel like with a sub 10 second test suite that's a trade off I'm willing to make.

I'm going to close this issue and accompanying PR #434 for now. Thanks to everyone who provided feedback!


Prez SPARQL result is wrong

When running a query, the result is returning with results from previous results of the same query.
I feel like it's probably a caching logic issue where we are repeatedly adding the result to the cache.
Example:
Prez instance: https://d34tz48z3oqfi8.cloudfront.net/#/sparql
Run the following query:
PREFIX skos: <http://www.w3.org/2004/02/skos/core#>

SELECT (COUNT(?c) AS ?count)
WHERE {
    ?c a skos:Concept .
}

Each time you run the query, it will get the result back along with all the other times this query was run.

there shouldn't be any caching
the FE or yasgui is adding a comment in the first line of the SPARQL query that gets sent, which seems to not be handled by Fuseki.
Compare: 50 results ("# application/sparql-results+json") on first line of sparql query
https://d1sx2k22urhvtf.cloudfront.net/s/sparql?query=%23 application%2Fsparql-results%2Bjson
PREFIX rdf%3A <http%3A%2F%2Fwww.w3.org%2F1999%2F02%2F22-rdf-syntax-ns%23>
PREFIX rdfs%3A <http%3A%2F%2Fwww.w3.org%2F2000%2F01%2Frdf-schema%23>
SELECT * WHERE {
  %3Fsub %3Fpred %3Fobj .
} LIMIT 10
no comment: 10 results - no comment
https://d1sx2k22urhvtf.cloudfront.net/s/sparql?query=PREFIX rdf%3A <http%3A%2F%2Fwww.w3.org%2F1999%2F02%2F22-rdf-syntax-ns%23> PREFIX rdfs%3A <http%3A%2F%2Fwww.w3.org%2F2000%2F01%2Frdf-schema%23> SELECT * WHERE { %3Fsub %3Fpred %3Fobj . } LIMIT 10
Not sure why the comment is getting added (don't think specifying a mediatype as a comment is part of the spec), but also not sure why it doesn't appear to be handled (ignored) by Fuseki.
Will come back to this

This original issue was reported with usage on the all endpoint. There appears to be inconsistent/wrong results when querying on the individual subsystem endpoints as well.
Prez instance: https://gsq-prez.dev.kurrawong.ai/sparql
Query:
PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
SELECT * WHERE {
  ?sub ?pred ?obj .
} LIMIT 10

all endpoint:

as described above, adds 10 rows for every request

vocprez endpoint:

appears to be correct results and respects sparql limit

spaceprez endpoint:

same behaviour as vocprez endpoint but does not respect sparql limit.
always returns the largest result rows from previous queries
result looks wrong, for example, if limit is set to 10, and previously it's been set to 30, it returns 30 rows, but with the actual 10 rows tripled.

catprez endpoint:

didn't test since catprez is not enabled for the above Prez instance


保护性场景的数据集

作者您好，请问文章中提到的保护性场景的数据在哪里，我看代码中没有，找不到对应的文件夹

Training datasets can be downloaded at 🤗 this Link, which contains nine characters experience data used to train Character-LLMs. To download the dataset, please run the following code with Python, and you can find the downloaded data in /path/to/local_dir.
from huggingface_hub import snapshot_download
snapshot_download(
    local_dir_use_symlinks=True,
    repo_type="dataset",
    repo_id="fnlp/character-llm-data",
    local_dir="/path/to/local_dir")

The prompted/ contains datasets that can be used for supervised fine-tuning directly. And generated/ consists of raw data that generated by gpt-3.5-turbo, which can be converted into prompted style. Here is the statistics of the training data.

数据集的获取方法已经放在README中，下载的generated/下为正常dialogue数据和保护性数据。

谢谢，感谢您的回复，我去网站下载看一下
---- 回复的原邮件 ----
| 发件人 | Yunfan @.> |
| 日期 | 2024年07月27日 11:51 |
| 收件人 | @.> |
| 抄送至 |<EMAIL_ADDRESS>|
| 主题 | Re: [choosewhatulike/trainable-agents] 保护性场景的数据集 (Issue #12) |
Training datasets can be downloaded at 🤗 this Link, which contains nine characters experience data used to train Character-LLMs. To download the dataset, please run the following code with Python, and you can find the downloaded data in /path/to/local_dir.
from huggingface_hub import snapshot_download
snapshot_download(
local_dir_use_symlinks=True,
repo_type="dataset",
repo_id="fnlp/character-llm-data",
local_dir="/path/to/local_dir")
The prompted/ contains datasets that can be used for supervised fine-tuning directly. And generated/ consists of raw data that generated by gpt-3.5-turbo, which can be converted into prompted style. Here is the statistics of the training data.
数据集的获取方法已经放在README中，下载的generated/下为正常dialogue数据和保护性数据。
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


defining two "identical" sets

Our models often require to define the same set on both rows and columns of a variable. This is compatible with 2d matrices but not for 1d tabular database like SQL, which they require different names for each column.
It would be nice to be able to add a property of a set, where you can define it equal to another one. The user would just provide one.
Example:
flows_from:
symbol: flows_from
table_name: _set_FLOWS_FROM
equal_to: flows_to
table_structure:
name: [ff_Names, TEXT]

done. You can now indicate in the parameter "copy_from" the name of the set to be copied. Remember you have still to indicate the structure of the set (headers names must be different with respect to the mirrored set).


Postgre DDL generation skips constraints

Description
In prior versions, it worked perfectly but I noticed that above version 24 the Postgre DDL generation skips the constraints. What else could be missing? It's a big problem for me because I used it for backing up the schema DDLs before a change.
DBeaver Version
<IP_ADDRESS>406231636
Operating System
Windows 11
Database and driver

PostgreSQL 14.9
JDBC 42.7.2

Steps to reproduce

Right-click on the schema name
Generate SQL and choose DDL
Check the "Show full DDL"
Click on Copy

Additional context
No response

What kind of constraint is missing?
I can't reproduce. Foreign keys, primary keys, check constraints are generated correctly.
The only one thing could be an issue if you created a constraint and did not refresh the list of objects in a tree of databases before generating DDL, which I would also treat as a bug.

Please provide minimal example to reproduce the issue.

I'm always refreshing the tree before the DDL exports. Unfortunately, I know this "refreshing issue".
The steps I did were the following:

I created a DDL export from a schema to have a DDL before the changes that I would apply.
I moved a very old table called table_A to table_A_bck
I created table_A with a new structure.
I checked all the referenced objects and they are pointed to table_A_bck as expected.
I refreshed the tree and generated the schema DDL export again.

After your answer, I checked my export again and I noticed the following.

No foreign keys depending on table_A_bck can be visible in the export. I searched for their names but did not succeed. The table was there.
I checked the DDL export generated in Step 1 and no foreign keys were pointing to the original table.
Finally, I exported only the table DDL, and the missing foreign keys were there.

@horv001 Hi. Could you provide a backbone for your tables, especially their relation? And what exactly did you mean under "moved a table A to B"?

@HocKu7 Hi, Sorry, I meant I renamed the table_A to table_A_bck. This is the reason why all the dependent objects are pointing to the table_A_bck table. There is no relation between these tables.
The table_A_bck is the original table (but renamed) and table_A (created in step 3) is the new table with the original name.

Hi, @horv001. Thank you for providing additional information, but unfortunately, I'm still not able to reproduce the issue. Can you please provide footage showing your issue with every STR? Thank you.

We were unable to reproduce the issue. If it's still actual, please provide a video showing it.


boringssl 0.20240930.0

Not a whole lot of changes since last snapshot, but we aim to just do these systematically and periodically (TBD what the cadence is). For now I just wanted to run through our processes.

Hello @agl, @bob-beck, modules you maintain (boringssl) have been updated in this PR. Please review the changes.


streamFramer.streamQueue will leak memory

streamQueue is uses a slice as a queue but never shrinks the slice. You'll probably want to use a deque (e.g., https://github.com/gammazero/deque). However, given the lack of generics in go (and the performance implications of this queue), you'll probably want to copy that implementation and optimize it for quic (e.g., make it work with int64 only).

There are probably simpler ways to handle this if it's not a performance bottleneck, it's just that the current way will leak quite a bit of memory over time.

When popping, we're removing the first element of the streamQueue slice:
https://github.com/lucas-clemente/quic-go/blob/ffdfa1f6760a75b2f919eb495fd99aa5ff1c6ad1/stream_framer.go#L74-L75
When adding, we're appending to the streamQueue slice:
https://github.com/lucas-clemente/quic-go/blob/ffdfa1f6760a75b2f919eb495fd99aa5ff1c6ad1/stream_framer.go#L43
As far as I understand, append is aware of the beginning of the slice, and won't allocate memory for unreferenced elements. I created an Go playground example to confirm: https://play.golang.org/p/hwk29ZSy_kB.
cap doesn't grow indefinitely, so I don't think we have a memory leak here. Or am I missing something?

If you want more details, take a look at https://github.com/golang/go/wiki/SliceTricks

Thanks. I actually knew about those tricks, just didn't realize go would reclaim memory on reallocation when shifting off the front (there's also quite a bit of misinformation on this topic on stackoverflow...).


Use of unresolved identifier 'ExamplesDefaults' Revisited

I'm having the same problem as noted before:  For the detailed sample code, I get same 4 errors on different lines with "ExamplesDefaults:"
ex.: Use of unresolved identifier 'ExamplesDefaults'
I also get the same error message for two lines with "ChartPointCircleView"
I'm using xCode 7.2.1 and CocoaPods.
Here the pod file I am using:
platform :ios, '8.0'
use_frameworks!
pod 'SwiftCharts', :git => 'https://github.com/i-schuetz/SwiftCharts.git', :branch => 'swift2.0', :commit => 'b7c523b'

Any suggestions?
Thanks

I tried the spec'd pod file first:
platform :ios, '8.0'
use_frameworks!
pod 'SwiftCharts', '~> 0.3'

Nas

Hmm I haven't tried the library on 7.2.1 but it should work. Using the tag is correct, the swift 2.0 branch is not longer used and outdated. Can you narrow down the cause by building the framework? ExampleDefaults is not the problem.

Just tested on 7.2.1 and it works, could you find more details?


Closes: #1

Updated validations.py python scripts
Fixed the behavior of validate_user function in validations.py
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[ ] Tests pass
[ ] Appropriate changes to README are included in PR

@googlebot I signed it!


Redoc 6.0 multiple app.UseRedoc no longer working

I'm using multiple app.UseRedoc calls to generate multiple documentation paths with diferent swagger specs.
It works until version 5.63, but in 6.0.0 no longer works. Only the last UseRedoc call is applied.
This same issue happened on change to version 5.0.0:
#1559

Dup of #1996


path_length_analysis notebook issue

the notebook has some issue
https://gdsfactory.github.io/gplugins/notebooks/path_length_analysis.html

@tvt173

is this after a recent change? the image in the notebook on the docs looks good and correct

the image is a screenshot :)
I don't know how to make bokeh display an image on the notebook

ah, yeah I understand that part. i was just saying that the screenshot version in the notebook looks correct. so it looks like it was working at some point, and i was curious if you knew when it broke

Im not sure but the tests were failing because gdsfactory/get_route was adding non serializable data, so i added clean_dict into it

it looks fixed now


Connection issues using Cloudflare Tunnels

📑 I have found these related issues/pull requests
I checked and didn't find similar issue
🛡 Security Policy

[X] I agree to have read this project Security Policy

Description
When trying to connect to my uptime instance over cloudflare tunnels to my host machine hosted on a vps i am sometimes getting either an 502 error or when i get past the 502 error im getting connection issues with some error messages at the top of the page.

If I keep waiting or refresh the page a few times it finally connects and seem to work, until I refresh the page or try to connect from a different device.
👟 Reproduction steps
I followed everything described in this wiki:
Additionally im using the env variable to setup my cloudflare token.
👀 Expected behavior
Visiting the url defined in the cloudflare tunnel should connect me to the uptime kuma dashboard.
😓 Actual Behavior
Visiting the url results in either a 502 gateway error, waiting time until the xhr polling error gets resolved or sometimes it just works as expected.
🐻 Uptime-Kuma Version
1.23.11
💻 Operating System and Arch
Ubuntu 22.04
🌐 Browser
Google Chrome Version 121.0.6167.160
🖥 Deployment Environment
latest install of every runtime setup on a fresh and updated ubuntu 22.04 vps.
nr. of monitors: 5
📝 Relevant log output
No response

Maybe this SO post is relevant to this issue:

When the guide was made, we indeed had transport: ["websocket"] as the only option.
This change was primarily a security fix and secondary a fix of how we understood long polling.
See https://github.com/louislam/uptime-kuma/releases/tag/1.23.9 and the associated PRs like https://github.com/louislam/uptime-kuma/pull/4216#issuecomment-1850362953 / or the security advisory for further context.
On the other hand https://demo.kuma.pet/ is run via cloudflare tunnels, so I don't know what you are experiencing precicely…
=> given that these are 5xx errors you are experiencing, what are the server logs?

Changed to help as it is running fine for all my instances and cannot reproduce.
Some directions to determine the root cause:

Try to reproduce on https://demo.kuma.pet/
Try different browsers
Try different networks
Try different server locations


Wrong screenshot in documentation

Hi everyone,
just started using Bruno and I really like it! I just noticed a small issue in the documentation (I would have fix it myself but it is in the screenshot). In chapter Testing -> Get Started the code in the screenshot seems wrong. If you tun this you get "res.getData() is not a function". The code snippet is anyhow correct using "res.getBody()" even if I am not sure if this call is really needed there. I left here a screenshot, I hope this is helpful.

Cheers,
Yari

Hi @yari-may,
Thanks for reporting this issue.
As you mentioned, res.getBody() is working fine because it's currently supported, whereas previously it was res.getData(). The example shown in the image is incorrect, and I’m currently working on a fix for this.

Hey @yari-may,
I’m closing this issue now as it has been resolved. You can find more details here.


Not possible to set password from mobile

I am using the newest Obsidian version on android with the plugin innstalled. After submitting a password and clicking the next menu item about what to hide i get the prompt that i must set a password first.
I have given it multiple attempts and restarted the app without any change in behaviour.

Thank you for your feedback. I have fixed this bug in the latest version. You're welcome to try it out, and if there are any more issues, please let me know promptly. @Gjessing1

It is working now, thank you very much!


Brass Funnel: IllegalStateException: May not call getCurrentUnsafe() from a close callback.

Describe the Bug
Server crashes immediately when loading in a (bugged) brass funnel.
Reproduction Steps
Unfortunately, currently unknown. Might update later when we figure it out, but for now, the issue was caused on a server and not by me myself.
Expected Result
No crash.
Screenshots and Videos
No response
Crash Report or Log
https://pastebin.com/48Qv2B8P
Operating System
Windows Server 2019
Mod Version
0.4.1
Minecraft Version
1.18.2
Other Mods
No response
Additional Context
No response

Has already been fixed, just needs to be released


[Role Request] Enabling/disabling secure boot

Description:
Enables managing the state of the UEFI Secure Boot through the DPU Redfish interface.
This allows clients to set whether UEFI should authenticate the OS image during the boot process.
Input:
SecureBootEnable(bool)
Output:
Success/failure
Nvidia Docs example:
https://docs.nvidia.com/networking/display/bluefieldbmcv2310/bios+secure+boot+configuration#src-2506859311_BIOSSecureBootConfiguration-SettingSecureBootState

see https://github.com/opiproject/ansible-opi-dpu/tree/main/roles/enable_secure_boot template code


32 PRs ?

i'm wondering if this is "summer effect" ?

I don't see how this issue is helpful. do you maybe want to close?


ComicInfo.xml Format section for docs

Following up on this https://github.com/anansi-project/comicinfo/issues/41#issuecomment-1521118952
A Format section for the ComicInfo docs.
The documentation provided is descriptive, in that It's based on what I've seen in the wild. I have never used ComicRack and don't actually know the original intention for this field.

Here is a good list of some of them:
    Special
    Reference
    Director's Cut
    Box Set
    Box-Set
    Annual
    Anthology
    Epilogue
    One Shot
    One-Shot
    Prologue
    TPB
    Trade Paper Back
    Omnibus
    Compendium
    Absolute
    Graphic Novel
    GN
    FCBD

Thanks @ajslater


Suggestions / Federation

Hello,
as far as I know from ZDF colleagues or Verwaltungsrat, this project should once federate.
I would strongly suggest to use ActivityPub ▸ Activity Vocabulary from the very start to create a healthy contributing environment.
This is affecting https://github.com/ZDFDigitalTechnology/wearenewpublic-demos/tree/main/client/data and the changes would be easy.
E.g. in the Godzilla Article ( :scream: please be safe, private media here, can we use your footage? we print name uppercase! ;)
https://github.com/ZDFDigitalTechnology/wearenewpublic-demos/blob/main/client/data/articles/godzilla.js :
{
    title: 'Giant Radioactive Lizard Unleashes Chaos in Manhattan',
    subtitle: 'As New York faces a previously unimagined threat, leaders contemplate how best to react.',
    author: 'Joe Bloggs',
    photo: 'godzilla_new_york.jpeg',
    authorFace: 'face2.jpeg',
    photoCaption: 'The radioactive lizard walking through the streets of Manhattan. Photo taken from the Empire State Building.',
    date: 'April 1, 2023',
    rawText: '[...]'
}

becomes e.g.
{
    "@context": "https://www.w3.org/ns/activitystreams",
    "id": "http://example.org/ZDF/phoenix/Godzilla-ReactionsAfterIncident",
    "type": ["Article"],
    "name": ["Giant Radioactive Lizard Unleashes Chaos in Manhattan"],
    "summary": ["As New York faces a previously unimagined threat, leaders contemplate how best to react."],
    "attributedTo": [
        {
            "type": "Person",
            "name": "Joe Bloggs",
            "image": {
                "type": "Image",
                "name": "Joe Bloggs / ZDF Investigative",
                "url": [{
                    "type": "Link",
                    "href": "jo-face2.jpeg.jpeg",
                    "mediaType": "image/jpeg"
                }],
                ...
            }     /*what reads authorFace in your example */
        }
    ],
    "image": [
        {
             "type": "Image",
             "name": "Alyssa P. Hacker / Ostkreuz",
             "url": [{
                 "type": "Link",
                 "href": "godzilla_new_york.jpeg",
                 "mediaType": "image/jpeg"
             }],
             ...
         }
    ],
    "published": "2023-04-01T12:12:12Z",
    "content": ""
}

Standards are good and now possibilities are infinte (see later below) :)
To be explicit all properties which are not "functional" are done as Array, but due to the way JSON-LD works, this is optional
"name": "Giant Radioactive Lizard Unleashes Chaos in Manhattan" would be the same cause will be expanded to Array.
content would be the same like rawText unless you specify another `` like "html" and/or the source property
Just for clarity I did also expand the attrbutedTo object …
Let's assume that Joe Bloggs is on scene in the footstep of Godzilla and appears multiple times and is an Actor, a simple link to the Profile does the trick
"attrbutedTo": "http://joe.example.org"
Then about translations :
Please see the https://www.w3.org/TR/activitystreams-core/
ActivityPub is multilanguage by default
Simply add 'Map' to the properties name, summary, content or to Links.
It is flexibel, if the server decides for many languages, single files are fine like
{
    "@context": "...",  "id": "...", "type": ["Article"],
    "nameMap": {"de": ["Radioaktive Riesenechse verursacht Chaos in Manhattan"],`}
}

but if you serve only some languages like EBU, Eurovision or e.g. for next Wetten, dass..? only ["de-DE","de-AT","de-CH"] then one object might do the trick :)
:point_right:  Due to JSON-LD now the possibilities are infinite and beyond!
We can build nice Collections.
We can attach Godzilla locations (Place) or Events to the Article.

About the "Roles" example see ,
if you simply define oneOf, the user can select a role but you can also create a Collection of Question for the complete workflow.
In general the spec. is written as generalized as possible and we should give them definitions for broadcaster or journalist personas …
E.g. instrument  Identifies one or more objects used (or to be used) in the completion of an Activity.
This can be used to create transparency in story making ...

This would be the rough basics.
Now let's say we do not want creative-content-stealing machines like ChatGPT …
We would like to incorporate the common knowledge of the world created by human beings
(with much more languages, codes and codizes than AI) instead.
To make "it" (aka wikibase) even better. Not to make Sam A. profit!
Simple.
In its simplest form, we add to the @context
"@context": [
    "https://www.w3.org/ns/activitystreams",
    { "wd": "http://www.wikidata.org/entity/",  "wdt": "http://www.wikidata.org/prop/direct/" }
]

(or any other Linked Data Vocab)
Now we can use all well described and qualified wikidatata properties and entities to say e.g. that the right after the Article movies were made by Roland Emmerich and Warner/netflix
[ wd:Q24075, wd:Q7731172 ]
or to say of which specific type / wdt:P31 the Article is –
or most important
{"describes": "wd:Q6567"} to say that this Article is about the well known and explicitly linked https://www.wikidata.org/wiki/Q6567
E.g. this component prototype was created in a day
https://digitalcourage.social/@sl007/113023369977466510 and it's all WIP here ...

PS highlighting that ZDF will be at https://berlinfedi.day/ where Evan, the inventor of above vocabulary is a speaker :)
cc @ZDFDigitalTechnology
just btw: The particular godzilla example reminds me of our top Linked Data type [..., 'redaktor:factual'] or [..., 'redaktor:fictional' cause my strong believe is that we must give any user to describe whether a post is meant factual and to mark manipulated Images, cofounder of freelens here - the symbol is "[M]"] - please also read our german book from ARD colleague Björn https://socialmediafalle.de/ or see the english Talk at Public Spaces Amsterdam https://video.publicspaces.net/w/9USsJ37cHVy4tY9Pn7DX2X
We are doing a huge visual ActivityPub Component library for various clients.
Including

all the types
with federated geocoding
wikibase, wikidata, OSM, EBU and IPTC integration
baseline solid typography with isomorphic items as Card, Grid (table/list), full view
theming with aspects like color, spacing, typo, depth, motion etc.
all as a solid HTML experience with JS enhancements and PReact cause if we do it all clientside without sending the data over the wire we leave many Open protocols out which rely on the way the web works (e.g. microdata parsing instead of JSON)
using the ActivityPub Client2Server API
etc.

ZDF might know me from war reportage, investigative or frontal reportage but this is really not my heart thing at the moment.
I hope, we can create a nice conversation about how any public broadcaster or journalism / science can use ActivityPub and the Fediverse for the most healthy public democratic conversation and in the most conformant way.
Did also co-org the official Confs e.g. in Prague or virtual, where the Talk videos are on https://conf.tube/
We just need to be aware of the amount of e.g. google controlling it cause they control the browser.
ActivityPub could long be a trusted protocol like "mailto:" but registerProtocolHandler is broken (can send demos) and so we need to enter our handle on other pages one time which is just cause google ...
Also trying to connect ypu to various parts of the community.
E.g. https://github.com/dahlia/fedify for the Server.
Or "Embedded Instance ..." which might be what https://iconet-foundation.org/ already did within a stipend.
:popcorn:  Best
sebi

2 months later:
Considering this project to be dead.

The project isn't dead. We moved to a new repo based on a different architecture that is better suited to real production use. That repo is currently private, but will become open source at some point in the future.
If you have suggestions for ZDF, then probably best to talk to them directly. I believe you have contacts.

The first time we talked about it was 2016, in 2019 I organized the Conf.
Now it is 2025 soon.
That is 9 years. Recently drove 1.500km to Berlin to the meeting at Fediday. Voluntary.
Thank you very much.
PS I described in our Talk at Public Spaces Amsterdam why this would have been urgent
https://video.publicspaces.net/w/9USsJ37cHVy4tY9Pn7DX2X

I did update the W3C Social CG, Maybe you could update ZDF chiefs with better knowledge, Then people don't have to drive 1.500km for nothing.
My only goal for the Policy SIG  with this issue was to assure compability, conformance and interoperability with the rest of the fediverse from the start. Also W3C Portability or Security Task Force can help, there are 7 ActivityPub Task Forces and 2 SIGs.
There would be a „community“.
A good start would be Verwaltungsrat Leonhard Dobusch who did also write https://netzpolitik.org/2023/neues-aus-dem-fernsehrat-95-fragen-und-antworten-zum-public-spaces-incubator-des-zdf/
PS I did also describe in books why this would have been important https://socialmediafalle.de/ -
Sorry, if I misunderstood "New Public" …

@robennals
So, I took this project out of the active projects at W3C now.
Nobody of you responded to ZDF, all the videos from 2018 are still on conf.tube –
we will now develop the federated and Open Source thing we voted for in 2018 in our own team.
Please keep in mind that it is Public Money which you burn.
We all work volunteerly and I can't explain to the audience what you are currently doing cause it is against anything we had in mind with the project at the W3C meeting 2018 and ActivityPub Conf 2019 and 2020.
As you know, the ARD joined.

As you know, Björn Staschen, the other guy in the Talk is from ARD.
I did give all my money for this project and I never experienced such a rude response @ZDFDigitalTechnology
This sounds like a very white and very old alpha male and I doubt we have the right partners here.
I'll tell it Eli and will speak to Dunja Hayali, Susana Santina, Norbert etc.
Incredible unsocial.


When pulling a package from upstream and a branch diverges, straight still asks me to solve it through my fork

Here's my recipe for a package called awesome-tab:
(straight-override-recipe
   '(awesome-tab :host github :repo "manateelazycat/awesome-tab" :depth 1
                 :fork (:host github :repo "AmaiKinono/awesome-tab" :depth full)))

When pulling from upstream (calling straight-pull-package with a prefix arg), Emacs shows me this:

I think the right behavior here is ask me to solve it through "origin/master".
Update: Actually I don't know git very well, so I think I'll explain the situation to let you decide if this is a bug or not:

I was using the upstream URL directly in my recipe, and my local repo is up to date.
I have a fork that's not up to date with upstream.
I created the recipe override, and did what I always do: normalize the package, pull from upstream, and I'm going to edit it and push to my fork.

So there may be some conflict to solve, but I think that should be when I push to my fork. As it's been said, my local repo are up to date to the upstream, so I think nothing should really happen when I pull from upstream. Is that right?

I think this is because straight.el wants to first merge fork/master into master and then merge upstream/master, and then push master to fork/master. But I could be wrong; it's been a while since I wrote this code. Do you think that sounds like the right thing to do? And does it seem like what's happening here?

does it seem like what's happening here?

Yes.

Do you think that sounds like the right thing to do?

It makes sense, since dealing with conflict later may likely be more troublesome. But if there's no one else working on the fork, it's likely I would pull upstream/master, make changes, then force push to fork/master.

Ah. But I don't think straight.el should be encouraging force-pushing; doing that will break your ability to revert to a previous version of your config and have the right version of your fork from the lockfile.
It is definitely an option to merge from upstream/master before merging from fork/master. That would make sense to me. (The merge from fork/master could then have an option to just do the force-push, because sometimes it is in fact what you want to do.)
This is a little too complicated for me to immediately tell what to do. But if you or someone else proposes a concrete change to the flow that sounds reasonable, I'd be happy to adopt it.


Get depth API

Forgot to include this in #277

Thanks for the PR!
I think this patch needs a bit more work before we can merge it.  We've updated our contributing.md to make our PR guidelines more explicit.  Please take a look - specifically for this change, I think we'd need

An explanation of what this API does and why it needs to be written in C++;  as it stands this information can be much more efficiently calculated from the view()s config object.
A Javascript API
Tests and JSDoc


Adjust Prometheus example diagram and move the example to the root folder

Description
Changes proposed in this pull request:

Adjust Prometheus example diagram
Move the example to the root folder diagram

Related issue(s)
Fixes #336

Hi @NHingerl
The diagram should be now in line with the guidelines. PTAL :)


Ignore the default empty layout objects when loading a .ui file

Lets try this again, this time without the phantom user:
The default empty layout object bool(QMainWindow().layout()) evaluates to True in PySide and False in PyQt4. So I added a check to see if an existing layout is empty.

Ok, I'm getting a Travis build failure on the PyQt implementations. From what I can track down, calling QMainWindowLayout::count() emits the warning qWarning("QMainWindowLayout::count: ?");, and that warning is what's causing the failure.  However, I haven't the foggiest idea how to either fix it, or have the test ignore that warning.

Thanks @tbttfox.
I've tracked down the original commit from which this clause got added, I think it'd be helpful to future readers if we included a comment on what it's doing there.

https://github.com/mottosso/Qt.py/commit/e4a736ab1d9ae214f4caaca20147ed3c83d2925c#diff-cd1d7c0a982bce680146d5b248151256R861

The reason being to mimic PyQt throwing an exception. Which now that I think of it sounds a little backwards. It's PyQt who's supposed to mimic PySide2.
Do you think it's possible to have PyQt support this feature, as opposed to PySide inheriting shortcomings of PyQt? It might not be, in which case this would be fine.

From what I can see, PyQt does support this feature. Nosepipe is just confused by the qwarning (that doesn't actually break anything), and I'm not familiar enough with nosepipe to tell it that the warning is expected, because it's not a normal python error.
And FYI:
My test passes all cases if I remove the layout existence check (the other tests fail, of course). So I'm guessing the act of checking for a layout on a new QMainWindow instance creates the layout. PyQt4 then emits that qwarning when the ui is loaded.

From my testing for both PyQt and PySide:

QMainWindow().layout() returns a QLayout with a count of 0.
QDialog().layout() returns None.
QDockWidget().layout() returns a QLayout with a count of 2. It stores the close and float buttons used internally.

And if you call bool(widget.layout()) or if widget.layout():

QMainWindow returns False in PyQt, and True for PySide
QDialog returns False in both PyQt and PySide
QDockWidget returns True in both PyQt and PySide

This is consistent in both Qt4 and and Qt5 versions.
This means that due to the artificial check, you can't use Qt.QtCompat.loadUi on QDockWidget at all, and only in PySide/2 you cant use loadUI on QMainWindow.
I've done some testing and PyQt4/5 do not error if you use PyQt5.uic.loadUI on a Widget that already has a layout assigned to it.  I used the code from the unit test to verify that. I only have access to PySide2 from inside Maya so I haven't verified this in PySide.
Qt's c++ code for QLayout raises a qWarning 'QLayout: Attempting to add QLayout "" to QMainWindow "", which already has a layout' I'm assuming this goes to stderr, and nose detects it as a error.
This is a c++ output, so I'm not sure if you can redirect its stderr output away from nose, but I think this is the original reason for raising the RuntimeError in Qt.QtCompat.loadUi. Just so the unittests didn't error out.
Here is a simple example of the problem, in this case it was run with PyQt4 from a windows command prompt:
>>> import sys
>>> from Qt import QtWidgets
>>> app = QtWidgets.QApplication(sys.argv)
>>> win = QtWidgets.QMainWindow()
>>> layout = QtWidgets.QVBoxLayout(win)
QLayout: Attempting to add QLayout "" to QMainWindow "", which already has a layout
>>>

No error was raised, but "QLayout: Attempting ..." is written to the command prompt, not python. I haven't seen it in Maya, but I assume its there just not being shown.
Is it possible to make nose ignore stderr from c++ for these specific tests? Or make Qt not log qWarnings? I don't think the check added in e4a736a is needed at all and it actually breaks things.

I did a little more searching and I think we could control the qWarning output using this function already exposed in Qt.py
http://doc.qt.io/qt-5/qtglobal.html#qInstallMessageHandler
Some example code that looks promising: https://stackoverflow.com/a/25681472

Thanks for the excellent investigatory notes, @MHendricks.

I don't think the check added in e4a736a is needed at all and it actually breaks things.

Would you be able to take the lead on resolving that? I don't use loadUi myself so it's hard for me to find out about these kinds of problems.

It may be a few days before I can get to this (production support gets in the way). You don't need to test with loadUi, just attempt to create a layout and pass a parent widget(that already has a layout) into its constructor like I did in the code sample above.
I'll try to find some time to give it a try, or I can help @tbttfox debug it if he has time.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: tbttfox:x: Tyler FoxTyler Fox seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Ok, so @MHendricks and I got together and got this working, but there's some extra stuff we found out
In the Qt4 bindings, the message handler is called qInstallMsgHander
In the Qt5 bindings, it's called qInstallMessageHandler
In both cases, they take exactly 1 function as an argument... however, that function requires a different signature between 4 and 5 (Two args in Qt4, vs. Three args in Qt5)
So, for now, we've added qInstallMessageHandler as a misplaced member, and it's up to the implementation to handle the different signatures. For the tests we just grab *args and parse from there.
There is probably a bigger discussion to be had on how to handle the message handlers, but I think we can do that in a separate PR.

I'm sorry for the silence here. I'm very busy at work and my wife is expecting in about a week... so I'm not sure exactly when I'll be able to review this.

I pulled some commits from @MHendricks.
The layout existence check in _loadUi was removed. Having that check was causing failures on Linux where the code would run just fine otherwise. The test checking for this was removed.
Tests for running loadUi on QMainWindow QDialog and QDockWidget were added.

There is some inconsistency between the windows and Linux builds of Qt4 when dealing with QDockWidgets.
>>> from Qt.QtWidgets import QDockWidget
>>> dw = QDockWidget()
>>> dw.layout().count()
2
>>> dw.layout().isEmpty()
True

For QDockWidgets on Windows, isEmpty() returns True, but on Linux it returns False. I'm not sure why the layout existence check in _loadUi was added in the first place so I removed it.
QMainWindow has a default .layout() object and return False when .layout().isEmpty() is called on a new instance. This seems consistent for both Linux and Windows.
QDialog and QWidget do not have a default layout.
Also, thanks @tbttfox for cleaning up the unfinished mess I left on my test repo.

For QDockWidgets on Windows, isEmpty() returns True, but on Linux it returns False.

Maybe we could add a QtCompat.isEmpty(my_widget) to account for the differences?

I'm not sure why the layout existence check in _loadUi was added in the first place so I removed it.

 In this case, I found:

Added exception to PySide loadUi if there is an existing layout to mimic PyQt4 behavior
reference

Not sure what this means given the changes in this PR. @dgovil do you remember what issues you where having before that commit? Does this resolve those issues?

QtCore.qInstallMessageHandler

Not sure how this slipped in here, there hasn't been any mention of this so far? I'm happy to keep it though, it looks well thought out and documented.

@mottosso It seems PyQt4 would error if you tried to load a ui file on to a widget that already had a layout assigned, which was the reason for that warning.
However I've recently discovered that it really depends on the PyQt version whether that is an issue or not. Some versions do not care while others do.
I'm not sure what's the best way to proceed here? IIRC the version that the tests download will fail, but the version we have at work does not. Not sure what's entirely different and noone seems to have answered me

So I added a test to see that error. And it wasn't an actual error, it was just nosepipe freaking out about a qWarning again. I wrapped the test in a message handler, and everything passes!

After some thought, we decided that qInstallMessageHandler should be moved to QtCompat because of the handler signatures are different, and the types passed to the handlers are different.
And with that, I think this beast is finally ready, pending review.

Well done everyone. I think it looks great. I've bumped the version and will merge and release once the tests do one final round.

Merging this, sorry for the delay!


Can't use nested Stack Navigator inside BottomTabNavigator

I created stack navigator and tried to use inside tab navigator and it gives;
The component for route .... must be a React component. For example....... error.
I don't know why it's happening but I could use it before, (when tabs, drawers and other modules were inside react-navigation package) so I don't understand why it's gives that error.
Code sample
const MainNavigator = createBottomTabNavigator(
    {
             ....
             ....
             ....

        Camera: {
            screen: MenuStack,
             ....
             ....
        },
             ....
             ....
             ....
        },
    },
    {
        initialRouteName: 'Camera',
    }
)

const MenuStack = createStackNavigator({
    Camera: {
        screen: Camera
    },
    Menu: {
        screen: Menu
    },
    Order: {
        screen: Order
    },
    Addition: {
        screen: Addition
    }
},
    {
        initialRouteName: 'Camera',
        defaultNavigationOptions: { header: null }
    }
)

const AppNavigator = createStackNavigator(
    {
        MainNavigator,
             ....
             ....
    },
    {
        initialRouteName: 'MainNavigator',
    }
);

Your Environment

software
version

ios or android
android

react-native
0.61.2

react-navigation-tabs
^2.5.6

node
10.16.0

npm or yarn
npm

Define MenuStack before MainNavigator

Define MenuStack before MainNavigator

Why do we have to do this?


Bug: 2255499 [fusion-hci-4.14] Api added for generating the token

manual cherry-pick of #2339

merge after #2350


Fix agent tag command step link

The command step attributes incorrectly reference the build meta-data docs, instead of the agent tags docs (probably from when agent meta-data was renamed to agent tags). This updates the link and words to point to the new setting tags doc, and keeps the link to the targeting section as well.

Those sneaky links.


Improve modref docs

Just docs, no downstream impacts or code coverage requirements.

@rsoeldner @jwiegley I rewrote a lot of the sections with code examples and removed the TODOs. I do mention pinned modrefs as a possible future feature, and expanded the vuln description. Do you mind re-reviewing now?

Are the rst files automatically generated or hand curated? It looks like the last commits special modifications?

Are the rst files automatically generated or hand curated? It looks like the last commits special modifications.


Added Turkish translation

Here is a translation file for Turkish language.
Good work!

Thank you very much @bekirkarul :+1:


Remux MKV to MP4 to allow direct browser viewing

It's common to find MKV videos being shared in MEGA. Some of those videos use codecs supported by browsers, just the container, MKV, which isn't supported. We can use node-matroska to demux those videos and mp4box to mux into MP4, a container supported by browsers.
Edit: Seems node-matroska requires a seekable source, so qgustavor/mega#17 is blocking this feature. the related issue was fixed
Edit 2: Seems isn't possible to demux MKV files using node-matroska; also this library do too much (it handles I/O operations, instead of only handling Matroska files);
An alternative is FFmpeg, which don't requires a seekable source, but seems isn't possible compiling it to JavaScript without dropping streaming support.
Edit 3: seems the original project, node-ebml, supports streaming.
Edit 4: I tried parsing a MKV file with node-ebml and it worked well: https://qgustavor.github.io/mkv-extract/
But there are some issues: it's slow, seems it leaks memory, demuxing streams are quite hard as those are edited when muxed (removing any information which can be provided by MKV, like timestamps and bitrates), and video and audio information couldn't be demuxed.

Closed because #21


update networkservice table

NetworkService + netsh proxy - should be "yes" in the table instead of "no"

#sign-off


Set up Task

Fixes #17

[ ] Set up Haskell

[x] GHC
[x] Stack
[ ] VS Code plugin
[ ] Formatter
[ ] LSP
[ ] Prelude
[ ] Warnings
[ ] Text
[ ] Records
[ ] MTL

[x] Test multi : task traversal
[ ] Generate root taskfile
[ ] Generate project taskfiles
[ ] Fix esbuild
[ ] Fix prettier
[ ] Set up root Prettier & dprint (.md, .yaml, ...)

Yes, multi : is OK:
version: "3.0"

tasks:
  hello:
    deps: [":hello", "::hello"]
    cmd: echo bbbbb


Specimen Type vs. SampledMediumType

I think I have these terms backwards in the current version of the template.  Just creating this issue to remind myself to look into it.

Fixed in both versions


pulley: Fix interpreter push/pop

Add stack-overflow checking to push and other decrements of sp.
Fix the up/down direction of push/pop (push goes down, pop goes up).
Fix the order of operation sin push, first decrement then write.
Move methods to Interpreter to use ControlFlow more heavily.

Review-wise this is stacked on https://github.com/bytecodealliance/wasmtime/pull/9629

rebased!


Add simple Autoencoder model. Using new dynamicallyCall API

Added simple model to illustrate base features of dynamicallyCall.

Awesome!

Great work! Currently we have no CI for swift-models yet, but let's manually test it and get it merged.

Actually, there are some issues with model. No optimizers yet, so it is in progress. But at the result you can see graphics in result folder.

Lack of optimization is fine, given that this is an early-stage repo and not meant to be an offical model zoo.

@VolodymyrPavliukevych I left some random style-related comments. Great work and thanks for bearing with all the bugs and crashers in the early phase!

@rxwei and johndpope thanks for your review.
Question for future, is there any any rules for creating branches for my code, any branch names style, etc?

@VolodymyrPavliukevych We don't have any rules for branches yet.

@rxwei Super, I will handle that.

Thanks! One last thing: we recently deprecated Tensor.dot in favor of matmul. Could you update to the latest Swift for TensorFlow toolchain (6/1) and use matmul?

LGTM. Merging.

Thanks for everyone!


Added Gruntfile with js, css, and html lint capability

I'm going to clean up the history for this. A PR this simple doesn't need this many commits.


BUG - Playbook Module failure

This is to refer and address https://github.com/briandelmsft/SentinelAutomationModules/issues/427
It seems that we might need to adjust the API version for the REST call for playbooks calls. Need to check if that impact other types of calls potentially using the ARM endpoint.

@piaudonn Have you been able to reproduce this?  I can only reproduce it when the STAT identity doesn't have access to execute the playbook.  The 2022-07-01-preview API works fine for me.  I note the permissions issue because it doesn't throw a 401/403, it throws a 400 / Bad request

I just tried. Works with both api-versions. Shan't we update the version anyways?

Oh I just saw #32

@piaudonn As long as the input is structured the same we can update to the new version, the doc isn't clear but I think based on your testing it likely is.
We should probably also add some error handling for the 400 to include some text to verify permissions to the logic app as the error isn't very intuitive at all.  Not even a 401/403 like you may expect for a permissions error


Table widget to select multiple predefined values as a table

Is your feature request related to a problem? Please describe.
It's basically  the makefile --enable/--disable feature matrix. I'd like to have it a in a single screen with defaults selected.
I can make defaults for each, but they'll appear as two options on top of eachother. Instead i'd like if a variable like cfg: <feature1> <feature2> etc could be shown as a quasi-table, where tab cycles the options in a single line, and down selects another feature. I may have missed a example like this.
Describe the solution you'd like
A mode for display of lines line this with multiple variables that allows this mode.
Describe alternatives you've considered
The usual, selecting them all once at a time. This multiplies the times you press enter by the number of features you allow to be shown, instead of a single enter if you don't want to change anything from the default.
Additional context
None

where tab cycles the options in a single line, and down selects another feature

I'm not sure that's gonna be possible unless I implement my own fuzzy finder (instead of using fzf).
A workaround would be:
# my make command
make <cfg>

$ cfg: for x in 1 2 3; do for y in a b c; do echo "$x $y"; done; done ---  --expand

By default we would have 1 a (which could be selected using ) and all other combinations would be listed too.

I'm sorry, could be selected using what? I thought i had to place '\n' in between options, do you mean to say you can select single options side by side?
That said, it's not quite the same as being able to show all the defaults and skip ahead.
Ah well, it doesn't matter that much anyway, the current approach looks fine. It's just annoying to have to press enter 10+ times until you get to the interesting options or the ending if you don't want to change anything.
Speaking of that, it comes to mind that a special widget is not strictly necessary if there was a 'eager' mode for variables that selected their default and allowed you to skip ahead for them - though what form of user interaction would allow that skip, i don't quite know.


Add data-lists to Blockly.Categories

Resolves
There's not a standalone issue for this but the discussion is in https://github.com/LLK/scratch-blocks/pull/1267#issuecomment-347996948
Proposed Changes
Now that list blocks are a different color from scalar variable blocks, add an entry for them in Blockly.Categories and update the vertical blocks accordingly. This makes it so that the svg <g> tag that represents the block will have the attribute data-category="data-lists"
Note that I named the property Blockly.Categories.dataLists -- if you guys have anything against camelcase I have no problem changing that.
Reason for Changes
To make scratch-blocks fully styleable with CSS! Before this change, all blocks in the data category could be styled but there was no way to focus in on list blocks.
Test Coverage
Right now there are no tests for all the stylability data-attributes, but maybe that's something to consider! I tried my best to get the test runner working but I'm still having some difficulties -- anyway, vertical_playground.html seems to work fine and all blocks in the data category are showing the expected data-category

LGTM.


style: clang-format file, for discussion

adds a clang-format file, exported from my clion settings that closely match the dpp code style. for discussion or inclusion.
Code change checklist

[x] I have ensured that all methods and functions are fully documented using doxygen style comments.
[x] My code follows the coding style guide.
[x] I tested that my change works before raising the PR.
[x] I have ensured that I did not break any existing API calls.
[x] I have not built my pull request using AI, a static analysis tool or similar without any human oversight.

finally it's here! there's no harm in having .clang-format file as long as it follows coding guidelines. It makes it easier for project development among different tools ppl use

I'll try this at some point and see how it is


[MRG] enhance configure() and add data_transform() method

Two additions to the API here:
configuration
First, configure() is enhanced to handle arguments similarly to encode(). So you can do
Layer(data).configure(MarkConfig(color='red'))

as a shorthand for
Layer(data).configure(mark=MarkConfig(color='red'))

transformation
Secondly, I added the data_transform() method similar to configure() and encode(), so you can do this:
population = load_dataset('population')
Layer(data).data_transform(
        filter="datum.year==2000"
    )

in place of the current approach:
Layer(data, transform=Transform(filter="datum.year==2000"))

I realize data_transform is a bit awkward/redundant. This really should be called transform, but that is already used as an attribute name in vega-lite. IMHO, it would be more consistent if the attribute were transformation and the action were transform, but we can't control everything :smile:

In Vega-Lite, the cause of confusion is that transform can be noun too (A filter transform / A calculate transform).
I agree that data_transform is awkward.  Is there a way to name the method transform?
I saw that you have custom code for setter / getter for data (which is stored in _data).  Can't we use the same approach (transform / _transform)?

Just added to this the update rather than overwrite behavior from #22

I like this idea. Questions:

How do you map between attribute names and know which config class they should get passed to?
What if there are two config classes that have the same attribute?

I thought about having a transform method previously and encountered the conflict with the attribute name. What about calling the method transform_data to follow a verb+noun construction?

How do you map between attribute names and know which config class they should get passed to?

The Config class contains the mapping from names to classes – I do some dictionary gymnastics to determine the mapping automatically. It occurred to me that we might be able to do the same type of thing with encode() as well.

What if there are two config classes that have the same attribute?

In general this approach would fail in that case. We're just lucky that the Config traits don't have any duplicates

I like transform_data instead.

OK sounds good. Is there any further work you want to do on this branch or
should we merge and play/iterate?
Also, I pushed some stuff directly to master over the past hour or so...
Also, were you going to add the mark_*(attr=value) stuff?  I forget where
you had commented on that. Like the idea a lot.
On Fri, May 20, 2016 at 7:46 PM, Jake Vanderplas<EMAIL_ADDRESS>wrote:

I like transform_data instead.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/ellisonbg/altair/pull/103#issuecomment-220754501

--
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

When you say do this with encode, do you mean allowing things like:
X('foo', maxbins=10)

So more at the level of the channels than the top-level encode function. Doing this at the level of encode wouldn't work well because all of the channels have almost identical attributes.

were you going to add the mark_*(attr=value) stuff?  I forget where you had commented on that. Like the idea a lot.

Haven't started on that yet, but I agree we should do it. I can tackle it if you'd like – it shouldn't take too long.
As for this branch, I'll rebase, rename data_transform to transform_data, and then merge.

Great, feel free to tackle the mark_ stuff as well.
On Fri, May 20, 2016 at 8:28 PM, Jake Vanderplas<EMAIL_ADDRESS>wrote:

Merged #103 https://github.com/ellisonbg/altair/pull/103.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/ellisonbg/altair/pull/103#event-667848085

--
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

Mark stuff implemented in #104


Update spring boot version and azure spring boot version

Changemelog:

Update spring boot version to 2.4.5.
Update azure spring boot version to 3.5.0
Update maven-checkstyle-plugin version to 3.1.2.

Hi @selvasingh, I am updating this doc Spring with Cosmos on App Service, I saw that the last one commit was you, cloud you please review this  PR? or please help add @saragluna,  @backwind1233 as a code reviewer. Many thanks.

For this PR, I suggest only make change required, do not change the whole file or it's hard to tell what's changed


Flutter self signed certificate

Hi, tremulous team, you're just handsome, after flutter development on native platforms seems outdated. Flutter it's wonderful. In this regard, we want to transfer the current application to the flutter. We encountered a problem in the form of CERTIFICATE_VERIFY_FAILED when I connected to our servers (web_socket_channel) , I read similar problems, and the solution is to add a certificate to the application, but we have many servers and we can add new ones at any time, with  new certificate. Therefore, the solution DART_VM_OPTIONS = - root-certs-file = some_file pub get does not suit us.
At the moment, as a solution, I see the entry kotlin / swift (channels) and sends answers from the server in the application, but it looks like a crutch. Even if it helps now, it turns out that in the future our application will not be able to work in Fuchsia?
Please tell me how you can solve this problem in other ways?
P.S.sorry for my bad english

Is tis about the development environment, the mobile app, or both?

Is tis about the development environment, the mobile app, or both?

At the moment, only the development environment for mobile devices, but as soon as a stable version appears under the PC, then a PC will need some kind of solution.

but as soon as a stable version appears under the PC

You mean a desktop version when Fuchsia is released. So it's only about the application you are developing, not the development environment (flutter upgrade, flutter packages get, ...)

but as soon as a stable version appears under the PC

You mean a desktop version when Fuchsia is released. So it's only about the application you are developing, not the development environment (flutter upgrade, flutter packages get, ...)

Probably we did not understand each other, i mean i do that on mobile
IOWebSocketChannel ws = IOWebSocketChannel.connect('wss://myserver.com');     ws.stream.listen((data) {       print('data = $data');     });
and get an error
ERROR:flutter/shell/common/shell.cc(186)] Dart Error: Unhandled exception: E/flutter (24337): WebSocketChannelException: WebSocketChannelException: HandshakeException: Handshake error in client (OS Error:  E/flutter (24337): 	CERTIFICATE_VERIFY_FAILED: Hostname mismatch(handshake.cc:363))
The solution that is offered here #24586 does not help, since we have a lot of servers, and each has its own self-signed certificate.

Oh, sorry it's my fail!!! Very very sorry

That's because that's for the development tools, not for the created app.
I guess this is a duplicate of https://github.com/dart-lang/sdk/issues/34284

https://docs.flutter.io/flutter/dart-io/RawSecureSocket-class.html
https://docs.flutter.io/flutter/dart-io/SecurityContext/setTrustedCertificates.html might help

How did you fix that CERTIFICATE_VERIFY_FAILED with IOWebSocketChannel @1AlexFix1 ?
I want to know yet


UX: hub pull-request strips Markdown headers

I was creating a pull request for Ansible by running hub pull-request.  It downloaded Ansible's PULL_REQUEST_TEMPLATE.md very felpfully and spawned Vim for me.  I edited the PR description, which looked something like
##### ISSUE TYPE
 - Bugfix Pull Request

##### COMPONENT NAME
blah blah

##### ANSIBLE VERSION
ver ver

##### SUMMARY

bug bug bug

and then I quit vim and looked at the PR that hub created for me.
I discovered that hub had stripped off all the Markdown headers, resulting in a nonsensical-looking

Bugfix Pull Request

blah blah
ver ver
bug bug bug

This is rather unfriendly to projects that use the # header syntax in their .github/PULL_REQUEST_TEMPLATE.md.
(I was using hub version 2.3.0-pre4.)

This is known, but thank you for opening the issue because I feel this is something that I need to fix. The # character is the default comment character for various git messages, such as commit subject & body, but this default doesn't work as well with Markdown. Maybe hub pull-request and hub issue create should use a different default comment character.

@mislav I think changing the default git comment char may resolve this. It does not seem to work with an auto setting, however, it plays nicely with core.commentchar=-.

FWIW - is often used for Markdown lists, and it'd be a shame it hub stripped those.  ; sounds safer.

You may prefix - in lists with a space and it does not count as a comment then, but in general yes, ; is a better choice.

Another workaround is to use ==== and ---- underlining the headers, since that is also valid markdown for headers.
A First Level Header
====================

A Second Level Header
---------------------

I've seen some projects switch from ## in templates to ==== and ----- due to this, but not all.  E.g. the OP example of Ansible wants tiny level-5 headers to can't use -----.

hub could invoke git with different commentchar just for that command (to not mess with user settings otherwise)?
wait, git is not used to open PRs!  Does hub just emulate same behavior?  If so we fully control it?

emulating commentchar  auto could be nifty.
we could make the recognition stricter, recognizing a "comment string".  Requiring #  followed by space would avoid collisions with #123 references and ## and deeper headings.  Hub could also pre-fix # headings to ## headings, not perfect but than having them stripped.

https://stackoverflow.com/a/2788126/239657 says prepending a single space prevents git from stripping the chars.  Indeed that worked through hub, and GitHub still rendered it as header: https://github.com/cben/sandbox/pull/6 (also in worked in README.md).  http://spec.commonmark.org/0.27/#atx-headings says "The opening # character may be indented 0-3 spaces.", this is consistent with other constructs in markdown, so can be relied upon.
So another kludge hub could use to workaround this is prepend a space to every template line starting with commentchar.

@mislav I'll try to send a PR, if you choose desired behavior.

@cben commentchar=auto support is coming and there's no need to contribute anything there right now. However, auto support is not a definite solution to this problem. Supporting auto is definitely useful when there is a pull request template that has markdown headings, for instance, because a comment character such as ; would automatically be used instead of #, but in the absence of # characters in the initial PR message, you might be tempted to create a markdown heading yourself by typing one out, which wouldn't work.
I still think we should change the default comment character for these commands. The question, however, is whether we would break certain automations that people have set up using hub? 🤔

Speaking only for myself, the scripts that I have using hub don't involve manually editing the PR message, but rely on providing PR message on the command line with -m.

For anyone looking to copy and paste, before its fixed in the upcoming release
git config --global core.commentChar ";"

Could we just strip the last four lines of the PULL_REQUEST (if they all start with #) file rather than stripping out all lines that start with the # symbol?

There is also scissors cleanup mode.
Maybe it is a good fit to be used as default?

@anton-rudeshko That's an excellent idea. Instead of comments being stripped, everything below the cutoff line will be stripped. This will allow people to freely write Markdown in pull requests, issues, releases.
Any takers?

BTW, you also can bypass this little nuisance by prefixing your MD headers with one space:
.github/PULL_REQUEST_TEMPLATE.md:
-#### Template header
+ #### Template header

 _template text_

@mislav OK if I take a stab at this?

@mislav what was the solution here? Has it been fixed?

Thanks for the reminder @redreceipt! I've just opened a PR to fix this. :heart:

Looking at the code change here it seems like there's no longer any way to add comment lines to PR templates, is that correct?
We were relying on that feature to add notes and suggestions for the PR author in our templates which didn't render in the final description itself — the new scissor syntax doesn't let us do that, because our non-rendering comments are interspersed with visible lines.
Would you be open to adding a comment syntax (which doesn't interact accidentally with markdown) or making the scissors mode switchable?

GitHub issue/PR templates usually use <!-- commends --> to tell the submitter what to do.  Even if these aren't deleted by the submitter, they won't be visible in the rendered markdown.


Transformation query under step 6 does not produce expected results

Seems to be parsing issue here. However, the two queries that follow do work as expected

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

ID: ff27c536-d522-1480-f886-3d4d3d96b302
Version Independent ID: 332e8683-7525-edc9-52ad-3e858ac513c3
Content: Tutorial - Send custom logs to Azure Monitor Logs (preview) - Azure Monitor
Content Source: articles/azure-monitor/logs/tutorial-custom-logs.md
Service: azure-monitor
Sub-service: logs
GitHub Login: @guywi-ms
Microsoft Alias: guywild

Thanks for bringing this to our attention. We will investigate it further and update you shortly.

@iwafula025 Thanks for your dedication to our documentation! We've created a PR to incorporate your suggestions. We are closing this issue for now, but feel free to comment here as necessary. #please-close


frankenphp: add darwin support

Description of changes

Added Darwin support for Frankenphp

Added required flags as mentioned in https://github.com/dunglas/frankenphp/blob/main/docs/compile.md to php package

Disabled Zend Signals Support on Linux and Darwin as suggested in the docs
Enabled Zend max execution timers support for Linux (max_execution_time is so working)

Things done

Built on platform(s)

[ ] x86_64-linux
[X] aarch64-linux
[ ] x86_64-darwin
[X] aarch64-darwin

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

We can remove the sqlite3 substitute when https://github.com/dunglas/frankenphp/pull/331 is merged and released

Nice! I'll pass this time as I don't know much about Darwin stuff !

@GrahamcOfBorg build frankenphp

@shyim Could you please push/amend an empty commit to trigger again ofborg-eval ?

@gaelreyrol Good for you?

Awesome @shyim! Would you consider adding yourself as a maintainer too?

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

1 package built:

frankenphp

I added myself also as maintainer 👍

Congrats guys, very nice :)


Question about colcon-verylowmem.meta default settings

So I recently opened an issue about services not working with micro_ros_arduino. #1392
The problem was quickly solved by modifying the colcon-verylowmem.meta file in micro_ros_arduino library and rebuilding the library afterwards.
However, that got me thinking why is the DRMW_UXRCE_MAX_SERVICES set to 0 in that file. What is the reasoning behind initially setting the maximum services to 0? What benefits does it bring?
I would greatly appreciate if someone was able to give me a brief explanation to why it might be wise to limit maximum services if I'm not currently using them in my system.
Thank you.

DRMW_UXRCE_MAX_SERVICES is zero in verylowmem.meta to use less memory. User can tune it's meta to fit its requirements


Bring back use of cursor in s3 container

Follow up to https://github.com/graymeta/stow/pull/171/ where cursor was removed but shouldnt've been

retest this please