Test are failing in the example code

It throws: NullInjectorError: R3InjectorError(DynamicTestModule)[MsalService -> MsalService]:

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

ID: 28c13084-08f6-c015-7769-c2ab9170c1d2
Version Independent ID: 44d5c264-8c95-0ae5-be9c-8982cea33223
Content: Tutorial: Create an Angular app that uses the Microsoft identity platform for authentication using auth code flow - Microsoft Entra
Content Source: articles/active-directory/develop/tutorial-v2-angular-auth-code.md
Service: active-directory
Sub-service: develop
GitHub Login: @henrymbuguakiarie
Microsoft Alias: henrymbugua

@mtulikowski
Thanks for your feedback! We will investigate and update as appropriate.

@mtulikowski
It seems like you are encountering an error related to the MsalService in your Angular application. This error message usually occurs when the Angular injector cannot find the required dependency.
Based on the error message, it seems like the MsalService is not being injected properly. This could be due to a few reasons such as:
The MsalService is not imported correctly in your Angular module.
The MsalService is not provided correctly in your Angular component.
The MsalService is not initialized correctly.
To resolve this issue, you can try the following steps:
1.Make sure that you have imported the MsalModule in your Angular module and added it to the imports array.
2.Make sure that you have provided the MsalService in your Angular component. You can do this by adding the MsalService to the providers array in your component.
3.Make sure that you have initialized the MsalService correctly. You can do this by calling the initialize() method of the MsalService in your component's constructor.
Here is an example of how you can import and provide the MsalService in your Angular component:
import { Component } from '@angular/core';
import { MsalService } from '@azure/msal-angular';
@Component({
selector: 'app-root',
templateUrl: './app.component.html',
styleUrls: ['./app.component.css'],
providers: [MsalService]
})
export class AppComponent {
constructor(private authService: MsalService) {
this.authService.initialize({
clientID: 'your-client-id',
authority: 'https://login.microsoftonline.com/your-tenant-id',
redirectUri: 'http://localhost:4200',
cacheLocation: 'localStorage'
});
}
}
Please replace your-client-id and your-tenant-id with your actual client ID and tenant ID respectively. Also, make sure that the redirectUri matches the redirect URI that you have registered in your Azure AD app registration.


Tab Bar issue

Not sure if this is my implementation or the library but having trouble with layouts using the library with a react-navigation tab bar.
When the keyboard is show, the KeyboardAccessoryView has a space between the keyboard and the bottom of the view equal to the height of the toolbar.

Hello,
Thank you for the question.
It is the problem in the library most definitely. I didn't think about tab bar case because it is not common to have a chat screen with a visible tab bar (usually when you have a chat in a tab there is a list of people you are currently chatting with, and when you select one - you present a chat screen without a tab bar visible). Also, tab bar takes some space, so you see less messages.
Because of above I wouldn't do automatic detection of a tab bar, but I can try adding a prop where you can specify a custom offset - you would need to know the height of a tab bar.
What do you think?

I think a custom offset prop would be the way to go - that way the library could support different scenarios rather than just adding "Tab bar" support.

Hi @mortocks, hopefully fixed in https://github.com/flyerhq/react-native-keyboard-accessory-view/pull/5, I have also added a new section to the README regarding this, please read it. Let me know if that works for you. Thanks!

Nice - confirmed on iOS that this additional api allows support of a tab bar. Not to future devs that you're going to want to take bottom insets into account rather than just hard coding a variable but the api works as you'd expect.
Thanks

Thanks! Yes, you are correct, you should use bottom safe area insets and/or the size of a component that is adding unwanted margins, I've described the whole process in the docs - https://github.com/flyerhq/react-native-keyboard-accessory-view#handling-wrong-offsets


adding ttl to ddb

This is re: #23
We only use data from the last month to create ranks or insert values. Which means technically speaking, we don't really need to store anything past a month. This Pr tries to address that by adding dynamodb ttl columns. Which has no additional cost but helps us reduce the time it takes to scan the table and general savings for the amount of data that we will end up storing. I haven't deployed this to be honest but looking for some reviews to see if the approach is okay before I setup the dummy bot to test.
Why 31 Days Sakib?
Makes sense to store for the worst case scenario.
What about the stuff that already exists?
We'll have to write a script to clean that up

why arent we getting this merged? any blockers?


Server keeps crashing due to unknown error

I'm looking for someone who can help me decipher these debug messages; the OS is CentOS 7, the script is compiled with -d3 parameter:

[30/03/2020] [04:26:20] [debug] Server crashed while executing vwhrp.amx
[30/03/2020] [04:26:20] [debug] AMX backtrace:
[30/03/2020] [04:26:20] [debug] #0 0000003a in ?? (77, 97, 114, 105, 111, 95, 72, 117) at C:\Users\Rudy\Desktop\SA-MP Server\pawno\include\float.inc:103
[30/03/2020] [04:26:20] [debug] #1 0000003a in public OnPlayerTakeDamage () at C:\Users\Rudy\Desktop\SA-MP Server\pawno\include\float.inc:103

Please follow this guide and re-compile your script with debug info enabled:
https://github.com/Zeex/samp-plugin-crashdetect/wiki/Compiling-scripts-with-debug-info
After that when this issue happens again you will see more details in the crash report (function names, source files, arguments, etc).

The script is already compiled with the -d3 flag and as you can see, it doesn't give me much details.
I suspect it is an exploit they are using to crash the server.

Oh right, sorry, I missed that part.
Please provide the following info:

What version of crashdetect are you using? You can find this in the server log
What version of the Pawn compiler are you using? Are you using the standard compiler or this one?

Also, you can try to find a function that has the same number of parameters as the top function in the stack trace and that is called directly from OnPlayerTakeDamage. Then after you find it, you can match the arguments with its parameters (easy for integers, not so easy for strings). This might give you an idea about what causes this crash.
If you are not using the latest version of crashdetect, I'd suggest you upgrade the plugin first.

I'm using the latest CrashDetect plugin:

[30/03/2020] [11:08:19] Server Plugins
[30/03/2020] [11:08:19] --------------
[30/03/2020] [11:08:19]  Loading plugin: crashdetect.so
[30/03/2020] [11:08:19]   CrashDetect plugin 4.19.4
[30/03/2020] [11:08:19]   Loaded.
[30/03/2020] [11:08:19]  Loading plugin: sscanf.so
[30/03/2020] [11:08:19]

[30/03/2020] [11:08:19]  ===============================
[30/03/2020] [11:08:19]       sscanf plugin loaded.
[30/03/2020] [11:08:19]          Version:  2.8.1
[30/03/2020] [11:08:19]    (c) 2012 Alex "Y_Less" Cole
[30/03/2020] [11:08:19]  ===============================
[30/03/2020] [11:08:19]   Loaded.
[30/03/2020] [11:08:19]  Loaded 2 plugins.
As for the compiler, I'm using the SA:MP default compiler. I'll replace it with the one you developed.


Feature request: Provide state helpers like submitting, pristine

Description

Currently there is no native way to disable the submit button when a form is in a pristine state (has the same data as it did initially). This means that users are able to submit the form without form state change.

Currently there is no native way to disabled the submit button a form is in a submitting state (is being sent to the server). This means that users are able to submit the form multiple times without the UI blocking these requests. This has larger security implications.

It's a common pattern of form providers, for example Angular and Redux-form to provide state booleans that can be used for customising form behaviour. Here's the example from Angular's docs:

ng-valid is set if the form is valid.
ng-invalid is set if the form is invalid.
ng-pending is set if the form is pending.
ng-pristine is set if the form is pristine.
ng-dirty is set if the form is dirty.
ng-submitted is set if the form was submitted.

The way I am currently working around this is by overriding form behaviour and extending state, which is far from ideal as well as limited.
One way that I imagine this could work:
const Form = () => {
  const Buttons = ({submitting, pristine}) => {
    return <div>
      <button type="submit" disabled={pristine || submitting} />
    </div>
  };
  return (
    <Form schema={{foo:'bar'}}
          transcluded={Buttons} />
  )
};

This feature request is also touched on here: https://github.com/mozilla-services/react-jsonschema-form/issues/402
Version
0.43.0

I tried to rely on the status value in onChange in this jsfiddle but realized that we're switching between initial and editing while typing in a field, which is rather surprising and probably a bug to investigate.

any hacks around this one for the moment? or ways to accomplish this?


Single interface to ignore dependencies, configurations and CVEs

The idea of this feature request is to merge and discuss the two feature requests which provide a way to ignore specific dependencies, artifacts, gradle configurations and CVEs (#3 #7).
I think all these  requests should be done at once to share a common way to define ignored stuff.
My proposal would be to have as less methods as possible with different overloads (going from general => more specific):
ignore (configuration, artifact, CVE)

audit {

    // ignore a specific CVE in a specific artifact in a specific configuration
    ignore 'compile' 'vulnerable-library' 'CVE1234'

    // ignore all CVEs in a specific artifact in a specific configuration
    ignore 'compile' 'vulnerable-library'
    ignore 'testCompile' 'vulnerable-test-library'
    ignore 'classpath' 'vulnerable-plugin'

    // ignore all CVEs in a specific configuration
    ignoreConfiguration 'classpath'

    // ignore a specific CVE everywhere
    ignoreCVE 'CVE1234'

   // ignore a library/plugin in any configuration
   ignoreArtifact 'vulnerable-artifact'

   // only print warnings
   failOnError = false // already implemented
   failOnPluginErrors = false // don't break the build if a gradle plugin introduces vulnerabilities
}

I don't quite like the 3 specific methods ignoreConfiguration, ignoreCVE and ignoreArtifact but I don't think there is a better way to do this.
I'm not very savy with groovy, but I guess having Java overloads with different types would still lead to new up some objects (like ignore new CVE('1234').
Please tear this apart :-)

There already is a attribute named ignore which takes a list of artifacts (as stated in the docs):
ignore = [ 'org.dependency:thelibrary', 'net.awesomelibs:anotherlib:1.0.0' ]

We shouldn't break it and also shouldn't introduce confusion by having attributes and methods with the same name but having different meanings (taking artifact, configuration, ...)

