@types/vfile-message should be added as dependency

Subject of the issue
Getting this error from TS
node_modules/@types/vfile/index.d.ts:11:31 - error TS7016: Could not find a declaration file for module 'vfile-message'. '/Users/smashercosmo/Documents/projects/UmbraMarketingWebsite/node_modules/vfile-message/index.js' implicitly has an 'any' type.
  Try `npm install @types/vfile-message` if it exists or add a new declaration (.d.ts) file containing `declare module 'vfile-message';`

11 import * as vfileMessage from 'vfile-message';
                                 ~~~~~~~~~~~~~~~

Your environment
Packages<EMAIL_ADDRESS>Steps to reproduce
Just try to use package with typescript

nwm... some mess in dependencies

I encountered the same issue after a clean yarn install.
ERROR  ERROR in node_modules/@types/vfile/index.d.ts(11,31):            nuxt:typescript
11:31 Could not find a declaration file for module 'vfile-message'. 'node_modules/vfile-message/ind
ex.js' implicitly has an 'any' type.
  Try `npm install @types/vfile-message` if it exists or add a new declaration (.d.ts) file containing `declare module 'vfile-message';`
     9 |
    10 | import * as Unist from 'unist';
  > 11 | import * as vfileMessage from 'vfile-message';
       |                               ^
    12 |
    13 | declare namespace vfile {
    14 |     type VFileContents = string | Buffer;

yarn why vfile-messsage returns
info Reasons this module exists
   - "stylelint#postcss-markdown#remark#unified#vfile" depends on it
   - Hoisted from "stylelint#postcss-markdown#remark#unified#vfile#vfile-message"

@smashercosmo How did you solve the problem?

nvm, https://github.com/gucong3000/postcss-markdown/issues/32


[FEAT] Improve user

[x] Check email for register
[x] OTP 2FA
[x] Rate limiting
[x] Invite user when register is disabled
[ ] Login brut force
[ ] Session management

https://github.com/aquatracking/server/issues/23#issuecomment-1987280930


validate fails with commit hash

With the example file repos.test :
repositories:
  vcs:
    type: git
    url: https://github.com/dirk-thomas/vcstool.git
    version: daf389377310f7f31b2171f51a79af82c31bf3e2

The validate command fails
$ vcs validate --input repos.test
=== vcs (git) ===
Invocation of command 'validate' on client 'git' failed: UnboundLocalError: cannot access local variable 'version_type' where it is not associated with a value (/usr/lib/python3/dist-packages/vcstool/clients/git.py:744)

While a clone works just fine
$ vcs import --input repos.test test/
=== test/vcs (git) ===
Clonage dans '.'...
Note : basculement sur 'daf389377310f7f31b2171f51a79af82c31bf3e2'.

Note that the validate works with tags if the commit hash is changed by 0.3.0
$ vcs validate --input repos.test
=== vcs (git) ===
Found git repository 'https://github.com/dirk-thomas/vcstool.git' with tag '0.3.0'

#239 might fix this. Can you try it out? You should be able to install the version from that PR like this:
pip3 install git+https://github.com/furushchev/vcstool@fix-validate-git-hash

#239 might fix this. Can you try it out? You should be able to install the version from that PR like this:
pip3 install git+https://github.com/furushchev/vcstool@fix-validate-git-hash

Yes it works thank you. Any plan to merge this soon?

I don't know. vcstool is in no/low maintenance mode (see #242), so I don't know when that will get merged.

This was solved in vcstool2, my fork of vcs :


Web interface should use protobuf interface and not depend on rasctl

Instead of relying on rascsl (output format and command syntax) the web interface should directly use the protobuf interface. A code generator for protobuf is available for Python, see https://developers.google.com/protocol-buffers/docs/pythontutorial.

@rdmark I'd suggest to generate it on the fly, similar to how it is done for the generated C++ code.

@rdmark You have to write the serialized string to a socket and receive the result from the same socket. First the header (see the comment in rascsi_protobuf.proto), then the actual data.
See SendCommand() in rasctl.cpp and the code in protobuf_util.cpp for the equvialent code in C++.

I got it to work at a basic level!  WIP feature branch here https://github.com/rdmark/RASCSI/tree/feature_webapp_protobuf

All commands have been reimplemented using protobuf now, and functionality seems unchanged from before.
I've also added some error handling for sockets and protobuf response.
Currently trying to figure out how to capture the response correctly. When deserializing the response I don't seem to get the object that I expect, e.g. PbResult.

I was able to capture and parse the responses properly now, and implemented the get_type() method with protobufs.
What's left to do is implement the list_device() method, and we should be entirely independent of rasctl for the web ui!
Also need to improve error handling, show correct result messages in the UI, and do a ton of cleanup.

@uweseimet @akuker @erichelgeson Please review this PR draft. https://github.com/akuker/RASCSI/pull/229
The behavior of the webapp should be generally unchanged, with some minor differences in device names displayed.


[Question]: Support for Preprocessor Symbols in AL-GO Workflows for NextMinor/NextMajor Builds

Question
Does the current AL-GO workflow support producing NextMinor and NextMajor artifacts built from the main branch with specific preprocessor symbols for each release? For instance, we’d like to trigger conditional code blocks specific to these builds only and publish those as separate artifacts.
#if NEXTMAJOR
Message('Hello NEXTMAJOR feature!')
#endif

We aim to include conditional logic in the main branch that is only activated for NextMinor or NextMajor builds using preprocessor symbols like NEXTMAJOR, NEXTMINOR, CLEAN25, CLEAN26, etc.

Hi @freddydk, appreciate your insights on this.
I was hoping that also Test Next Major.settings.json file would support a property for preprocessorSymbols to support this such as:
"preprocessorSymbols": [
        "NEXTMAJOR"
    ]

@mazhelez  - can they use BuildModes for this?
Or is cleanModePreprocessorSymbols hardcoded for buildmode = cleanMode only?

cleanModePreprocessorSymbols setting is currently only used in the "clean" build mode.
But artifacts are not output for the different build modes, but the default one.

@mazhelez @freddydk What's the best way to approach this? We used PreprocessorSymbols in our custom Azure DevOps CICD to build different versions from the same codebase and MSFT uses it in the base app as well:

I guess the request here is:

Add the ability to define preprocessorsymbols when running Test NextMajor, Test NextMinor and Test Current workflows.
Produce build artifacts in these workflows (like CI/CD)

Is this what you are looking for?

@freddydk - Correct, that will work!

Is this something we will be able to follow on the Roadmap?
I interested in the timeline, if and when will this be available.

I added an item to the roadmap this morning, merging this and a few other requests
Sendt fra Outlook til iOShttps://aka.ms/o0ukef

Fra: Ivan Đorđević @.>
Sendt: Thursday, December 19, 2024 10:30:39 AM
Til: microsoft/AL-Go @.>
Cc: Freddy Kristiansen @.>; Mention @.>
Emne: Re: [microsoft/AL-Go] [Question]: Support for Preprocessor Symbols in AL-GO Workflows for NextMinor/NextMajor Builds (Issue #1358)
Is this something we will be able to follow on the Roadmaphttps://aka.ms/ALGoRoadmap?
I interested in the timeline, if and when will this be available.
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/AL-Go/issues/1358#issuecomment-2553186332, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACSGUA2ASPUILLBATYENL3D2GKG37AVCNFSM6AAAAABTQBXCJWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJTGE4DMMZTGI.
You are receiving this because you were mentioned.Message ID: @.***>

Can you share the card so we can follow?

https://github.com/orgs/microsoft/projects/521/views/1?pane=issue&itemId=91449371 - a little strange heading, but this is because this workitem will solve some other issues as well (together with this problem)

See https://github.com/microsoft/AL-Go/pull/1374
If you want to try out an implementation of this, you can run Update AL-Go System Files with freddydk/AL-Go@thisbuild on a test repository and see whether this works as expected.


remove sphinx build action for now

... since it requires a CI/CD environment w/ all dependencies, and since it's just causing noise at the moment.

Looks good!


Add test for check_overwrite() function in debug_tokenize_test.py.

Missing test coverage in debug_tokenize_test.py for function check_overwrite().

Closed with PR #50


FR: Add commitlint, husky and commitizen

The use of standard-version is tightly coupled to the use of conventional-changelog-angular, and the use of these libraries has become a de facto standard to enforce correct use. It would be nice to allow the installation and configuration of these libraries, even if it is optional.

commitlint: check commit messages to follow the conventional commit pattern
husky: hook into git events and run code at specific points
commitizen: helper for writing conventional commit messages

I'm now testing the setup of these libraries with semver to ensure that all works well together.
The project ngx-semantic-version is doing something similar, but focused in Angular apps.

Hey, thanks for the issue, it's a great suggestion!
We can re-use some work done in ngx-semantic-version to set up the dependencies, unfortunately, because this package is not publicly exporting these functions, we have to copy the code.

I'm now testing the setup of these libraries with semver to ensure that all works well together.

Let me know if you face any issues here.
As we are currently focusing on another feature with semver, we won't take this quickly, but if you want to pick it up I would help you.

Hello. Thank you for accepting this feature request.
At the moment everything seems to be working as expected. Now I am finishing a small test project. I finish it, upload it and we see the minimum configuration.

@RicardoJBarrios any update on this?

Hello.
Yes, sorry, I've been testing it locally and is configured and working in https://github.com/RicardoJBarrios/fgc. I've found no issues, and all works together with the config in this project, that's basically the default one.

@edbzn , I'm not experienced with nx plugins, but I'll try to add this config and create a pull request.

Closed by #203


Add an annotations to inject the API key into the action context.

See https://github.com/apache/incubator-openwhisk/issues/4226. Note that this is a breaking change - actions that are deployed need to be updated to add this annotation.
Description

Related issue and scope

[x] I opened an issue to propose and discuss this change (#4226).

My changes affect the following components

[ ] API
[ ] Controller
[ ] Message Bus (e.g., Kafka)
[ ] Loadbalancer
[x] Invoker
[ ] Intrinsic actions (e.g., sequences, conductors)
[ ] Data stores (e.g., CouchDB)
[ ] Tests
[ ] Deployment
[ ] CLI
[ ] General tooling
[x] Documentation

Types of changes

[ ] Bug fix (generally a non-breaking change which closes an issue).
[ ] Enhancement or new feature (adds new functionality).
[x] Breaking change (a bug fix or enhancement which changes existing behavior).

Checklist:

[x] I signed an Apache CLA.
[x] I reviewed the style guides and followed the recommendations (Travis CI will check :).
[x] I added tests to cover my changes.
[ ] My changes require further changes to the documentation.
[x] I updated the documentation where necessary.

I know there are actions we're deploying that will need to be updated, waiting for travis to tell me which ones.

I will need to update a few API tests which check the API response and now are missing the new annotation.

Codecov Report

Merging #4284 into master will increase coverage by 21.28%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##           master    #4284       +/-   ##
===========================================
+ Coverage   59.79%   81.07%   +21.28%
===========================================
  Files         163      163
  Lines        7594     7605       +11
  Branches      502      507        +5
===========================================
+ Hits         4541     6166     +1625
+ Misses       3053     1439     -1614

Impacted Files
Coverage Δ

...org/apache/openwhisk/core/controller/Actions.scala
93.33% <100%> (+12.35%)
:arrow_up:

...org/apache/openwhisk/core/entity/WhiskAction.scala
86.9% <100%> (+9.19%)
:arrow_up:

.../openwhisk/core/containerpool/ContainerProxy.scala
92.03% <100%> (+6.48%)
:arrow_up:

.../apache/openwhisk/core/controller/WebActions.scala
92.33% <100%> (+19.57%)
:arrow_up:

...a/org/apache/openwhisk/core/entity/Parameter.scala
95.45% <100%> (+2.27%)
:arrow_up:

...whisk/connector/kafka/KafkaConsumerConnector.scala
61.19% <0%> (+1.49%)
:arrow_up:

.../org/apache/openwhisk/core/entity/EntityPath.scala
100% <0%> (+1.88%)
:arrow_up:

.../org/apache/openwhisk/http/PoolingRestClient.scala
90% <0%> (+3.33%)
:arrow_up:

...hisk/core/controller/actions/SequenceActions.scala
92.1% <0%> (+3.5%)
:arrow_up:

... and 100 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 619c86d...b5daa48. Read the comment docs.


Use Data Studio for Reporting

Data Studio can prepare some very cool looking reports & charts, and it can also use Cloud SQL as a datasource.  So, we should see if we can use it to visualize things like how much inventory has been collected, how many violations have been found, and how many things have been enforced.
Also see if the basic reports can be given to users.

is this solution possible now ?


feat: support jsonrpc 0.2.1

These changes add support for the jsonrpc 0.2.1 spec for issue 244.

Tried to remove use of untagged where possible. Not sure if there is a way to avoid using .clone() in the add transaction methods? I added it because initialising the enum there to add the tag takes ownership of the method param.

FYI, this patch is needed to use the json rpc provider with infura. Any way I can help to get this merged?

@fracek ima get it done tmr

Removed the tests for add_deployTransaction because StarkNet v0.10.3 removes the deploy transaction and was deployed to goerli yesterday. Also removed tests for adding version 0 transactions because they are deprecated on the docs.

Superseded by #255.


Add Support for .NET Core 2.0 and Standard 2.0

Hi Samuel,
I am in the process of converting a project to .NET core so that I can run it cross platform and as a docker container. The only nuget that does not support .NET core is MimeTypeMap, so I have gone a head and converted it, in this pull request.
This solves issue #53.
It does not create a different solution and/or project file, because that is not necessary anymore.
I have attached an updated Nuget file, if you don't have a current environment to create one.
MimeTypeMap.1.0.3.zip
Let me know if you have any questions or are looking for help maintaing this repo?
Thank you,
Jack

Jack,
Thanks for putting this together in a pull request. Merged!
I'll look into uploading the latest to NuGet now.
Sam

Thank you!

Oh, I forgot to mention you will need to unzip the nuget before uploading it. Github did not allow a .nupkg to be uploaded.
Let me know if you are having any issues.


Implement metadata mechanism: code preview, thread id, file attachments, etc

It would be better if the reporter could show how the test code looks like instead of showing Code preview is not available:

Suggested solution

Provide IPC communication between the environment context and the reporter.
Provide an optional hook for Jest environments:

based on #handleTestEvent(), attaches metadata to DescribeBlock and TestBlock: test code, start time, end time, etc.
attaches metadata about WORKER_ID used for specific test file

Finish implementation of MetadataService to extract the metadata described above and use it for the reports.
Bonus: Provide an API for external users: attach files (Allure attachments) to the report, etc. It will unblock #2337.

The work is happening in https://github.com/wix-incubator/jest-extend-report repo meanwhile. It will be used then as a dependency to extend jest reports with metadata available only from Circus environment.

Heads up for the people following the issue – the work is ongoing and already halfway.  👷♂

Update: there's a beta release of jest-metadata already, so hopefully soon I'll be able to integrate with it.

@noomorph but why are you waiting for jest-metadata? Everything is already implemented in the allure-js-commons module. The request was mostly about getting access to all allure metadata how it was implemented here https://github.com/zaqqaz/jest-allure
Because without it allure reporter looks useless.

@Gorodb I have a certain technical vision around this project, and nothing among existing alternatives can satisfy my needs. I am aware of your fork, yet I view the decision to use those "commons" as a dead end. That approach with the environment augmentation and JSDoc pragma parsing they use is too opinionated and one-sided.
jest-metadata will definitely see the public release within the next two months or sooner. I have big plans on it even beyond the context of this particular project.

The work is in progress. 🏃  Since I work on this project only one day in a week, it might take 2-3 weeks to finish it, but I have a cautious optimism that the feature will land in mid- or end-June.
The new version will be most likely 2.x, and I'll start dogfooding in a few projects I work with.

The alpha release is ready for trying out (under 2.0.0-alpha.2).
It lacks JSDoc annotation support and, overall, might be moderately buggy (especially around the dynamic allure.* API), but courageous users can try it.
I've started dogfooding the release here in Detox: https://github.com/wix/Detox/pull/4211
Please note that the website might be "hallucinating" about certain features and APIs (some are yet to be implemented, and some are because I wrote docs before implementing). Consult with the roadmap at the top of this issue page to see where we're at).
Website: https://wix-incubator.github.io/jest-allure2-reporter/

I guess this issue stays open for too long, whereas the state of the project is a solid beta+.
The docs still need some love, but I'll create that as a separate issue now.
On the tags and branches side, we exited beta.


Inject Func<Owned> parameters

This enables classes to choose when and how many times to get a reference to a dependency and when to release a dependency while being perfectly agnostic about the lifespan of the dependency before and after this (singleton, transient, pooled, etc).
It also enables a class A to obtain dependency B which causes dependency C to be created. Dependency B knows about dependency C, but class A does not know about dependency C and cannot properly release or dispose it when it is finished using dependency B. Dependency B also can't assume that it owns and should dispose dependency C when it is itself disposed. The solution is to inject Func<Owned<B>> into A instead of Func<B>.
A comparable feature is Castle Windsor's Typed Factories feature where Windsor auto-implements an IFactory interface that you declare yourself and register as a typed factory. The T IFactory<T>.Resolve() call is logically equivalent to T Func<Owned<T>>.Invoke() and the void IFactory<T>.Release(T) call is logically equivalent to void Owned<T>.Dispose().
I don't really have an opinion on whether injecting bare Owned<T> should be supported, rather than injecting a delegate with Owned<T> as the return type.

Sounds great!
The way I would recommend this be implemented is that an Owned<T> creates it's own scope, exactly like a Func<T>, but unlike a Func<T> the disposeAction is not stored for later, but given as one of the parameters to the Owned<T>.
I think this should be fairly straightforward conceptually, but there'll be lots of places which will need changing in the code.


Clarification

I just logged into the hera account and noticed that the number in this code is different from what I use (I use -512- compared to -256-). Is this outdated or is this based on user account? If it's user specific we can add a note to clarify.
https://github.com/MOshima-PIFSC/NSASS-HTC-HPC-Computing/blob/56b322d4feec04d71bedaf66e09dd6c5f1bf589f/assets/hera_documentation.qmd#L19
Also for clarity, what does the -p22 flag do? I don't usually add it when I log in.

To answer your first question, 512 vs. 256 this is just a difference in the encryption algorithm used to open the ssh connection. The flag -p22 species opening "port 22" and may be optional.

I guess the encryption algorithm is flexible since either one appears to work. However, I'm not sure it is tied to when you generated the ssh key for RDHPCS.


Rework Label Input

[x] tweak for mobile
[x] tweak input

[x] play with font
[x] make it more inputty when unfocused

Addressing some of script racoons feedback.
Make label more prominent with icon and font size increment.
When in focus, input floats and gets as much space as its needs.
$

@SarcevicAntonio why the change in font when focused? It seems a bit abrupt. I would probably keep the same font in both status.
Also what do you think of making the input more "inputty" even in unfocused mode so that more people will understand it's an input?

I change the font because of how the input sizing works it only works very good on monospace fonts, but they do take more space, so this is the best compromise i tired so far.
I can try adding other fonts that work for both? :shrug:
Will make it more inputty o7

I change the font because of how the input sizing works it only works very good on monospace fonts, but they do take more space, so this is the best compromise i tired so far. I can try adding other fonts that work for both? 🤷
Will make it more inputty o7

What if we use monospace for both and maybe keep the font size a bit smaller?

I will maybe rework it again when adding the menu bar. For now this has to do 😅


[WIP] Add Sphinx build of API docs

General setup for Sphinx build - config, style, etc.
A few regular scons files are updated to address build errors/warnings.
TODO:

[ ] integrate the Makefile steps into scons' own scripts - Can punt on this for the initial checkin.  Just update the https://github.com/SCons/scons/wiki/SimplifiedReleaseProcedure and file an enhancement so we don't lose this.
[x] epydoc did not present Tool modules, should we? - No. we didn't previously.
[x] decide whether to document private and/or special methods - No.
[x ] decide path where built docs should end up - build/doc/API
[ ] document doc building - Add to : https://github.com/SCons/scons/wiki/SimplifiedReleaseProcedure
[ ] pick/document docstring conventions

Specific errors:

[ ] modules containing ++ in filename cause errors (and, indeed, syntactically this is not legal in Python). SCons has a remapping mechanism, but it's not quite that simple. aixc++, c++, g++, hpc++, sgic++, sunc++
[x] index.rst:9: WARNING: toctree contains reference to nonexisting document 'SCons.Tool.packaging.'
[ ] WARNING: autodoc: failed to determine Null(0x7F706BF19210) to be documented.the following exception was raised: cannot unpack non-iterable Null object (SCons' Null is a hack - no checkers like it either)

Fixes #3604 #3121
Signed-off-by: Mats Wichmann<EMAIL_ADDRESS>Contributor Checklist:

[ ] I have created a new test or updated the unit tests to cover the new/changed functionality.
[ ] I have updated src/CHANGES.txt (and read the README.txt in that directory)
[x] I have updated the appropriate documentation

Re: docstring style. Didn't we discuss using Googles style?

RE: "++" modules, can we get Sphinx to ignore them?

RE: "++" modules, can we get Sphinx to ignore them?

in a way... by not looking deeper in Tools, they do get ignored, but I can't call them out by name to be ignored for the same reason they cause trouble if processed.

Re: docstring style. Didn't we discuss using Googles style?

Yes, and that's what I've been using recently.

I think if you add a blurb to the wiki page and assuming I can just do make somearg I'd be ready to merge this one.


Refactor colors to reflect styleguide

Overview

Updated colors and names in UIColor+Shared to match the style guide, update color/font use, and update shadows throughout to match final screen designs on Figma.
Changes Made

Biggest changes in:

UIColor+Shared.swift and replacing usages throughout app
Histogram.swift
ClassList calendar header
FilterViewController.swift
a lot of little font changes and styling to match designs better

Test Coverage

Verified visually that app matches designs.
Related PRs or Issues

Addressed: #181, #143
Screenshots

New Histogram

Updated Classes Page

 Empty state fix

iPhone 8
iPhone 6s

Just a small concern on the names gray01-gray05

Used these color names specifically to match the color names that design used in the style guide to make it a lot easier to figure out what color to make things


Project with path ':bugsnag_react-native' could not be found in project ':app'.

ok
Describe the bug
I am trying to upgrade my gradle to 7.x but i keep getting this error. I tried to search the entire project but there is no mention of a bugsnag_react-native.
Caused by: org.gradle.api.UnknownProjectException: Project with path ':bugsnag_react-native' could not be found in project ':app'.
Tried

delete / re-install node modules
Invalidate cache and restart on android studio

Steps to reproduce
Just try to sync in android studio
Environment

Bugsnag version: "@bugsnag/react-native": "^7.11.0",
"@bugsnag/react-native-cli": "^7.10.5",
"react-native": "0.63.3",

Hi @enigmablue
Can you upgrade to the latest @bugsnag/react-native and confirm whether you still see the issue as we've shipped a number of fixes since the version you're using:
https://github.com/bugsnag/bugsnag-js/releases
Also, if your node_modules is in a non-standard location you'll need to specify that in your app's build.gradle:
https://docs.bugsnag.com/build-integrations/gradle/#custom-node_modules-directory
If you're still seeing issues then it would be useful if you could share further details of your project including your build.gradle so we can try and reproduce. Feel free to email<EMAIL_ADDRESS>if you'd rather not share these publicly.
Thanks!

Closing as we haven't had a response, but we'd be happy to investigate further if you can confirm this affects the latest version and share the other details which would help us try to reproduce the issue.


GitHub auth doesn't report a useful error message with no public email

If a GitHub account has no public email address associated with it, then GitHub registration gives a confusing "Field is required" error message.
I think we should do one of these 2 things:
(1) See if we should be asking for additional permissions from GitHub Oauth that include a private email.
(2) Give a better error message explaining the user needs to set a public email
@umairwaheed can you look into this one?

Sure. @zulipbot claim.


V2 : WEB enhance help

These changes update the help for the WEB UI.

correcting links to online documentation and forums
adding multiple language support for help

All Submissions:

[X] Have you followed the guidelines in our Contributing document?
[X] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[X] Does your submission pass tests?

@SimonClark please take a look.
If you happen to know French or German then I can add some additional translations for ‘help’. :)

If you happen to know French or German then I can add some additional translations for ‘help’. :)

:) I am not the person to do that.  I might be able to reach out to some folks, if getting those languages done is important.


chore: use ooni/probe-cli v3.16.6

I don't fully understand why the CI is failing here 🤷
Here's the full log:

jest -c test/lib/integration.config.js --testRegex 'e2e.js' --runInBand
PASS test/onboarding.e2e.js (29.971 s)
  Onboarding Story 1
    ✓ App is running (132 ms)
    ✓ App launches with correct title (92 ms)
    ✓ First screen renders correctly (141 ms)
    ✓ App goes to the second screen (292 ms)
    ✓ App loads up Pop Quiz (275 ms)
    ✓ App accepts first Pop Quiz Answer (1644 ms)
    ✓ App accepts second Pop Quiz Answer and goes to Crash Reporting page (1673 ms)
    ✓ App lets user opt-in for Crash Reporting (214 ms)
    ✓ Finishing Onboarding process brings up the Dashboard (307 ms)
    ✓ Check if Crash Reporting is enabled in Settings (295 ms)
  Onboarding Story 2
    ✓ App plays cross animation and shows warning if first pop quiz answer is wrong (4853 ms)
    ✓ App plays cross animation and shows warning if second pop quiz answer is wrong (1811 ms)
    ✓ App lets user opt out of Crash Reporting (250 ms)
    ✓ Finishing Onboarding process brings up the Dashboard (292 ms)
    ✓ Check if Crash Reporting is disabled in Settings (304 ms)
PASS test/sidebar.e2e.js
Sidebar Works
✓ has window title set to "OONI Probe" (3495 ms)
PASS test/dashboard.e2e.js (5.361 s)
Dashboard tests
✓ Run button is displayed on Dashboard (101 ms)
✓ Clicking on "Test Results" tab loads the Test Results Page (284 ms)
✓ Clicking on "Settings" tab loads the Settings page (309 ms)
All 5 test cards are visible
✓ websites test card is visible (144 ms)
✓ im test card is visible (138 ms)
✓ circumvention test card is visible (129 ms)
✓ performance test card is visible (135 ms)
✓ middlebox test card is visible (130 ms)
PASS test/localization.e2e.js (7.518 s)
Localized version is displayed for supported languages
✓ Check if the app shows content in French (104 ms)
Unsupported language (Malayalam) falls back to English
✓ Run button label in English (97 ms)
PASS test/settings.e2e.js (7.139 s)
Tests for Settings page
✓ Clicking on "Settings" tab loads it up correctly (312 ms)
✓ Language changes to Spanish (374 ms)
✓ Language changes in other screens (497 ms)
✓ Changing language back to En (373 ms)
✓ Clicking on button to edit Website categories brings up modal (234 ms)
✓ Modal Deselect All buttons work as expected (235 ms)
✓ Modal Select All buttons work as expected (329 ms)
✓ Individual categories can be enabled or disabled (788 ms)
PASS test/runtest-individual.e2e.js (242.898 s)
IM test
✓ IM test successfully starts (500 ms)
✓ IM test runs with all 4 network tests (5762 ms)
✓ Loads Test Results page on completion (815 ms)
Websites test
✓ Website measurement test loads correctly (392 ms)
✓ Website network runs successfully (4055 ms)
✓ Loads Test Results page on completion (89967 ms)
Custom websites test
✓ Run button is disabled by default (282 ms)
✓ Allows entering custom URLs (411 ms)
✓ Runs the custom websites test (220 ms)
✓ Tests custom URLs (3054 ms)
✓ Loads Test Results page on completion (844 ms)
Circumvention test
✓ Circumvention test successfully starts (434 ms)
✓ Circumvention test runs with all 3 network tests (10191 ms)
✓ Loads Test Results page on completion (31968 ms)
Performance test
✓ Performance test successfully starts (452 ms)
✓ Performance test performs both network tests (3181 ms)
✓ Loads Test Results page on completion (20892 ms)
Middleboxes test
✓ Middleboxes test successfully starts (430 ms)
✓ Middleboxes test performs both network tests (2143 ms)
✓ Loads Test Results page on completion (5509 ms)
Experimental test
✓ Experimental test successfully starts (488 ms)
✓ Experimental test performs some tests (164 ms)
✓ Loads Test Results page on completion (36173 ms)
FAIL test/runtest-all.e2e.js (237.019 s)
All network tests run successfully
✓ Tests start successfully on click of RUN button (369 ms)
✓ Website test runs from start to finish (95847 ms)
✓ Circumvention test runs from start to finish (39883 ms)
✓ IM test runs from start to finish (5955 ms)
✕ Middleboxes test runs from start to finish (30687 ms)
✕ Performance test runs from start to finish (30090 ms)
✕ Experimental test runs from start to finish (30100 ms)
● All network tests run successfully › Middleboxes test runs from start to finish
waitUntilTextExists waitUntil condition timed out after 30000ms

  at node_modules/webdriverio/build/commands/browser/waitUntil.js:24:19
  at Browser.wrapCommandFn (node_modules/@wdio/utils/build/shim.js:63:29)
  at Browser.waitUntilTextExists (node_modules/@wdio/utils/build/shim.js:63:29)

● All network tests run successfully › Performance test runs from start to finish
waitUntilTextExists waitUntil condition timed out after 30000ms

  at node_modules/webdriverio/build/commands/browser/waitUntil.js:24:19
  at Browser.wrapCommandFn (node_modules/@wdio/utils/build/shim.js:63:29)
  at Browser.waitUntilTextExists (node_modules/@wdio/utils/build/shim.js:63:29)

● All network tests run successfully › Experimental test runs from start to finish
waitUntilTextExists waitUntil condition timed out after 30000ms

  at node_modules/webdriverio/build/commands/browser/waitUntil.js:24:19
  at Browser.wrapCommandFn (node_modules/@wdio/utils/build/shim.js:63:29)
  at Browser.waitUntilTextExists (node_modules/@wdio/utils/build/shim.js:63:29)

PASS test/test-results.e2e.js (19.355 s)
Tests for Test-Results screen
✓ Page shows two IM measurement result rows (90 ms)
✓ Page shows three Websites measurement result rows (96 ms)
✓ Page shows two Circumvention test result rows (85 ms)
✓ Page shows two Middleboxes test result rows (84 ms)
✓ Page shows two Performance test result rows (146 ms)
IM test measurements
✓ There are total 4 IM measurements (208 ms)
✓ Result rows displayed for all 4 tests (131 ms)
✓ Detailed Measurements load up correctly (241 ms)
✓ Explorer button is displayed with correct link (1471 ms)
✓ Methodology link is correctly displayed (89 ms)
✓ Data button loads up raw data (278 ms)
Website test measurements
✓ There is at least one URL row (307 ms)
✓ Detailed Measurements load up correctly (268 ms)
✓ Explorer button is displayed with correct link (1258 ms)
✓ Methodology link is correctly displayed (91 ms)
✓ Data button loads up raw data (209 ms)
Circumvention test measurements
✓ There are total 2 Circumvention measurements (130 ms)
✓ Result rows displayed for all 3 tests (97 ms)
✓ Detailed Measurements load up correctly (233 ms)
✓ Explorer button is displayed with correct link (1331 ms)
✓ Methodology link is correctly displayed (134 ms)
✓ Data button loads up raw data (329 ms)
Performance test measurements
✓ There are total 2 Performance measurements (191 ms)
✓ Result rows displayed for all 2 tests (100 ms)
✓ Detailed Measurements load up correctly (385 ms)
✓ Explorer button is displayed with correct link (1125 ms)
✓ Methodology link is correctly displayed (111 ms)
✓ Data button loads up raw data (248 ms)
Middleboxes test measurements
✓ There are total 2 Middlebox measurements (188 ms)
✓ Result rows displayed for all 2 tests (100 ms)
✓ Detailed Measurements load up correctly (286 ms)
✓ Explorer button is displayed with correct link (855 ms)
✓ Methodology link is correctly displayed (85 ms)
✓ Data button loads up raw data (244 ms)
Experimental test measurements
✓ There is at least one Experimental measurements (251 ms)
✓ Detailed Measurements load up correctly (2225 ms)
Test Suites: 1 failed, 7 passed, 8 total
Tests:       3 failed, 97 passed, 100 total
Snapshots:   0 total
Time:        553.361 s
Ran all test suites.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
/bin/bash /home/runner/work/_actions/GabrielBB/xvfb-action/v1.0/cleanup.sh
No xvfb processes to kill
Error: The process '/usr/bin/xvfb-run' failed with exit code 1
</pre></details>


TypeError: the JSON object must be str, not 'bytes'

Unsure what's going on here or how to fix it.
python C:\view\twitch-viewer.py test
Obtaining the channel...
Obtained the channel
Preparing the processes...
Traceback (most recent call last):
  File "C:\view\twitch-viewer.py", line 112, in <module>
    prepare_processes()
  File "C:\view\twitch-viewer.py", line 100, in prepare_processes
    "url": get_url(), "proxy": {
  File "C:\view\twitch-viewer.py", line 64, in get_url
    url = json.loads(response)['streams']['audio']['url']
  File "C:\Users\Me\AppData\Local\Programs\Python\Python35\lib\json\__init__.py", line 312, in loads
    s.__class__.__name__))
