make backend-run fails

The make backend-run` command in the readme fails for me on latest master.
$ make backend-run

cargo run -p backend -- --frontend_folder packages/playground/dist --port 4000
    Finished dev [unoptimized + debuginfo] target(s) in 0.15s
     Running `target/debug/backend --frontend_folder packages/playground/dist --port 4000`
thread 'main' panicked at 'Command backend: Short option names must be unique for each argument, but '-h' is in use by both 'host' and 'help' (call `cmd.disable_help_flag(true)` to remove the auto-generated `--help`)', /home/joshy/.cargo/registry/src/index.crates.io-6f17d22bba15001f/clap_builder-4.3.0/src/builder/debug_asserts.rs:115:17
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
make: *** [Makefile:133: backend-run] Error 101

The issue seems similar to this one https://github.com/mozilla/rust-code-analysis/issues/997 Both about clashing -h options. I notice there is no Cargo.lock file committed, so maybe this happens because of changing dependencies.
Let me try to fix it the same way.

Great, thanks! Indeed, this happened somehow because of a recent Clap update, thanks!

https://github.com/paritytech/ink-playground/pull/732 fixed this and the new CI config provided  by https://github.com/paritytech/ink-playground/pull/734 and https://github.com/paritytech/ink-playground/pull/735 should prevent these types of problems in the future.


Restic autocompletion does not work in Fish shell when adding RESTIC_PASSWORD_FILE in /etc/environment

Output of restic version
restic 0.16.0 compiled with go1.20.7 on linux/amd64
Expected behavior

Install fish shell (the current version: 3.6.1)
Run fish in any terminal
Type $ sudo restic <Press TAB>  in any terminal to show auto completion, that works fine as expected.

Steps to reproduce the behavior (Issue)

/etc/environments adds  RESTIC_PASSWORD_FILE=/no_password_file
Reboot
Try to type  restic <TAB>  in fish shell, auto completion does not work.
The issue is caused by adding RESTIC_PASSWORD_FILE in /etc/environments if there is no password file or this password file is not readable for normal users except admin/root.
But bash and zsh  have no issue.

Do you have any idea what may have caused this?
/etc/environments adding  RESTIC_PASSWORD_FILE=/no_password_file  breaks auto-completion of restic in fish shell if the password file is not readable for users.
But bash shell and zshshell have no issue with that.
Do you have an idea how to solve the issue?
Remove RESTIC_PASSWORD_FILE=/... in /etc/environments , then reboot. The issue is fixed.
But that is not nice.

This can be reproduced using RESTIC_PASSWORD_FILE=/sdgsdf/ restic __complete backup.


Small error in documentation

I'm not sure if i'm right or wrong, so that why i didn't create a PR, but i thing there a small error here
https://github.com/SergioBenitez/Figment/blob/c730bdf644e8ee0d39c82a6fdc6bd58bd551fa61/src/providers/env.rs#L243-L254
I think we should see this at the line 254
// We now have `FOO=100`, `BAR_FOO=hi`, and `foobar=hi`.

the map in the documentation is looking for something that start with foo_, not just foo

Good catch! I think I meant to have foo_bar as an original env var here. Fixing now.


Stop waiting for ripsaw crd to delete when cleaning up

Added --wait=false when deleting ripsaw crd as it was frequently hanging during CI.

Is this still a problem we need to address?

This can be closed, because --wait=false only results in a background deletion of the objects and thus doesn't address the problem directly. However given that we no longer maintain infra/other operators with in Ripsaw, I don't think this would be needed.


filteredTypes disable interfaces does not work

monaco-editor version: 0.18.0
Browser: Chrome
OS: Windows 10
Steps or JS usage snippet reproducing the issue:
The new feature filteredTypes does not work with interfaces.
Using the Monaco playground:
https://microsoft.github.io/monaco-editor/playground.html#creating-the-editor-hello-world
Use this testcode:
monaco.editor.create(document.getElementById("container"), {
	value: "function hello() {\n\talert('Hello world!');\n}",
	suggest: { filteredTypes: { interface: false } },
	language: "javascript"
});

Open the suggestions in the editor and the interfaces are still visible.

My guess here is that's because those aren't only interfaces. If you look into lib.dom.d.ts you'll find two definitions of e.g. AbortController. One is an interface the other one is a variable declaration:
/** A controller object that allows you to abort one or more DOM requests as and when desired. */
interface AbortController {
    /**
     * Returns the AbortSignal object associated with this object.
     */
    readonly signal: AbortSignal;
    /**
     * Invoking this method will set this object's AbortSignal's aborted flag and signal to any observers that the associated activity is to be aborted.
     */
    abort(): void;
}

declare var AbortController: {
    prototype: AbortController;
    new(): AbortController;
};

If you test with the following code, the interface Test is not shown in the suggestion list:
monaco.editor.create(document.getElementById("container"), {
	value: "interface Test {}\n\nfunction hello() {\n\talert('Hello world!');\n}",
	suggest: { filteredTypes: { interface: false } },
	language: "typescript"
});

However, I don't know if there is another filter you could apply to hide those members.

You can see all suggestion items and their corresponding icons by adopting https://microsoft.github.io/monaco-editor/playground.html#extending-language-services-completion-provider-example and replacing createDependencyProposals like this:
function createDependencyProposals() {
    // returning a static list of proposals, not even looking at the prefix (filtering is done by the Monaco editor),
    // here you could do a server side lookup
    return Object.keys(monaco.languages.CompletionItemKind).filter(kind => Number.isNaN(Number(kind))).map(kind => {
        return {
            label: kind,
            kind: monaco.languages.CompletionItemKind[kind]
        }
    });
}

You are right, the suggestions show the global vars and not the interface. I saw it by mistake because it correctly shows "interface" as type of the variable.


(Bug) Claimed Amount isn't updates after the first claim

I claimed 9.77 but my records did not capture nor sum up this 9.77
Created via Reamaze:
Link: /admin/conversations/i-claimed-9-dot-77-but-my-records-did-not-capture-nor-sum-up-this-9-dot-77
Message:
Today I claimed and got 9.77 $; somehow I saw my iPhone screen still at 1$ like yesterday screenshot.  Did not accumulate today’s claim. Kindly advise what went wrong in my account. Thanks for your assistance and clarification.
Hsieh Jinyu
9/10/2020

Browser: (iPhone) Mobile Safari 13.1.2 on iOS 13.6.1

if re-login the app, the amount becomes corrected

@serdiukov-o-nordwhale @mauriguz
We have been testing it and We can't reproduce the issue.
Details:
-Tested on iOS 13.6.1, Mobile Safari.
-The first claim in the account.
-Also, we tested in our accounts on other devices and it works that is expected.
-We searched issues related into the Analytics dashboard (Sentry, Amplitude) and didn't see any log.
-We are waiting for the next claim (We see that the issue happened in the second claim).

@serdiukov-o-nordwhale ask user to report again if still happens after next claim


Fix for #650: Generate friendly class names

(Addresses #650)
I'm giving this one another try, with the latest version (plus my suggested fixes from PRs #893 and #900).
I've been working from a build off this branch for a couple of weeks now, with no adverse side-effects. This has resulted in this kind of rendered HTML:

...

...which at this point, my brain quickly reads as (by ignoring the hashes):

...

I find that vastly more helpful, for debugging purposes, than a sea of hashed classes that mean nothing to me.

Proposed API
Users can pass in a string as the last parameter of their calls to styled, like so:
// Renders as `c-Label-sOm3h4Sh`
const Label = styled("label", {...}, "Label")

This proposed solution can be combined with a babel plugin, to make friendly class names possible with no extra effort, for those using Babel.

Related Discussion
There was a related discussion at #677, but the solution proposed there by the Stitches team (defaultProps) was removed from the v1 API.

why is this being blocked?

why is this being blocked?

I'm not sure it's being blocked, so much as the Stitches team has been focused elsewhere; to my knowledge, it is not an intentional blocking.

Should we add tests for the feature?
I can take over a unit test.

Oh, good point. I think I had done so already in my old commit; I'll see if I can find them and add them here. Thanks!

I've added some tests to both core and react packages, and changed that confusing variable name.

Hope this PR gets merged soon

Hope this PR gets merged soon

@guipolitano Sadly, i don't think it's possible to get this merged as is as the API conflicts with another stitches API which is composing n number of styles into one component
const Button = styled('button', {...styles}, {...morestyles}, anotherStyledComponent)

To be clear, We love this feature and we know how important it is for the reasons outlined in the PR but we just need to think more about the API in order to maintain the DX that everyone loves about Stitches
We will think more about this and hopefully come back with a plan/decision for the API sometime next week and discuss it with @LucasUnplugged and everyone in here.

@guipolitano Sadly, i don't think it's possible to get this merged as is as the API conflicts with another stitches API which is composing n number of styles into one component

const Button = styled('button', {...styles}, {...morestyles}, anotherStyledComponent)

@hadihallak  my code shouldn't conflict with that usage, because it only applies if there are at least 2 arguments, and the last argument is a string. In your example, only the first argument is a string, so it should still work as intended.

That's true but it's re-using the same API which we've so far only reserved for styling so i'm wondering if we can do it differently so that it can be more clearly documented and easily readable for someone who isn't familiar with Stitches and reading the code for the first time
Maybe we could add a method or something similar that more explicitly tells the user what's going on behind the scenes.
We will think this through and get back and discuss things here with you

That makes sense, @hadihallak. Something like this would indeed be clearer:
const Button = styled('button', {...}).named('Button').

I'm not even sure if that's (realistically) possible, so didn't even attempt it.

Hope this PR gets merged soon

@guipolitano Sadly, i don't think it's possible to get this merged as is as the API conflicts with another stitches API which is composing n number of styles into one component
const Button = styled('button', {...styles}, {...morestyles}, anotherStyledComponent)

To be clear, We love this feature and we know how important it is for the reasons outlined in the PR but we just need to think more about the API in order to maintain the DX that everyone loves about Stitches
We will think more about this and hopefully come back with a plan/decision for the API sometime next week and discuss it with @LucasUnplugged and everyone in here.

Sadly =/.
Maybe it wouldn't be better to use babel-plugin, just as Styled-Components do? I had try to create one, but i know nothing about it so I couldn't achieve it.

@guipolitano
yeah that's actually one of the main reason we need this feature. to enable us to automate the process of creating stable hashes and friendly classNames which is currently not possible as we have no API underneath to support it yet

@guipolitano yeah that's actually one of the main reason we need this feature. to enable us to automate the process of creating stable hashes and friendly classNames which is currently not possible as we have no API underneath to support it yet

Understood, hope you guys find a way. Thx for the great job, im loving to use Stitches with Radix. :)

Closing in favor of #1005

Closing the loop here: withConfig has been introduced after this issue was closed, achieving the desired behavior. It's still missing in the docs, but instructions can be found here.


[Event Request] table 7001 "Price List Line" - OnAfterCopySourceFrom

Dear ALAppExtensions team,
On behalf of 4PS I would like to request integration event 'OnAfterCopySourceFrom' to be added to procedure 'CopySourceFrom' in  table 7001 "Price List Line".
    procedure CopySourceFrom(PriceListHeader: Record "Price List Header")
    begin
        "Source Group" := PriceListHeader."Source Group";
        "Source Type" := PriceListHeader."Source Type";
        SetSourceNo(PriceListHeader."Parent Source No.", PriceListHeader."Source No.");
        "Source ID" := PriceListHeader."Source ID";
        OnAfterCopySourceFrom(PriceListHeader, Rec); //**4PS>MS.n
    end;

    [IntegrationEvent(false, false)]
    local procedure OnAfterCopySourceFrom(PriceListHeader: Record "Price List Header"; var PriceListLine: Record "Price List Line")
    begin
    end;

If 'var PriceListLine: Record "Price List Line"' is replaced with 'IncludeSender = true', that's fine for us too.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 53020.


Comment out log_file options in glance configs

Comment out log_file options in glance config files
to make log output appear in g-api and g-reg screen windows,
like the other server daemons...

+1 on jesse's comments, but lgtm for now


appsody deploy picks the APPSODY_PORT from the config of the stack image instead of the application image

When appsody deploy modifies the app-config.yaml, it has to pick a port to assign to APPSODY_PORT. Today it does this by examine the env variables in the stack image. This seems dangerous to me - for instance you may have different ports (for debugging purposes) exposed in Dockerfile-stack that you do not have in your final application image. This was the problem that caused issue: #461
You can demonstrate this by setting different ports in Dockerfile-stack and running appsody deploy --generate-only and inspecting the app-config.yaml file.
imho, Appsody deploy should pick the ports based on those exposed by the built application image, not the stack image.

@henrynash Do you mean the CLI should look for the ports exposed in Dockerfilerather than theDockerfile-stack`?