=> [CVE-2012-1833]  Permissions, Privileges, and Access Controls (see https://ossindex.net/resource/cve/350388) => [CVE-2014-0053]  Permissions, Privileges, and Access Controls (see https://ossindex.net/resource/cve/359719) => [CVE-2014-2857]  Permissions, Privileges, and Access Controls (see https://ossindex.net/resource/cve/361888) => [CVE-2014-2858]  Improper Limitation of a Pathname to a Restricted Directory ("Path Traversal") (see https://ossindex.net/resource/cve/361889) => [Unconfirmed] Cross Site Scripting (XSS) in exception messages (see https://ossindex.net/resource/vulnerability/8402731112) => Cross Site Scripting (XSS) in selection values (see https://ossindex.net/resource/vulnerability/8402731113) => Fix XXE vulnerabilities (see https://ossindex.net/resource/vulnerability/8402731131)
would it make sense to take the ossindex id instead of cve?
and have something like
ignore = [ 'org.dependency:thelibrary', '8402731131' ]

An additional feature request has been added with some additional requirements for the dependency feature: https://github.com/OSSIndex/ossindex-gradle-plugin/issues/10

Typically because they only exist in dev and not production or because the vulnerability is in a feature within the package that isn't used by the project.
My concern is that by ignoring the entire package, I will miss if the developers of it introduce a new vulnerability into the package. So now nobody will be alerted and given the opportunity to assess the impact.
I think there is a general case, especially when running in a pipeline, to ignore specific vulnerabilities, within a given package, so that I can then choose to fail the build because a new vulnerability has appeared.

I have put together a short Wiki document to track some ideas taken from this and several other issues: https://github.com/OSSIndex/ossindex-gradle-plugin/wiki/Advanced-Ignore-Functionality
As a first step I will be implementing a Utility class/method which will be used to perform the filtering itself (and some test code). Then I will be implementing the config file fields required to control the filtering.
Comments and edits on the wiki alternatively on the issues themselves are welcome. Once I have a start to the code I will make a pull request which can be a single location for the discussion.

At long last the features have left "beta" and are official. The newest (non-beta) version is 0.3.21, with documentation on more advanced vulnerability exclusions described here: https://github.com/OSSIndex/ossindex-gradle-plugin#alpha-exclusions-advanced-vulnerability-management
Sorry for the delay in notification of this feature.
We are looking forward to any feedback and requests for improvements on these features. They have been in production-type testing for a while now and seem to be quite stable.
I will also take this opportunity to mention that there is a rather major release incoming which will be adding support for the OSS Index v3 REST API, which provides access to a new database with many more vulnerabilities and is being actively maintained.

I will also note at this time that moving to the new API (when available) will mean that vulnerability IDs are changing since the new API uses UUIDs. This is a one time change: we don't intend on changing IDs again.


Add execution bounds for stagefright bug(s)

cve-2015-1538-2 seems to cause a hang ... and because there is no timeout on the exec, it causes the whole app to hang.

Closed by pull #25


Feature/beams3 d restart grid

This implements the "-restart_grid filename" flag, which reads the (possibly modified) B_R, B_PHI, B_Z, S_ARR and U_ARR fields from a previous BEAMS3D run to conduct the simulation on. Kinetic profiles are supplied by the input namelist as usual, and interpolated according to the given S_ARR as with the other equilibrium options.

I'm going to say we should wait a few days on this.  What I'd like to do is implement a continue functionality which does two things.  First it'll initialize the background grids from a previous BEAMS3D run.  Second, it'll intialize the particles and distributions from a previous run, to continue the run.  The results are then written back into the continue file.  In this way a run can be continued.  To do this I'll need to implement a beams3d_continue_particles, beams3d_continue_wall, and probably change beams3d_restart_grid to beams3d_continue_grid.  Then the restarting of a grid just becomes a suboption of the others.

I need to use this branch together with the new RHS for AUG simulations. Should I change the function naming and the flag name to -continue, and we can add the other features to that once we get to it? Or should I just merge the branches locally for now?

Go ahead and change the function names and add flag -continue.


step_executor.py attribute bug

Got this error message today, but without trying to come up the MWE I'm wondering if it is obvious to eyeball and fix?
TRACE: Set _index to 0 of type <class 'int'>
  File "/scratch/midway2/gaow/miniconda3/lib/python3.6/site-packages/sos/step_executor.py", line 1920, in run
    res = Base_Step_Executor.run(self)
Traceback (most recent call last):
  File "/scratch/midway2/gaow/miniconda3/lib/python3.6/site-packages/sos/step_executor.py", line 1920, in run
    res = Base_Step_Executor.run(self)
  File "/scratch/midway2/gaow/miniconda3/lib/python3.6/site-packages/sos/step_executor.py", line 1512, in run
    if not g.valid() and statement[0] != ':':
AttributeError: 'list' object has no attribute 'valid'
DEBUG: Step extract_sumstats_1 sends exception 'list' object has no attribute 'valid'
DEBUG: Worker SoS_Worker-1 completes request 'step', <sos.parser.SoS_Step object at 0x7f..., ... (7 items)
DEBUG: Master receive a result AttributeError("'list' object has n...
DEBUG: Master received an exception
DEBUG: 3c5d884b72fecaae: 1 slots released from 1 active, 0 remain
  File "/scratch/midway2/gaow/miniconda3/lib/python3.6/site-packages/sos/__main__.py", line 372, in cmd_run
    executor.run(args.__targets__, mode='dryrun' if args.dryrun else 'run')
Traceback (most recent call last):
  File "/scratch/midway2/gaow/miniconda3/lib/python3.6/site-packages/sos/__main__.py", line 372, in cmd_run
    executor.run(args.__targets__, mode='dryrun' if args.dryrun else 'run')
  File "/scratch/midway2/gaow/miniconda3/lib/python3.6/site-packages/sos/workflow_executor.py", line 1409, in run
    raise exec_error
sos.workflow_executor.ExecuteError: [extract_sumstats_1]: 'list' object has no attribute 'valid'
[extract_sumstats]: 1 pending step: extract_sumstats_2
ERROR: [extract_sumstats_1]: 'list' object has no attribute 'valid'

This is actually caused by a bad input on my end, so i should be able to reproduce with MWE if you need it. When my input is good there is no problem.

In what sense the input is bad?

Here, easy to reproduce, I should have looked and provided it:
[1]
input: glob.glob('*.non-existing-suffix'), group_by=1, concurrent=True
print(_input)

it's glob.glob problem.


When Context API is stable, provide two documentation paths

When the Context API is stable, we want to provide examples. At the meeting today (Nov. 1), it felt like it would make sense to have two tracks in the documentation for different users:

For more casual users, a cookbook approach would be good, using the Context API.
For developers on the project, or users who want to go behind the Context API, lower-level examples would be helpful.

No action here until API is stable.

I think this is covered by the banner redesign: some users want "Getting Started", others "API", and some want "Theory". Closing as duplicate.


[BUG] Add dep fix for pydantic in thin client

Description of changes
Summarize the changes made by this PR.

Improvements & Bug fixes

#799 introduced a max version for pydantic but this change was not propagated to the thin client. This makes the same change in the thin client.

New functionality

...

Test plan
Existing tests for client

[ ] Tests pass locally with pytest for python, yarn test for js

Documentation Changes
None

Need to rebase on #1054


Support partition key for Kafka binding

A user needs to be able to specify a partition key when writing to a Kafka Topic.

Closed via #303


How to insert action and Icon

How do I insert action and Icon

Please look for this on StackOverflow.


Dotted lines?

Any plans for dotted line support? Dotted polygons?

I don't have any plans to add it - it would be a bit complicated to get this working with line joins. I'd consider a PR with it, but it would be best to come up with a plan first on how to deal with line joins and how it would be integrated it into the current code.

Closing this now - if someone is willing to do the work reopen and post your ideas.

In the meantime, I am using juwalbose's GraphicsLineRenderer for dashed lines (haven't investigated dotted but the repo also has that). Comment out the textures you don't need, download the ones you do need from core/assets and add Gdx.gl.glEnable(GL20.GL_BLEND) for transparency.


feat(async): add async I/O support

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

92 of 263 (34.98%)  changed or added relevant lines in 19 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-5.6%) to 94.437%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/Psl/Async/await.php
0
1
0.0%

src/Psl/Async/Exception/TimeoutException.php
0
2
0.0%

src/Psl/Async/Exception/UnhandledAwaitableException.php
0
3
0.0%

src/Psl/Async/all.php
0
4
0.0%

src/Psl/Async/later.php
0
6
0.0%

src/Psl/Async/any.php
0
8
0.0%

src/Psl/Async/run.php
6
14
42.86%

src/Psl/Async/Deferred.php
0
9
0.0%

src/Psl/Async/Internal/State.php
20
29
68.97%

src/Psl/Async/concurrent.php
0
9
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-5.6%

Covered Lines:
2903

Relevant Lines:
3074

💛  - Coveralls


Consider replacing OffsetDateTime with library Time class

OffsetDateTime is a critical but annoying piece of the library. I don't want external users of the library to have to mess with it, though there may be good reasons for keeping it around.
I would prefer to wrap it in a simple Time class that delegates the small chunk of behavior we need from it. If anything, we could get a much prettier toString representation and make it much easier to create an instance of the class.

Replacement completed and merged into master.


remove logic from frontend and move to separate file

Describe the bug
Remove any logic in frontend files like dark mode or any other logic present in frontend files as script tags should be moved to an external js file in public folder and linked in the header.ejs
Note:

Do mention if your are working under GSSoC'21.
If you want to work on an issue, you should check if it has already been assigned to anyone. If the issue is free you can comment /assign to get the issue assigned to you.
If you are raising a new issue and want to work on it then also you should comment /assign under the issue to get it auto assigned.
Please refrain from adding labels to your issue/pull-request on your own. It is the job of the Project Admin and the Mentors to review your issue/pull-request and add labels accordingly.
According to the level of the issue, respective time will be allotted under which the task needs to be completed/resolved by the assigned person. If the issue is not resolved within the given time, it will be assigned to the next person. In case of any discrepancies, the decision of the maintainer will be final.

level - 0: 2 days
level - 1: 3 days
level - 2: 4 days
level - 3: 5 days

/assign


AutoNBEATSx not in model dictionary

What happened + What you expected to happen
When saving an AutoNBEATSx model, it is impossible to read it back in currently as is since you end up getting a KeyError since MODEL_FILENAME_DICT in core.py does not have autonbeatsx as a key.
The current workaround for this is to rename the saved .ckpt file from autonbeatsx_0.ckpt to nbeatsx_0.ckpt, which is mildly annoying.
Versions / Dependencies
NeuralForecast 1.5.0
Reproduction script
models = [AutoNBEATSx(h = HORIZON,
                          loss = MAE(),
                          config = nbeatsx_config_space,
                          num_samples=10)]
nf = NeuralForecast(models=models, freq='B')
nf.fit(df=train_dataset)

nf.save(path='./nf_models/',
        model_index=None,
        overwrite=True,
        save_dataset=True)
nf2 = NeuralForecast.load(path='./nf_models/')

results in KeyError: 'autonbeatsx'
Issue Severity
Low: It annoys or frustrates me.

Hey @upadhyan,
Sorry for the inconvenience, I will take a look to add the AutoNBEATSx method.
For the moment you can get the generic version of NBEATSx-g to work using anNHITS with n_freq_downsample=1 like this:
models = [NHITS(h=horizon,                           # Forecast horizon
                input_size=2 * horizon,              # Length of input sequence
                loss=HuberLoss(),                    # Robust Huber Loss
                max_steps=1000,                      # Number of steps to train
                dropout_prob_theta=0.5,
                interpolation_mode='linear',
                stack_types=['identity']*2,
                n_blocks=[1, 1],
                mlp_units=[[64, 64],[64, 64]],
                n_freq_downsample=[1, 1],           # Inverse expressivity ratios, set to 1 for NBEATSx-g
                val_check_steps=10,                  # Frequency of validation signal (affects early stopping)
              )
          ]