TypeError: the JSON object must be str, not 'bytes'

Had to download a previous version of python to get it to work. Won't work in 3.


Are there maintainers?

Hi - is this still maintained?

Hi @moofish32
Sorry for our late reply and not updating some features.
Yes, we maintain this library.
We have some new features, and will update within days.

Let me close this issue, thank you.


Fix "method_lines" issue in src/features/discord/messages/services/discord-message-service.ts

Function _sendMessage has 28 lines of code (exceeds 25 allowed). Consider refactoring.
https://codeclimate.com/github/Sonia-corporation/il-est-midi-discord/src/features/discord/messages/services/discord-message-service.ts#issue_5e81d19476162700010000bb

Too old.


create csvs for downloaded mailarchives

Hi all,
To be able to import downloaded mailingists, one needs to create pandas dataframe (csv) from mailarchives. This is exactly what this script does, and does so in utf-8, so this will hopefully be a workaround for the chardet/unicode issue #304  .

Seems to me that Niels has found a pressing use case for this script and so we should include this functionality.
I agree with Nick that the bin directory is the right place for this.
Also, this hard-codes the directory of the archives directory, which we know causes a bunch of problems (#113, #117, etc...)
I think it would be best if the default archive directory from the configuration file were used (see #309) with an optional command line override.

This was fixed with new changes in mailman.py and collect_mail.py, better to keep it there instead of adding smth new.


Presenting form on startup will crash with [UIApplication _runWithMainScene:transitionContext:completion:]

If we present a view on startup, on iOS9 the app crashes because MZFormSheetBackgroundWindow does not have a rootViewController.

I fixed this issue and create a PR #186


More checks (changelogCheck, systemlogCheck, thumbnailConfigCheck), and a bit of cleanup.

Requested changes done.


:sparkles: Kafka2 middleware support

 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: devkanro:x: zhaozhao 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.


update error info

Codecov Report

Merging #16 into release-rc2 will decrease coverage by 0.42%.
The diff coverage is 41.66%.

@@                Coverage Diff                @@
##             release-rc2      #16      +/-   ##
=================================================
- Coverage          70.27%   69.85%   -0.43%
+ Complexity           157      156       -1
=================================================
  Files                 21       21
  Lines               1258     1267       +9
  Branches              86       87       +1
=================================================
+ Hits                 884      885       +1
- Misses               304      311       +7
- Partials              70       71       +1

Impacted Files
Coverage Δ
Complexity Δ

...wecross/stub/fabric/EndorsementPolicyAnalyzer.java
51.21% <41.66%> (-8.16%)
7.00 <1.00> (ø)

...va/com/webank/wecross/stub/fabric/FabricBlock.java
77.90% <0.00%> (-1.17%)
9.00% <0.00%> (-1.00%)

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 48c7b02...c02665d. Read the comment docs.


Using this project in other projects

Hi
Is there any way to use this project in other spring projects without copy & pasting the source? Like maven dependencies? or if you know similar project?
Thank you

Hi @sparse91, sorry for the late answer. Currently it is not available as a dependency, and it is unlikely I will implement that. I am not aware of similar projects, but feel free to contribute. :)
Regards, Gabor


Windows 10 Pro

Hi Team,
I have access to single rdp connection how can I enable multiple concurrent rdp connections ?
I tried increasing limits in group policy but it doesn't work
following are my Build details
Edition: Windows 10 Pro
Version: 20H2
OS Build: 19042.867
Regards,
Mangala-A

I tried to use the last release of rdpwrap on "Windows 10 pro" and the message it's  "not supported"

Hi,
Can I know what is the stable rdpwrap version we have and which windows build does it support ?
Thanks.

I found a solution, this pull request work perfect!!!!
https://github.com/stascorp/rdpwrap/pull/1160

Applicable to https://github.com/stascorp/rdpwrap/issues/1317


how to setup spark_home into spark_lyr

Reporting an Issue with sparklyr
I am trying to connect to a cluster via spark_lyr. How can I connect it? Which files do I need to modify?

@sebastien1981 you need to set the right Sys.setenv(SPARK_HOME = "<path-to-clusters-spark-home>"). This is something that your cluster admin would know, it is assumed that the machine you are using is already inside the cluster for this to function properly. Most users install RStudio Server in a cluster machine and RStudio from that URL.

Thanks you. Can you tell me on which file I need to set it up? I am trying to set it up into rocker/rstudio.


List compression status of file

Hello,
Is it possible to make the tool list the compression status of a CZI file? We would like to scan our local storage in search of uncompressed files.
Thanks!!

Hi @diego-rt, thanks for your interest in our CZI tools. Strictly speaking, a CZI file does not necessarily have a single compression status. The pixel data in a CZI file is organized into units called subblocks and each of these can be compressed (with one of various methods - one of which is zstd) or uncompressed. That said, most of the time, all subblocks have the same compression 'status'.
With 'the tool' are you referring to CZI Shrink (the UI tool), or would it be acceptable for you to use a command line tool? If so you could use CZIcmd from the libczi repo. The basic usage is
CZIcmd -c PrintInformation -i AllSubblocks -s Your.czi

which will print something like
Complete list of sub-blocks
---------------------------

#0:  M=0 logical=(0,0,100,100) phys.=(100,100) pixeltype=gray16 compression=zstd1
#1:  M=1 logical=(100,0,100,100) phys.=(100,100) pixeltype=gray16 compression=zstd1

if your CZI is zstd-compressed,
and something like
Complete list of sub-blocks
---------------------------

#0:  M=1 logical=(100,0,100,100) phys.=(100,100) pixeltype=gray16 compression=uncompressed
#1:  M=0 logical=(0,0,100,100) phys.=(100,100) pixeltype=gray16 compression=uncompressed

if your CZI is uncompressed.
With this, we can build a script that finds CZI files with at least one uncompressed subblock. Here's how you could do it for the bash shell (which is also available for windows; you can install it e. g. with the git installer):

Build libczi
Find the CZIcmd executable and put it on your path, for example like this:

path_to_czicmd=$(find $(pwd -P) \( -name CZIcmd -or -name CZIcmd.exe \) -type f -executable | head -n 1)
dir_of_czicmd=$(dirname "$path_to_czicmd")
PATH="$PATH:$dir_of_czicmd"

Check that you can actually run CZIcmd

CZIcmd --version

Create a short script file called has_an_uncompressed_subblock.sh with the following contents:

#/bin/bash
file="$1"
if CZIcmd -c PrintInformation -i AllSubblocks -s "$file" | grep -q 'compression=uncompressed'
then
  echo $file
fi

Now you can run

find /folder/to/search -iname '*.czi' -exec bash /path/to/has_an_uncompressed_subblock.sh '{}' \;

and it will output a list of files that have at least one uncompressed subblock. You can redirect the output to a file using > list_of_uncompressed_czis.txt.

Hi @m-ringler !
Thanks a lot for the fantastic and very informative explanation. This sounds exactly like what we need. I will give it a try with the command line tool.
Thank you!!!

If you have difficulties building CZIcmd please let us know (with the information which operating system you want to run it on). We can probably provide a compiled binary.

@diego-rt In my fork of the libczi repo, the build can now upload CZIcmd as pipeline artifacts. And you can download compiled CZIcmd binaries from e. g. https://github.com/m-ringler/libczi/actions/runs/7046393353
If you are on Windows, either of the 'win-x64' artifacts should work for you, I'd suggest that you try CZIcmd-StreamsOFF-win-x64.
If you are on Linux, building yourself is probably the better option because

it is unlikely that the libraries used on the github build runner are the same as on your machine
It's relatively straight-forward to make your own build on linux.


/healthz endpoint

We need health endpoint to determine status of dashboard. It may get status from database.
Status should be fail, if node not in sync.

Done.

Done.


Debug ergonomics

Currently, our errors are coarse-grained (which is fine), and are returned as results rather than panicking (which is also fine).
A consequence of this is that it is very hard to trace down where an error occurs, because you can't just set break points to the constructor of (say) an EDHOCError::ParsingError, so without a time-travelling debugger and without std printf, it is very hard to find where parsing actually failed. (For example, to find https://github.com/openwsn-berkeley/lakers/pull/279#issuecomment-2125201223, I added a ParsingErrorS(&'static str) variant and changed all potential construction sites to include a label).
Thing is, I don't know a good way to do that so that we can have the labels around. The labels I'd like to have are not intended as content for the error messages, merely as debug output (winding up in the impl Debug of the errors), and on production builds, those should be elided at compile time. None of the options seem to work right:

If we add a ('static str) content to all the error variants, we'll have to add a label to all constructors (much work but OK), but we can't compile time disable it with a #[cfg()] unless we also cfg-gate the arguments in the constructors (tedious)
If we change EDHOCError to be a struct { EDHOCErrorVariant, Option<'static str> }, we'll have to construct them through the internal variant as EDHOCErrorVariant::ParsingError.with_label("foo"), need to add a .without_label() or .into() whenever we directly return errors (on ? paths we can skip it and use the automatic .into()), and the match branches grow more verbose.
We could simplify 2 a bit if the EDHOCError had associated constants EDHOCError::ParsingError = EDHOCError(EDHOCErrorVariant::ParsingError, None), but that requires duplicating the variants across both types, requires a clippy override to allow an associated constant to use enum variant naming conventions, and will be super confusing in match because you can list all the variants and then the compiler complains about unhandled variants.

So, the issue is a bit annoying (esp. during plug testing), but I like none of the solutions I can come up with. Do you have better ones?

Yeah, normally I only do "hot debug", i.e. rust-gdb --tui target/debug/coapclient, but that needs to be interactive.
I think the simple and good enough solution would be a logging system, but of course we don't have stdout so, I also don't have a solution.
... or maybe we could have it just be enabled for native builds, and have it be a no-op for embedded ones; that would be of some help.
I don't recall though if it is easy to do, maybe something like #![cfg_attr(not(feature = "python-bindings"), no_std)] but for the logging definitions.

Logging might be a good idea: We'll need to check whether pulling in the log crate is really as free as I think it is (when logging is not enabled), and whether hax successfully ignores it when disabled, but at worst we'd have a trace!() or error!() macro that by default does nothing but if enabled calls the log macros. Maybe we can find an easy idiom to wrap that around some errors at creation time.

Btw, just found out about defmt (and defmt-or-log), might be useful.

defmt is awesome. I was unaware of defmt-or-log, that even more so.

After #283 and #295, would you consider this issue solved, @chrysn ?


Use the new codius-sandbox IPC API

Closing because this is super old and a new PR should be made against the rustbox.


xSCEP module available but needs community assistance

A module for System Center Endpoint Protection has been developed but needs tests and documentation to be considered for the resource kit.
https://github.com/robwi/xSCEP
HELP WANTED

This is labeled as help wanted so that anyone in the community can run with it. Please note that the DSC Resource Kit no longer accepts new resource modules. Any contributor may make a module submission of there own resource module, so basically the resource module is linked as a submodule in this repository (linking it to the DSC Resource Kit).
As the DSC Resource Kit no longer accepts new resource modules, this issue might be closed in the future.

This issue was moved here: https://github.com/PowerShell/xSystemSecurity/issues/24


PermissionError: [Errno 13] Permission denied

./test_index.sh
+ ./prophyle/prophyle.py download bacteria
[prophyle] 2017-07-06 22:51:24 Downloading "bacteria" started
[prophyle] 2017-07-06 22:51:24 Checking library 'bacteria' in '/Users/karel/prophyle/bacteria'
[prophyle] 2017-07-06 22:51:24 Skipping downloading library '/Users/karel/prophyle' (already exists)
[prophyle] 2017-07-06 22:51:24 Downloading "bacteria" finished
+ ./prophyle/prophyle.py index -k 5 -s 0.05 -T /Users/karel/prophyle/bacteria.nw _index_test
[prophyle] 2017-07-06 22:51:25 Index construction started
[prophyle] 2017-07-06 22:51:25 Running: make -C /Users/karel/github/my/prophyle/prophyle
/Applications/Xcode.app/Contents/Developer/usr/bin/make -C prophyle_assembler
make[1]: Nothing to be done for `all'.
/Applications/Xcode.app/Contents/Developer/usr/bin/make -C prophyle_index
make[1]: Nothing to be done for `all'.
/Applications/Xcode.app/Contents/Developer/usr/bin/make -C prophyle_assignment
make[1]: Nothing to be done for `all'.
Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/site-packages/psutil/_psosx.py", line 196, in wrapper
    return fun(self, *args, **kwargs)
  File "/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4/site-packages/psutil/_psosx.py", line 266, in memory_info
    rss, vms = cext.proc_memory_info(self.pid)[:2]
PermissionError: [Errno 13] Permission denied

fixed by https://github.com/karel-brinda/prophyle/commit/90f662743653794786b220aae632dd155284b3ef


Move generic helpers from hawtio-utilities to hawtio-core

So that we can avoid duplicate functions.

@akieling Can we close this as you've merged the code from hawtio-utilities?

Yes, we can close it.
On 9 Mar 2018 1:34 am, "Tadayoshi Sato"<EMAIL_ADDRESS>wrote:

@akieling https://github.com/akieling Can we close this as you've
merged the code from hawtio-utilities?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/hawtio/hawtio-core/issues/24#issuecomment-371710967,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB0lT23sYS_fbotNDiNm7qlSJ2FLK8hpks5tcgZQgaJpZM4SOx9k
.


update to 3.4.1

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

please review @bgruening , @jdblischak
this one is a bit different because the recipe pins the versions of all the packages. I tried to update the pins to the most up-to-date of each package.


refactor: complete rewrite of the generation command, adds fsnotify hot reload

This PR updates the generation command.
This could solve various issues, including:

github.com/a-h/templ/issues/464 - since the command execution code has been rewritten
https://github.com/a-h/templ/issues/439 - I've added slog, with a custom colourised handler
https://github.com/a-h/templ/issues/395 - since the code has been completely rewritten
https://github.com/a-h/templ/issues/146 - since the hot reload code is completely new and now uses fsnotify

This builds on top of the excellent PR from @stephenafamo (https://github.com/a-h/templ/pull/366) which added the dev mode facility where Go recompilation isn't required if only the text changes.
Here's a video showing the updated experience:
https://github.com/a-h/templ/assets/1029947/70fbfe60-2197-4095-ad1c-fd59971a5386

Still in the process of grokking the bulk of this PR! An initial comment would be on the new level flag, I wonder if a more standard flag approach such as -v and -vv would be more intuitive.

Im guessing this will also work if Im running the app from a Docker container for testing ? Assuming it can be used with air.

@FACorreiaa I don't think this would interop with air too well, it's almost an alternative. Air does the watching for you, and will rebuild your code anyway if I understand it correctly.
I think we would have to have a mode where templ only regenerates templ code, and then you could leave the recompiling of Go when required to Air.

If you run templ generate --watch it generates dev mode code which - creates/updates _templ.txt files with the strings that make up the HTML, and Go code that reads from the file instead of having the strings embedded in the output code.
If you get air to run templ generate --watch continuously, that would be ideal (if you want to use air to do other things). The key thing is that if you have templ generate --watch mode running, air shouldn't restart your program if *.templ or _templ.txt files are updated, but should if any *.go files are updated.
If you run templ generate --watch --cmd="", then templ is smart enough to only stop and start the cmd if that's the case.
If you then add templ generate --watch --cmd="go run ." --proxy="http://localhost:8080" templ starts a proxy and opens the browser to that page. The proxy adds some JS to the page that initiates a background SSE (server-sent events) session. If the text on a page is updated, or the Go code changes and the cmd has to reload, the proxy mode then sends an SSE to the browser triggering a page reload (i.e. you don't need to reload the web browser page manually to see the changes).

Looks good to me!

https://github.com/a-h/templ/blob/1a1ba9731926fe6382bb45d4d9c773ad75632a3c/cmd/templ/generatecmd/cmd.go#L252-L255
Where is this relevant? I didn't see any code that pushes ctx.Err() to the errs channel.

https://github.com/a-h/templ/blob/1a1ba9731926fe6382bb45d4d9c773ad75632a3c/cmd/templ/generatecmd/cmd.go#L252-L255
Where is this relevant? I didn't see any code that pushes ctx.Err() to the errs channel.

I don't think there is any code that does that. I think I can remove it.


Patchy conflict

The patchy module conflicts with https://pypi.org/project/patchy/ , meaning django-more cant be packaged for distros as-is.
Perhaps rename it django_patchy , and ideally release it separately on PyPI so as to reserve the name.

It might also be possibly to use one of the existing patching tools, such as patchy, but https://github.com/pakal/compat-patcher-core is also nice(and actively maintained by a Django dev who I have interacted pleasantly and would be likely to accept any bits you needed), and https://github.com/theatlantic/python-monkey-business is used by a few django apps.


CI: improvements

Adds a gtk-rs/checker job
Use the common gtk4 docker image
Adds a docs job to provide decent docs until there's a release of the crate

Once merged, for the docs, someone has to set the github pages's branch to gh-pages after a successful pipeline as the docs are built from the master branch for now

cc @sdroege @GuillaumeGomez

Once merged, for the docs, someone has to set the github pages's branch to gh-pages after a successful pipeline as the docs are built from the master branch for now

You mean the on the gtk-rs.org website?

You mean the on the gtk-rs.org website?

No, just from this repository settings, so that https://gtk-rs.github.io/graphene/graphene would work unless there's something else that could be done for the docs?

That seems useful so that we also have docs (at a different place) for latest master and not just the stable docs.

I'm going to go ahead and merge this one, I will do the same for the gtk4 crates


Infrastructure rebuild

Changes

restructure infrastructure packages
add baseline Kubernetes resource file
various pkg module fixes
remove unused bin scripts/resources

Comments

This is all a basic outline for the Kubernetes integration. Several pieces here are unfinished at not currently working.

@chrisaddy I've added in some fixes for Ruff because that got broken somewhere along the way. The failing lint is related to the financials package and I'll save that for a separate PR.


fix: ignore linkerd crd changes

these show up over and over and cause resyncing like crazy.

:tada: This PR is included in version 2.0.0-alpha.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


osbuild-worker: handle error wrapping from dnfjson package

osbuild/images#751 wrapped the errors in the images/dnfjson package to provide more details, the depsolve job should take this into account to map the dnfjson error to the correct worker client error.
This caused user input errors errors to be misclassified as internal errors, triggering depsolve job failure alerts.

Thank you! Out of curiosity, what error causes this issue? is it the one from makeDepsolveRequest() that is now wrapped?

The one in dnfjson.Solver.Depsolve.


Fix can not reconnect websocket after turn off then turn on wifi. Thi…

Summary
On some Samsung devices, when turning off and then turning on Wi-Fi (or when Wi-Fi is not stable), it cannot auto-reconnect.
Ticket Link
none
Checklist

[ ] Added or updated unit tests (required for all new features)
[ ] Has UI changes
[ ] Includes text changes and localization file updates
[ ] Have tested against the 5 core themes to ensure consistency between them.

 A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

@yasserfaraazkhan Do you have a Samsung device to test this? If not, do you know if anyone in the QA team has one to test this?
Regarding the QA steps, the description of the issue is really detailed, but if you need anything let me know.

@yasserfaraazkhan Do you have a Samsung device to test this? If not, do you know if anyone in the QA team has one to test this?
Regarding the QA steps, the description of the issue is really detailed, but if you need anything let me know.

@larkox I dont have Samsung.
I've a different android phone. I'll try this in previous version of app and then check the fix.

Building app in separate branch.

@yasserfaraazkhan This ticket doesn't have any Jira ticket for QA tracking. Do you want me to create one, or will you create it?

Hi @larkox , no worries 😃
I can create one for tracking


fix: Updated config files location in capture.py

In capture.py, paths and name of configuration files are from the old architecture of the repo (before the last release)
This short PR introduces the following modifications:

in capture.py : updates path to .env
in capture.py: updates name and path to camera credentials

Happy to discuss it !

Just FYI: I did update all scripts but the capture one so far :sweat_smile:
So it actually needs some rework

Hehe, I don't doubt it given the quality of the rest :D
This quick fix makes it functional, but I agree a rework has to be done !


Specifying dependency by alias causes error

Using just 1.16.0 Linux x86_64 build downloaded from https://github.com/casey/just/releases/tag/1.16.0
Minimal test justfile:
foo: a
	echo 'Foo'

actual-recipe:
	echo 'this recipe has an alias'
alias a := actual-recipe

Running just just errors with -
$ just
error: Recipe `foo` has unknown dependency `a`
  |
1 | foo: a
  |      ^

Same error still occurs when putting the aliased recipe and/or its alias before the recipe that depends on it.
Workaround: instead of using an alias, define it as another recipe:
foo: a
	echo 'Foo'

actual-recipe:
	echo 'this recipe has an alias'
a: actual-recipe

Is it possible to make this work with alias?

This currently isn't possible. I'm not sure this is super desirable, since you can always use non-aliased recipe name in the dependency. And using an alias is less readable, since you have to look for the alias to see which recipe it is. Is there a reason you can't do this?

The "workaround" is fine when recipe doesn't take parameters, but recipes with parameters would run into this problem - #1302 (reply in thread)

I checked out that discussion, and can't figure out how it relates to this issue. Can you give an example justfile which demonstrates the problem?

So aliases only apply in the command line, not anywhere in a justfile? If so, and if that is the desirable behavior, it should be documented. Would it be helpful if I made a pull request to clarify the documentation?

I think some documentation would be great!

In this case, why not modify test2 to call main-recipe directly, e.g, (main-recipe '123' '456')?

Ah, I see. Yah, in that case maybe that would be the best solution.


MSID: 98347 Version: 1 DOI: 10.1101/2<IP_ADDRESS>0453

MSID: 98347
Version: 1
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>0453
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=98347
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>0453

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/98347v1
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>0453
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/98347/v1/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

Moving supp captions to supplementary-material


Warning when filtering and sorting results

I'm getting this warning when I try to filter results by entering something in the prompt.

@h4rr9 The issue is fixed
If you update to the new version, you should not get this error anymore.

@jvgrootveld Thank you!


What's the license of the yaml files?

Hi rosdistro team,
I want to use the yaml file with superflore to generate new recipes for humble. Need confirmation:
What's the explicit license of the generated cache.yaml file by ros-generate-cache.sh in meta-ros?
Hope you can confrim it, thanks a lot.

hi team,
can you update on this issue?


bump mesos-dns to bring in changes for mesos state endpoint

High-level description
Mesos state.json endpoint has been deprecated in favor of state endpoint. This patch bumps mesos-dns to bring in those changes
Corresponding DC/OS tickets (obligatory)
These DC/OS JIRA ticket(s) must be updated (ideally closed) in the moment this PR lands:

DCOS_OSS-3941 mesos-dns is using deprecated mesos endpoint /master/state.json

Checklist for all PRs

[ ] Added a comprehensible changelog entry to CHANGES.md or explain why this is not a user-facing change:
[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[ ] Read the DC/OS contributing guidelines
[ ] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[x] Change log from the last version integrated (this should be a link to commits for easy verification and review): https://github.com/mesosphere/mesos-dns/compare/114915e5ce05376be2b237b5016d6832d273ea6f...211986ed6af9de08332adc696ceb20191e1aa36f
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

PLEASE FILL IN THE TEMPLATE ABOVE / DO NOT REMOVE ANY SECTIONS ABOVE THIS LINE
Instructions and review process
What is the review process and when will my changes land?
All PRs require 2 approvals using GitHub's pull request reviews.
Reviewers should be:

Developers who understand the code being modified.
Developers responsible for code that interacts with or depends on the code being modified.

It is best to proactively ask for 2 reviews by @mentioning the candidate reviewers in the PR comments area. The responsibility is on the developer submitting the PR to follow-up with reviewers and make sure a PR is reviewed in a timely manner. Once a PR has 2 ship-it's, no red reviews, and all tests are green it will be included in the next train.

@mesosphere-mergebot label Ready For Review

@jdef @vespian request for review

@mesosphere-mergebot bump-ee

@mesosphere-mergebot bump-ee

@mesosphere-mergebot bump-ee

@GoelDeepak could you please rebase this one and then bump-ee again to resolve the merge conflicts?

@mesosphere-mergebot bump-ee

@mesosphere-mergebot override-status teamcity/dcos/test/azure/hybrid-cloud DCOS-42798

@mesosphere-mergebot override-status teamcity/dcos/test/azure/arm DCOS-41677

@mesosphere-mergebot override-status teamcity/dcos/test/aws/onprem/static DCOS_OSS-2115


Add MAP_GUARD for FreeBSD 12+

As per https://github.com/freebsd/freebsd-src/blob/main/sys/sys/mman.h#L103

r? @Amanieu
(rust-highfive has picked a reviewer for you, use r? to override)

I got confused. Seems it's already there


Remove isCollapsible behaviour entirely from Filters.Filter component

Release Type: Dev Improvements
Fixes https://x-team-internal.atlassian.net/browse/XP-2854
Description
Remove isCollapsible behaviour entirely from Filters.Filter component
Checklist

[x] set yourself as an assignee
[x] set appropriate labels for a PR (In Review or In Progress depending on its status)
[x] move respective JIRA issue to the IN REVIEW column
[x] make sure your code lints (npm run lint)
[x] Flow typechecks passed (npm run flow)
[x] Snapshots tests passed (npm run jest)
[x] component's documentation (.stories.js file) is changed or added accordingly to reflect any new or updated use cases or variants usage
[x] if any snapshots have been changed, verify that component still works and looks as expected and update the changed snapshot
[x] manually tested the app by running it in several different browsers (Firefox, Chrome, Opera, Safari, MS IE/Edge, etc.) and checked nothing is broken and operates as expected!

Related PRs

branch
PR

XP-2854-remove-expand-collapse-from-filter-inputs
Auto

Steps to Test or Reproduce

run npm start
go to http://localhost:9001/?selectedKind=UI Components%2FFilters%2FDebug&selectedStory=standalone Filter
observe that the isCollapsible prop is no longer available

Impacted Areas in Application

Filters/Filters.stories.js

Screenshots

Resolved merge conflicts


State restoration doesn't work because of wrong HomeAssistant.state attribute's value when async_added_to_hass is called.

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.39.0.dev0 (fresh pull from github)
Python release (python3 --version):
Python 3.5.3
Component/platform:
restore_state
Description of problem:
State restoration doesn't work. Yield from async_get_last_state() always return None. I've checked the implementation of the function and it fails on check
    if (_RECORDER not in hass.config.components or
            hass.state != CoreState.starting):
        return None

because hass.state is CoreState.not_running at the moment of adding entity (not CoreState.starting as expected by the function).
Entites are created and set up by calling bootstrap.from_config_file() in __main__ module. The async_added_to_hass coroutine is called at that stage. The HomeAssistant.state propery is changed to CoreState.starting AFTER bootstrap.from_config_file() finishes by calling hass.start() method.
Expected:
Entities should have their state restored after restart.
Problem-relevant configuration.yaml entries and steps to reproduce:
homeassistant:
  name: Home
  unit_system: metric
  time_zone: Europe/Warsaw

frontend:

http:

updater:
recorder:
  purge_days: 30
history:
logbook:

input_boolean:
  bool_test:
    name: Boolean Test

input_select:
  sel_test:
    name: Select Test
    options:
      - Opt1
      - Opt2
      - Opt3

Run hass
Change values of inputs in frontend
Restart hass (either using homeassistant.restart service or by closing it and running again).

lol, this never worked!  FAIL.
Good catch, thanks @yawor


Add navigation from federal subject to country

The feature
Add a way to navigate back up to country level from a federal subject page.
Why?
Thanks to #351 we now have a way of adding entire pages for subjects on a level lower than country, for example for a state or bundesland. But currently, we have no easy way of navigate back up to the top, which would be good if one enters on this level and cannot use the back button.
Examples and inspiration
No response

Hi! I'm interested to take on the issue, but need to clarify this first. Does this feature already added in the form of button labeled as country? like in this page https://www.govdirectory.org/indonesia/Q3724/

@naufandarmawan  Like this: https://www.govdirectory.org/united-kingdom/scotland/ In this case, there should be a navigation/back button to the United Kingdom.


Styles: Update select

Design: https://www.figma.com/file/xZ0IW0MJO0vnFicmrHiKaY/Components?node-id=7802%3A33963&t=NxYB7ZrwohQXWwaV-0
### Tasks
- [ ] Validation states
- [ ] Check floating label behaviour
- [ ] Check margins for hints and validation messages
- [ ] Check paddings
- [ ] https://github.com/swisspost/design-system/issues/3216
- [ ] Design review

Closing in favor of v2 select


Stateful dataloader README

Please read through our contribution guide prior to
creating your pull request.

Note that there is a section on requirements related to adding a new DataPipe.

Fixes #{issue number}
Changes
Adds README.md for torchdata.stateful_dataloader
Testplan:
Checked rendering and links in the branch preview on github:

It seems that CI gets skipped when the last action is by facebook-github-bot


Make committed virtualenv test a bit less strict

It's ok to have gitdir/bin and gitdir/lib, they may /not/ have a virtualenv in them :)

That's why it's only a warning at the moment. It will only reject if there's an actual conflict.
Soon, we'll be moving the virtualenv to it's own directory .heroku/venv, and this will be removed completely.

Sweet.
On Fri, Dec 30, 2011 at 10:03 PM, Kenneth Reitz <
<EMAIL_ADDRESS>
wrote:

That's why it's only a warning at the moment. It will only reject if
there's an actual conflict.
Soon, we'll be moving the virtualenv to it's own directory .heroku/venv,
and this will be removed completely.

Reply to this email directly or view it on GitHub:
https://github.com/heroku/heroku-buildpack-python/pull/17#issuecomment-3316555

Keep the pull requests coming :)


Support the use of do as a connective in UCS

Main features:

Keyword do can appear in place of then, and the default value of its UCS expression will be replaced with UnitLit.
Keyword do can appear in a split of UCS to introduce expressions whose results are not needed between branches.

Relevant changes:

Keyword do has the same left and right precedence as then and can be parsed as an infix operator.
Add two Sets to Desugarer tracking the usage of do and then. If they are all used in the same UCS expression, an error will be reported.
Add test file ucs/syntax/Do.mls, which shows the semantic difference between do and then.

Not so relevant changes:

Add a unified apply to Desugarer. It should be called no matter we want to desugar case, if, or UCS shorthands.
Add kwLoc: Opt[Loc] field to IfLike and Case for better error reporting.

Nice change! There are a few places to update that currently use while imperatively but with then because we didn't have do at the time.

Can you please squash this PR when you merge?


Fix misprediction where a bullet would be "lost" on wielding

About the PR

Fixes https://github.com/CM-14/CM-14/issues/2343
Why / Balance

Bugfix. I elaborated a bit more in Technical Details.
Technical details

Given that the cycle is not being handled server-side I assume that the
intended behavior is for the gun to not cycle when you press z. I think this is
a better approach than binding two actions to the same key because wielding is the
more frequent action. If this is not the case let me know and I am happy to
figure out a better solution.
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

:cl: Aquif

fix: The gun will no longer pretend to cycle when you try to wield it by pressing z.

This is also a issue upstream. could this be used to fix the issue upstream?

Maybe? I thought that it actually cycled upstream where here it does not. I will test it now.

Just tested it. The behavior is different upstream. On CM z toggles whether or not you are wielding it. Upstream, z acts differently depending on when it is used. It seems like it also has a form of this bug, but I don't think it is exactly the same one.

I need to check this, but as far as I know this is a mispredict (where the client thinks it should cycle, but the server does not), this should be fixed by checking what code is running in client that the server is not, and making both run the same code.
Otherwise this would remove the ability to cycle entirely, which is not intended.
It might be a little involved to find what the difference is, since you would need to breakpoint all handlers of UseInHandEvent related to guns, but this should also be upstreamed when the fix is found.

Maybe this happens due to virtual item spawning always failing on the client's side: https://github.com/space-wizards/space-station-14/blob/c79384c5fd0156cea5db6db9576674fab28e534c/Content.Shared/Inventory/VirtualItem/SharedVirtualItemSystem.cs#L219

Maybe this happens due to virtual item spawning always failing on the client's side<EMAIL_ADDRESS>
I think so, there's a PR for that here https://github.com/space-wizards/space-station-14/pull/28840

Ah, right. I have been sick the past few days or I would have looked into it myself. I am going to close this because it is probably an upstream issue.


Low TSS Enrichment Scores

The last few samples I analyzed had unusually low TSS Enrichment Scores (compared to other samples I ran last night and my collaborator's analysis of the same samples). I saw the latest updates today had to do with the TSS_enrich plots - could that affect it? Thanks!

Hi - if you are seeing a difference between updates (as in, the TSS enrichment scores before the update were fine and then afterward were lower) then yes, that is likely an effect of the annotation update.

Hi, yes exactly.
Here's analysis I ran before the last update (2/8/17):

Here's the same sample, re-run today:

The first matches up with my collaborator's analysis - great quality. The second would indicate that it (and all of my other samples) need to be thrown out! For now, I'm going to continue with downstream analysis and assume it's a problem with calculating or displaying the TSS enrichment score, but just wanted to point it out.
Thanks!!
-Becky

Hi Becky,
Just checking in on this. The annotations have significantly stabilized, so if you'd like to run the QC again you should get very similar results to your first result. (If you do re-run, make sure to get the latest code as well as the latest download of genome annotations) Let us know if you run into any problems with it.
Cheers,
Daniel

Hi Daniel,
Thanks for the update! I’ll be running all of my samples through the pipeline again once I get my next set of sequencing back, hopfully next week. I’ll let you know if it looks right!
Best,
-Becky
Rebecca Leylek
Immunology Graduate Student
Idoyaga Lab
On May 9, 2017, at 3:17 PM, Daniel Kim <notifications<EMAIL_ADDRESS>wrote:
Hi Becky,
Just checking in on this. The annotations have significantly stabilized, so if you'd like to run the QC again you should get very similar results to your first result. (If you do re-run, make sure to get the latest code as well as the latest download of genome annotations) Let us know if you run into any problems with it.
Cheers,
Daniel
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/kundajelab/atac_dnase_pipelines/issues/35#issuecomment-300317849, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AYYvuiTyTUa4LLNL1jLVOLXSjND31_pHks5r4OXwgaJpZM4L9C-p.


fix use of grep in build.sh binary-has-bitcode

I could reproduce the build.sh package-ios-static failure locally, and this fixed it, strangely enough. /cc @bdash

This passed the objc_ios job of releasability_pipeline: https://ci.realm.io/job/releasability_pipeline/1317/console

I really wish we understood why this was a problem. We use grep -q in a few other places in build.sh, and it'd be unfortunate if they also weren't behaving as we expect.

As far as I can tell, the -q flag does change the result in some cases: https://github.com/freebsd/freebsd/blob/master/usr.bin/grep/util.c#L211-L238


[Infra] Rethink addon primitives as contextual and not UI components

Currently this addon makes some opinionated choices about how the UI of the collapsible panels is rendered.
A better fit for this addon might be to provide contextual components that don't render anything but instead provide the primitives needed for collapsible panels without the UI.

Now that modifiers are out, I think this would best be served with modifiers. I just made a pull request for ember sortable, very similar in the demands.

Ok where this differs from ember sortable is the hiding of the body. A modifier cant really do that except to make the DOM element hidden. Not really the same thing.
Where you are going to run into the problem with primitives that dont render anything is where to put the toggle. When it comes down to it a collapsible panel is an if and an isOpen variable.
The panels component yields some functionality.

So what would this look like. Im guessing the below? If user wanted animation they would replace if with animated-if or their animation addon of choice. Its not this addon's responcibility.
The click me isnt an anchor but they could make an anchor and put the {{on}} it. Thats the point really. Allow them to specify the DOM.
{{#cp-panel as |p|}}

Click me!

  {{#if p.isOpen}}

Lorem ipsum dolor sit amet, consectetur adipisicing elit. Nemo repellendus nisi asperiores esse aperiam aliquid nulla ad dolor autem neque, nihil inventore temporibus delectus earum facere corporis, quam ipsum maxime.

Lorem ipsum dolor sit amet, consectetur adipisicing elit. Doloribus neque magnam, hic quis beatae repellendus harum modi pariatur minus quidem alias! Eius incidunt impedit eaque, est, illo officiis expedita molestiae.

  {{/if}}
{{/cp-panel}}

I hate to say it but how far is that from below, which I believe is a collapsible panel

Click me!

{{#if this.isOpen}}

Lorem ipsum dolor sit amet, consectetur adipisicing elit. Nemo repellendus nisi asperiores esse aperiam aliquid nulla ad dolor autem neque, nihil inventore temporibus delectus earum facere corporis, quam ipsum maxime.

Lorem ipsum dolor sit amet, consectetur adipisicing elit. Doloribus neque magnam, hic quis beatae repellendus harum modi pariatur minus quidem alias! Eius incidunt impedit eaque, est, illo officiis expedita molestiae.

{{/if}}

(toggle) is available from https://github.com/DockYard/ember-composable-helpers#toggle


Dev marie remove third party search

Removes Google and Wolfram results from the 'Marie' page of the website and the funtionality to run the searches in the Marie service itself.

Self-approving this PR, as the changes don't introduce any new code and have been tested locally.


Breaks when dependabot PR body format changes

It seems like (at least for group updates) the PR body that dependabot is outputting changes fairly frequently. Its already changed twice since releasing this action.
It would be great to look into reading the package.json diff to figure out changes instead as that format is not really going to change.

Example of the latest version that doesn't work with this action:

Bumps the all group with 1 update: lucide-svelte.

Release notes
Sourced from lucide-svelte's releases.

New icons 0.293.0
New icons 🎨

user-round-cog (#1638) by @jmsv
user-round-x (#1638) by @jmsv
users-round (#1638) by @jmsv

Modified Icons 🔨

cassette-tape (#1698) by @ericfennis
drama (#1698) by @ericfennis
life-buoy (#1698) by @ericfennis
rotate-ccw (#1698) by @ericfennis
spade (#1698) by @ericfennis
store (#1698) by @ericfennis
text-cursor-input (#1698) by @ericfennis
theater (#1698) by @ericfennis

Commits

75e9724 Make sure we apply all classes to the lucide icons (#1691)
See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
@dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
@dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
@dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
@dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
@dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions


Plugin errors when exporting an image with multiple layers.

Hi,
Prior to the rewrite, the plugin had no problems exporting multi-layered images (using GIMPJPEGXRPlugin 1.0.1) as a .jxr. With the release of the rewrite, however, the plugin throws an error whenever the image I'm exporting has multiple layers.
A screenshot of the error:

I'm on a Windows 7 install running GIMP 2.8.22 in conjunction to gimp-jxr 2.1.

Thanks for reporting the issue but I haven't been able to reproduce it, yet. Does the error occur with this multi-layered image? If not, can you upload a sample image which reproduces the issue for you? Thanks.

I encountered the very same error with the sample image you provided.
By the way, I forgot to mention that the plugin does work -- I'm able to successfully export multi-layered images as .jxrs and open said .jxrs successfully in an image viewer -- it's just that whenever I export the images, the error pops up.
The error itself doesn't seem to be hindering the export process, but it is still mildly annoying to deal with.

I was able to reproduce the issue now. Version 2.1.1 fixes it.


More helpful error message when trying to import by folder from non-github

The old message was really confusing when using an actual correct integration, but which does not support the "folder mode".

Just some vale woes to fix.


User feedback with features suggest

Hi there,
I just tried the email plugin and it is great! No bug to mention so far, from windows 10, outlook mail provider.
I Feel closer to my communication needs, less inertia in respect to my mailing tasks.
Some brief thoughts to share:

would be amazing to extend the plugin to whatsap, telegram and other messenger services (I guess it's a lot of work and harder to find the right contact)
the syntax used to separate entries ';' made me wish to be able to edit a csv file in the same way. So I could make tagged entries in a daily task database for example. Or to make it possible to add quick note (fleeting notes) with tags in a pre-set spreadsheet file. Maybe with the possibility to enter timestamps, and have kind of a zettlerkasten display.

Thank you and congrats for all the work!

Thanks for the kind words, I'm glad you find the plugin useful.
I could probably do something for those other services but you're right that there would be more in it.  I don't really use them, are you thinking something for telegram like a keyword "tg" space target group or person name with autocomplete space message?  eg. tg nick Hey bud, gonna be 10 min late for bowling practice tonight
There are a couple plugins for todo lists and note apps already, I'm not aware of fleeting notes but I'll look into it.  Have you ever used Microsoft Todo?

like a keyword "tg" space target group or person name with autocomplete space message?

Yes, precisely.
Todo lists apps : True, I tried the simple todo plugin with flowlauncher and it has some value. I have fallen in the rabbit hole of tasking and writing productivity for a while. I do use ms todo, with google task, and notion. In short, I found myself with a growing number of list in ms todo, getting a bit lost sometimes. Because then I have to think 'in what list I put it again?'. Their search feature could help but I have to think...'how I call it again?'... But their app is quite snappy and integration with outlook panels is promising. G task is more to the point in some way, but you can't add steps. The deal with both of them is the follow-up for bigger (time horizon) projects. So my last move goes toward notion, where you can create, add stuff, while maintaining a minimal outlook on what you are doing (i.e. search by project, by statut). Key is their changing views feature.
Note-taking: I do use Zotero, onenote, keep, and obsidian. As for a plugin, search in obsidian already exist. But not add a note. You could think of a plugin to happen a textstring to a preselected file (text, md, csv), or a preselected folder (like simple todo does). Then if you select an obsidian folder for that, it might behave like an "add note to obsidian" plugin... Obsidian comes later in my writing workflow, making use of their # recognition to retrieve my thoughts, eventually making permanent note [[]] from that. Zotero come for pdf notetaking (I am doing a degree in social sciences), onenote is more like diary for when I already know the kind of writing I will do (as opposed to fleeting usecase) and is quite useful for taking note on mobile outside my desk (conferences, street wandering). Keep... for fleeting note use case, though the onenote quicknote has a tendency to substitute it, making a case for quick note too. To resume, the best I have now is putting onenote to my taskbar and use it from win+1 hotkey. However : i) I got some trouble to find quick notes back l ii) would be nice to unify things with alt+space flowlauncher fashion.
If I had to formulate a nice-to-have feature from that being said: being able to add text with #s and [[]]s so my obsidian will recognize it later-on. Could be the same file everyday or a new file at every entrie.
PS: powertoy recently added the search in your onenote feature, quite nice. But still no add new note feature. My guess is that they have people working on that. And maybe on to-do integration too. So if you thought of a ms to do integration with flow-launcher, you may risk to double the work (high on speculation here).


Testing framework

We could use wish for assertions
I wish Your Love was true
It will throw/panic if Your love is not true

Can the testing framework be called Roadie?


Feature Request: Support for Apollo Federation in Tailcall

Summary
Enable Tailcall to support Apollo Federation by adding a flag in the @server directive. When enabled, this flag will support the _entities query, allowing Tailcall to function as a subgraph in a federated architecture.
Detailed Description
To integrate Apollo Federation with Tailcall, we propose the following enhancements:

Flag Addition in @server:

Introduce a new flag within the @server directive to enable federation support.
When this flag is activated, Tailcall will automatically handle the _entities query, essential for Apollo Federation's distributed schema architecture.

Support for Resolver Directives on Types:

Enable resolver directives like @http, @grpc, @const, and others to be applied directly on Types.
This will allow Tailcall to infer the key fields required for federation based on the resolver configuration.

Key Inference:

Analyze the resolvers attached to Types and automatically infer the appropriate @key directive.
Example:

For @http(path: "/users/{{.value.id}}"), the inferred key would be @key(fields: "id").
For the query:@http(path: "/users/", query: [
  {key: "id", value: "{{.value.id}}"},
  {key: "name", value: "{{.value.name}}"},
  {key: "org_id", value: "{{.value.organisation.id}}"},
  {key: "org_name", value: "{{.value.organisation.name}}"}
])

The inferred key would be @key(fields: "id name organisation {id, name}").

If multiple resolvers are attached to the same type, multiple keys will be inferred and handled accordingly.

Support for _entities Query:

Implement the _entities query required by Apollo Federation.
Example of how the query to the subgraph would look:type Query {
  _entities(representations: [_Any!]!): [_Entity]!
}

Example query:query ($representations: [_Any!]!) {
  _entities(representations: $representations) {
    ... on User {
      id
      username
    }
  }
}

Corresponding variable:{
  "representations": [
    {
      "__typename": "User",
      "id": "5"
    }
  ]
}

References

For a reference implementation of Apollo Federation, see the async-graphQL implementation.

Subgraph Documentation

Technical Requirements

Integration & Unit Tests are required.
Update the documentation on website

/bounty 380$

/attempt #2639

please provide some working config


Add Issue-template and prow workflow

This PR proposes

GitHub Issue templates
GitHub workflow for action by command-style comments (inspired by Kubernetes Prow))

Supported comments are as follows,
/assign
/unassign
/approve
/retitle
/area
/kind
/priority
/remove
/lgtm
/close
/reopen
/lock
/milestone
/hold
/cc
/uncc
This GitHub workflow is based on jpmcb/prow-github-actions .
https://github.com/jpmcb/prow-github-actions/blob/main/docs/commands.md
You can see a demo PR from https://github.com/seokho-son/docs/pull/18 to check actions.

@seokho-son

Thanks for upgrading!

/assgin @powerkimhub

/assign @powerkimhub

/assign @powerkimhub

/assign @powerkimhub

/lgtm

@seokho-son

Thanks for upgrading~!


Routes not displayed in UI on new deployed apps

Issue:
Routes are not displayed in UI when an app is pushed

Possibly related to: https://github.com/epinio/epinio/issues/1799
Checked on Epinio Server Version: v1.4.0-18-g12e7d143 using UI v<IP_ADDRESS>.0.1
Note: custom routes created after initial deployment are displayed:

That's correct @andreas-kupries , it's using [] to ask for default. So changing it to ask for null will pretty much solve this, right?

Yes

The code has been merged to epinio-dev. @mmartin24 I think it's probably time to change back the UI source used in the CI pipeline from the tag to epinio-dev. Note - The CI will need to run the UI with the new env vars just like when you run the UI locally

Thanks @richard-cox . We will switch back the ci to epinio-dev and will check how it goes

Tested fixed locally on local epinio-dev and working:

The code has been merged to epinio-dev. @mmartin24 I think it's probably time to change back the UI source used in the CI pipeline from the tag to epinio-dev. Note - The CI will need to run the UI with the new env vars just like when you run the UI locally

@richard-cox , the changes have been applied to latest epinio qa image and works. Thanks

Closing issue.


More targeted crosstalk veto

Original report by Joseph Fowler (Bitbucket: joe_fowler, ).

We need a crosstalk veto system that can be more targeted. Ideally, it will allow us to veto crosstalk from any of a list of potential perpetrator channels into a single victim.
The current code allows all channels to veto all others, but in some cases that is overkill.

Original comment by Joseph Fowler (Bitbucket: joe_fowler, ).

See my email sent to Dan, Joel, Randy, Kelsey on June 16. I had little success on a targeted crosstalk. It took 2 minutes per channel to run (maybe could be faster with Cython), and it did not improve resolution as much as a general array-wide veto does.
Put on hold for now, until we better understand the requirements.


microbit/microbit-common/src/display/nonblocking ⸺ defect in timings?

I went through example regard using nonblocking display — https://github.com/nrf-rs/microbit/blob/main/examples/display-nonblocking/src/main.rs.
I noticed that some LEDs shine very dimmly in their core that should not. This is permanent for pattern being displayed. Since I verified using blocking API there is no issue with LEDs on this, I suppose some wrong.
My unqualified guess is there is some interferrence regard timing.
From doc.

This uses a 6ms period to light each of the three internal LED rows, so that the entire display is updated every 18ms.

I tried some interrupt priorities and RTC0 frequencies variations but issue is resistable to this.
Sample of displaying letter E; RTC0 with 100 prescaler, NVIC priority 32, TIMER2 NVIC priority 64

So I wonder if there is bug somewhere seeking for remendy.

Yes, it's same.

@lulf Should I make a release based on this merged PR plus other stuff?


Which one is the "CV-DoG" mentioned in the paper?

Open CV Difference of Gaussians (SIFT).

@etrulls
https://arxiv.org/pdf/2003.01587.pdf
In figure6, I see another CV-SIFT other than CV-DoG. What's the difference between Open CV Difference of Gaussians (SIFT) and CV-SIFT?

"DoG" is shorthand for the SIFT detector (we call it "CV-DoG" as we also have a few experiments with VLFeat's implementation of DoG). So for instance "CV-DoG/Hardnet" means Hardnet descriptors on SIFT (DoG) keypoints. "CV-SIFT" means SIFT descriptors on SIFT keypoints.

@etrulls Now I get it, thank you very much!


Exclude ffi 1.9.22 and ffi 1.9.23

Excluding ffi 1.9.22 and ffi 1.9.23 due to Segfault on macOS and SIGABRT on Centos/RHEL 6+7. Fixes #86

Coverage decreased (-12.0%) to 79.426% when pulling 97543793ffdb619dc1d67bcf48c52718d925d35f on msducheminjr:ffi-fix into 562b0a99c169eb41b31d39b88ec22ebd5fb6dcac on guard:master.

Coverage decreased (-12.0%) to 79.426% when pulling 97543793ffdb619dc1d67bcf48c52718d925d35f on msducheminjr:ffi-fix into 562b0a99c169eb41b31d39b88ec22ebd5fb6dcac on guard:master.

Assuming this is no longer a problem.


feat: Load 3rd-party images from higress image repo

Ⅰ. Describe what this PR did
Load 3rd-party images from higress image repo.
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

This should require support for multiple architectures. Shall we address this by creating a manifest?

This should require support for multiple architectures. Shall we solve this throught docker manifest?

I'll see if we can do it.

This should require support for multiple architectures. Shall we solve this throught docker manifest?

I'll see if we can do it.

I've synced all image arcitectures found in Docker Hub to the Higress image repo.