@skoh7645 Essentially yes. In fact what deploy does in run a docker inspect on the stack image, extract the Config section and parse it for the ports. So I am saying we should be inspecting the final application image (which is built using Dockerfile, not Dockerfile-stack) to parse for ports.


Lambda Alias does not expose name property

What happened?
When creating lambda Aliases, it's missing the name property in the forProvider section to set the name of the Alias. The resource name from the metadata session is used instead. This means:

We can't follow our resource naming scheme for lambda aliases, without trickling the name down to the aliases themselves
We can't use the same alias name for two different functions, as there is a name clash between the resources
Our CI/CD pipelines then cannot rely in the consistency of alias naming for automation

How can we reproduce it?
Create two lambda Alias resources with the same name, but pointing to different functions, as part of the same deployment.
apiVersion: lambda.aws.upbound.io/v1beta1
kind: Alias
metadata:
  name: production
spec:
  forProvider:
    functionNameSelector:
      matchLabels:
        testing.upbound.io/example-name: my_first_function
   <...>

apiVersion: lambda.aws.upbound.io/v1beta1
kind: Alias
metadata:
  name: production
spec:
  forProvider:
    functionNameSelector:
      matchLabels:
        testing.upbound.io/example-name: my_first_function
   <...>

It won't work since there will be a name clash between the two resources.

Can you use crossplane.io/external-name annotation ?


Fix registration links

MKdocs links don't automatically link like they do in the Github preview, so this link was created as raw text.

Haha, I just totally forgot to put in the actual links! Thanks!!!


Cleanup null safety experiment from DDC modular test suites

We should no longer be using the experiment flag in the modular suites.

The experiment flag is no longer used and null safety modes are properly tested in different suites as of https://dart-review.googlesource.com/c/sdk/+/285922.


DRAFT: E2E ProcessBlockPoS Testing

Current dependencies on/for this PR:

feature/pos-fast-hotstuff-consensus

PR #742

PR #746

PR #747

PR #748   👈

This comment was auto-generated by Graphite.

closed in favor of #762


Open Android Apps

Can this be used to open Android apps (on an Nvidia Shield) remotely via a PC?
Thanks

You can control your Nvidia Shield remotely with mouse and keyboard, so you could probably open Android apps that way.

Thanks, what I was really after is if there was a way I could send an ADB command to the shield to get it to launch a specific app. Not sure if this can be done a different way. I essentially want to be able to program a button on my streamdeck which will send the command (probably via a batch file) to open a different app on the Shield.
scrcpy looked like it could be a good way to do that.

adb is sufficient: https://stackoverflow.com/questions/4567904/how-to-start-an-application-using-android-adb-tools


Not Working - Subscribing to a channel with a dynamic name

Hello,
I've added actioncable-vue to my project. All is excellent! Just one detail that has me stumped.
Example 3. Subscribing to a channel with a dynamic name.
https://github.com/mclintprojects/actioncable-vue#3-subscribing-to-a-channel-with-a-dynamic-name
I've defined a computed method for the channel name to use in the channels: definitions. It seems the computed method is not available. [this.channelId]:. If I replace "this.channelId" with a litteral, "CourseStatusChannel_1106" it works great! Channel name is: ["CourseStatusChannel_1106"]:
I am defining the channels in a component of my app.
What do you think?
Thanks for you help!
Best,
Paul

Hmm. I just noticed that I never wrote tests for that feature. Also, you're right. It doesn't work. I'll try to find a fix and get back to you as soon as I do.

@mclintprojects Thank you! I look forward to your solution! I like what you've put together.
Looks like you do freelance work. What's your favorite kind of work? Are you available?

@PaulRHanson316 I think the solution is to create a variable to hold your Vue instance and then use to that access the computed property.
It'd look something like this:
const vue = new Vue({
  channels: {
    [vue.channelId]: {}
  },
  computed: {
    channelId(){
      return 'CourseStatusChannel_1106';
    }
  }
});

Try that and let me know if it works so I'll update the README.

@PaulRHanson316 My favourite kind of work in order of preference: Vue.js (Frontend) > Kotlin (Mobile) > Rails (Backend). Yes, I'm currently available.

I'm not getting it to work. Seems it might have to do with the scope at the point it's defining the channels key. Inside the channel methods the scope access works great for the computed methods.

For vue.channelId, vue is not defined.

Wait! I got it!
I moved the channels definition from the component to app.js and referenced window.store to get the course id from the store.
Thank you!
if (element != undefined) {
        window.store.state.course = JSON.parse(element.dataset.course)
        window.store.state.sadministrator = JSON.parse(element.dataset.sadministrator)
        window.store.state.administrator = JSON.parse(element.dataset.administrator)

        const application_wizard_app = new Vue({
            el: element,
            store: window.store,
            channels: {
                [`CourseStatusChannel_${window.store.state.course.id}`]: {
                    connected() {
                        console.log(`${window.store.state.course.id} Successful Connection!`)
                    },
                    rejected() {
                        console.log("1106 Rejected Connection.")
                    },
                    received(data) {
                        console.log(`${this.courseStatusChannel} received`, data)
                        if (data.commit) {
                            this.$store.commit('updateCounts', data.payload)
                        }
                    },
                    disconnected() {
                        console.log(`${this.courseStatusChannel} disconnected`)
                    }
                }
            },
            template: "<courseStatus />",
            components: { courseStatus }
        })
    }

How are you with HTML and CSS to make your VUE apps look great? Do you have any sample work I could check out?

@PaulRHanson316 Hmm. Interesting. I don't think dynamic channel names will work then so I'll take it out of the README. I'm glad you managed to get it to work anyway.

Dynamic channels are working GREAT! I think you should leave it in. At
least, I really need a way to create channels that are unique per
activerecord model. This is great. Good job!
On Fri, Mar 22, 2019 at 3:56 PM Mbah Clinton<EMAIL_ADDRESS>wrote:

@PaulRHanson316 https://github.com/PaulRHanson316 Hmm. Interesting. I
don't think dynamic channel names will work then so I'll take it out of the
README. I'm glad you managed to get it to work anyway.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mclintprojects/actioncable-vue/issues/2#issuecomment-475808680,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA1zwUFZfIQQTG4aUW_hUSeWsh5mFkdIks5vZV-CgaJpZM4cEMjj
.

--
Paul Hanson
Business Automation Software Developer

I think I'm pretty great at HTML + CSS. Here are a few of my handiworks.

https://ideabag2.netlify.com/ (VUE)
https://present-sir.herokuapp.com/ (VUE)

Also, you can check out my CodePen for other cool pens I wrote: https://codepen.io/mclint_/#


app.Down() behavior implements "remove"

What happened (or feature request):
I note that ddev rm is implemented in terms of Down(). Those are not the same semantics, and it would be a good thing to merge them.
What you expected to happen:
I expect something that destroys data to be named "Destroy()" or "Remove()" or something like that. Not "Down()" which would seem to imply a stop.
How to reproduce it (as minimally and precisely as possible):
Anything else do we need to know:
Related source links or issues:

This is implemented as down because it directly maps to docker-compose down https://docs.docker.com/compose/reference/down/
That doesn't mean we can't change it, of course, but I'm more hesitant than I normally might be since it's mirroring compose language.
I do agree down was a crappy name for them to pick, though :)

Seems like a reasonable choice. Closing this for now. We may want to figure out a way to change this in the future.


Updated unit tests

Description of Work
Fixes #53
Updated the unit tests such that they don't fail anymore.
Testing Instructions

In the /fitbenchmarking/fitbenchmarking/tests/ folder, run the tests in the mantidpython console.
Make sure all the tests pass.

In [10]: run loadParseNeutronTests.py
E.Load-[Notice] Load started
Load-[Notice] Load successful, Duration 0.05 seconds
* Testing fitting of problem ENGINX 193749 calibration, spectrum 651, peak 19
.
======================================================================
ERROR: test_getFittingNeutronData_return_MockProblemData (__main__.LoadAndParseNeutronFiles)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "C:\Midlertiddig\fitbenchmarking\fitbenchmarking\test\loadParseNeutronTests.py", line 120, in test_getFittingNeutronData_return_MockProblemData
    get_fitting_neutron_data(neutron_mock_data, prob)
  File "C:\Midlertiddig\fitbenchmarking\fitbenchmarking\input_parsing.py", line 317, in get_fitting_neutron_data
    wks = msapi.Load(Filename=fname)
  File "C:\MantidInstall\bin\mantid\simpleapi.py", line 165, in Load
    'description: ' + str(ve) + '\nIf the file has been found '
ValueError: Problem when setting Filename. This is the detailed error description: Invalid value for property Filename (list of str lists) "C:\Midlertiddig\fitbenchmarking\fitbenchmarking\test\mock_problems\data_files\NeutronMockData.nxs": File "C:\Midlertiddig\fitbenchmarking\fitbenchmarking\test\mock_problems\data_files\NeutronMockData.nxs" not found
If the file has been found but you got this error, you might not have read permissions or the file might be corrupted.
If the file has not been found, you might have forgotten to add its location in the data search directories.