nf = NeuralForecast(models=models, freq='M')
nf.fit(df=Y_train_df)


The mod menu GUI has some flickery problems

yeah so when i press tab to open the menu
it flickers but idk why

somehow the video didn't upload so here it is :
https://github.com/TobyAdd/GDH/assets/96695375/03118819-af79-4009-9e2b-ffabd658fa55

Disable Vertical Sync

I think i found the issue
the fullscreen is making the menu flicker but when i disable it, it doesn't do it

wait i accidentally closed it

i think the issue is the fullscreen mode since i tried without the fullscreen and it perfectly worked


minor spelling mistake

minor spelling mistake

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests


fix: rename docs folder to software_engineering

:tada: This PR is included in version 0.6.5 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


How do you validate radio buttons?

Hello
How do you validate radio buttons?
I do not see a validator in validators.js file

How you can validate it? Could you post a fiddle with example?

Hello
I have a created a fiddle here: https://jsfiddle.net/sjordan/p66mv49o/8/
Hope you don't mind, I expanded the question to:

How do I validate radio buttons? (In my example, one value must be selected before the form is allowed to be submitted)

How do I validate checkbox? (In my example, I want the checkbox to be checked before the form is allowed to be submitted)

Hi, thanks the fiddle. I updated: https://jsfiddle.net/p66mv49o/10/
So I used required validator for radios: validator: VueFormGenerator.validators.required
And created a custom validator for agree checkbox:
validator: function(value) {
	if (value !== true)
		return ["Please agree!"];
}

And you need to define onSubmit handler in the schema.

@icebob Thank you. I'll try to incorporate this into my code.

@icebob Thank you


updated privacy and policy css #663

changes that are done are listed below

Background Image:
Replaced the plain background with a nature-inspired image for a more engaging, wild-themed aesthetic.

Text Colors:
Updated text colors for better contrast and readability against the new background.

3.Container Styling:
Added a semi-transparent background to the content container, along with rounded corners and a soft shadow for a modern look.
4.Button Styling:
Improved button design with brighter colors, rounded edges, and hover effects for better visibility and interaction.
5.Responsive and Accessible:
Ensured the design is responsive across devices and adheres to accessibility standards.

Resolve the conflicts in the mentioned files. Ensure you pull all the latest changes before pushing your feature/bug fixes to the main branch. After resolving the conflicts, please open a new PR for review.
Thank you!


how to use gpu or somethingelse to increase the speed of prediction

I want to use vedio frame as the input, but the fps of the vedio get only 3-4fps

my fault, but unfortunately, tensorflow-gpu cannot work on my laptop whatever version it is. I have tried dozens of combination of cuda, cudnn and tf-gpu, and all of them don't make sense.


[Feature Request] Ability to enable gitdoc for a non active vscode project

Hi Team. Thanks for this great tool. I use this to sync my todo, notes and journal across different devices. I have all my notes, daily todo as part of a github repo called planner. Presently, I am able to sync (commit & push) to my github repo when I have planner project open in github.
However, the way I work is with help from VSNotes. This allows me to open my notes & todo from within any of my vscode projects.
Let's say I'm working on a VSCode python project foo, I can still open my notes & todo and update them ( without switching from VSCode project foot to planner. In my current workflow, gitdoc doesn't work as my gitdoc enabled project ( planner) isn't active as a VSCode project.
Is it possible to provide ability to enable gitdoc for a non active vscode project? Pleaset let me know if I'm unclear on my request here. Thanks.

This behavior is unfortunately out of the scope of GitDoc, and would be more appropriate for a CLI tool.


Fix the regression in pausing cds ack until cluster is in warming state

Signed-off-by: Vikas Choudhary<EMAIL_ADDRESS>
Commit Message:
Functionality of pausing the cds ack was introduced in https://github.com/envoyproxy/envoy/pull/5887. During the refactoring done in https://github.com/envoyproxy/envoy/pull/7236, it got broken.
There is also discussion about this regression on this issue which got closed on stale state.
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

/retest

cc @htuch

Thanks for contributing!
I'm trying to understand what cds-ack pausing scenario this PR is solving. Can you add a test that this PR fixes (this is also good as a regression test)?
We may also want to runtime guard this.

I'm trying to understand what cds-ack pausing scenario this PR is solving. Can you add a test that this PR fixes (this is also good as a regression test)?

Hey, while trying to add a test, I realized there is already a test for this CdsPausedDuringWarming and functionality is already working. When I looked closer, found out that my change is not needed and ack is paused from the loadCluster() itself. Hence closing the PR. Thanks for taking a look.


Mutagen section header prints when running pytest without mutants

The line
===== Mutagen =====

prints out below tests when running normal pytest with the mutagen plugin installed, even if mutations aren't set up for the project (and we are not running with the mutation flag).
Users might find this behavior slightly intrusive.

Fixed in 8a249ac


Create monorepo architecture

To enable the extractions of libraries and plugins out of the core we need a monorepo architecture to make development and version management simpler.

[x] use lerna for monorepo management
[x] use lerna in build/verify stage to check all projects
[x] automate tags/releases for main and develop
[x] automate versioning
[x] make sure husky checks all folders

Create a packages folder with all nuts and bolts of the core.

packages/

core/
cfg-core/
plugin-core-x/

Create a packages folder with all nuts and bolts of the core.

packages/

core/
cfg-core/
plugin-core-x/

In the end we chose the following structure:

packages/

core/
cfg-core/

plugins/

plugin-core-x/


Can't Save Changes

Subject: Can't Save Changes
Description:
Edit Profile
Results:
No save button
Backend version: develop-eaffe5a6
Frontend version: dependabot-npm-and-yarn-sentry-nextjs-7-46-0-a81c465b
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
Page: https://couchers.org/account-settings
User: michael_trepanier (27406)

#4071


Accessibility of runtime_deps and transitive deps

Hey,
We're (cc: @arifogel) having a heck of a time trying to understand how the IntelliJ plugin handles transitive deps. The issue we're having is that only direct compile dependencies (hjars for bazel-built or maven jars) are in External Libraries. When we're debugging, we're unable to see source code for or set breakpoints in the runtime_deps or the dependencies of our direct compile dependencies.
Adding them to the bazelproject, e.g., targets: @external_project//some/java_library does not make that library indexable.
Is there a different recommended approach to solve this problem?
Thanks!

We intentionally exclude transitive deps from the project for performance
reasons -- only deps (both direct and transitive) actually required to
resolve the source code are added to the project libraries.
One exception to this is that for locally modified files we include all
direct deps if "Blaze > Sync > Expand sync to working set" is checked.
So you won't be able to debug into transitive deps, unless they're required
to resolve some source file in your project, or are listed as a direct dep
of a target with modified source files, and that option above is enabled.
We never treat external libraries as 'source' code of the project for these
purposes.
On Wed, May 13, 2020 at 5:58 PM Dan Halperin<EMAIL_ADDRESS>wrote:

Hey,
We're (cc: @arifogel https://github.com/arifogel) having a heck of a
time trying to understand how the IntelliJ plugin handles transitive deps.
The issue we're having is that only direct compile dependencies (hjars for
bazel-built or maven jars) are in External Libraries. When we're
debugging, we're unable to see source code for or set breakpoints in the
runtime_deps or the dependencies of our direct compile dependencies.
Adding them to the bazelproject, e.g., targets:
@external_project//some/java_library does not make that library indexable.
Is there a different recommended approach to solve this problem?
Thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/bazelbuild/intellij/issues/1825, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE3KDEIZE4RIEPHO7V7UV4TRRMJZTANCNFSM4NAEWMOA
.

Thanks for the info!
I'm guessing this works for Blaze - there's a monorepo, no such thing as external deps really, since folks use copybara instead.
Seems an ill fit for Bazel where external projects is a recommended way to operate. (But I am generally aware Bazel support is not much of a concern for this team.)