----------------------------------------------------------------------
Ran 3 tests in 0.062s

FAILED (errors=1)
An exception has occurred, use %tb to see the full traceback.

SystemExit: True

In [14]: run ResultsOutputTest.py
....F.....C:\Midlertiddig\fitbenchmarking\fitbenchmarking\results_output.py:683: RuntimeWarning: invalid value encountered in less_equal
  if value <= color_descr[0]:
.........
======================================================================
FAIL: test_buildIndivLinkedProblems_return_NIST_files_Misra1a_linked_problems (__main__.ResultsOutputTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "C:\Midlertiddig\fitbenchmarking\fitbenchmarking\test\ResultsOutputTest.py", line 270, in test_buildIndivLinkedProblems_return_NIST_files_Misra1a_linked_problems
    self.assertListEqual(linked_problems_expected, linked_problems)
AssertionError: Lists differ: ['`Misra1a 1 <file:///d:/fitbe... != [u'`Misra1a 1 <file:///C:/Midl...

First differing element 0:
`Misra1a 1 <file:///d:/fitbenchmarking/fitbenchmarking/test/dump/nist/VDPages/nist_lower_misra1a.html>`__
`Misra1a 1 <file:///C:/Midlertiddig/fitbenchmarking/fitbenchmarking/test/dump/nist/VDPages/nist_lower_misra1a.html>`__

- ['`Misra1a 1 <file:///d:/fitbenchmarking/fitbenchmarking/test/dump/nist/VDPages/nist_lower_misra1a.html>`__',
?                        ^

+ [u'`Misra1a 1 <file:///C:/Midlertiddig/fitbenchmarking/fitbenchmarking/test/dump/nist/VDPages/nist_lower_misra1a.html>`__',
?  +                     +++++ ^^^^^^^^^

-  '`Misra1a 2 <file:///d:/fitbenchmarking/fitbenchmarking/test/dump/nist/VDPages/nist_lower_misra1a.html>`__']
?                        ^

+  u'`Misra1a 2 <file:///C:/Midlertiddig/fitbenchmarking/fitbenchmarking/test/dump/nist/VDPages/nist_lower_misra1a.html>`__']
?  +                     +++++ ^^^^^^^^^

----------------------------------------------------------------------
Ran 19 tests in 0.204s

FAILED (failures=1)
An exception has occurred, use %tb to see the full traceback.

SystemExit: True

tested and is working


[android] seeing if AppVeyor can run android tests

Don't merge this, I will keep rebasing this to see if we can get Android/emulator tests running on AppVeyor.

I will maybe revisit this later, doesn't seem like they support it: http://help.appveyor.com/discussions/questions/5638-android-emulator


Fix quantity types

Fix wrong type and shape in metainfo quantities. @TLCFEM

This seems all fine to me. You may also want @ndaelman-hu to take a quick look in terms of some of the more specific things that you changed.
Question: Is there any case that one would use np.dtype() now? I vaguely remember in the past having to use this for some more complicated array structure, but I can't really remember or might be mistaken, or maybe something has changed.

You can stil use np.dtype() and it would be equivalent to not using it, it is a matter of preference I guess but @TLCFEM may know more.

@ladinesa Are there any quantities that you didn't feel sure about? Anything that you want me to check in particular?

@ladinesa Are there any quantities that you didn't feel sure about? Anything that you want me to check in particular?

Nothing in particular. I did not make any changes in the schema, simply made sure that the assigned values are compatible with the defs.


The operation did not complete within the time allotted.

[Enter feedback here]
The above message was not listed as one of the causes for 'Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor." I am getting this error continuously when trying to deploy an app to HoloLens 2.
There is no info on this document page to guide me.

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

ID: 284b9094-8c91-69e1-01a2-0183ca3ec2a9
Version Independent ID: 8f7a16bb-32f6-3047-16e3-b82b82fbb7c0
Content: Unable to Connect to the Microsoft Visual Studio Remote Debugging Monitor - Visual Studio
Content Source: docs/debugger/unable-to-connect-to-the-microsoft-visual-studio-remote-debugging-monitor.md
Product: visual-studio-windows
Technology: vs-ide-debug
GitHub Login: @Mikejo5000
Microsoft Alias: mikejo

@dershver -- thank you for your feedback.  Please consider these resources:

https://social.msdn.microsoft.com/Forums/vstudio
https://www.stackoverflow.com
https://www.reddit.com/r/VisualStudio/

cc @Mikejo5000 for awareness
I am closing this issue now.  You are welcome to @ mention me for any followup.
We hope to hear from you again.


 I'm then forced to kill the docker instance forceably and
Your environment

version of lnd
d51f61af252e30eb39e3c85dd366b525f89f9267

which operating system (uname -a on *Nix)
Ubuntu 18.04

version of btcd, bitcoind, or other backend
0.21.0

Steps to reproduce
Haven't been able to point out what the issue is in order to reproduce the issue. It happens enough that we need to kill the instance once a week at this stage.
Expected behaviour
lncli stop stops the machine.
Actual behaviour
lncli stop does no change to the lnd instance
Screen Recording
https://user-images.githubusercontent.com/2574011/116299997-5b008780-a76c-11eb-8b4a-baf9d983f1b4.mov

Weird. Could you please post the logs from the moment you issue the "stop" command onward?

Could be helpful to get a goroutine profile as well, see https://github.com/lightningnetwork/lnd/blob/master/docs/debugging_lnd.md#capturing-pprof-data-with-lnd.

@guggero lncli logs from when lncli stop is ran here: https://paste.ubuntu.com/p/zccwFBfWjN/
@wpaulino gorouting logs here: https://paste.ubuntu.com/p/WvZ49pjr7j/

@andrerfneves can you confirm this node is indeed on commit d51f61af252e30eb39e3c85dd366b525f89f9267? The goroutine profile doesn't match the source code at that commit.

@wpaulino seems like we're running d5aedbcbd9db510c974c9f7be5ab177ad6546994 instead of d51f61af252e30eb39e3c85dd366b525f89f9267. Both d5s. Wonder if that's the issue, most likely?
Here are two other nodes, running the same commit and having the same problem. The nodes become unresponsive and lncli stop doesn't work. Channels and HTLCs also fail, and yet lncli getinfo and lncli version still work so we don't get alerted that the node is unreacheable/has problems.
https://paste.ubuntu.com/p/m5HDJQFJ5h/
https://paste.ubuntu.com/p/MXbYPvZC6H/
https://paste.ubuntu.com/p/xCmR6q4CBT/
https://paste.ubuntu.com/p/Nr82nSqDpd/

@andrerfneves I've opened https://github.com/lightningnetwork/lnd/pull/5258 to address the issue if you'd like to give it a try.

@wpaulino I'll update to that PR on our dev lnd's tomorrow and will watch them accordingly. Thanks


Made the update_scan able to use files with an "rmX_" prefix

I've found a number of update files use this prefix, mainly a convenience tweak

@ddvk


Greek Translation

I am willing to translate DogeHouse to Greek. I would like to have more info on how to do that.

fork the repo
switch to staging branch
go to kofta/public/locales
copy "en" to "gr"
edit .json file in gr/
submit pull request

Greek has been added #744


Platform support, Application property wrapper and notifications support

Platform support, Application property wrapper and notifications support
:recycle: Current situation & Problem
Currently, the Core Spezi infrastructure is only developed for iOS. However, we are aiming to support Spezi on all Apple platforms. This step required to reengineer some Spezi infrastructure that was heavily tailored towards the iOS platform (e.g., the LifecycleHandler). This PR deprecates the LifecycleHandler in favor of using SwiftUI native approaches like the ScenePhase environment property or platform-specific publisher-based solutions like willEnterForegroundNotification.
Further we introduce the new @Application property wrapper for Modules and the Standard to access application-specific properties like launchOptions.
Based on the new @Application infrastructure we resolve issues like #80 to provide Modules with Module-specific Logger instances.
To further validate our @Application approach, we added infrastructure around (Remote Push) Notifications. You can use @Application to trigger application actions like registerRemoteNotifications or unregisterRemoteNotifications and additionally adopt protocols like NotificationTokenHandler and NotificationHandler to react to notification actions, control how notifications are delivered in foreground or fetch additional content for background notifications.
:gear: Release Notes

Add support for visionOS, tvOS, watchOS and macOS.
Deprecated the LifecycleHandler protocol.
Added new @Application property wrapper to access application properties and actions in a a platform-agnostic way.
New protocol NotificationTokenHandler and NotificationHandler to easily support notification handling within your apps.

:books: Documentation
There are two new articles Interactions with Application and User Notifications that provide an overview for those new infrastructure elements.
:white_check_mark: Testing
TBA
:pencil: Code of Conduct & Contributing Guidelines
By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines:

[x] I agree to follow the Code of Conduct and Contributing Guidelines.

Thanks for the review @PSchmiedmayer. Will try to add some minimal unit testing where possible and sensible to validate functionality. Should make the codecov checks go green ✅

Thank you @Supereg; sounds like a great plan!

@PSchmiedmayer Added some tests to cover the new notification registration actions and test most of the new delegate functionality. We can't test the UserNotification delegate functionality as those types cannot be constructed by us and the NotificationCenter itself is not available in the testing environment.
This results in a slightly decreased coverage (also like 5 lines that are just comments). I would propose to force merge this PR because of the above-stated.

Sounds great; I merged the PR @Supereg 👍


v1 release vs semver tag

- uses: phrase/setup-cli@v1

This downloads the hard coded v1 release, which results in the warning Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: phrase/setup-cli@v1.
It does not act like semantic versioning by downloading the latest v1.0.2 release.  You might need to delete the v1 release here and then create a v1 tag that you maintain each release according to semver.
I think your intent was meant to be similar to how actions/checkout does it where uses: actions/checkout@v4 downloads v4.1.1 (current) instead of v4.0.0.
My workaround for now is uses<EMAIL_ADDRESS>and rely on dependabot for updates.

@jimmymcpeter could you pls retry with @v1, should be resolved


Changing error string conversions to use to_utf8string

@jplafonta,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


.dapr\\bin\\daprd.exe file does not exist Win11 + Kubernetes

Describe the issue

I installed DAPR using scoop.sh, then installed the DAPR helm chart with dapr init -k onto my local kube cluster (rancher desktop) with success. I can see all the pods, and even able to spin up the dashboard. However, the dapr "runtime" is n/a:
$ dapr status -k
  NAME                   NAMESPACE    HEALTHY  STATUS   REPLICAS  VERSION  AGE  CREATED
  dapr-dashboard         dapr-system  True     Running  1         0.11.0   50m  2022-10-17 22:11.42
  dapr-placement-server  dapr-system  True     Running  1         1.9.0    50m  2022-10-17 22:11.42
  dapr-sentry            dapr-system  True     Running  1         1.9.0    50m  2022-10-17 22:11.42
  dapr-operator          dapr-system  True     Running  1         1.9.0    50m  2022-10-17 22:11.42
  dapr-sidecar-injector  dapr-system  True     Running  1         1.9.0    50m  2022-10-17 22:11.42

$ dapr version
CLI version: 1.9.1
Runtime version: n/a

When I try to run the quickstart/pubsub/python, it says daprd.exe does not exist
$ dapr run --app-id order-processor --components-path ../../../components/ --app-port 5001 -- python3 app.py
Starting Dapr with id order-processor. HTTP Port: 52401. gRPC Port: 52402
exec: "C:\\Users\\Kennedy\\.dapr\\bin\\daprd.exe": file does not exist

URL of the docs

https://docs.dapr.io/getting-started/quickstarts/pubsub-quickstart/#step-3-subscribe-to-topics
Expected content

I am not sure, but I assume dapr will run the python app in the background, then I can proceed to the next step and publish to the topic
Screenshots

Additional context

Win11 x64
installed dapr via scoop.sh
kubernetes via rancher desktop
kubectl is pointing to rancher desktop cluster
dapr chart did not fail with positive health checks

@msfussell do you have any suggestions here?


Make launcher non-optional for GroovyCompile

Makes the JavaLauncher property of the GroovyCompile a non-optional input via the fallback toolchain selection for the unconfigured case.
Follow-up for #22108

@bot-gradle test qfl

OK, I've already triggered the following builds for you:

QuickFeedbackLinux build

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test and merge

OK, I've already triggered a build for you.

Pre-tested commit build failed.

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

I addressed the comments and improved the tests to better demonstrate current behaviors. PTAL!

@bot-gradle test and merge

OK, I've already triggered a build for you.


How to make the path smooth?

skan is a very good project. However, I wonder whether there is a method to make the path smooth? I need to calculate the resliced image along the skeleton, and the path (skel.path_coordinates) is not smooth. How can I make the path more smooth? Thank you very much!

@qiang-zhang-neu right now, we don't have any tools for that in skan. I suspect that adding them would require something like object.simplify from Shapely. You can find the docs here:
https://shapely.readthedocs.io/en/stable/manual.html#object.simplify
Including the reference for the algorithm, reproduced below for convenience. Shapely is 2D-only, though. I would definitely welcome a contribution to skan implementing this algorithm in nD, but I myself don't have time to work on this at the moment...
David H. Douglas and Thomas K. Peucker, “Algorithms for the Reduction of the Number of Points Required to Represent a Digitized Line or its Caricature,” Cartographica: The International Journal for Geographic Information and Geovisualization, vol. 10, Dec. 1973, pp. 112-122.


[c2cpg] Name/FullName/Signature refactoring

The split between fullname related methods in AstCreatorHelper.scala and FullNameProvider.scala is unclear to me.

This has been fixed.
Sptests is also happy with many fixed fullnames (for lambdas).


Fix for issue #116

Having a classname like RemoteLiveWebCache2 is unacceptable.
If RemoteLiveWebCache2 is fully functionally equivalent, but more robust than RemoteLiveWebCache, it should simply replace the old class. If this is the case, I'd like input from IA as they are the other big user of this facility.
Otherwise, if RemoteLiveWebCache2 is in some way different from the old class, making it sensible to retain both, then two things need to happen.

RemoteLiveWebCache2 needs to be renamed to reflect this difference. It may be acceptable to also rename the old class if that helps to clarify their difference.
The JavaDoc for both classes must be updated to include a description of their differences so that users can choose the appropriate one. This can be added to the class level JavaDoc comment (currently empty on both except for an author tag).

In this scenario (where both classes are retained) I think we should retain the old one as the default option in LiveWeb.xml unless there is a strong argument for changing it.

Rethinking about it, it is perhaps better to describe this class as an alternate implementation.
The new class is a modified version of the old that works with a standard proxy server (e.g., Squid), not with the ArcRecordingProxy. We went that route initially because our experience using the ArcRecordingProxy was not a good one, and we kept on bumping into connection issues, making the Wayback unusable.
I could suggest renaming the old and new classes to the following, respectively:
ArcRemoteLiveWebCache
StdRemoteLiveWebCache
I realize the new class needs a good deal of cleaning up, but it works so far, and it is what we have in production at the BA right now.
Thank you for any feedback.

That's starting to make sense to me. Perhaps start with adding the JavaDoc descriptions on the classes functionality?

OK, I will work on it next days. Should I push more commits on the same branch or create a new branch with modified contents?

You can push the commits to the same branch. They will then become part of this pull request.

I finished adding JavaDoc descriptions on both classes (StdRemoteLiveWebCache.java and ArcRemoteLiveWebCache.java) and updating LiveWeb.xml to fit with the changes.
As shown above, Travis CI failed to build my first commits. This is because LiveRobotsNoCache.java  is extending ArcRemoteLiveWebCache.java and I should've committed it first. Anyway, do you think you could rebuild 'Update ArcRemoteLiveWebCache.java' (e980049) and 'Update LiveWeb.xml' (4815ab1) instead of committing them again? Thank you.

Please don't merge stdRemoteLiveWebCache because after doing some tests, I noticed it is not working properly. I have added 2 features to the current version of stdRemoteLiveWebCache.
Lines 122-126 set connection time out to 10 seconds which increases openwayback responsiveness. This part is working perfectly normal.
As you know that Openwayback gets robots.txt from the live web. If any domain is down (or is not responding) because its http status code is 404, then Openwayback will fail to get robots.txt and will throw a connection time out exception (Openwayback unable to get the robots.txt document to display this page). Lines 133-142 should fix this issue, but it is not working as expected.
Openwayback is stable somehow if we excluded lines 133-142 from stdRemoteLiveWebCache, but it will not display contents of any down domain (http status is 404), which breaks the idea of web archiving. I will work on it and commit it again if it worked gracefully.

Please don't merge stdRemoteLiveWebCache because after doing some tests, I noticed it is not working properly. I have added 2 features to the current version of stdRemoteLiveWebCache.
Lines 122-126 set connection time out to 10 seconds which increases openwayback responsiveness. This part is working perfectly normal.
As you know that Openwayback gets robots.txt from the live web. If any domain is down (or is not responding) because its http status code is 404, then Openwayback will fail to get robots.txt and will throw a connection time out exception (Openwayback unable to get the robots.txt document to display this page). Lines 133-142 should fix this issue, but it is not working as expected.
Openwayback is stable somehow if we excluded lines 133-142 from stdRemoteLiveWebCache, but it will not display contents of any down domain (http status is 404), which breaks the idea of web archiving. I will work on it and commit it again if it worked gracefully.

Closing in favor of PR #251


Adding username to Drawer

This addresses issue #719.
Please let me know if I am doing something horribly wrong.

Thanks for pr! I see nothing horrible:) Only lines are too long, maybe adding some breaks could work. Plus, I think you can use the default shared preferences instead, this could also shorten the code. Please let me test this in morning and others can also check it.
Note: Yes, there is some inconsistency about organization of shared preferences. But this should be solved on another pr.

The functionality works nice according to my tests, but I think getting it on LoginTask might be a problem for the case: When user cleared data from settings of the phone, then go back to the app, somehow user is still logged in but username disappears. Does anyone have an idea to prevent this @nicolas-raoul @misaochan ?
Plus, appearance of the text should be fixed. Maybe we can write it to bottom of the commons icon. Here current look:

Thanks for the PR, @Nethermane !
Sorry, but I am not sure at the moment how we can prevent the loss of username when user clears data, while using sharedpreferences to store the username. Indeed that would be a drawback of that method. Hopefully someone else has an idea?
I agree with @neslihanturan re: the text. Personally I think it would be nice for the nav drawer to say "Welcome, [username]!" just above "Home".

I've met this issue on previous projects - when you clear data it doesn't affect what the Android account manager has stored.  The trick is to ask the account manager for the current user's name and not store it in shared preferences.
Sadly the account manager is a little annoying to work with - all I can do is ask for an array of accounts of a particular type.  As we log in and log out what we need to do is flag which of those accounts is "live" and store any other additional data there that is pertinent to our account.  When we grab the array of accounts, we can look for the logged in flag and pull the name from that one.

I think the design could be something like this:
Design 1

Design 2

My vote for design 1 with a different font (the font used on nav drawer). @psh thanks for the solution, but I couldn't understand where to save these flags. Maybe sample code can work tomorrow.

I was playing around in the LoginActivity and added a quick log message to the onResume() to illustrate things:
protected void onResume() {
    super.onResume();
    if (prefs.getBoolean("firstrun", true)) {
        WelcomeActivity.startYourself(this);
        prefs.edit().putBoolean("firstrun", false).apply();
    }
    Account currentAccount = app.getCurrentAccount();
    if (currentAccount != null) {
        Log.e("MW", "### Current account name = "+currentAccount.name);
        startMainActivity();
    }
}

What I noticed is that the getCurrentAccount() method that does a bunch of work for me - it queries the Android account manager and returns either the current logged in account, or null.  I think the name field is what we're looking for, right?
The log that printed out when I logged in said
### Current account name = Paul.hawke

Which is what I would be happy seeing on the navigation drawer.  Oh, and I vote "1" for the design.

Design 1 looks good to me too. :)

It works without a problem now, thanks @jorgecasariego :). But my last feedback is adding some space between the text and commons logo. Currently it looks like:

If you can fix Codacy and appearance, it can be merged immediately.

I am still unsure about how to get the font to look like the drawer items, but other than that it looks pretty good.

Thanks @Nethermane for adding this needed property!

This branch failed on integration tests, and needs to be solved before being merged. Sorry for my confusion.


[BUG] - Pagination component warnings in console

Describe the bug
When import Pagination component using documentation in console throws errors.
Setups:
NextJS v13 using pages routing.
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue

Setup NextUI providers
Import Pagination component
Use them for example
Open console
Warning: [object Object]: key is not a prop. Trying to access it will result in undefined being returned. If you need to access the same value within the child component, you should pass it as a different prop. (https://reactjs.org/link/special-props)
Warning: Invalid ARIA attribute ariaLabel. Did you mean aria-label?

Expected behavior
As a user, I expect that these are minor bugs.
I am grateful for the opportunity to use this product and believe that you have done a great job.
Screenshots or Videos

Operating System Version
macOs
Browser
Chrome

Hey which version are you using?
I believe this issues were already fixed:
https://github.com/nextui-org/nextui/pull/1315
https://github.com/nextui-org/nextui/pull/1314


set CMAKE_CXX_STANDARD to 11

Coverage remained the same at 88.274% when pulling 68ae17775324f69a96f87c2c32a2ffc5038183c1 on hendrikmuhs:cmake-cxx11 into b629766535faaf57bc113bed241de88f18d06d1e on KeyviDev:master.


Updated TS definitions for props that are passed to  Modal from react-native

@ionut-movila shouldn't the values props be optionals? 🤔 Thanks for submitting the PR and for also adding all the other props btw!


(WIP) Remove PrimaryButton.tsx and SecondaryButton.tsx and DangerButton.tsx & update places they are used

This issue was refactored out of a previous issue to look at the usage of PrimaryButton, SecondaryButton, and DangerButton and refactor them accordingly.

PrimaryButton.tsx and SecondaryButton.tsx are really old components and should no longer be used. In many places now, specifically for forms, we use SubmitButton.tsx, but a new component should be created for more general cases.
Clarification needed before turning into ticket

Decide on a look for buttons that are not submit. Ideally these would look slightly different as they have different functionalities, but some more research might be helpful on best UI practices.

@calisio I think that this is something you brought up in a different ticket when we discussed some refactoring. Without digging too deep, do you know of any more context that we should add to this issue right now?

The places that these buttons are used should instead use the class button and it should apply the necessary styling. There are several examples (such as the Add Provider button on provider platforms) that it should look like. Please do not use btn btn- classes, these are daisy ui styling we want to move away from!!


Use postgresql travis addon/sudo:false

As we rollbacked in https://github.com/CartoDB/Windshaft-cartodb/pull/393 to sudo: true builds.
Depends on: https://github.com/travis-ci/travis-ci/issues/5737

This was fixed by #395.


[3.x] feature: add back footer logo toggling

Not sure if you want the config for this in the actual config file. Feels a bit excessive to have to write custom CSS to hide the logo using the filament-footer-logo class.

I agree actually removing the logo from the footer (instead of hiding with CSS) should be possible. Don't think the config file is the right place though. @danharrin thoughts?

What if we remove the logo from the unbranded Filament and only render it from within a theme service provider that adds logos to the sidebar and footer (in addition to branded styling)?

I'm tempted to say we should just remove it completely


Race condition in timer-manager can delay firing a timer until the next-timer's deadline

Here is a possible scenario:
Lets say there are two threads in timer-manager T1 and T2.  Lets also assume T1 is calling grpc_timer_check while T2 is in gpr_cv_wait in wait_until function (and perhaps T2 is the current timed-waiter thread)
The sequence causes a timer to be delayed:

T1 calls grpc_timer_check and got a return of GRPC_TIMERS_CHECKED_AND_EMPTY and next == t1
T1 now goes into wait_until() but just before acquiring the g_mu, a new timer with time t2 (which is LESS than t1) is added. This makes the timer system (i.e the function grpc_timer_init in  timer_generic.c) call grpc_kick_poller and wake up thread T2 (also grpc_kick_poller sets g_timed_waiter to false - so there is no timed waiter in the system now)
(SEE FOOTNOTE for a different problem that can happen here)
T2 wakes up, goes out of wait_until and back to timer_main_loop function, calls grpc_timer_check and picks up the new timer added i.e next == t2
Now T1 which just entered wait_until() grabs g_mu, becomes the timed waiter and is now sleeping till t1
T2 also enters wait_until(), finds that there is already a timed waiter and sleeps until kicked! . So even though t2 < t1,  the thread T2 is sleeping until kicked thereby delaying t2 timer until t1 is fired!

Code here:
timer_main_loop() {
  for(;;) {
    switch (grpc_timer_check(exec_ctx, now, &next)) {
      ...
      case GRPC_TIMERS_CHECKED_AND_EMPTY:
        if(!wait_until(next)))  return;
        break;
   }
}

static bool wait_until(gpr_timespec next) {
  gpr_mu_lock(&g_mu)
  ...
  if (!g_has_timed_waiter && gpr_time_cmp(next, inf_future) != 0) {
    g_has_timed_waiter = true;
    ..
    sreek: SLEEP UNTIL "next": This thread just came the timed-waiter
    thread will wait until the next timer is due (or rather *its view* of
    when the  next timer is due - AND THIS IS A PROBLEM)
    ..
  } else {
    next = inf_future;
     -- sreek: SLEEP UNTIL KICKED: Since this thread isn't timed waiter,
    this will wait until it is kicked (either by timer system which would call
    grpc_kick_poller or by a timed-wait thread which wokeup and is running
    some timers in run_some_timers()
    ..
  }

  -- WAIT until next timer is due or until kicked --
  gpr_cv_wait(&g_cv_wait, &g_mu, next);
  ....
}

NOTE: There is another scenario where we may miss a kick. In the second step above, if thread T2 wasn't in gpr_cv_wait and was perhaps executing the timers (i.e run_some_timers), then no thread receives the kick there-by failing to pick up the updated new time t2 (and delaying it until the next timed-thread's wakeup)

I have a fix in mind - will be sending a PR today


Add missing line from 21.3.0 to 19.3.0 database

Refs https://github.com/oracle/docker-images/pull/2238#issuecomment-1065252008

@gvenzl I suggest this get merged with priority.


fix bug where backToInitial Flag did not work for cloned scenes

Also seems to fix this issue from stackoverflow:
https://stackoverflow.com/questions/47352572/react-native-router-flux-reset-stacknavigation/51388834#51388834

Sorry for the delay, we were working hard on new version based on React Navigation 2.x, please check 4.0.0-beta.40 and if the bug exists, reapply this PR, thank you


get the user's IP in the first request

How to get the user's IP in the first request, because it is rendered on the server side, I can only get the IP address of the server and not get the IP of the user

Something along the lines of:
const ip =
  req.headers['x-forwarded-for'].split(',').pop() || // From proxy headers, can be spoofed if you don't have a proxy in front of your app, so drop it if your app is naked.
  req.connection.remoteAddress ||
  req.socket.remoteAddress || // socket is an alias to connection, just delete this line
  req.connection.socket.remoteAddress // no idea where this might be a thing, just delete this line
// probably add a default at the end here, although there shouldn't be a case when req.connection.remoteAddress is unset.

so, tl;dr:
If you likely have a proxy in front of your app:
const ip = req.headers['x-forwarded-for'].split(',').pop() ||
  req.connection.remoteAddress

If your app is naked to the internet:
const ip = req.connection.remoteAddress

Thank you for your attention, your method can be used in the client request, but once I send the request in the asyncData, the request will be done on the server, and get the wrong user IP address.

You're sending a request from the client.
Hence, whatever API you're hitting inside the asyncData should look at the client request object. (On the server)

Yes, it was the headers, I fixed it.

That's a good solution, thank you very much! @canyoudev


How to get all tweets in the date range?

Hey,
I am having a trouble to come up with the solution which could give me all tweets matching searching criteria and not to restrict response collection set on MaximumNumberOfResults value.
Speaking in example:
I have since and until date time range set on a day, location and radius and now I want to get all tweets regardless on how many of them are available. The best solution saves the rank of requests needed to trigger from client side.
Thanks in advance

I think you could set MaximumNumberOfResults to int.MaxValue, which is a little hacky but should work unless you expect to have in excess of ~2bn results.
I don't know how well Tweetinvi will handle the rate limits for the Search API endpoint here though (so if it took 1000 API requests to get all of the results you're interested in, would Tweetinvi wait the correct amount of time between requests or exceed the rate limits and error). It might be fine, but I've never tried it.
Alternatively, you could set the maximum to 100 (or just not touch it) and handle the paging yourself, making lots of requests for 100 results each in a loop. You'd just need to specify Since ID for the next call based on the results of the last API call. The advantages of this are that it isn't hacky & lets you handle the rate limits yourself, so you could look to do things like switching the credentials you're using between requests so you can make more requests per window, but it's a bit more complex to implement.