You're right, it's not an ideal set of features for Bazel. Internally,
there's no concept of an external workspace, it's simply not supported by
Blaze.
I would personally enjoy spending time restructuring the plugin to better
support Bazel (there's so much potential there), but we don't have the
bandwidth unfortunately.
Note we have the same debugging issue internally (though it doesn't come up
often) -- we don't attach transitive deps to the project, so you can't step
into that code when debugging. One workaround would be to add those deps to
the target you're debugging (with 'expand to working set' enabled).
On Fri, May 15, 2020 at 12:16 PM Dan Halperin<EMAIL_ADDRESS>wrote:

Thanks for the info!
I'm guessing this works for Blaze - there's a monorepo, no such thing as
external deps really, since folks use copybara instead.
Seems an ill fit for Bazel where external projects is a recommended way to
operate. (But I am generally aware Bazel support is not much of a concern
for this team.)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/bazelbuild/intellij/issues/1825#issuecomment-629349896,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AE3KDEKCMPF6O2VZJC36RSLRRVTEXANCNFSM4NAEWMOA
.

I want to emphasize Brendan’s point- I think this specific issue is not related to blaze/bazel as the issue isn’t external workspaces but debugging transitive deps.
Brendan- there isn’t a setting or something to allow loading all transitive deps as external libraries? Sounds like this can be an easy fix which could be only available to Bazel.
Wdyt?

@ittaiz I might take a look at implementing such a feature, if at least to see whether it might be worth forking.

We could add that feature to the plugin -- JavaWorkspaceImport / JavaSourceFilter is the code which limits which deps are added as libraries.

Hi there! We're doing a clean up of old issues and will be closing this one. Please reopen if you’d like to discuss anything further. We’ll respond as soon as we have the bandwidth/resources to do so.

I don't think anything has changed with respect to why this is a big problem.

Please reopen if you’d like to discuss

I don't seem to have this power, FYI.


nuget.config: drop internal feed

We don't need this feed, and it is causing build problems during
release.

It's too bad that we cannot re-run only failed jobs, the macOS jobs seem to fail with an SSL connect error (which I assume is transient). The Ubuntu-20.04 job seems to fail because gvfs-helper was killed via SIGTERM (numeric: 15), which is somewhat odd, but probably just a flake because the other Ubuntu jobs seem to do Just Fine.


Change variable task to theTask to fix test

Change variable task to theTask to fix test

fixing in another branch

can we please change this to var @task instead?


fix: update highlight for today when date change

fix #15

Wait, it works, but why can I use the API in 0.0.15? 😲

@xyhp915 PTAL

Hi @xyhp915 I've tested it for several days and it works on my machine. Could you please take a look?

It's my bad for this. It works well! Will build a new release soon :)


Stage with merge conflicts warning still appears after all conflicts resolved

VSCode Version: 1.16.1
OS Version: Windows Server 2012 R2

Steps to Reproduce:

Do a git merge/rebase operation that causes merge conflicts
Using the Source Control pane, open each file with conflicts, resolve the conflicts, and save
Try to stage the file--even though all the conflicts are resolved (and all conflict markers removed), I still get the message "Are you sure you want to stage _______ with merge conflicts?"

This is annoying since I have to take extra time/clicks to confirm the dialog before moving on to the next file.
Reproduces without extensions: Yes

#33983


GH3545: Add DotNetClean alias (synonym to DotNetCoreClean)

DotNetCore

DotNet synonym

DotNetCoreClean
:arrow_right:
:new: DotNetClean

DotNetCoreCleanSettings
:arrow_right:
:new: DotNetCleanSettings

New DotNetClean aliases are being introduced
DotNetClean aliases contain the code of the existing DotNetCoreClean (rename/move)
Existing DotNetCoreClean aliases are forwarding calls to newly introduced DotNetClean aliases
New DotNetCleanSettings class is being introduced
DotNetCleanSettings class contains the code of DotNetCoreCleanSettings (rename/move)
The previous DotNetCoreCleanSettings is now empty and inherits from the new DotNetCleanSettings
Namespaces Cake.Common.Clean.DotNetCore.* have been preserved as to not introduce breaking changes
Unit Tests and Integration Tests remain the same, and call the old DotNetCore*** aliases, exercising the new DotNet*** aliases in the process

Closes https://github.com/cake-build/cake/issues/3545

@augustoproiete your changes have been merged, thanks for your contribution 👍


Missing x-v header

Describe the bug
The mandatory header x-v is not being returned
To Reproduce
Steps to reproduce the behaviour:

Call the discovery/status or the discovery/outages endpoint
Examine the header being returned

Expected behaviour
Return the x-v header as per DSB published standard

Thank you for getting in touch with us to raise this issue.
We have run replicated the issue using steps provided and cross checked against the standard.
We have logged the issue and will include a fix in a future release.

The fix for this issue has now been merged in to the main branch. https://github.com/ConsumerDataRight/mock-data-holder/pull/37


Generate interfaces classes when generateDataTypes=false with generateInterfaces = true

The PR that fixes the original issue did not address the following scenario:
Here's a simple case:
interface Animal {
   name: String
}

type Dog implements Animal {
   name: String
}

It generates IDog but not Animal.

Bug exists. Created PR with fix: https://github.com/Netflix/dgs-codegen/pull/285

PR is merged so I think it solves the problem

Fix available in 5.1.10

@berngp @npwork There is a same issue with Kotlin generator
https://github.com/Netflix/dgs-codegen/issues/330


Feature Request: Change file (and Interface?) name when using rename code action for a class

As described in the titel, it would be very nice if the lsp-rename method would also automatically adjust the filename if it is a class-rename and the containing file has the same name as the class, since you should always have the same file name as the class.
Additionally, I don't know if this would violate any LSP rules, but often you have a corresponding interface that has the same name as the class just with the "I" added as a prefix. Maybe if there is a match you could also change the interfaces name and its file name if it is machting?
Lastly but also least important there is often the naming convention to name a service as its class just with a lowercase letter, maybe this could also be included in the renaming?
If I missed any config where I could get this functionality, please let me know.
Thank you

+1

would be cool if it supports renaming .meta files for unity ppl - perhaps ability to define file matches like ["{className}.cs", "I{className}.cs", "{className}.cs.meta", "I{className}.cs.meta"]?


Online Tetris Game

What game are you using for this project?

This one, with the "back to basics" theme
We are running it on BlueStacks, while running the bot under Windows

Ok thanks so much


Unable to create index on M1 macbook pro with lancedb 0.3.3

Here's a minimal reproducible example with macOS Ventura 13.6.1 and lancedb==0.3.3
⚡  python3
Python 3.10.13 (main, Nov  1 2023, 17:29:04) [Clang 14.0.3 (clang-14<IP_ADDRESS>.1)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import lancedb
>>> uri = "~/data/lancedb"
>>> db = lancedb.connect(uri)
>>> num_items = 100
>>> embedding_dim = 384
>>> data = [{"vector": row, "item": f"item {i}"}
   for i, row in enumerate(np.random.random((num_items, embedding_dim)).astype('float32'))]
>>> tbl = db.create_table("my_vectors", data=data)
>>> tbl.create_index(num_partitions=16, vector_column_name="vector")
Illegal instruction: 4

I've seen identical behavior for macOS Ventura 13.5.1 and python 3.11
It's unclear to me that this is a OOM issue because the behavior is identical for num_items = 10 and num_partitions=1
Update: the issue cannot be reproduced with lancedb==0.3.2

Gonna look into this today. Stay tuned.

I was unable to reproduce this on an M2 air running macOS 13.5.2.  Can you use lldb to gather some more information?
% lldb python foo.py
(lldb) target create "python"
Current executable set to 'python' (arm64).
(lldb) settings set -- target.run-args  "foo.py"
(lldb) run
Process 50691 launched: '/Users/pace/micromamba/envs/lancedb/bin/python' (arm64)
Process 50691 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x0)
    frame #0: 0x000000019e853e64 libsystem_platform.dylib`_platform_strlen + 4
libsystem_platform.dylib`:
->  0x19e853e64 <+4>:  ldr    q0, [x1]
    0x19e853e68 <+8>:  adr    x3, #-0xc8                ; ___lldb_unnamed_symbol282
    0x19e853e6c <+12>: ldr    q2, [x3], #0x10
    0x19e853e70 <+16>: and    x2, x0, #0xf
Target 0: (python) stopped.
(lldb)

This snippet is just an example.  You will need to type lldb python some_script.py and then when that starts you will need to type run (you may need to install lldb).  Once it crashes it should show you something similar to the above.  The line with the arrow will contain the illegal instruction which might give us some clue as to what the cause is.  If you can also type bt and then press enter (after the crash) then lldb should give a stack trace which might help as well:
(lldb) bt
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x0)
  * frame #0: 0x000000019e853e64 libsystem_platform.dylib`_platform_strlen + 4
    frame #1: 0x0000000100755c70 _ctypes.cpython-312-darwin.so`string_at + 96
    frame #2: 0x000000010077c04c libffi.8.dylib`ffi_call_SYSV + 76
    frame #3: 0x000000010077974c libffi.8.dylib`ffi_call_int + 1208
    frame #4: 0x0000000100758750 _ctypes.cpython-312-darwin.so`_ctypes_callproc + 1216
    frame #5: 0x0000000100752280 _ctypes.cpython-312-darwin.so`PyCFuncPtr_call + 1208
    frame #6: 0x0000000100067ed8 python`_PyObject_MakeTpCall + 316
    frame #7: 0x0000000100183ca4 python`_PyEval_EvalFrameDefault + 54644
    frame #8: 0x0000000100175814 python`PyEval_EvalCode + 300
    frame #9: 0x00000001001eea74 python`run_mod + 228
    frame #10: 0x00000001001ee564 python`_PyRun_SimpleFileObject + 1536
    frame #11: 0x00000001001ed788 python`_PyRun_AnyFileObject + 268
    frame #12: 0x000000010021a660 python`Py_RunMain + 2684
    frame #13: 0x000000010021b2f4 python`pymain_main + 660
    frame #14: 0x00000001000024bc python`main + 56
    frame #15: 0x000000019e4cff28 dyld`start + 2236


Include PKAPI in non-default export

This allows people to do
import { PKAPI, /*other things*/ } from "pkapi.js"

Thanks for the PR! Guess we overlooked that one 😅


[Feature Request] maven-assembly-plugin时程序有问题

Checklist

[X] I searched exising issues and no one else requests similar feature.
[X] I think that 25%+ users are positive towards this feature.

Describe the feature
todo
Additional context
No response

打包exe


Make README more exciting and friendlier.

I edited the README to make it a bit nicer and more enticing for people landing from my Reddit post or other links.

Hmm, perhaps a nice picture would top it off?


Update request: anydesk 6.3.2 → 6.3.3

Package name: anydesk
Latest released version: 6.3.3

Current version on the unstable channel: 6.3.2
Current version on the stable/release channel: 6.3.2

[ x] Checked the nixpkgs pull requests

Notify maintainers
@cheriimoya
@shyim

Note for maintainers: Please tag this issue in your PR.

Add a :+1: reaction to issues you find important.

A brief note:
Currently Anydesk is not working for me on my NixOS system, a few days ago it started crashing when I try to open it. The same issue is affecting other Linux distros: openSUSE, Arch, and the Steam Deck. According to the reddit post, the solution is to update to version 6.3.3. Thanks all.

Same problem for me

Same problem for me

Its already merged, you just need to wait a little bit longer until the new version is available in nixpkgs unstable

If you run this snippet in the terminal
NIXPKGS_ALLOW_UNFREE=1 nix run --extra-experimental-features 'flakes nix-command' --impure github:nixos/nixpkgs/ccc4ef55e3a40f3bcd92396a8ba932a13071cfca#anydesk

it should download and run AnyDesk 6.3.3. Its what I've been using and will use until the package is in nixpkgs unstable.


Initial Data Loading code

Converts the data into a pandas.DataFrame object for easier processing.

@peterasujan please review!

Good stuff, @dylandaniels! My main comment would be to resolve the style/linting errors for the two .py files. I've also left a couple line comments on the diff.

There are still a couple styles issues to fix--I'll incorporate them later but we should merge this in for now.

To be most proper, this should probably be rebased to remove the need for the merge commit (4d5a8c4).

Looks good, thanks!


fix: replace  with ~/work/jx for nested repositories in gitlab

Signed-off-by: ankitm123<EMAIL_ADDRESS>

/approve

/hold

/hold cancel


e2e-test

/claim #466
Issue Reference(s):
Fixes #466
Build & Testing:

[x] I ran cargo test successfully.
[x] I have run ./lint.sh to address and fix linting issues.

Checklist:

[x] I have added relevant unit & integration tests.
[x] I have updated the documentation accordingly (if applicable).
[x] I have performed a self-review of my own code.

added test for untested in server
if server_ctx.blueprint.server.enable_cache_control_header {
    if let Some(ttl) = req_ctx.get_min_max_age() {
      response = response.set_cache_control(ttl as i32);
    }
  }

@wrath-of-god
We should achieve ~100% coverage in server.rs
https://app.codecov.io/gh/tailcallhq/tailcall/pull/511/blob/src/http/server.rs
PS: Im scared to tag you every time.


Add Ant build support for code coverage

This pull request derives from #269. So needs to be handled after that.

Closes #147
This pull request allows to generate the code coverage report using Ant build script.
The new property xspec.coverage.enabled controls that. (default false)
How to use
Command line

Clone this pull request.
Just add -Dxspec.coverage.enabled=true to your usual command line. For example,ant -buildfile /path/to/xspec/build.xml -lib /path/to/saxon-ee.jar -Dxspec.xml=/path/to/your.xspec -Dxspec.coverage.enabled=true

==> *-coverage.html will be generated in the xspec subdirectory.

Oxygen

Clone this pull request. For example, clone it into /test/xspec/.
In Oxygen, open your .xspec file.
In the Transformation Scenarios pane, duplicate Run XSpec Test.
In the Options tab of Edit Ant Scenario dialog, specify /test/xspec/ in Working directory.
In the Parameters tab, set xspec.project.dir = /test/xspec/
Click New in the Parameters tab and add xspec.coverage.enabled = true.
Click New in the Parameters tab and add xspec.coverage.html = ${cfd}/${cfn}-coverage.html.
In the Output tab, set ${cfd}/${cfn}-coverage.html in Open.
Click OK to close the Edit Ant Scenario dialog.
Apply the new duplicated transformation scenario.
==> XSpec Ant begins collecting code coverage. Oxygen will open the coverage report in your default browser.

Test
Using the files in #197, I manually verified that this pull request generated the same HTML file as the current master.
No automated tests for now. It should be addressed by #195.
Further work

Document xspec.coverage.enabled in Wiki.
(xspec.coverage.html should be kept undocumented unless xspec.result.html is documented...)

Although labelled as enhancement, this PR is actually required for testing. The following tests depend on this PR.

Regression test for code coverage (#326)
Test code coverage report files (as well as XML, HTML and JUnit) (#341)
Fix issue 214 (coverage-report.xsl fails to parse CDATA) (#342)

So, in short, I hope this PR get merged asap and move forward :)

@yamahito
This will close #147. Please let us know if you have a concern.

@AirQuick: this is the next pull request to review on my list. I'll try to review by the end of this week, please bear with me for few days.

@AirQuick: I tried to run it on the command line and on oXygen but I got inconsistent coverage reports, I'm not sure if it is an issue in my configuration and want to double check with you first.
Command line
Environment: Linux
Shell: bash
Ant version: 1.9.6
Saxon EE: 9.7
Command:
ant -buildfile build.xml -lib /home/cirulls/Documents/programming/saxon-9ee/saxon9ee.jar -Dxspec.xml=tutorial/escape-for-regex.xspec -Dxspec.coverage.enabled=true

I get this coverage report:

This is what I expected and it's the same coverage report I would get via xspec.sh -c. So far so good.
oXygen
oXygen version: 20.0
Ant version: 1.9.8 (default on oXygen 20.0)
Saxon EE: <IP_ADDRESS> (default on oXygen 20.0)
I followed your instructions for setting the transformation scenario, here is my setting:

However, I get a different coverage report:

I would expect the same report but instead I get no missing target (i.e. nothing is highlighted in red).
Could you double check if you get the same report at your end?
I initially suspected that Saxon EE was not picked up in my transformation scenario settings but a) I could not see any option in the transformation scenario to specify which Saxon processor to use; b) I would expect the transformation scenario to fail in case Saxon HE is used by default.
Can you see any obvious mistake on my oXygen settings? Could you share your configuration?

That difference comes from the Saxon version difference.
Using the current master + command line, Saxon 9.6 and 9.8 behave differently in the same way as you found. It's my impression that the 9.8 output (and your oXygen output) is correct.

And that's why I filed #196, submitted #197 (now #299) and used the files in it for testing this pull request.

Thanks for your comments, it makes sense now. I tried the same with the tutorial files for code coverage you committed in #299 and I got identical code coverage reports on both the command line and oXygen 20.0 so this is good.
I'll finish off my review and keep you posted, I expect to merge this soon into master.

Document xspec.coverage.enabled in Wiki.

Done:

Running with Ant
Code Coverage

Looks good, thanks for updating the documentation.


Simplified Chinese translation

My friends and I have finished the Chinese translation, please add this into the mod ::)
If you want to add credits, just write "星际拓荒讨论群群友".