Hi Josh,
this is how I did originally use it. Int.MaxValue works fine and i was wondering if you guys figured it how to get over 100 tweets/request in order to save few requests from dedicated rate limit.
I see a that library is looping until number of results is matching (regardless how many requests has been used, I guess she goes efficiently per entire possible batch of tweets/request).
Only 2 cents for nice to have feature would be that if no Max is specified than gives me everything.
Thanks.

@stenly311 This is something that we cannot do anything since it is a limitation from the twittler API. We can have maximum 100 hundred tweets per page as mentioned in API documentation.
https://dev.twitter.com/rest/reference/get/search/tweets

@stenly311

Only 2 cents for nice to have feature would be that if no Max is specified than gives me everything.

I understand your point but this has been done intentionally. The reason is that I don't want users to say Search.SearchTweets and have Tweetinvi consumer the entire set of search RateLimits.
I think it is more reasonable for the user to ask for such behaviour.


Support for RethinkDB database

I'm considering RethinkDB as the event store due to the simplicity to setup as cluster in 1 node / multiple node.

PR are welcome ;-)

Closed since this issue is inactive for multiple years now.


Updating singly linked list with python

🚀 Feature
I'm going to update the python code of singly linked list, where removing is done by using value instead of index
Have you read the Contributing Guidelines on Pull Requests?
Yes
Motivation
By using this operation we don't need to know the index for the specific value
(Please outline the motivation for the proposal.)
Pitch
In the existing file, removal of a node is done by using index  but I'm going to do with value

/assign


Advanced usage with custom items

Hi
I have the Project page with route/project/:projectId and Task page with route /task/:taskId. Project page contains the list of tasks and clicking on it redirects the user to the Task page.
Those two pages have independent routes, defined on the top level. When displaying Task page I want to have a breadcrumb project_name -> task_name which requires some custom logic because the library will not display the whole chain since Task route is not nested inside the Project route.
How I can achieve that?

Hi
It need to mention that the length of url (filed to) is used to sort crumbs when breadcrumbs is generated.
So you have several ways:

correct routes to match object relation:

<Route path='/project/:projectId' component={Project} />
<Route path='/project/:projectId/task/:taskId' component={Task}
...
<BreadcrumbsItem to=`/project/123` children={projectName} />
<BreadcrumbsItem to=`/project/123/task/123` children={taskName} />

use special filed for sorting and specify compare function at breadcrumbs instance:

<Breadcrumbs compare={(a,b)=>a.weight-b.weight} />
...
<BreadcrumbsItem weight=0 to=`/project/123` children={projectName} />
<BreadcrumbsItem weight=1 to=`/task/123` children={taskName} />

add some unsignificant text to increate length of url to correct sorting (see remark about sorting above):

<BreadcrumbsItem to=`/project/123` children={projectName} />
<BreadcrumbsItem to=`/task/123#something` children={taskName} />

Thank you @oklas. Multiple BreadcrumbsItem with weight fixed the problem.


⚠ SceneTime has degraded performance

In 386d1c9, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 1436 ms

Resolved: SceneTime performance has improved in fdbff79 after 6 minutes.


Autplay Enabled - Jump to a specific slide fix

Before fix:

Enable Autoplay
Disable Loop
Go to last slide and wait for "end" state.
Execute $elmt.vegas('jump', any_slide_goes_here);
Result: Vegas will jump to specific slide but will not play next slide. It appears like autoplay is killed (which is sort of right due to _end function).

After fix:

Enable Autoplay
Disable Loop
Go to last slide and wait for "end" state.
Execute $elmt.vegas('jump', any_slide_goes_here);
Result: Vegas will jump to specific slide and after that it will autoplay next slide as it supposed to do.

Thanks a lot.
Sorry for (huge) delay.


Add a unit for CPU in the validator health check

In the validator health check, I've noticed the CPU quantity doesn't have a unit.

issue resolved and merged in main with the following PR: https://github.com/sigp/lighthouse-ui/pull/94


feat(proof): encode solidity calldata for proof

Just a quick PR to make it easier for users to encode calldata for solidity. If using JS you probably don't need that, but I'm using Foundry, so it makes it a bit easier for me, and I thought it could be useful to others.
I also update the docs

Hi @teddav, the code looks good! Can you add more context on why Foundry needs the proof to be encoded?


feat: create user profile page

Your checklist for this pull request
🚨Please review the guidelines for contributing to this repository.

[x] Make sure you are requesting to pull a topic/feature/bugfix branch (right side). Don't request your default branch!
[x] Make sure you are making a pull request against the default branch (left side). Also you should start your branch off default branch.
[x] Check the commit's or even all commits' message styles matches our requested structure.
[x] Check your code additions will fail neither code linting checks nor unit test.
[x] I have added necessary documentation (if appropriate)

Linked Issues
Fixes #329
Description
Please describe your pull request.
❤Thank you!
Post merge checklist

[ ] Follow steps from the guidelines for contributing to this repository.
[ ] If you are a new contributor, ping in the thread and one of the maintainers will add you to all-contributors list.

@anish-patro add images of your work in the description.

@anish-patro add images of your work in the description

@anish-patro add images of your work in the description.

@sambit-sankalp @120EE0692 please proceed with this ASAP.


Add Move Button and Double click with shared group

First of all wonderful plugin.
I am looking following two things with two sortable shared list

How can we add double click even to move items between list?
Along with each item, I want to add a move button. It will move item between list. How can we add that event to shared list ?

Thank You

You can do this just by manipulating the DOM itself, it won't affect Sortable at all as that's all Sortable is doing when you drag.


CakePHP 3.4 uses query param instead of session for login redirect

Since CakePHP 3.4, query parameter is being used to store redirect URL for login, instead of session. Using AuthComponent's redirectUrl() to store it no longer works.
Also, to be more "Cake-ish", we should let AuthComponent handle login redirect. That is easily done by setting authorize action as denied.
OAuth spec however requires to validate OAuth params (client_id, redirect_uri, ...) before login redirect, so I moved these into beforeFilter.
Since change is using default Cake behavior, it should even be 3.3 compatible, did not test it though.

The test fails on CakePHP 3.3, because redirect URL is not stored in URL and the test expects it there, but it should work.
I would leave the test like this, to be sure that redirection works in the future.

Thank you

Hi. I cannot get the authorize site working properly. If the user is not logged in there is no redirect to the login page after update to cakephp 3.4. Help highly appreciated.


Add glue permissions

Adding necessary IAM permissions to run OOTB WRT glue checks
glue:GetConnections
glue:SearchTables

Without these an OOTB run of prowler does not succeed due to AccessDeniedException due to these permissions.

I was only confirming this via the util/codebuild CloudFormation template, but noticed the bootstrap IAM was doing something similar so added the permissions there as well.
Feedback welcome on that.
Thanks!

Thanks @joshes, I did that (partially) in branch 2.5 (current devel one) but I just noticed that I missed glue:SearchTables. I will add it. Thank you!


Unable to run dvector_create.py, file does not start with RIFF id

Running dvector_create.py with default arguments and the TIMIT data throws the exception:
Traceback (most recent call last):
  File "dvector_create.py", line 94, in <module>
    times, segs = VAD_chunk(2, folder+'/'+file)
  File "PyTorch_Speaker_Verification/VAD_segments.py", line 131, in VAD_chunk
    audio, byte_audio = read_wave(path, hp.data.sr)
  File "PyTorch_Speaker_Verification/VAD_segments.py", line 26, in read_wave
    with contextlib.closing(wave.open(path, 'rb')) as wf:
  File "/usr/lib/python3.7/wave.py", line 510, in open
    return Wave_read(f)
  File "/usr/lib/python3.7/wave.py", line 164, in __init__
    self.initfp(f)
  File "/usr/lib/python3.7/wave.py", line 131, in initfp
    raise Error('file does not start with RIFF id')
wave.Error: file does not start with RIFF id

Make a transformation using SPHFile


Usage of buffer_time

hi
I have questions about the usage of buffer_time.
I read from the doc
buffer_time: ElastAlert will continuously query against a window from the present to buffer_time ago. This way, logs can be back filled up to a certain extent and ElastAlert will still process the events.

what does  back filled up mean?  update log or index log?
If  'index log',   it means  log doesn’t get indexed immediately, so I can use query_delay
if 'update log', in my opinion,  log doesn't need updated once indexed.
Any ideas?

back fill in these case refers to documents uploaded where the @timestamp is behind the current time.
For example:
if {"@timestamp": "11:50"} was uploaded at 12:00, you'd need a buffer_time of at least 10 minutes to catch this document.
This will never occur if Logstash adds the @timestamp when it processes the document, but can occur if Logstash is parsing logs from another source that contain their own timestamps.
The issue with having a HUGE buffer_time then is that each query is more network traffic and elastalert uses more memory to keep track of events.
Query_delay achieves a similar goal, you can have smaller query windows but they are shifted backwards in time.

This will never occur if Logstash adds the @timestamp when it processes the document, but can occur if Logstash is parsing logs from another source that contain their own timestamps.

Even with Logstash adding @timestamp, isn't it possible for there to be a delay between when Logstash creates @timestamp and when  the document is actually indexed that could result in a document being missed by an elastalert query?  See: https://github.com/elastic/elasticsearch/issues/15644 for an exhaustive discussion.

Yes, you are right "never" is not really accurate. And in fact, that's why query_delay is basically necessary if you're using count or terms query, because those don't have overlapping queries.
I suppose what I meant in this context is that you'll never have to worry about changing buffer_time from the default value if your documents are being timestamped by logstash.

Blacklist is a bad example since that's a ruletype, not a query type. In fact, you can't use it with anything other than the default.
The other query types are use_count_query, use_terms_query. With these ones, there is no overlap, so in your example, D2 would be missed. You pretty much have to use query_delay. We can't have overlapping queries here because there's no way remove duplicate values, which we normally do by storing all the _ids of processed documents.
Metric aggregations are similar, but they do actually can have overlapping queries, since aggregation values (think average) can be computed over overlapping windows, and it's not "duplicating" anything.


docs: rewrite intro

✅ Checklist

[x] I have followed every step in the contributing guide (updated 2022-10-06).
[x] The PR title follows the convention we established conventional-commit
[x] I performed a functional test on my final commit

Changelog

improved docs intro
no more nelson gif
move the axioms into the intro page

I'd suggest to make similar changes to the main readme if this looks good to everyone else. Could also see going even further on rewriting a completely different intro, lmk - just wanted to open a PR so we get started discussing it :)
💯

The link should be updated to point towards /introduction#typesafety-isnt-optional instead of /t3-axioms#typesafety-isnt-optional, since the T3 Axiom page doesn't exist, and will lead to 404.


bug: can't make --config-path arg to work

Neovim version (nvim -v)
NVIM v0.9.2
Operating system/version
MacOs 13.6 (22G120)
Output of :ConformInfo
Log file: /Users/henryoliver/.local/state/nvim/conform.log

          	Did you mean '--config-path'?

          	If you tried to supply `-- --config-path` as a value rather than a flag, use `-- -- --config-path`

          USAGE:
              stylua --config-path <CONFIG_PATH>

          For more information try --help

          22:14:57[ERROR] Formatter 'stylua' error: error: Found argument '-- --config-path' which wasn't expected, or isn't valid in this context

          	Did you mean '--config-path'?

          	If you tried to supply `-- --config-path` as a value rather than a flag, use `-- -- --config-path`

          USAGE:
              stylua --config-path <CONFIG_PATH>

          For more information try --help

          22:14:57[ERROR] Formatter 'stylua' error: error: Found argument '-- --config-path' which wasn't expected, or isn't valid in this context

          	Did you mean '--config-path'?

          	If you tried to supply `-- --config-path` as a value rather than a flag, use `-- -- --config-path`

          USAGE:
              stylua --config-path <CONFIG_PATH>

          For more information try --help

          22:20:00[ERROR] Formatter 'stylua' error: error: no files provided

Formatters for this buffer:
LSP: lua_ls
stylua ready (lua)

Describe the bug
Cant make this arg work:
			local stylua = require("conform.formatters.stylua")
			stylua.args = { "--config-path", vim.fn.expand("~/.config/lsp/stylua.toml") }

The path is correct:
❯ cat ~/.config/lsp/stylua.toml
indent_width = 4
column_width = 120
indent_type = "Spaces"
line_endings = "Unix"
call_parentheses = "Always"
quote_style = "AutoPreferDouble"
collapse_simple_statement = "Never"

If you look at the definition of the stylua formatter, you're going to need more args than that
https://github.com/stevearc/conform.nvim/blob/bbb7df3b3210fff165f2be429cf669726d159de4/lua/conform/formatters/stylua.lua#L9
You could use the util.extend_args helper documented as part of this recipe


Is this possible to add a form field in menu drop down

I am trying to create advance search for which I want to add form element in search dropdown. But it seems not working . Any idea?

Can you describe what actually not working for you?
I see two problems - form closed on click, even on a text field, and the form labels inside dropdown makes overall content overflow a little.
To fix the first, you need to stop click even propogation for the form - <form onclick="window.event.cancelBubble = true">
And the second one could be fixed with a small piece of CSS:
.dropdown-content .input-field.col  label {
  width: auto;
}

Here is the demo:
http://codepen.io/kmmbvnr/pen/gLbger

Drop down dissapears when you click on form fields on mobile

@ProProPro1 yeh, propagation need to be stoped for the touch event as well

I'd updated the codepen with  <form onclick="event.stopPropagation()" ontouchstart="event.stopPropagation()">

Closed due inactivity


Is this project being actively worked, or is it abandoned?

 Issue by LarrySmith-1437
Tuesday Oct 10, 2017 at 22:02 GMT
Originally opened as https://github.com/gsscoder/commandline/issues/488

I've used this library quite a bit, and have always liked it.  I stopped in to see how things are going, to find a lot of issues and outstanding pull requests.
I'm curious to know if there's anyone who is an active custodian for the project and if it's receiving any updates or fixes.

 Comment by nemec
Wednesday Oct 11, 2017 at 20:27 GMT

I watch the issue queue and try to help out with questions, but I don't really have the time to actively develop this project. I'm happy to accept pull requests too, but I don't own the project so I'm a little hesitant about making huge architecture changes. Bug fixes are A-OK though.
That said, the project's owner has been in and out of contact (mostly out) for the past few years so I'm not sure if/when he will come back.

 Comment by ericnewton76
Wednesday Oct 11, 2017 at 15:27 GMT

Yes, there are people working on the project.  One of the issues, four eighty five (spelled out to prevent auto issue link) was responded to by part of the community barely 14 days ago.
I also respond as well to some of the questions.
What is the reason you ask?  Would be great to have another contributor etc!  Any help is certainly welcome and appreciated

 Comment by LarrySmith-1437
Wednesday Oct 11, 2017 at 22:54 GMT

Well, there were a few reasons that prompted me to ask.  This is the library I go to for command line parsing support.  My apps are moving over to .net core and .net standard.  Given it's importance to me,  I wanted to see how it was doing.
When I started looking around at the project overall, I saw a high count of outstanding (not closed) issues, outstanding code pulls, no code commits since 2/17 (until, I see now, there was just a commit today for the  readme.md), plus a whole host of forks, many of which are dead, including the one that the original author designated in the Wiki as his favorite to take on the mantle temporarily as a maintained fork, namely https://github.com/cosmo0/commandline
That plus it's had a beta release pending since at least midway through 20015...  It lead me to wonder.

It's sad, but this smells like a zombie library.

 Comment by LarrySmith-1437
Thursday Oct 12, 2017 at 22:26 GMT

I'd like to append my answer.  I think in stating my reasons for asking the question, I may have sounded a little negative.  I'm not negging the project, I love it!  I've just been away from the pulse of it a good long time.
So, are there people who are minding the store?   Someone with the permissions to act on the issues and code?  (maybe the owner could be put upon to turn over the mantle?)
If not here, then is there an active fork to take on the lead?

 Comment by ericnewton76
Tuesday Oct 31, 2017 at 16:34 GMT

So after thinking about this more, there seems to be no leader in place, and nobody wants to take the role.  Not a problem... life throws things at people and you gotta adjust. @gsscoder if you're listening, chime in!  We need to push the project forward.
I am tempted to nominate myself for creating an official fork and new official nuget package and being the driving force for new releases, managing issues, reviewing pull requests etc
If I'm wrong that there no leadership here, let's discuss it.
We have to start moving the project forward.  This is why it makes the most since to start a team and adopt the project into the team and allow for a more responsible group of people instead of a single.
I'm also going to research appveyor support of team based instead of individual accounts and switch other OSC projects into team based as well, so I dont become the bottleneck of progress.

 Comment by nemec
Tuesday Oct 31, 2017 at 17:24 GMT

@ericnewton76 I've been thinking about this lately as well. I think it would be good if you or someone else picked up a fork to integrate more meaningful changes/features to the library. Once that is done I can make an additional commit to this repo that deletes all files except the README, noting that the project has moved. If @gsscoder finds the time to work on this again, he can restore from the previous commit and keep working.

 Comment by ericnewton76
Tuesday Oct 31, 2017 at 16:48 GMT

So next steps would be:

Establish new leadership of the project. I will assist and push the agenda forward as a (self)nominated leader to get this project on track.
Deal with ownership of the code.
-- Option A, we petition github admins to either mark this exact repo as abandoned or defunct with a proper link to our team based repo.  We then start manually dealing with the pull requests, perhaps a bulk copy/transfer of issues via code (github apis) from this repo to the new one
-- Option B, we petition github admins to transfer ownership of this repo to the team.  This obviously is best because issues/pull requests/etc dont get lost and have to be recreated.

 Comment by gaston-e-nusimovich
Tuesday Oct 31, 2017 at 18:01 GMT

I guess that once the new leadership and team for the fork is established and settled, it would be great that the team proposes to the community a basic roadmap for the new fork, with same major user stories and a rough time frame for the main items on the roadmap.
Just to give some more feedback on the roadmap to propose, it would be awesome if it (eventually) includes a branch for a .NET Core version and a branch for the (existing) .NET Standard version.
Kind regards, GEN

 Comment by nemec
Tuesday Oct 31, 2017 at 18:11 GMT

FYI @gaston-e-nusimovich both the latest beta and the master branch of this repository fully support .net core (standard 1.5, if I remember correctly)

 Comment by ericnewton76
Tuesday Oct 31, 2017 at 18:42 GMT

@nemec Indeed.  One of the pull requests #458 appears to deal with some of the NetStandard support.  And he made the object factory pluggable.  (Havent thoroughly reviewed the commits though)

 Comment by ericnewton76
Tuesday Oct 31, 2017 at 18:59 GMT

@nemec do you have direct commit powers to this repo?  do you have the ability to go to settings and transfer ownership?  if so, we should create a github team, add yourself, gsscoder, myself and then we can start establishing pull request reviewers and branch management to control the process of releasing.
Then we have to petition nuget to reassign that packageid to the team (if possible) so we can get some formal proper releases out there

 Comment by nemec
Tuesday Oct 31, 2017 at 19:23 GMT

I have commit privileges but no access to the repository settings (I think that's reserved for gsscoder). As a co-owner of the NuGet package it looks like I can add new owners at will, so I don't think it will be a problem to add you. There is no built-in concept of team ownership:
"For example, the Microsoft ASP.NET packages are co-owned by microsoft, aspnet, and sometimes individuals on the feature team. The ‘microsoft’ and ‘aspnet’ accounts are simply set up with a mailing list email address that reaches the teams that manage the accounts."
If you don't mind, will you do the team setup + fork? I think you've come up with a good plan.

 Comment by ericnewton76
Tuesday Oct 31, 2017 at 18:44 GMT

Road map for time being is simple:

get to a stable version to publish to nuget.  Realistically the current codebase appears stable enough to at least put out a formal v2 release.  You guys will have to clue me in on how ready for release it is.  Timeframe mid Nov 2017.
Full support for lowest NetStandard support, i'm thinking NetStandard 1.3 for Framework v4.5.2+.  Address issues with that low of netstandard support or just say unsupported.  I see some conditional compilations in there, would like to minimize that as much as possible... thats the whole point of NetStandard in the first place.  Timeframe mid Dec 2017 (possibly)
Squash any real major bugs for a solid v2.1 release.  Timeframe end of Jan 2018

For New Features, I dont know what really would be needed beyond whats already here.  Call out issues on this discussion of desired features.

 Comment by clmcgrath
Tuesday Oct 31, 2017 at 21:44 GMT

I have had pull request to add pluggable object factories open since july

 Comment by clmcgrath
Tuesday Oct 31, 2017 at 21:41 GMT

Maybe it is time to fork the project and move on...

 Comment by ericnewton76
Thursday Nov 02, 2017 at 14:19 GMT

FYI, new github organization created, "commandlineparser" at https://github.com/commandlineparser with nemec, myself, gsscoder as co-leaders
Forked this repo into https://github.com/commandlineparser/commandline
General Question: I have found a python3 script that can copy github issues from repo to repo.  So should we copy all OPEN issues only, or ALL issues as preservation?

 Comment by gaston-e-nusimovich
Thursday Nov 02, 2017 at 14:56 GMT

IMHO, I suggest that you copy only open issues into the new repo. Any user can navigate back to the previous repo and search for any given closed issue.

 Comment by ericnewton76
Thursday Nov 02, 2017 at 15:48 GMT

Started an issue that will be a progress report in the new repo:
https://github.com/commandlineparser/commandline/issues/2

 Comment by ericnewton76
Thursday Nov 02, 2017 at 15:08 GMT

In the new repo, commandlineparser/commandline here's a few things I'd like to do to have more process control around releasing:

I also propose having a formal release branch that actually kicks off a release build into Nuget/Github Releases/etc.  All developer forks/work is still based on master.  Release will never really have actual commits to it, but provides a last stop guard on the road to publishing a release during build/deployment process.
Update Appveyor with correct version number and Fake to actually utilize it.  It does support "2.1.1-beta" and a pull request could make a pull request that includes an update the version number if their pull request makes a breaking change (ie, increment major)  I think nemec, myself and others will end up coordinating on that and having final say, by either submitting a commit into master updating appveyor.yml with correct version then merge into release

Any objections?

 Comment by clmcgrath
Thursday Nov 02, 2017 at 18:53 GMT

I am good with that ,  can we move open pull requests to the new repo automatically as well ?
i know there is an import tool not sure if that works with other github repos or not

 Comment by clmcgrath
Thursday Nov 02, 2017 at 18:58 GMT

guess not ,  looks like it only does repo cloning

The docs and readme states project supports .net core but not which specific version of .net standard and when I installe the NuGet package it brings down the .NET Framework 4.6.1 version for which VS then says it is incompatible with my .NET Core 2.0 console project.
What's that about?

Please file this as a separate issue.
Thanks.
On Mon, Nov 27, 2017 at 5:07 AM, mare<EMAIL_ADDRESS>wrote:

The docs and readme states project supports .net core but not which
specific version of .net standard and when I installe the NuGet package it
brings down the .NET Framework 4.6.1 version for which VS then says it is
incompatible with my .NET Core 2.0 console project.
What's that about?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/commandlineparser/commandline/issues/171#issuecomment-347135187,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACG_zLzZIqdWxEktRCmbpqHr4kvN8EXiks5s6onsgaJpZM4QSHTQ
.

--
E.Newton
Senior Software Craftsman
Cell:<PHONE_NUMBER>
EMail<EMAIL_ADDRESS>

@ericnewton76 This seems like it could be closed.


Add PA scraper

Multiple HTML pages, line break delimited: https://www.dli.pa.gov/Individuals/Workforce-Development/warn/notices/Pages/default.aspx

*adding this comment here as well
Switching the function to write_rows_to_csv and dicts to lists helps. The layoff date and layoff type are switched after a certain month, so fixing that should solve all the problems.

Thanks! If you wanted to open another PR with that change, I wouldn't object.


Breaking Community page few seconds after loading. Dark/white theme toggle. Changing the state of the like button on blogs page

I am new to open source and this project in particular. I would like to improve on the following states of your application

Breaking community page a few seconds after loading. I am having a challenge using navigation bar to access the Community page section. It says "Unexpected Application Error! Invalid time value".

Implement the toggle button on "light" and "dark" theme. Using the inbuilt chrome light/dark theme is making the user miss important updates, the UI is not very user friendly on dark theme.

Was the thumbs up button on blogs page meant to change state as like button? I would recommend its subsequent change in state when i click  👍 to it.

Hey @allanmathenge, thank you for creating this issue 😌. Would you be interested in jumping on a call with me to discuss this issue some more?
We're always looking out for people willing to get into open source and I'm sure you can help us out a ton. 🙂

YES. We can schedule a call. I'll be impressed.
On Wed, Jan 24, 2024, 10:40 Sonia Lomo @.***> wrote:

Hey @allanmathenge https://github.com/allanmathenge, thank you for
creating this issue 😌. Would you be interested in jumping on a call with
me to discuss this issue some more?
We're always looking out for people willing to get into open source and
I'm sure you can help us out a ton. 🙂
—
Reply to this email directly, view it on GitHub
https://github.com/SpaceyaTech/SYT-Web-Redesign/issues/116#issuecomment-1907565616,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A7RCJ5CWEDMQ27GUW4KSLLLYQC3G7AVCNFSM6AAAAABCF6W2LSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBXGU3DKNRRGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

What's your email address?

@.***
On Fri, Jan 26, 2024, 09:58 Sonia Lomo @.***> wrote:

What's your email address?
—
Reply to this email directly, view it on GitHub
https://github.com/SpaceyaTech/SYT-Web-Redesign/issues/116#issuecomment-1911579075,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A7RCJ5E4LKP4UPBFP3R2BRTYQNH2NAVCNFSM6AAAAABCF6W2LSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJRGU3TSMBXGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

Reach out to me via email<EMAIL_ADDRESS>so we can arrange a call.

Reach out to me via email<EMAIL_ADDRESS>so we can arrange a call.

did this call happen?

Yes, on Jan 27. I've been working on that.
On Wed, Feb 7, 2024, 08:09 Jimmy Oty @.***> wrote:

Reach out to me via email @.***) so we can arrange a call.
did this call happen?
—
Reply to this email directly, view it on GitHub
https://github.com/SpaceyaTech/SYT-Web-Redesign/issues/116#issuecomment-1931294854,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A7RCJ5BE73NSMSMAOIXLBKDYSMEAJAVCNFSM6AAAAABCF6W2LSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZRGI4TIOBVGQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