Thanks! Sure, I'll add you to credits and ingame credits as well!

@REME-easy seems like ingame credits don't support any other language, just english

How I can give you a credit there?

Oh, "Chinese Outer Wilds lovers" is also OK, because many people have contributed.
Thanks for your mod too!!

done! will make an update soon. Thx for contributing guys, hope you liked this mod!


Updates fetch-mock

This PR updates fetch-mock to use the branched version that implements fetch globally.
todo: test failures due to issues with snapshots

This has already been done


Check that --params option was added

See nunit/nunit#1829

Checked and all the code is complete. Closing without action.


check(pod): Check bad events related to pod

check(pod): Check bad events related to pod
Checks and ensures that there are no bad events
related to a Kubernetes pod.
Signed-off-by: Johnson Shi<EMAIL_ADDRESS>

Inspiration for this work was due to a recent debugging experience I went through where a pod had unhealthy events - it may be a good idea to expose this as part of the tool.
~/Dev/osm(main) » kubectl describe pod bookstore-v1-6cb4994855-lrvn5 -n bookstore |  grep -e Warning
  Warning  FailedMount  5h51m                  kubelet            MountVolume.SetUp failed for volume "envoy-bootstrap-config-volume" : failed to sync secret cache: timed out waiting for the condition
  Warning  FailedMount  5h51m                  kubelet            MountVolume.SetUp failed for volume "kube-api-access-rw8wr" : failed to sync configmap cache: timed out waiting for the condition
  Warning  Unhealthy    5h51m                  kubelet            Startup probe failed: Get "http://<IP_ADDRESS>:15903/osm-startup-probe": dial tcp <IP_ADDRESS>:15903: connect: connection refused
  Warning  Unhealthy    72m (x9 over 5h14m)    kubelet            Liveness probe failed: Get "http://<IP_ADDRESS>:15901/osm-liveness-probe": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
  Warning  Unhealthy    67m (x2 over 72m)      kubelet            Readiness probe failed: Get "http://<IP_ADDRESS>:15902/osm-readiness-probe": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

Test output:
./bin/osm-health connectivity pod-to-pod bookstore/bookstore-v1-6cb4994855-lrvn5 bookstore/bookstore-v2-79fc8bc8f9-7rh6h
...
...
12  Checking whether pod bookstore-v2-79fc8bc8f9-7rh6h has events of type!=Normal  -- FAIL: pod 'bookstore-v2-79fc8bc8f9-7rh6h' has events that are of 'type!=Normal' - run 'kubectl get events --field-selector type!=Normal' to inspect events


Remove usages of path with getUrl function

Will be done in https://github.com/enonic/nextxp-demo/issues/738


feat: Implement LeftMark join to fix subquery correctness issue

Which issue does this PR close?

Closes #13135
Rationale for this change
In https://github.com/apache/datafusion/pull/12945 the emulation of an mark join has a bug when there is duplicate values in the subquery. This would be fixable by adding a distinct before the join. This can also be resolved by using a LeftMark join. The LeftMark join exists in several other query engines. This will help us produce correct answers for TPC-DS (https://github.com/apache/datafusion/issues/4763)
Note: This patch does not implement the full null semantics for the mark join
described in http://btw2017.informatik.uni-stuttgart.de/slidesandpapers/F1-10-37/paper_web.pdf which which will be needed if we and ANY subqueries. The version is this patch the mark column will only be true for had a match and false when no match was found, never null.

What changes are included in this PR?
This patch instead implements a LeftMark join with the desired semantics and uses that. The LeftMark join will return a row for each in the left input with an additional column "mark" that is true if there was a match in the right input and false otherwise.
This join is then used in decorrelate predicate subqueries to simplify the
implementation and fix a correctness issue.

Are these changes tested?
Yes, new unit and fuzz tests.

Are there any user-facing changes?
Fix of correctness issue with decorrelated subqueries.

I merged up from main to get a clean CI run

FYI, I created an epic for the other join types which are I think worth investigating.
https://github.com/apache/datafusion/issues/13181

🚀  -- thanks again @Dandandan and @eejbyfeldt


Add the "Support net neutrality" widget

See https://github.com/fightforthefuture/battleforthenet-widget

Sorry, I don't agree with adding this to this page but thanks anyway.


sec_mem: add note about the minimum size parameter.

Add a note indicating that the minimum size parameter to CRYPTO_secure_malloc_init() should be small.

[x] documentation is added or updated

I think also saying it must be smaller than the first value.

@richsalz good suggestion.  Out of interest what values do you guys use?
I'm half tempted to ignore the value and use sizeof(SH_LIST) (rounded up to the nearest power of two) directly.

I've added a second commit for consideration.  This calculates the smallest legal minsize value, rather than relying on being passed something sane.
If this is acceptable, I'll revert the type change from #11003 and update the documentation.

I don't like enforcement of a policy for minsize because it really depends on what the app is doing.  Perhaps make "zero" be "please choose a default"?  Akamai proxy server uses 16 as minvalue.

Zero as default is reasonable.  The default will be twice the size of a pointer which will be 8 or 16 on most systems.
I still can't see a compelling reason for using anything bar the smallest value.  Fragmentation shouldn't be a problem, neither is the extra time cost.

If you have limited size for secure heap and you only want RSA/ECDSA keys and don't care about negotiated session keys.

I still don't see a reason :(
I'll just assume that there is one.

The secure heap is partitioned into "minsize" blocks, and record-keeping is done with standard heap structures.  If you have limited secure heap, you might as well make minsize by similar to your keysze.

Ah, the bitmap overhead.  That's reasonable.

Ping @openssl/committers for a review.

Rebased in the hopes that some of the build problems disappear.

Travis is the perpetual timing out build.  All good otherwise.

Merged to master after trivial rebase fix: <= changed to == and an assert relocated.


exit with staus code 1 if decaf fails

It should probably not exit with status code 0

@bouk Any other comments on this? It'd be awesome to get this in, currently my team is blocked on this and would love to be able to use your npm package

bump @bouk

@juliankrispel Tagging you since you were the last person to commit

Anyone want to merge this in? Been sitting here for quite a while

Hey sry will look at it in the morning - thx
Julian Krispel-Samsel
rainforestqa.com
goodafternoon.co

On Mar 7, 2017, at 3:33 AM, Kyle Holzinger<EMAIL_ADDRESS>wrote:
Anyone want to merge this in? Been sitting here for quite a while
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Looked now and merged - thx a ton!

Thanks man! No worries


RC Spot-Check Test: Density 1.1.3-rc.1

RC Spot-Check Test
Mentions: @jonathanolson @samreid
Simulation links

github repository for issues
phet top-level directory
sim: all_phet.html
phet-io wrapper index
link to phet-io zip file

Test Matrices
General Test:

[x] Tester = KW, Platform = Win 11 Chrome, Firefox, iPad, Time =1.5
[ ] Tester = NS , Platform = macOS 14 + safari , Time = .5

PhET-iO Test:

[ ] Tester = , Platform = , Time =
[ ] Tester = , Platform = , Time =

Additional Features Test:

[ ] Tester = , Platform = , Time =
[ ] Tester = , Platform = , Time =

Features included
PhET-iO
~Alternative Input~
~UI Sound~
~Sonification~
~Description~
~Voicing~
Focus and Special Instructions

In https://github.com/phetsims/phet-io-wrappers/issues/551 it was discovered that Density 1.1.2 throws an exception with ?webgl=false on a device that doesn't support webgl (like our puppeteer browsers that test CT). Not great! This RC fixed it in my local testing, but it would be best for QA to have some time with it.

Ensure no regressions on a couple browsers (including safari/firefox) with ?webgl=false and ?webgl=true.
If you are able to test with your GPU turned off, that would be great too. For example on chrome, the setting is called "use hardware acceleration when available".
Test the above items in your PhET-iO studio spot check please.

I don't think we need a ton of time on this or anything, as the change was pretty small. But it would be good to make sure that this complicated sim didn't break from it.
Here is the expected view when running with ?webgl=false:

For QA...

General features

What to Test

Click every single button.
Test all possible forms of input.

Test all mouse/trackpad inputs.
Test all touchscreen inputs.

If there is sound, make sure it works.
Make sure you can't lose anything.
Play with the sim normally.
Try to break the sim.
Test some query parameters. (See QA Book for a
list of query parameters.)
When making an issue, check to see if it was in a previously published version.
Try to include version numbers for browsers.
If there is a console available, check for errors and include them in the Problem Description.
As an RC begins and ends, check the sim repo. If there is a maintenance issue, check it and notify developers if there
is a problem.
As the RC ends, notify the developer of any new QA credits that need to be added.

PhET-iO features

What to Test

Make sure that public files do not have password protection. Use a private browser for this.
Make sure that private files do have password protection. Use a private browser for this.
Make sure standalone sim is working properly.
Make sure the wrapper index is working properly.
Make sure each wrapper is working properly.
Launch the simulation in Studio with ?stringTest=xss and make sure the sim doesn't navigate to youtube
For newer PhET-iO wrapper indices, save the "basic example of a functional wrapper" as a .html file and open it. Make
sure the simulation loads without crashing or throwing errors.
Load the login wrapper just to make sure it works. Do so by adding this link from the sim deployed root:/wrappers/login/?wrapper=record&validationRule=validateDigits&&numberOfDigits=5&promptText=ENTER_A_5_DIGIT_NUMBER

Further instructions in QA Book
Conduct a recording test to Metacog, further instructions in the QA Book. Do this for iPadOS + Safari and one other
random platform.
Conduct a memory test on the stand alone sim wrapper (rc.1).
Test one platform combination with ?phetioDebug=true on the Studio and State wrapper.
If Pan/Zoom is supported, make sure that it works when set with PhET-iO State.
Test that the sim works offline:

Click the link to the phet-io zip file (at top of issue) to download the zip file.
Unzip it to a spot locally.
Open index.html by double clicking it on your desktop or in a Finder-view.
It should look like the standalone version of the sim in PhET-iO brand.

Accessibility features

What to Test

Specific instructions can be found above.

Make sure the accessibility (a11y) feature that is being tested doesn't negatively affect the sim in any way. Here is
a list of features that may be supported in this test:

Alternative Input
Interactive Description
Sound and Sonification
Pan and Zoom
Mobile Description
Voicing

Test all possible forms of input.

Test all mouse/trackpad inputs.
Test all touchscreen inputs.
Test all keyboard navigation inputs (if applicable).
Test all forms of input with a screen reader (if applicable).

If this sim is not in this list or up to date there, make an
issue in website to ask if PhET research page links need updating. Please
assign to @terracoda and @emily-phet.

Screen Readers
This sim may support screen readers. If you are unfamiliar with screen readers, please ask Katie to introduce you to
screen readers. If you simply need a refresher on screen readers, please consult the
QA Book, which should have all of the information
you need as well as a link to a screen reader tutorial made by Jesse. Otherwise, look over the a11y view before opening
the simulation. Once you've done that, open the simulation and make sure alerts and descriptions work as intended.

Platforms and Screen Readers to Be Tested

Windows 10 + Latest Chrome + Latest JAWS
Windows 10 + Latest Firefox + Latest NVDA
macOS + Safari + VoiceOver
iOS + Safari + VoiceOver (only if specified in testing issue)

Critical Screen Reader Information
We are tracking known screen reader bugs in
here. If you find a screen reader bug,
please check it against this list.

Keyboard Navigation
This sim supports keyboard navigation. Please make sure it works as intended on all platforms by itself and with a
screen reader.
Magnification
This sim supports magnification with pinch and drag gestures on touch screens, keyboard shortcuts, and mouse/wheel
controls. Please test magnfication and make sure it is working as intended and well with the use cases of the
simulation. Due to the way screen readers handle user input, magnification is NOT expected to work while using a screen
reader so there is no need to test this case.

FAQs for QA Members

There are multiple tests in this issue... Which test should I do first?
Test in order! Test the first thing first, the second thing second, and so on.

How should I format my issue?

We typically assign the developer who opened the issue in the QA repository.

My question isn't in here... What should I do?
You should:

Consult the QA Book.
Google it.
Ask Katie.
Ask a developer.
Google it again.
Cry.

When I was fuzz testing on the debug version of the sim in firefox, I saw these errors pop up while switching tests. Such as switching from testing with ?webgl=true to ?webgl=false. They didn't come up in the tests themselves, so I'm not sure what to think.

@zepumph I wasn't sure how to turn off GPU in safari.

I was also unable to find a way to do so on Firefox.

Thank you! The quick turnaround time here is much appreciated.


Removing private SSH key

I noticed you had commited a private ssh key to your repo.
"I know. It was intentional."
Sorry to bother you then. Feel free to ignore this PR.
You know you can also secure private data while keeping it under source control.
"I didn't notice. What is this file? Is it a problem?"
This can be a very bad thing
"I keep accidentally typing git add ., any way I can prevent that from being an issue?"
There are a couple of steps you should take immediately:

Avoid commands like git add . and git add *. It's better to be more explicit when you can.
Assume your key is compromised. Unassociate it from any accounts you are using it for and generate a new key.
Store your keys in a location outside of your project.
Use a .gitignore file to prevent accidental commits of certain files.

Github also has a page about how to remove sensitive data from a repo.
Hope this PR finds you well

Thank you,I have not notice it.
2018-01-31 17:02 GMT+08:00 Edward Romano<EMAIL_ADDRESS>
I noticed you had commited a private ssh key to your repo.
"I know. It was intentional."
Sorry to bother you then. Feel free to ignore this PR.
You know you can also secure private data while keeping it under source
control https://keybase.io/blog/encrypted-git-for-everyone.
"I didn't notice. What is this file? Is it a problem?"
This can be a very bad thing
http://www.securityweek.com/github-search-makes-easy-discovery-encryption-keys-passwords-source-code
"I keep accidentally typing git add ., any way I can prevent that from
being an issue?"
There are a couple of steps you should take immediately:

Avoid commands like git add . and git add *. It's better to be more
explicit when you can.
Assume your key is compromised. Unassociate it from any accounts
you are using it for and generate a new key
https://help.github.com/articles/reviewing-your-ssh-keys/.
Store your keys in a location outside of your project.
Use a .gitignore file https://git-scm.com/docs/gitignore to
prevent accidental commits of certain files.

Github also has a page about how to remove sensitive data from a repo
https://help.github.com/articles/removing-sensitive-data-from-a-repository/
.
Hope this PR finds you well
You can view, comment on, or merge this pull request online at:
https://github.com/newbiechen1024/NovelReader/pull/32
Commit Summary

Remove file containing private key

File Changes

D .ssh/id_rsa
https://github.com/newbiechen1024/NovelReader/pull/32/files#diff-0
(27)

Patch Links:

https://github.com/newbiechen1024/NovelReader/pull/32.patch
https://github.com/newbiechen1024/NovelReader/pull/32.diff

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/newbiechen1024/NovelReader/pull/32, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ANKHJeXxzwRKnSUHnvl9SsNkPC5QE1-gks5tQCwxgaJpZM4RzoQL
.


fixes(HMS-4620): add RHEL 8.10

SSIA
@loadtheaccumulator can you guide me what else I need to do in order to add RHEL 8.10?

Ugh. @lzap Test failing, and not sure why 81 hasn't failed before now.
 --- FAIL: TestValidateRepo (0.00s)
    --- FAIL: TestValidateRepo/validate_major#01 (0.00s)
        repo_config_test.go:27: "81" not found: ""
FAIL
FAIL	github.com/redhatinsights/edge-api/config	0.006s

I see the line in the test. It should only be failing in the test, and not elsewhere in the code.
It should get passed through, although, I am not sure what value IB is expecting.

Right, it appears that image builder has now two forms for distros: rhel-89 and rhel-8.10. I have rewritten the test to use regular expression to capture both formats.
What is next? Do we need to add this to UI?

UI is next. I can also use 8.10 for my next test this morning via the API


Update the Readme.md file

📚 Documentation
update the Readme.md file to tell people how to start the project locally using Docusaurus
Add relevant screenshot or video (if any)
No response
Additional context
No response

Closed by #339


⚠ Bofrost.de has degraded performance

In 30afa93, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1237 ms

Resolved: Bofrost.de performance has improved in ffd18d7 after 13 minutes.


Update adobe.github.com/data/server.json

adobe.github.com/data/server.json needs to be updated, because data is outdated.
"1 year 5 months since last commit"

Interesting... It shows "20h..." on my side.

Did you full refreshed the page? (Ctrl+Maj+R) What browser are you using?
Thanks for the issue filing though!

It seems that request to http://server-adobe-github.herokuapp.com/ fails and and outdated json from adobe.github.com/data/server.json is loaded instead (as a backup?) when browsing using HTTPS protocol.
https://adobe.github.io/ "1 year 5 months since last commit"
http://adobe.github.io/ "3 h 38 min since last commit"


Use rustup in serde-syntex-example instead of multirust

Multirust is deprecated.

@homu r+

:pushpin: Commit 7afb8b5 has been approved by oli-obk

:hourglass: Testing commit 7afb8b5 with merge a52e7f5...

Coverage remained the same at 69.5% when pulling 7afb8b52ae5823f5d41d28bf566d82e7157bb960 on dtolnay:rustup into 58fa30200708cd1ccc91d2bbea0b620f69b5397b on serde-rs:master.

:sunny: Test successful - status


Add a few missing dots, remove some extraneous dots, fix a typo

Well done article, much appreciated! 😃

Glad you liked it @d1vanov  I appreciate the PR :)


Add support for mocking GL Contexts

During discord discussion of #660 , Ben initially suggested moving the included tests to integration rather than the unit folder. However, these tests do not use the GL functionality directly, and only need a valid-seeming context to instantiate the shapes.
We agreed that having a way to mock the GL context would be helpful to keep these tests pure, possibly using monkey patching.

Fixed in master, so closing.


Cannot get Vaccination data for germany Error: Corrupted zip : can't find end of central directory

adapter v0.6.8
pi4
Node.js v12.20.1
NPM 6.14.10
coronavirus-statistics.0	2021-02-07 11:19:19.020	info	(29795) Terminated (ADAPTER_REQUESTED_TERMINATION): All data handled, adapter stopped until next scheduled moment coronavirus-statistics.0	2021-02-07 11:19:18.793	error	(29795) Cannot get Vaccination data for germany Error: Corrupted zip : can't find end of central directory coronavirus-statistics.0	2021-02-07 11:15:02.414	info	(29795) starting. Version 0.6.8 in /opt/iobroker/node_modules/iobroker.coronavirus-statistics, node: v12.20.1, js-controller: 3.2.13 host.raspberrypi	2021-02-07 11:15:00.072	info	instance system.adapter.coronavirus-statistics.0 started with pid 29795 host.raspberrypi	2021-02-07 11:03:57.370	info	instance system.adapter.coronavirus-statistics.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) coronavirus-statistics.0	2021-02-07 11:03:56.843	info	(29678) Terminated (ADAPTER_REQUESTED_TERMINATION): All data handled, adapter stopped until next scheduled moment coronavirus-statistics.0	2021-02-07 11:03:56.688	error	(29678) Cannot get Vaccination data for germany Error: Corrupted zip : can't find end of central directory
getting these errors. uninstall reinstall nothing helped.

solved in latest


bugs fixed with distinct; more tests

Codecov Report

Merging #41 (695d2bc) into main (d6afd80) will increase coverage by 3.19%.
The diff coverage is 19.23%.

@@            Coverage Diff             @@
##             main      #41      +/-   ##
==========================================
+ Coverage   44.23%   47.42%   +3.19%
==========================================
  Files          37       37
  Lines        3436     3462      +26
==========================================
+ Hits         1520     1642     +122
+ Misses       1852     1752     -100
- Partials       64       68       +4

Flag
Coverage Δ