@allanmathenge , are you still experiencing the breaking community page issue? 👀

the first issue has been addressed
the second issue is low priority at the moment and will not be addressed for now
the third issue will be addressed in a future website redesign sprint


Import html format automatically changed to mark down

I have a preview knowledge base and the answer is html format.
But when I export and import to GA version, the html automatically changed to mark down.
For example:
link
changed to
link
Any idea how to keep the original format?

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

ID: 7cb10c01-db1f-1c61-f5cd-857df2b7fbd8
Version Independent ID: 3ef184f7-6288-caec-ea33-f3d5dadd8965
Content: Learn about QnA Maker - Microsoft Cognitive Services - Azure
Content Source: articles/cognitive-services/QnAMaker/Overview/overview.md
Service: cognitive-services
Product: unspecified
GitHub Login: @nstulasi
Microsoft Alias: saneppal

@Wayne-Shen Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.
@nstulasi Can you please take a look to see if you have any idea? Thanks a lot!

Close due to duplicate issue #8915


EPIC: Hyberboard owner admin panel

[ ] #1009

[ ] #1069
[ ] #1010

closing as everything moved to the hypercerts 'hypeboard project'


Rclone with GFS works, but crypt on top does not.

 It appears to work just fine. Using a command like (rclone lsd "localdrive:g:My Drive\enc") However when using the "crypt" on top of this it just produces errors.
I tried two differnt formats in the config.
type = crypt
remote = "G:\My Drive\enc"

and
type = crypt
remote = "localdrive:g:My Drive\enc"

2017/11/17 17:00:44 NOTICE: Local file system at : Replacing invalid characters in "\\Users\\userABC\\\"g:\\My Drive\\enc\"" to "\\\\?\\C:\\Users\\userABC\\_g_\\My Drive\\enc_"
2017/11/17 17:00:44 NOTICE: Local file system at : Replacing invalid characters in "\\Users\\userABC\\\"g:\\My Drive\\enc\"" to "\\\\?\\C:\\Users\\userABC\\_g_\\My Drive\\enc_"
2017/11/17 17:00:44 ERROR : : error listing: directory not found

Oh, I see the problem.  You have quotes " around your remote names.
Try removing those and they both should work.
PS I thought I posted this earlier but it seems to have disappeared - maybe I forgot to press the button!  Thank heavens for lazarus!

Ok i feel like a bonehead but i still cant get this to work.
[localgdrive]
type = local
nounc = true

PS C:\Users\userabc> rclone lsd localgdrive:g:
          -1 2017-11-18 21:18:39        -1 $RECYCLE.BIN
          -1 2017-11-18 21:18:39        -1 My Drive

[enclocalgdrive]
type = crypt
remote = localgdrive:g:My Drive\enc
filename_encryption = standard
password = REMOVED
password2 = REMOVED

PS C:\Users\userabc> rclone lsd enclocalgdrive:
PS C:\Users\userabc>

This is what i think it should be minus the quotes.

No worries - glad you got it to work.


IApplicationLifetime.StopApplication have no influence on IHostedService cancellation tokens

From @v-zubritsky on August 3, 2018 13:39
I've encountered an unexpected behavior with IHostedService implementation, cancellation tokens passed to it and IApplicationLifetime interface.
I have two hosted services, both of which perform some initialization on start, and if it succeeds, they do their work in background. But if initialization fails, I'd like to stop the application at all, as far as this background work is critical.
I inject IApplicationLifetime into services and call StopApplication on it in case of initialization failure. Application does stop, but cancellation tokens, passed to my IHostedServices and provided further for graceful shutdown handling, are not cancelled for some reason.
I have to link those tokens with IApplicationLifetime.ApplicationStopping to handle this issue, but this behavior doesn't seem too obvious.
public Task StartAsync(CancellationToken cancellationToken)
{
    var stoppingTokenSource =
        CancellationTokenSource.CreateLinkedTokenSource(
            cancellationToken,
            this.applicationLifetime.ApplicationStopping);
    ...
}

Repo to see this behavior reproduced is available by link.
Microsoft.AspNetCore.App 2.1.1 is used
dotnet --info outputs
.NET Core SDK (reflecting any global.json):
 Version:   2.1.302
 Commit:<PHONE_NUMBER>

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.17134
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\2.1.302\

Host (useful for support):
  Version: 2.1.2
  Commit:  811c3ce6c0

.NET Core SDKs installed:
  2.1.201 [C:\Program Files\dotnet\sdk]
  2.1.202 [C:\Program Files\dotnet\sdk]
  2.1.302 [C:\Program Files\dotnet\sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.0.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.0.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]

Copied from original issue: aspnet/Home#3384

Correct me if I am wrong but the IHostedService is transient. So it won't exist anymore once you have completed the start. You need a Singleton that the IHostedService calls some method on if you want to persist anything passed the start call.

The WebHost holds onto the resolved instances and is responsible for stopping them.

We periodically close 'discussion' issues that have not been updated in a long period of time.
We apologize if this causes any inconvenience. We ask that if you are still encountering an issue, please log a new issue with updated information and we will investigate.


Travis failures due phpunit strictness

What's up with the phpunit setup on travis?
What is the purpose of such setup?
install:
  - if [ "$TRAVIS_PHP_VERSION" = "5.5" ]; then composer require "phpunit/phpunit:^4.8" --dev; fi;
  - if [ "$TRAVIS_PHP_VERSION" != "5.5" ]; then composer install --prefer-dist; fi;

script:
  - if [ "$TRAVIS_PHP_VERSION" = "5.5" ]; then ./vendor/bin/phpunit; fi;
  - if [ "$TRAVIS_PHP_VERSION" != "5.5" ]; then phpunit; fi;

Currently travis is failing on 7.2, because it's using travis preinstalled version, that requires :void type hints for unit tests.
Example:
PHP Fatal error:  Declaration of Tests\chobie\Jira\Api\Client\AbstractClientTestCase::setUp() must be compatible with PHPUnit\Framework\TestCase::setUp(): void in /home/travis/build/chobie/jira-api-restclient/tests/Jira/Api/Client/AbstractClientTestCase.php on line 312

I've recently tackled with travis and phpunit, and ended up using composer global require only one specific version, so the phpunit deprecations and new methods don't end up conflicting.
https://github.com/eventum/eventum/pull/468
If you describe goal (phpunit version) i'd try to submit PR with that goal
cc @aik099

the 5.5 compare is from https://github.com/chobie/jira-api-restclient/pull/169

What is the purpose of such setup?

On Travis CI the preinstalled version of PHPUnit works well (has forward compatible namespaced PHPUnit class names). Unfortunately that's not the case with PHPUnit installed on PHP 5.5 version (that PHPUnit version is fixed in the container used to install PHP 5.5 VM). For that reason alone we've installing latest PHP 5.5.x compatible PHPUnit version and using it.
Not sure if the issue was fixed on Travis CI. I'd rather prefer to use built-in PHPUnit version to speed up build time.

PHP Fatal error:  Declaration of Tests\chobie\Jira\Api\Client\AbstractClientTestCase::setUp() must be compatible with PHPUnit\Framework\TestCase::setUp(): void in /home/travis/build/chobie/jira-api-restclient/tests/Jira/Api/Client/AbstractClientTestCase.php on line 312

That is tricky situation. Likely preinstalled on Travis version of PHPUnit is the one, where strict types are used and that breaks all out test case classes, because due to BC break introduced in PHPUnit we can't have same test case that would comply with all PHPUnit versions anymore.
What we need to use PHPUnit version corresponding to used PHP version and a single copy of a test case class to work on them. We can try limiting used PHPUnit version to which where strict types weren't introduced and use same .travis.yml trick to install that.

Speed up pipeline can be done with caching, so that shouldn't be an issue.
Do you have phpunit versions you wish to support? I know that need to have 4.8.36 for PHP 5.3, but what about the upper bound?

I don't care much what PHPUnit version is used on a particular PHP version during build as long as tests can run. We can pick PHPUnit version, that runs across all current PHP version and use it consistently in all builds as well. I'm not sure, that such version exists considering that PHPUnit is eager to increase minimal supported PHP version with every major release :(
I think, that for fixing PHP 7.2 failed build it's enough to lock PHPUnit version used there to PHPUnit 7 (good if it works) or PHPUnit 6 at least.

In #196 (when we moved to GitHub Actions) we started to use yoast/phpunit-polyfills library to automatically choose the latest PHPUnit version available on the currently used PHP version for us.
I guess this can be closed now.


List profiles

The profile editor now creates, reads, updates and deletes profiles from verso.
I disabled overwriting a profile record based on a matching title.   A warning is thrown that alerts the user that the title is not unique.
Vocabularies do not load now, since all of the server functions point to verso-- but I will get that working tomorrow.

The vocabularies have been loaded into verso.  Profile-edit now reads vocabs from verso and populates the select box.  There still is some work to do to get the objects to display properly in vocab list-- That'll have to wait until Monday.

Ok, Kirk:
The RDF data model is slightly different as stored in verso.  The actually text values are stored in the __text element.  This is why we were getting the [Object Object] error in the resources/property lists.
Everything looks good now.

The profile editor now fetches languages from verso.  The profile-editor still gets templateRefs from the file server.  Should these be moved over to verso as well?

I think moving templateRefs to verso is part of requirement 3.1.2, so maybe hold off on that for now?