go_tests
47.42% <19.23%> (+3.19%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

xopjson/attributes.go
47.96% <12.50%> (+10.16%)
:arrow_up:

xoptest/testlogger.go
51.87% <100.00%> (+8.04%)
:arrow_up:

basegroup.go
42.39% <0.00%> (+1.84%)
:arrow_up:

xopjson/jsonlogger.go
59.22% <0.00%> (+1.94%)
:arrow_up:

xopconst/attributes.go
44.89% <0.00%> (+2.04%)
:arrow_up:

span.go
54.23% <0.00%> (+10.16%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Fix grammar in alert after authorising account.

Thanks

Even though this has already been merged, technically the word data is plural not singular. Not a big deal though.

http://english.stackexchange.com/questions/39838/is-group-singular-or-plural


Engine does not compute child node dimensions properly if scene selector element has padding

When a scene selector element has padding, the engine uses the content size plus padding as the default size for child nodes.
An example may be seen at:
https://github.com/peacechen/famous-carousel
I've worked around the issue by wrapping the scene selector div within another container div.  The container div has padding, while the inner scene selector div does not.  To more easily see the issue, change the selector in example/index.js from .slideshow to .slideshow-container.  Run npm run example to build and run the server.
Notice how .famous-dom-renderer is correctly sized to the container dimensions (sans padding), but the .famous-dom-element slide nodes are sized to the container dimensions with padding.

Hello!
New message, please read http://10servis.com/to.php?rpj1
<EMAIL_ADDRESS>


Speed Alterations

A series of speed tweaks to make docbuilder faster. Fixes #53.

Both codeblocks tests failed on 68817a91cc35807329402a8c89bc8dcfdfd7a8d9.

Seems that in the documentation produced, blank lines are not being ignored by Docbuilder.

Last commit made 0 difference.

One test failure still:
FAIL: Test to see if code blocks indent correctly when compiled to Markdown
Traceback (most recent call last):
File "/home/rof/src/github.com/shakna-israel/docbuilder/tests/test.py", line 276, in test_markdown_indented_code_block
assert False
AssertionError:
-------------------- >> begin captured stdout << ---------------------
Indented code block failed to compile to Markdown.
Expected:     print('This is an indented code block.')
Recieved:     print('This is an indented code block.')```

PEP8 Failure
FAIL: Test that Docbuilder does comply with PEP8.
Traceback (most recent call last):
File "/home/rof/src/github.com/shakna-israel/docbuilder/tests/test.py", line 45, in test_pep8_complicance
"Found code style errors (and warnings).")
AssertionError: Found code style errors (and warnings).
-------------------- >> begin captured stdout << ---------------------
docbuilder.py:145:9: E265 block comment should start with '# '
docbuilder.py:146:45: E231 missing whitespace after ','

This is working as of d4dfef6, however, we can probably still get some more speed out of this.

Closing request. Should be merging to 0.5-dev, not master.


Key

floating for idle animation.
add a shine at random intervals (just an animation added on top of where the key is going to be)

Related to #18

Add point light to key


test(cypress): Adds image comparison, heatmap test, artifact upload, …

…single spec execution

Current implementation has rendering differences between local builds and CI.  I'm not sure this can be fixed, but if there are ideas let me know.

These changes are also in #549, so closing in favor of that PR.


Add support for Tables.jl interface?

I would be really nice if TupleVectors would support the Tables.jl interface, in the same fashion as StructArrays.jl and TypedTables.jl

This would be great. I've never done this before, ok to assign us both?

Sure! We can use ShapedAsNTArray as a template - the Tables.jl interface only need very few methods.

Not passing yet, but here's a start:
https://github.com/cscherrer/TupleVectors.jl/pull/29


[type:refactor] removed unnecessary singleton

removed unnecessary singleton of SignUtils
Make sure that:

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

Codecov Report

Merging #4230 (08466b4) into master (f6d40a5) will decrease coverage by 0.20%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master    #4230      +/-   ##
============================================
- Coverage     70.66%   70.46%   -0.21%
+ Complexity     7294     7270      -24
============================================
  Files           973      973
  Lines         27136    27126      -10
  Branches       2410     2407       -3
============================================
- Hits          19177    19113      -64
- Misses         6494     6548      +54
  Partials       1465     1465

Impacted Files
Coverage Δ

...java/org/apache/shenyu/common/utils/SignUtils.java
94.44% <ø> (-5.56%)
:arrow_down:

...rg/apache/shenyu/admin/model/entity/AppAuthDO.java
78.18% <100.00%> (ø)

.../shenyu/admin/service/impl/AppAuthServiceImpl.java
77.64% <100.00%> (ø)

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

.../client/server/consul/ShenyuConsulConfigWatch.java
58.33% <0.00%> (-27.09%)
:arrow_down:

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

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

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

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

... and 13 more

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


Implement Quickstart command

The power it up will also have to change, eg BBB - power up whilst holding the tiniest, hardest to hold button possible

@Page- I'll be printing the device instructions as the UI very soon (in this PR).


For readability in custom hooks, export type signatures of various functions via type aliases

When writing custom hooks, the type signatures can get really ugly. I think it would be useful to define type aliases to the type signatures of some functions, such as useTickEffect and capturesWith.
For example, without such a thing, this is what the full type signature of subscribeTo' looks like:
subscribeTo'
  :: forall a m output slots
   . { push :: a -> HookM slots output m Unit
     , props :: { capturesWith :: CapturesWithEqFn rows
                               -> (MemoValues -> HookM slots output m (Maybe (HookM slots output m Unit))
                               -> (forall hooks. Hooked slots output m hooks (UseEffect hooks) Unit))
                               -> HookM slots output m (Maybe (HookM slots output m Unit))
                               -> (forall hooks. Hooked slots output m hooks (UseEffect hooks) Unit)
                , subscribe :: (a -> HookM slots output m Unit) -> HookM slots output m Unit
                }
     }
  -> ({ state :: Maybe a } -> { state :: Maybe a } -> Boolean)
  -> (a -> HookM slots output m Unit)
  -> Hook slots output m UseEffect Unit

Here's what it looks like when we add type aliases:
subscribeTo'
  :: forall a m output slots
   . { push :: a -> HookM slots output m Unit
     , props :: { capturesWith :: CapturesWith slots output m (state :: Maybe a)
                , subscribe :: (a -> HookM slots output m Unit) -> HookM slots output m Unit
                }
     }
  -> CapturesWithEqFn (state :: Maybe a)
  -> (a -> HookM slots output m Unit)
  -> Hook slots output m UseEffect Unit

-- | Type signature for the `eqFn` value in
-- | ```
-- | Hooks.capturesWith eqFn { state } Hooks.useTickEffect do
-- |   someHookMAction
-- | ```
type CapturesWithEqFn rows = { | rows } -> { | rows } -> Boolean

-- | Type signatures for `Hooks.capturesWith`.
type CapturesWith slots output m rows =
  CapturesWithEqFn rows
    -> (MemoValues -> UseTickEffect slots output m)
    -> UseTickEffect slots output m

I agree this reduces the verbosity of something like subscribeTo', but I don't think that I would like to add this to the Hooks library for a few reasons:

I think the Fairbairn threshold applies to type signatures as well, especially type synonyms; I try to only add type synonyms when it reduces verbosity for a very common case, but not if it makes things nicer for a special use case. I don't yet think that libraries exporting functions using the captures function is a very common case. But I could change my mind in the future!

Users can add this type synonym to their code if they find it improves the readability of the function they're writing, like subscribeTo'. It's not needed that the Hooks library itself implements this, and as I've maintained more libraries over time I've found it's a good idea to keep the library core small when the cost is not high. Essentially, this puts (1) in the hands of the user writing this case; users in app code won't do this very often, if ever.

As a matter of style, I don't like type synonyms that hide functions except for very commonly-established patterns or newtypes needed for instances like ReaderT. I find that it makes it harder to see what arguments you need to supply and where and I end up having to look up the functions within the type. This might just be my own style, but for Hooks I'd like to stick to it where possible.

I'm willing to disregard these points if the benefit seems to be there, namely that introducing the new types will significantly ease a common situation (esp. for app users, not library authors) and it's not easy to implement the same thing in the library / app.

For example, if it turns out every Hooks-based library ends up doing something like this, then I'd be a lot more open to introducing this to the library itself. But it's too early to say that now.

I agree. It's too early to say.
I'll close this for now. If we ever want to reconsider it again after more time has passed, let's reopen and continue discussion. I'll also update halogen-hooks-extra to remove that type signature.

At the very least, can we fix the type signature for captures and capturesWith? While they are accurate as a can resolve to HookM slots output m (Maybe (HookM slots output m Unit)) -> (Hook slots output m hooks UseEffect Unit), can we be more explicit with that type signature? That is partly what led me astray when working on migrating select to a hook version.


[FINERACT-1678] Loan accounts stayed locked business event

Description
We raise a business event at the ond of the Loan COB with the loan IDs that styed locked.

not sure what the current rules are with the business event stuff... just putting it out there:

suffix Event.java => move to package "org.apache.fineract.xxx.event"
suffix Configuration.java => move to package "org.apache.fineract.xxx.configuration"
suffix Tasklet.java => move to package "org.apache.fineract.xxx.task"

... maybe for a later refactoring session... will approve.


Adding step 4 in the rundown README.md

I have added step 4 in the rundown at the bottom it is needed also for VM The script however says If "Vm reboot now"

hi peter. before i had to update step 4 in the README.md (focus on UEFI + correct grammar), grin and the linked grub.txt since bios is irrelevant (see their wiki update) in this context.
as far as i remember, syslinux is the default bootloader when using a VM. In this case, step 4 is not necessary, which is why step 4 does not appear in testing and the install.sh will inform the user "if VM:reboot right now".
If GRUB was the bootloader in your VM, could you please let me know what additional steps you took? this was a hasty change that leaves room for improvement, and i do not have extensive experience with VMs and less time for "sight" than last year. thx - you are the 1st direct contributor.


Titles for sections / section groups

Visiting https://ambuda.org/texts/ramayanam/ just shows a grid of numbers:

For navigation, it would be good to add titles: would be nice to have at least "Bālakāṇda", "Ayodhyākāṇda" etc, and maybe even titles for individual sargas.
(Not very proud of the following, but example from https://shreevatsa.net/ramayana/sarga/ , titles copied from https://www.valmikiramayan.net/ — of course the titles are very ad-hoc and inconsistent but given GitHub / making it editable on the actual website, we could probably make them better.)

Of course the same is true (titled would help) for https://ambuda.org/texts/mahabharatam/ or even https://ambuda.org/texts/shatakatrayam/


Problem with ">lake build bin"

Hi, I tried running

lake build bin

and the result was:

error: unknown target bin

Could you help me?

I am using:
$ lean --version
Lean (version 4.0.0, commit ec941735c80d, Release)
$ lake --version
Lake version 5.0.0-ec94173 (Lean version 4.0.0)

Just saw this.
Use lake build nqueens as there is no executable called bin.

It worked! Thanks!


[BUG] DataGrid clrDgSelected mutates array of selected items

Select one ...  (check one with "x")
[X] bug
[ ] feature request
[ ] enhancement

Expected behavior
The clrDgSelected binding on DataGrid should not mutate the array of selected items, but create a new array. It should not change anything if the binding is one way. This is required for OnPush change detection and Redux / ngrx workflows.
Actual behavior
A clrDgSelected binding mutates the array by pushing new items. This breaks Redux, ngrx, and OnPush change detection. It should instead clone the array.
Reproduction of behavior
https://stackblitz.com/edit/clarity-light-theme-v11-miey3g
Select items and open console to see error.
Environment details

Angular version: 5.2.1

Clarity version: 0.11.1

Browser: [ all ]

Thanks, we'll need to investigate this a bit further

This is fixed into v2.4.10 and v0.11 is out of support so I'm closing this.


Allow empty response content

Closes #238

Nice work @radowit 👍 This looks good to me, so happy to accept it as is 🙂 Thanks!
I'll release a new version now.


Color is too dark

Hey, this project is really cool!
However, I am feeling really hard to see clearly on the screen. Everything is just so dark. The box boundaries, the background, the text.
Please consider make a brighter theme.

Thanks @lclalalalala for bringing this up! I won't be able to fix this right away since other issues are in the pipeline, but I will definitely be adding support for themes in general.

Hey @iostreamer-X, if you don't mind I can start working on this.

Hello @IbrahimHamshari, that sounds great!
Feel free to join slack to discuss. Or we can do it here on github.

Hey @iostreamer-X , can i work on this as well ?

Hey @SahilLamba0008 sure! I have assigned the issue to you. Please check out this discussion for more context #38.

Hey @SahilLamba0008 sure! I have assigned the issue to you. Please check out this discussion for more context #38.

Before I start coding, I’d like to confirm if I’ve understood the task correctly and if my proposed approach aligns with your expectations. Please feel free to correct me if I’m off track anywhere.

I plan to modify theme.json as :
{ "dark": {  "base": "vs-dark",  "inherit": true,  // others ... }, "light": {  "base": "vs",  "inherit": true,  // others .... } }

Then, I’ll add a button in monaco-editor.tsx to toggle the theme. I’ll use either a Zustand store, local storage, or session storage to persist the theme selection across page reloads or revisits.

Hey @SahilLamba0008 let's continue this here.


Delay on save

If auto-save is enabled or you save often, it generated too many history files for only small changes.
Some cooldown timer / delay on history generation would be a great option to have, like:

create a new history file if the last one is older then 5 minutes

Why not... Good idea...

Fix in version 1.16.0
I added a settings local-history.saveDelay to specify the delay in seconds after which local-history is saved and so avoid too many history files.


docs don't define the term "length"

The API docs talk about the "length of the bar", eg in
https://docs.rs/indicatif/0.13.0/indicatif/index.html#templates

len: renders the total length of the bar as integer

but they don't explain whether this is the length of the visual bar, in characters, or the total amount of work to be done (e.g. the total amount of data to copy). From looking at the source it seems it's the latter. Would be nice to say this in the docs.

Just adding.
It's the latter, and if you look at example just above, it shows {pos}/{len} hinting further that it's the total amount of work to be done.
bar.set_style(ProgressStyle::default_bar()
    .template("[{elapsed_precise}] {bar:40.cyan/blue} {pos:>7}/{len:7} {msg}")
    .progress_chars("##-"));

Also when you call a ProgressBar::new() you pass it len.

I've tweaked the description in e3bd36b to hopefully be a little clearer.


Method for slowing down the tests

Reasons for adopting a new feature:
Protractor needs a method for specifying a delay between changing of each visual element so that QA engineers and other people not familiar with Protractor, can observe what is happening at each step. It is possible to enter manual browser.sleep() everywhere in your code, but for a few hundred lines of tests, it would mean a lot of code duplication. It would be great if we could just set a "speed factor" in the configuration and have the tests run in the browser in a reasonable speed that it can be observed by a third-party without knowledge of the code.
Is this a breaking change?
No, it would just be an additional optional functional that doesn't break anything.
[Edited to conform to feature request template]

Could you please update your request with the information for feature requests in the issue template?
I don't see how this is a dramatic improvement over browser.pause. You can also record your tests or use a service like SauceLabs that does something similar for you.

@NickTomlin Please the revised version. Basically, as a developer we can definitely do browser.pause() to debug, but in a real-life situation where you would have to demo it to others, it is good to have a version that automatically goes through each statement with delays in-between. If protractor doesn't want to offer an in-house solution, do you know how it could be done manually?
Thanks!

@philoniare you can record video and slow down playback instead

var origFn = browser.driver.controlFlow().execute;
browser.driver.controlFlow().execute = function () {
var args = arguments;
// queue 100ms wait
origFn.call(browser.driver.controlFlow(), function () {
return protractor.promise.delayed(200);   // here we can adjust the execution speed
});
return origFn.apply(browser.driver.controlFlow(), args);
};
This code worked out for me, add it in your beforeEach and you'll notice protractor runs a little slower, allowing anyone to see what's happening :)

This might be a nice thing to include in Blocking Proxy @mgiambalvo

This should be covered by https://github.com/angular/blocking-proxy/issues/14

above provided cod is not working at my end getting below error:
TypeError: Cannot read property 'controlFlow' of undefined


Add verification that values of COG have not changed in COG examples notebook

We need to add a section in our COG examples notebook that demonstrates existing methods for verifying that data values remain unchanged post-conversion to COG (Cloud Optimized GeoTIFF) format. This addition will directly address recent queries about data integrity during format conversion.
Ensuring data consistency through conversion processes is crucial for maintaining the integrity of our datasets. To enhance user trust and provide clear guidance, it's important to showcase the methods we employ to verify that the values in our datasets stay consistent before and after being converted to COG format. Including these methods in the COG examples notebook will serve as a valuable reference for users and stakeholders.
cc: @wildintellect

@omshinde recently put together a good example of this on a project. Going to ask for a contribution to this guide.


Start Daemons in Docker Image

Obviously, we don't start our containers with the /sbin/my_init script, that is provided by our Phusion base image.
The startup script /sbin/my_init needs to be executed as root user and can be further customized to allow additional daemons to be started. I tried replacing the sleep infinity command in job.go with /sbin/my_init, which didn't work due to the different users (root vs user). Do we have another idea on how to execute this task as root instead (either through Nomad during the execute call or using some Linux mechanism, such as the setuid bit for the file)?

The main reason for providing /sbin/my_init as startup script in Phusion base image is proper handling of child processes. Starting additional daemons was another issue being addressed by this script. However, starting additional daemons could be done in other stages of Nomads job management. So, what really matters is a solution for proper handling of child processes
sleep infinity clearly does not solve that problem. For obvious reasons the sleep command is not aware of any child processes at all. Starting and eventually stopping additional daemons will therefore result in zombie processes overcrowding the process table over time.
Instead /bin/sh -c 'sleep infinity' might be executed initially. As a matter of consequence /bin/sh becomes the PID 1 process being able to properly handle child processes and SIGCHLD signals. sleep infinity becomes a never ending subprocess which in turn prevents its parent process from terminating. To implement this behavior lines 20 and 36 in job.go need editing.

If the developer team wishes to allow additional daemons to be started at boot time and therefore might claim a noteworthy amount of system resources even in prewarmed state, a sufficient means might be the use of Dockers ENTRYPOINT command or --entrypoint command line option. The TaskCommand and args config options at lines 20 and 36 in job.go should then be treated differently, i.e. as default values for cases where no ENTRYPOINT was defined in the Docker image.
Using ENTRYPOINT will enable providers of execution environments to run another service as PID 1 process according to their particular use case. If someone wishes to start more than one daemon, the cron command would be sufficient as the entrypoint. In either case the Poseidon documentation should clearly state that only non-terminating commands with the ability to handle child processes, i.e. services, are suited as startup commands.

If the developer team wishes to allow running /sbin/my_init as startup script, then instantiating and prewaerming containers should be done as root. As a matter of consequence every subsequent exec call on existing, prewarmed containers should then be executed using the -u option of the docker exec command to set the user to user. This should prevent normal end users from gaining root access on containers or the Poseidon/Nomad system.

Thanks for your thoughts and the work you've done. Based on your requirements and your feedback, I drafted https://github.com/openHPI/dockerfiles/pull/23 and #215 to solve this issue.
Unfortunately, Nomad does not allow to specify a different user for executing a command within an allocation in their nomad alloc exec command (see documentation) as opposed to Docker with docker exec. Therefore, we're using the /sbin/setuser script available in our images to achieve this functionality.

With support in CodeOcean (https://github.com/openHPI/codeocean/pull/1377), all-new Docker images (see here or below) and the PR in #215, this feature is implemented and available.