Master layout strange window focus changing behaviour

This isn't a bug that brings everything to a crash, but it is definitely a strange behavior.
It also seems difficult to isolate.
Sometimes I will have a workspace full of tiles and it will get stuck in a strange state where the buttons I usually press to "cyclenext" or "cycleprev" will only cycle between two of the open windows. They are stuck like this until I close them all. In this state I can close the master window and the others will still stay stacked on the right hand side of the screen as if it were still there. This state is isolated to a single workspace, I can go to another and things work like normal. It is very weird, in this state "cycleprev" will always swap between the master and the top right window, and "cyclenext" will always swap between the bottom right and the window above it.
I think it may have something to do with Firefox, as it frequently happens after I use Firefox and go back to playing with tiles...But I am likely totally wrong.
Sorry I can't be more specific, I've been trying to see what the trigger is for some time now but I just can't figure it out.
I'm on Gentoo right now, but the same thing happened on Arch.
That all being said, I love the work you are doing. I was a long time dwm user, but Hyprland has really won me over, even though I turn off a lot of the selling points! (animations, gaps, rounding)

I also have the same issue. But cannot work out the trigger

I need this to be reproducible, cuz I've never seen this.

I have the same problem with stuck on focusing certain clients in master tiling . In my case I can  cycleprev and cyclenext fine until I move a client from another workspace into said workspace. When that happen cyclenext would only focusing between master and topmost slave client (just between 2 of them). cycleprev would be able to break that cycle only to be stuck on focusing the slave clients, and vice versa for cyclenext.
As of writing this, while trying to get the trigger right in my case, the workspace where I move the client from, wp3, had this problem where it doesn't stack properly with the master client missing. After I close the client in wp3, there was a client that seemingly in different layer of the WM, I can't focus and hyprctl kill it. Only until after I move  3 clients from the testing workspace, wp1, that it fixes the tiling. But after the 4th clients it is the same problem as in the first paragraph.

Yeah. I can confirm @rezaamashi I have the same trigger.
To summarise:
My configuration consists of
general {
    ...
    layout=master
    ...
}

master {
    new_is_master=false
}

Reproducible steps:

open 2 windows on workspace 1
open 1 window on workspace 2
move window from workspace 2 -> 1 using movetoworkspacesilent

The master-stack layout on workspace 1 now has this weird behavior cycling through these windows

IDK if my problem applies to the same issue or not, but basically  cyclenext  in full-screen mode changes the focus but doesn't swap the windows, so I end up with the unfocused window on top.

I have the same problem with stuck on focusing certain clients in master tiling . In my case I can cycleprev and cyclenext fine until I move a client from another workspace into said workspace. When that happen cyclenext would only focusing between master and topmost slave client (just between 2 of them). cycleprev would be able to break that cycle only to be stuck on focusing the slave clients, and vice versa for cyclenext.
As of writing this, while trying to get the trigger right in my case, the workspace where I move the client from, wp3, had this problem where it doesn't stack properly with the master client missing. After I close the client in wp3, there was a client that seemingly in different layer of the WM, I can't focus and hyprctl kill it. Only until after I move 3 clients from the testing workspace, wp1, that it fixes the tiling. But after the 4th clients it is the same problem as in the first paragraph.

Haven't check on this issue for a while. But for now, the reproducible problem (the first paragraph) is fixed in the latest hyprland-git from AUR. So far I only experienced the problem missing/phantom client once. But as the nature of it was irreproducible I can't get the hang of what was the cause.

There have been numerous improvements to master since this issue was opened, but I've never been able to repro this. I'll let the original reporters report back on the issue @queer-bird @patrickaldis


luci-theme-material: fix some style bug in LUCI newest version

Signed-off-by: Lutty Yang<EMAIL_ADDRESS>

merged.


support Libvirt

The first implement is just a normal binding, and it can't be build statically. Maybe this project can help us for the next version:
https://github.com/polachok/libvirt-rpc/blob/master/src/async.rs

duplicated


Use AuthoritativeDnsServerCache for creating the new redirect stream.

Motivation:
At the moment if a user wants to provide custom sorting of the nameservers used for redirects it needs to be implemented in two places. This is more complicated as it needs to be.
Modifications:

Just delegate to the AuthoritativeDnsServerCache always as we fill it before we call newRedirectDnsServerStream anyway.

Result:
Easier way for the user to implement custom sorting.

@trustin addressed


undefined externals compiling model to mexw64

In amiwrap and compileC, the following externals are undefined:
__imp___iob_func
__imp_fprintf
__imp_vsprintf
__imp_printf
In addition, sprint is causing a warning, even though stdio.h is imported.
The details are in the attachment.
error-2015-11-14.docx

I found the problem and fixed it in my code. This is caused by changes in the Microsoft C runtime in version 2015. I recently upgraded Visual Studio from 2013 to 2015 and Matlab from 2015a to 2015b. The fix is simply to delete all objects and recompile, so that all CRT components have the same version.
Here is a link to one for the descriptions:
https://connect.microsoft.com/VisualStudio/feedback/details/1144980/error-lnk2001-unresolved-external-symbol-imp-iob-func


2.0 docs: Source links not pointing to actual source

In many cases the source links don't actually point to the source of the described functionality, but to a search query on github that only rarely points to the relevant code.
It would be very helpful for learners who want to study the code behind functionality to be able to quickly access the source without having to search manually.

I'd be open to a PR with a better solution, but I'd like to keep these links automatically generated somehow, as I fear it would slow down Vue development having to manually update line numbers whenever making a change to a file. Do you have any ideas?

I didn't exactly understand this one.
What is the "source links" pointed?
If it's docs sources, the links are currently auto-generated.
Being source code links, never seen one in docs.

Actually, I was about to close this due to inactivity.


UI v3

The UI/UX should :

As an infographic : show useful information at page load, don't show too much information, be readable quickly and disturb the page flow as little as possible.
As an interactive dataviz and filter : allow to change as many parameters as possible and create the most possible combinations in the least possible interactions.

It wasn't really possible to keep the donuts of the first UI as soon as the number of data parameters increased, as the circles would take more space and the complexity increase as well. The second version of the UI allowed to show a large range of numbers in a single screen, regardless of the number of jobs. But the donuts of the first version, by making an emphase on jobs, included the graphs as a part of the author profile, of the biography. A sort of "Mr. X is a director, writer, producer born in...".

UI 1 (up to v0.3)
UI 2 (v0.4...)

As the number of parameters will rise again with the someday inclusion of type (movies/shows) and duration, a third version need to be designed, and should mix the advantages of each previous one. It will require the selection of which information would be available at the same time.

First wireframe for a third version :

Jobs :

Use badges-like UI, to act as a biographic element. Icons (camera, pencil...) could event emphasis that, but would take additional space.
Use loading bars to gain some space over donuts and allow more text inside the same radius.
Get rid of "All". The visual sum of each element should be enough to interpret the overall. Every jobs block would be selectable/unselectable. The "loading bar" would reflect the current filter, and by default being seen/not seen.

Filters "bar"

Use filter-like UI : selects and buttons.
The first select input would be the only interface to switch between movies and series.

It may include options for feature-length films and short films that would act as shortcuts for the next input.

Another input would be the only interface for selecting the duration.

As there will generally be not enough data to see a relevant visual distribution, there would be no graph of this data.
As there is probably no use to be able to select precise intervals, the input would give options to some specific ranges like less than 1h, about 1h30, about 2h, about 2h30, more than 3h.

seen / rated / collected / listed would be shown once and act as switches. To be able to reach didn't seen etc, we could consider activating seen on first click, then not seen on second click, and deactivating on third click.
Other inputs to give shortcuts to existing data and expose new notions :

liked : would select ratings ranges, for example don't liked / liked for 1-4 and 6-10, or don't liked / liked meh / liked, or don't liked / liked / loved ?

Graphs

Only decades and ratings. Duration don't seem relevant.
Aligned with the watchlist... buttons, as a sort of sidebar, to mark a separation between "dataviz" and "biographic elements" as the jobs.


Dev - Edit close does not reload data anymore, not even when saved

That was only temporary, new commit is on the dev branch.

Only work sometimes. I saved multiple times and it worked about 50% of the cases.
If it's really hard to get it working maybe a workaround would just be
< Return       Save and return

In the backbar.

Hooking into submitting the form as an action is probably even more unreliable than just trying to listen to a submit. :/

Maybe I have to set a higher timeout on the submit listener. Given that submits will occur a little later, cause they will involve changes that first have to be made.

I also tried to save and exit fast and it did not seem to keep up. What about this not so hackish solution? Too simple?
< Return       Return and refresh

Yea, cause I have to set a timeout before binding a listener to the submit event, cause if the panel hasn't loaded yet, this will crash otherwise.

Hmm, are we talking about the same thing? The latest suggestion was this:
< Return       Return and refresh

Return = Hide / remove the iframe with JS. It does not care if the panel is loaded or if something was saved or not.
Return and refresh = An url back to the page. It does not care if the panel is loaded or if something was saved or not.
Then this would make rid of the JS iframe listening to events thing?


Is there a way / are there plans to provide lifecycle / hooks methods?

Currently I'm providing structured config files alongside urfavecli, the problem with this is that config files for urfave are "just another way to declare flag values"; they are flat, not hyerarchical.
The workaround we're doing is ugly, as it goes against the defined priorities on urfavecli, since the only time I can set values on the flags are after these are already parsed (even the Before hook, flags have already been parsed by the time we reach it)
I've tried implementing the flag parsing myself but the prospects of maintaining this piece aside my usual work load is dark, and I haven't dig deep enough into urfavecli codebase to submit a patch, however I am willing to invest the time.
I guess I'm asking this because I've seen in some issues and comments that there is an active development for a v3, and perhaps this has been accounted for, perhaps not, or perhaps there is still room for feature submissions.
The reference point would be kong hooks, I have not personally used Kong, but these hooks seem to do just what we want.
This is the use case I'm trying to address: https://github.com/refs/urfave-yaml

@refs Yes we could implement this in v3. Are you willing to submit a PR ?

@refs Could you provide a description of the hooks you are looking for ?

Suggestion by user @axelrindle
The concept of lifecycle hooks sounds great to me. I'd like to propose the following:

beforeFlags (runs before flags are parsed)
afterFlags (runs after flags are parsed, but before commands are run)
beforeCommand (runs before command actions are run; maybe merge with the previous?)
afterCommand (runs after a command action has been run)

@axelrindle we already have Before and After Actions for Command. I definitely see the value in Before & After Flags. The After Flags becomes tricky. When should it be called ? If there is an error in flag parsing(maybe invalid flag parsing etc) should the after flag action be called. What about if there are no parse errors but one of the following happens

help requested(via -h)
Required flags not set.

When should it be called ?

After all flags have been successfully parsed, but before the command action is executed.

If there is an error in flag parsing(maybe invalid flag parsing etc) should the after flag action be called.

I would handle this the same way the AfterCommand hook is handled to stay consistent.

help requested(via -h)

The occurence of -h should not stop flag parsing and thus not prevent the hook from running.

Handle flags
Notice -h
Call AfterFlags
Show help
Exit

Required flags not set.

Treat this as a parsing error and therefore only run hook on success.

I just re-thought about -h and maybe it's better to don't call any hooks when help is requested as the help output should not change based on other flags.


Fix Public Photo Share Toast Notification

A regression happened in 4c2612b85c3799c479eee4112413c64d018b0c53 that caused the toast notifications to indicate the opposite effect when sharing a photo publicly.

Thanks for contributing! Looks good to me :)


GitHub Dependency Review POC

GitHub Dependency Review action POC.
Proposed Changes

Potential Breaking Changes

Acceptance Criteria

[ ] The proposed changes are covered by unit tests
[ ] The potential breaking changes are clearly identified
[ ] README.md is adjusted to reflect the proposed changes (if relevant)

PNPM is not supported 🤷🏼


closes #505 - allow fullscreen for videos

closes #505 by adding allowfullscreen attribute to iframe (reference: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/iframe)
Wait with merging until #503 and #504 are merged

Please rebase the PR, it includes commits which are on master already

@arekkas aren't those the commits from docker PRs? I can rebase to master too, but can't test it that way, so I thought I wait until the docker PRs are merged.

Ah sure, that makes sense

now it needs rebasing ^^

ah right, because the troubleshooting

done @arekkas


Revert "*: fix some test errors on AMD and/or modern Linux kernels

What have you changed?
this is a simple revert of #6497
What is the type of the changes?
Bugfix (a change which fixes an issue)
How is the PR tested?

Unit test
Integration test

PTAL @zhouqiang-cl @siddontang

/merge


process.argv[1] has trailing .tsx

Apparently this is the way to check whether you're running a script directly in ESM:
import.meta.url.startsWith('file:') and
process.argv[1] === url.fileURLToPath import.meta.url

Unfortunately, it doesn't work for scripts currently run via the civet CLI, because process.argv[1] ends up being not the original .civet filename but the pretend compiled filename .civet.tsx.  Thus we currently need to do:
import.meta.url.startsWith('file:') and
process.argv[1]+'.tsx' === url.fileURLToPath import.meta.url

I think we should probably not have the .tsx suffix in process.argv[1]. This should be an easy fix; just marking it for later.

This actually seems difficult to do right.  civet filename.civet is simply executing
node --loader @danielx/civet/esm filename.civet

The actual issue is that the ESM loader adds .tsx to the official URL:
https://github.com/DanielXMoore/Civet/blob/db932b8f7fb98ab67752178e73d7028421f8fcca/source/esm.civet#L80
This is kind of annoying in that import.meta.url now no longer refers to an actual physical file.
On the other hand, this kind of URL mangling is presumably necessary to trigger ts-node. (That's not happening in this case, but in other invocations could be necessary.)
Do you still a way to improve this situation? If not, maybe we just need to document this weirdness. I'll use import.meta.url.replace /\.tsx$/, '' for my application. (Detecting the "main" module is getting really hard!)

I think we can continue to append .tsx so that downstream loaders/transforms work as expected. We can then probably strip it out after awaiting the result of downstream loaders.


Multi-select with Contains() does not generate SQL

The following does not generate SQL with the IN operator.
var ids = new int[] {1,2,3};
_db.Table.Where(x => ids.Contains(x.Id)).ToList();

duplicate of https://github.com/aspnet/EntityFramework/issues/1243

Fixed in 32cb631986fbd10a1ec5e4aaa7dcaded0eab7270

@maumar, one small detail. What is the intended behaviour when the list of ids is empty, say:
var ids = new int[];
_db.Table.Where(x => ids.Contains(x.Id)).ToList();

Right now it generates the following invalid SQL:
SELECT [x].[Id], [x].[SomeOtherColumn]
FROM [Table] AS [x]
WHERE [x].[Id] IN ()
go

I know that I should probably check for the list to be empty before sending it to the database, but it would be nice, if this was handled probably inside EF.

EF should cover this case, will fix. Thanks for reporting!

Fixed in 5fe084e06ed743d4d8423815829b802bcb9c86f1


Upload 563 create json logger bulk upload api

Create a json logger for bulk upload api.

have you tested the logs are outputting in the format you desire in Azure? i.e have you tried deploying this code to dev and confirming?

Yes, the code is now in dev, tested, and outputs results in JSON. I'll do another test and send the portal link soon.


[G2M] cleanup - remove tech evangelist

Also upgrade runtime to node 18, relevant github actions, and dependencies

LGTM!
Also, (no hard intentions) but to keep everything in sync, I think you can also start creating issues under Notion PM and referencing that here, for back and forth linking. Other than this, all fine.

Sounds good. Would you like to create a Notion page for me for this one so I can follow along in the future, and I'll link it in here


"maximum recursion depth exceeded" in deepcopy() in fresh_finally_clause()

Using Cython master on Python 2.7.13:
This code
cdef inline bint g(int *x, int *y): return True

cdef cython_bug(int *u):
    try:
        assert g(u, u)
        assert g(u, u)
        assert g(u, u)
        assert g(u, u)
        assert g(u, u)
        assert g(u, u)
        assert g(u, u)
        assert g(u, u)
        assert g(u, u)
        assert g(u, u)
        assert g(u, u)
        assert g(u, u)
        assert g(u, u)
        assert g(u, u)
        assert g(u, u)
        assert g(u, u)
        assert g(u, u)
        assert g(u, u)
        assert g(u, u)
        assert g(u, u)
    finally:
        g(u, u)

hits Python's recursion limit of 1000 frames:
Traceback (most recent call last):
  File "/usr/local/src/sage-config/local/bin/cython", line 11, in <module>
    load_entry_point('Cython==0.26a0', 'console_scripts', 'cython')()
  File "/usr/local/src/sage-config/local/lib/python2.7/site-packages/Cython/Compiler/Main.py", line 694, in setuptools_main
    return main(command_line = 1)
  File "/usr/local/src/sage-config/local/lib/python2.7/site-packages/Cython/Compiler/Main.py", line 711, in main
    result = compile(sources, options)
  File "/usr/local/src/sage-config/local/lib/python2.7/site-packages/Cython/Compiler/Main.py", line 686, in compile
    return compile_multiple(source, options)
  File "/usr/local/src/sage-config/local/lib/python2.7/site-packages/Cython/Compiler/Main.py", line 664, in compile_multiple
    result = run_pipeline(source, options, context=context)
  File "/usr/local/src/sage-config/local/lib/python2.7/site-packages/Cython/Compiler/Main.py", line 494, in run_pipeline
    err, enddata = Pipeline.run_pipeline(pipeline, source)
  File "/usr/local/src/sage-config/local/lib/python2.7/site-packages/Cython/Compiler/Pipeline.py", line 340, in run_pipeline
    data = phase(data)
  File "/usr/local/src/sage-config/local/lib/python2.7/site-packages/Cython/Compiler/Pipeline.py", line 53, in generate_pyx_code_stage
    module_node.process_implementation(options, result)
  File "/usr/local/src/sage-config/local/lib/python2.7/site-packages/Cython/Compiler/ModuleNode.py", line 137, in process_implementation
    self.generate_c_code(env, options, result)
  File "/usr/local/src/sage-config/local/lib/python2.7/site-packages/Cython/Compiler/ModuleNode.py", line 365, in generate_c_code
    self.body.generate_function_definitions(env, code)
  File "/usr/local/src/sage-config/local/lib/python2.7/site-packages/Cython/Compiler/Nodes.py", line 418, in generate_function_definitions
    stat.generate_function_definitions(env, code)
  File "/usr/local/src/sage-config/local/lib/python2.7/site-packages/Cython/Compiler/Nodes.py", line 1920, in generate_function_definitions
    self.generate_function_body(env, code)
  File "/usr/local/src/sage-config/local/lib/python2.7/site-packages/Cython/Compiler/Nodes.py", line 1683, in generate_function_body
    self.body.generate_execution_code(code)
  File "/usr/local/src/sage-config/local/lib/python2.7/site-packages/Cython/Compiler/Nodes.py", line 424, in generate_execution_code
    stat.generate_execution_code(code)
  File "/usr/local/src/sage-config/local/lib/python2.7/site-packages/Cython/Compiler/Nodes.py", line 7034, in generate_execution_code
    fresh_finally_clause().generate_execution_code(code)
  File "/usr/local/src/sage-config/local/lib/python2.7/site-packages/Cython/Compiler/Nodes.py", line 7022, in fresh_finally_clause
    node_copy = copy.deepcopy(node)
  File "/usr/local/src/sage-config/local/lib/python2.7/copy.py", line 190, in deepcopy
    y = _reconstruct(x, rv, 1, memo)
  File "/usr/local/src/sage-config/local/lib/python2.7/copy.py", line 334, in _reconstruct
    state = deepcopy(state, memo)
[...long traceback involving deepcopy...]

It's not an infinite recursion since sys.setrecursionlimit(2000) fixes the problem.

This works fine for me. Are there some different options/directives I should be passing?

Maybe it depends on the Python version. Are you using 2.7.13?

Are there some different options/directives I should be passing?

No, this is just executing cython test.pyx with test.pyx the file in the issue description.

What is worrying here is that the required stack depth is O(n) in the number of statements inside the try clause.

f8b3405e926d2ba9bc2ee24d79848235875ee12e is the first bad commit
commit f8b3405e926d2ba9bc2ee24d79848235875ee12e
Author: Robert Bradshaw<EMAIL_ADDRESS>Date:   Thu Jun 15 15:51:15 2017 -0700

    Don't override unknown inherited __reduce__.

Yeah, that is worrying. I built a fresh 2.7.13 Python and cloned a fresh branch of cython/master and I still can't reproduce, e.g.
python cython.py lots_of_asserts.pyx
works just fine for me, even doubling the number of asserts.

Well, Sage is using a slightly patched version of Python 2.7.13 so it could always be that some of those patches are relevant. I'll investigate further.

It is failing on Travis CI, see #1745.
Could it be OS-specific? I'm on Linux and I guess Travis CI also.

I tried that test (thanks) on two separate Linux (Ubuntu) installs as well as my OS X laptop, and had no issues. But I do see the error up on Travis. The code touched at f8b3405e926d2ba9bc2ee24d79848235875ee12e shouldn't even get invoked if there aren't any cdef classes, so something really strange is going on here...

Here it's actually copying the finally clause, which shouldn't be sensitive to the size of the body. (I've always considered literally copying the finally for each exit to be a bit hackish though...maybe this will be the motivation to re-write, though I'd like to understand why there's such a deep stack here.)

I finally figured it out--the repro required a compiled Cython (which is also why the pickling code was actually involved).
This should be fixed at https://github.com/cython/cython/commit/114fe16bdaa527bb5024c975a8accfc1e052ab68

Nice!


Cloud Watch does not appear in AWS Explorer

Describe the bug

I'm trying to view my Amazon CloudWatch Logs in Visual Studio using the AWS Toolkit for Visual Studio and following this announcement which points to these instructions:  https://docs.aws.amazon.com/toolkit-for-visual-studio/latest/user-guide/cloudwatch-log.html
However, I don't see CloudWatch in the Services list.

To Reproduce

Open Visual Studio 2022
Open AWS Explorer
Ensure Crendentials drop down has a valid profile selected
Ensure Region is selecting a region with existing logs
Notice that Cloud Watch does not appear in Services List

Expected behavior

Expect a link to open Cloud Watch logs
Screenshots

Computer (please complete the following information):

Windows Version: 10
Visual Studio Version: 2022
AWS Toolkit for Visual Studio Version: <IP_ADDRESS>

Additional context

I can see my Cloud Watch Logs from AWS Console:

Hi @ppittle , please try updating to the latest version of the Toolkit (currently, version <IP_ADDRESS>). If it still does not appear for you, perhaps your Toolkit logs can help explain why it is missing. From that newer version of the toolkit, go to the Extensions menu > AWS Toolkit > View Toolkit Logs, then attach your logs to this issue.

Upgraded to 1.37.0 and can now see Amazon CloudWatch!


Update f95d394f-fbed-8d64-143d-a51368df158c.md

You are asserting that the expression is true, you therefore only break if it is false.

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

VBA/Language-Reference-VBA/articles/f95d394f-fbed-8d64-143d-a51368df158c.md
:white_check_mark:Succeeded

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

commit merged in local master repo


handling missing characters like ऩ ऱ ऴ क़ ख़ ग़ ज़ ड़ ढ़ फ़ य़ in Telugu/Tamil/Malayalam

Some nice pointers by @vvasuki in https://github.com/sanskrit-coders/indic_transliteration/commit/caeb1b4547c1a74469ced4760541aba10f0bcaae#r45792167

Should be handled now.


CodeceptJs v3.4.0 it doesn't retern when failing in Before hook

What are you trying to achieve?
I just updated to v3.4.0 so I can use "Retry Before". However, it's not returning when Before hook fails
What do you get instead?
It's not returning in console.
Details

CodeceptJS version: 3.4.0
NodeJS Version: v14.16.0
Operating System: Windows
Configuration file:

what do you mean by not returning?
could you provide more details on your case?

Case:
To make it simple and isolated issue.
I'm just running one feature file which has Before hook and one scenario.
Setup in Before hook is failing even after retry
Expected:
Marking the test case as failed and generate reports if any used.
Actual:
After setup fails, no information is console is shown. And console hangs. and the only way to end running is by force stop the console.

To regenerate the issue, just start new project from scratch.
I used Typescript with chromium.
And write one feature file with Before hook and a scenario where setup in Before hook fails.
Then run it.

sorry, that won't help me reproduce the issue
without a code sample, I can't help
could you paste a code of a test you are working on or create a repo with a reproducible example

Okay please check this repo https://github.com/MhdAlkh/BeforeHookIssue

Thanks, checking!

Thanks for a reproducable example
I worked on retries of before so long that forgot the case that Before could actually fail :smile:
Updated this and released 3.4.1

Amazing, Thanks a lot for the prompt response 💯

This issue doesn't seem to be resolved, we started getting a lot of stuck builds on Jenkins after we updated CodeceptJS to version 3.4.1.


Add features to Standard Library

This task should only be completed after research in #7 has been done.

exec
const execSync = require('child_process').execSync;
code = execSync('node -v');

fetch
https://www.npmjs.com/package/sync-fetch

random

FROM ARRAY
sort
reverse


Add a change function

I have an application with two DatePickers.  The second must have a date >= to the first.  This is the simplest solution I could come up with to update the second's value.
It might make more sense expose some, or all, of the Msg types. Maybe even adding a Next/PrevYear to deal with #5?
Thanks for the DatePicker, it is really helpful.

Thanks!  This looks good, but could you rename the function to something like changeDate or putDate? Also, please run the change through elm-format.

After working on this some more – I worked my code so this change wasn't necessary.
Instead of changing the second date picker, I replace it with the first.
That said, it probably would be good to have a change mechanism – but maybe this can be done by just exposing the Pick msg?

It looks like you might get what you want from #9 / #10 , which I'm working on merging now. getDate would let you retrieve updated dates without exposing the message tag Pick (which I'm told you generally don't want to do in an Elm API). 👍 ?
(In the meantime, closing PR).


[BUG] fixKeys fails for emailSend and senderProfile

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior

Expected Behavior
worked for direct deploy attempt though:

Steps To Reproduce

Go to '...'
Click on '....'
Run '...'
See error...

Version
6.0.2
Environment

OS:
Node:
npm:

Participation

[X] I am willing to submit a pull request for this issue.

Additional comments
No response

similar situation for senderProfile

12:32:40.155 info: Found 12 senderProfile keys to fix
12:32:40.158 info: mcdev:: Deploy
12:32:40.168 info: :: Deploying to R1/Randstad_X2GCQA2
12:32:40.182 warn: No deployable metadata found for type senderProfile for selected keys
12:32:40.184 error: No metadata found in deploy folder for selected BU
12:32:40.184 debug: Util.signalFataError() sets process.exitCode = 1 unless already set
12:32:40.185 info: :: Deployed 1 BUs
12:32:40.185 error: mcdev.fixKeys failed:
12:32:40.187 error:     Cannot convert undefined or null to object (undefined)
12:32:40.187 debug: Util.signalFataError() sets process.exitCode = 1 unless already set
12:32:40.188 debug: TypeError: Cannot convert undefined or null to object
at Function.values ()
at #fixKeys (file:///C:/Git/sfmc-devtools/lib/index.js:1224:52)
at async #runOnBU (file:///C:/Git/sfmc-devtools/lib/index.js:1092:44)
at async #runMethod (file:///C:/Git/sfmc-devtools/lib/index.js:1044:46)
12:32:40.189 info: :: Done


Necessary changes to observer for full Tracker compatibility

(This is all open for debate and I understand that it is previously undiscussed pull request, but it is easier to debate it with concrete code changes available.)
I am working on integration of Vue with Meteor and I would like that Vue could be a drop-in replacement for Blaze. That is almost possible, because architecture is very similar. Vue is also using reactive dependency tracking, observer, while Meteor/Blaze is using Tracker. Now, there is a lot of code written for Meteor which is using Tracker and it would be great if it could just work with Vue. And in fact it is doable. I managed to create a full 100% compatible Tracker implementation on top of Vue's observer. But there are some changes necessary to observer's implementation and some internals have to be exposed.
This pull request is initial version of changes I had to do to get this first version of Tracker implemented, to get discussion rolling. I would really like to see if this or something like this could get merged into Vue. From my perspective changes do not really change how observer is working, and all existing tests are still passing.
A list of changes:

added support for after flush callbacks
adding a way to force flushing
fixed exception recovery for pushTarget/popTarget
correctly cleanup queue if there is an exception from getter
exposing some internals (probably too much, API could be cleaner there)

Requesting comments, feedback, suggestions. This is work in progress. I will add tests in the future, after we finalize that this is OK to do and everything else.
Example app. Notice how I can use Meteor ReactiveVar inside computed value directly.

Thanks @mitar , you need to follow the contribution guide when opening a PR.  Please refer: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#pull-request-guidelines

@defcc: I thought I did. Which part from the guide I am missing? I will add tests later for new features. I will fix failing tests now. Is there anything else?

Hm, tests are now failing at "should get updated with model when in focus" which seems unrelated to my changes? Flaky tests?

Thanks @mitar , I opened a PR to fix that error.

Tests are passing.

Hey, I think this is an interesting approach, but here's why I think it's unlikely to get merged: these changes increases the public API surface and will impact how we can make changes in Vue in the future.
By exposing the internals, it creates a liability for Vue to keep these APIs intact in order to stick to semver (otherwise it would break anything that relies on them, e.g. your Tracker wrapper). However, the scheduler and the reactivity system really is considered internal, and I intend to keep them internal so that we can iterate and make non-trivial changes to them without affecting the public API. There are a few experiments going on currently (e.g. using ES6 Proxy for change detection, slicing scheduler workload with requestIdleCallback) that all may cause changes to how the scheduler/Watcher/Dep system works, but if these internal implementation details become part of the public API, it places a serious constraint on how we can iterate on things in the future.
I do see the benefits here in that it allows the two reactivity systems to integrate more seamlessly, however I'm not sure whether it justifies adding the extra liability.
For now, a fork seems like the best short-term solution to me. In the long run, I will probably refactor Vue's reactivity system so that it can be exposed in a way that is less coupled to the internal details.

@yyx990803, thank you for your answer.
I do understand your position, but I also think that there are some alternatives available here.
I am not sure what is your position of using _ prefixed symbols. But this could be one way to expose those internals in a way to communicate that those symbols are internal and could break at any point and using them requires that consumer makes sure things work and things are integrated correctly. For example, from our side we could simply exactly require specific version of vue and upgrade it in Meteor package only after a new version is tested. But at the same time, some other developer can try and force a new version much easier than forking our fork and changing things there to get this new version.
Another approach would be to provide a very simple API to register an "observer" module with which one can override default observer code (Dep, Watcher, and queueWatcher). Only the API of those would be fixed, but internal implementation would be left to the module to implement.

Exposing internals with _ while considering them not part of the public API seems fine to me. And the Meteor integration could pin the version of Vue.

@yyx990803, have you made a final decision on this? :)
We in the Meteor/Blaze community need this change in order to move over to your framework!  There's a lot of developers over there waiting excitedly for this development!
Can't we compromise on this by using the "_" to expose just the few internals we need?  We understand if you decided to make breaking changes to this portion of the API we're on our own.  Heck, shut down the said APIs if there is a breaking change and we'll be responsible for updating said APIs and brining them back online once everything passes.
I believe the effort will expose a entire community to your UI framework, possibly increasing the mindshare and popularity!

I love to see the enthusiasm of Meteor community for this. :-) Thanks.
Just to be clear, exposing symbols with _ is not enough, there are also some changes needed the code as shown in this pull request:

added support for after flush callbacks
adding a way to force flushing

(BTW, I will add tests for all those changes if we decide to merge this pull request.)
An alternative approach, of providing a way to register a custom implementation of Dep, Watcher, queueWatcher would allow us to simple completely swap the implementation, but of course the downside is that this common code would not be maintained together, which is a downside. But on the other hand it would not require from you to maintain this part of codebase.
I would also like to point out that some things should probably be merged in any case. I found out that current code is very bad at recovering from any exception, leaving the whole system in a undefined state. You can only reload to recover. This is why I added things like:

fixed exception recovery for pushTarget/popTarget
correctly cleanup queue if there is an exception from getter

Meteor Tracker tests are pretty hard on testing those edge cases and this is how I found them.

If this will be possible, in whatever form, I dare say that Vue will become the default used framework with Meteor. At least for every one still on Blaze. This would be the most sofisticated and imcremental way to start using Vue. Good for both communities!
I started rendering some parts of our app with React. Although React is a great framework, it feels like a mismatch with Meteor. Or tracker, to be more precise.
I truly hope this interoperability will see the light of day!

Resolved merge conflicts with current dev branch.

@yyx990803, you added a 'pending' label to this PR.  Sorry, but what does this mean for us waiting on this change to integrate Vue into our existing Meteor projects?  Do you plan to merge this PR?
Just in case: Blaze has been broken out from Meteor and is now a stand alone project.  @mitar is the primary owner/maintainer for Blaze (no longer MDG).  He is trying to use Vue as the foundation of a Blaze 2 that will serve as the "default" UI for Meteor (the alternative is React).  But without this PR, it will be an impossible task.
@yyx990803, please allow the Meteor community further migrate to Vue by accepting this PR and helping @mitar where needed.
Thank you for a super great framework!

Great work.

This is super awesome. I really Evan merges this in - thousands of Meteor apps that might switch to Vue as a result of this package.

 Do you know how I could configure something to notify me when this pull requests gets conflicting files. Now I see that it again has conflicting files, so branch should be updated.

@mitar

Do you know how I could configure something to notify me when this pull requests gets conflicting files.

maybe this can help: https://gitnotifier.io/

@mitar

Do you know how I could configure something to notify me when this pull requests gets conflicting files.

maybe this can help: https://gitnotifier.io/

@yyx990803: What is your take on how to integrate Minimongo the best? Now that we have proper Tracker support, it means that if you do collection.find().fetch() inside Vue computed function, it will rerun on every change, as expected. But what should we do if you return collection.find()? Should we do anything smart, or just call fetch() on it and Object.freeze it? We should also make so that Vue uses _id as a default key for Minimongo results (arrays or cursors). Should we specially handle cursors so that Vue observes changes to underlying data without having to compare whole arrays?

I have finished integrating Tracker with Vue. I think the result looks amazing. There are some internals we could continue improving, but I think that interface for developers works well.
To showcase it, I implemented TodoMVC in it. See this file for an example of Vue component using familiar Meteor concepts, like reactivity, subscriptions and methods. (And also some custom packages, to show how they continue working as they worked in Blaze.)
Some instructions how to use it can be found here. After more people tested it and more feedback, we can work on putting this into a package and more reusable form.
Also, this is on purpose very non-MVVM and trying to be as close to what experience with Blaze is. (So subscribing to data, calling methods to modify data on events, without any fancy multi-way data binding.) Those things can be future work.
Comments and feedback welcome. Best place for that is this issue.
This is all possible because of the amazing work by @akryum! It is just combining things he made in a bit different way.
One potential step (which I am not planing to do personally, but would invite somebody to do) is to convert spacebars compiler to convert Blaze template syntax to Vue templates, in a similar way how Vue allows to use Pug/Jade.

Also see #6079 with some more useful changes which would help make Minimongo integration smoother. (I am still unclear what would be the best way to do that integration.)

Any updates to this issue?

I'm using @mitar's fork, but maybe it would be interesting to have an official integration

My previous comment still stands true as we've planned to do a reactivity system overhaul (using Proxies internally) in early 2018. The chance for this PR to be compatible with the upgrade will be slim. If the need for Meteor integration is still in reasonable demand at that point, we can revisit what that entails after the upgrade.

What would be the best way for me to be involved in that system overhaul to help make sure things can work together from the very beginning. So that it is not a later change which as you see now is much harder to get in?
I think that 38 upvotes on this pull request is clear that there is some demand for this.
Also, why not still merge this in as it is now, and then as upgrade happens, also the new system could contain things useful for Meteor?

The main issue: the changes are too intrusive, so it is essentially asking the Vue team to take on liability, design constraints and potential technical debt for some need that is entirely induced by a 3rd party system.
In order to get involved in the process, it'd be helpful to have a proper write up of what is fundamentally preventing Vue's reactivity system to work with Tracker's; and instead of directly changing Vue's internals, providing a desired API surface that you'd like to see exposed (even better, test cases of these exposed APIs). That helps us gauge the constraints better and maybe can come up with something that decouples the two systems better.

In order to get involved in the process, it'd be helpful to have a proper write up of what is fundamentally preventing Vue's reactivity system to work with Tracker's; and instead of directly changing Vue's internals, providing a desired API surface that you'd like to see exposed (even better, test cases of these exposed APIs).

@mitar do you have any plans on providing the stuff he's asking for above or?

In order to get involved in the process, it'd be helpful to have a proper write up of what is fundamentally preventing Vue's reactivity system to work with Tracker's; and instead of directly changing Vue's internals, providing a desired API surface that you'd like to see exposed (even better, test cases of these exposed APIs).

@mitar do you have any plans on providing the stuff he's asking for above or?

@aadamsx, thanks for reminding me to reply here.
@yyx990803, I think there might be a slight misunderstanding there (of what this pull request is doing, or of what I am trying to achieve), so just to make sure I will summarize it. I ported Meteor's Tracker on top of Vue's reactivity system. It is really great reactivity system and Tracker was able to be ported to it with almost 1:1 API mapping only. The only small differences are that Tracker has some more hooks to be called (like after each invalidation, allowing to force flushing, smaller things like that). This PR might look intrusive, but it is mostly just adding such places for hooking in.
So I see two options, the first being this PR:

Vue reactivity system exposes few more callbacks so that Tracker can be directly built as a API transformation on top of Vue reactivity system (personally, I do not see it as too intrusive, but this is your call, and maybe they could even be made cleaner than I made them)
Vue makes its reactivity system pluggable, so that user can say, "hey, instead of this default implementation, swap it with this other JS module"; it would be on the second module to assure compatibility with default system

I think based on the feedback you gave here, I think the second approach would be better. Instead of us having to define API space and have to push back and forth on which callbacks Tracker would need and which one you would be OK to provide, you just freely design Vue reactivity system how it is, just allow that somebody can call something like Vue.useReactivity(module) and it would start using the new module instead. And if new module is buggy, it is on their maintainers to make it compatible. Based on PR here I see it that it would be easy to maintain such alternative implementation exposing few more callbacks. And it would be easier than providing the whole fork of Vue.
What do you think of this approach?
Just one reply from before:

we've planned to do a reactivity system overhaul (using Proxies internally) in early 2018

So because I am building Tracker on top of Vue reactivity system, I do not think it is really important how internally you implement it. I am glad that Vue reactivity system has a concept of "user" watchers but beyond that it is just using the external API. See here for details.

I heard the Vue logo is on Meteor.com - it sounds like this is going well :)

@yyx990803, what do you think about ideas I made above how we could make this work for both communities?

@yyx990803 ping. Is there a better channel to communicate about this?


AT128 HW interface crashes on GetLidarRange

When launching Nebula when connected to AT128, the HW interface crashes with a segfault in GerLidarRange.
The AT128 TCP protocol does not support request code 0x23 (Get Azimuth FOV) and sends an error response, which Nebula does not check. Instead it assumes the payload is larger than the error response, resulting in a segfault.

As a first step, I made issues like these detectable by introducing error checking and handling in hesai_hw_interface:

#131

Fixed by #131


Fix phone

Codecov Report

Merging #258 (41ab87a) into master (be8e6cf) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #258   +/-   ##
=========================================
  Coverage     73.40%   73.40%
  Complexity      675      675
=========================================
  Files            97       97
  Lines          2087     2087
  Branches        242      242
=========================================
  Hits           1532     1532
  Misses          484      484
  Partials         71       71

Impacted Files
Coverage Δ

...rc/main/java/seedu/address/model/person/Phone.java
91.66% <ø> (ø)

Continue to review full report at Codecov.

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


✨ [Feature] Add a config to allow turning off warnings that view folder don't exist

Before feedback (在反馈之前)

[X] There are no features that I want to submit in Issues (当前 Issues 中没有我将要提交的新功能)

Describe Feature (描述功能)
After updating the framework to version 1.13, if the resources/views directory does not exist, a warning message will be output every time the app is started.
I hope to add a switch to turn it off. (When working as a pure backend, there is no need to use views)

I think we can ignore the warning directly instead of adding a configuration.

Gin driver also need to do this, reopen it.


Revert "Python 3.6"

Reverts conda-forge/nlopt-feedstock#3

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

@jschueller the best way to avoid this, if you really do not want Python 3.6, is to add the skip: True  # py36. Otherwise future re-renderings will bring that up again.

No, I want py36, I just merged too soon by accident.

OK. Then ignore my comment :wink:


Log deliverable description #3948

Description
I added an info log with the current deliverable description when publishing DITA-OT project.
The log message has the following format:
Publishing deliverable 1 of 3: Product A Online Help [del-olh-A-map]
This is a continuation of https://github.com/dita-ot/dita-ot/pull/4097
Motivation and Context
This is a fix for the following issue:  #3948

I close this one to fix DCO


Add delete_all_packages.py to delete all packages from a repository

Helpful to bypass security measures from GitHub that requires literally hours.

Can you please move this file to ./overlay/scripts/
As custom addition it belongs into the overlay folder.

Done


Introduce heartbeat mechanism

Feature Description
We have found that sometimes the connection can break for a various amount of reason, but this might not be propagated properly through the connection. In order to know for sure the connection is alive both ways, a mechanism should be introduced that checks both directions of the connection; a heartbeat.
Current Behaviour
There is no heartbeat, so there is no complete guarantee that the entire connection is a live. It might be terminated by a smart load balancer and be kept alive. We actually see this happening as well.
Wanted Behaviour
Every 10 seconds, the client should send a heartbeat. The server can decide how many heartbeats can be missed. I would suggest 2, so terminate the connection from the server if it had no heartbeats for 30 seconds.
The client should receive a heartbeat every 10 seconds from the server. Two heartbeats can be missed before terminating the connection.
The client should indicate to the server that it supports heartbeats and they should be sent. Additionally, the client should eagerly set up a connection, instead of the current lazy behavior exposed.
Possible Workarounds
Rebooting the application

Made this issue instead, as it's the new client: https://github.com/AxonIQ/console-framework-client/issues/32


More patterns for github.com

Support of

SHOW_FILE (at file tab)
SHOW_FILE_HISTORY (at file tab)
SHOW_COMMITDIFF (in project context menu)

Fixed in 1.4.1


Android 13"Oneui 5.1" accessibility unavailable.

Preparation

[X] I tested the latest release
[X] I looked at other issues (even the closed ones)
[X] I read the Troubleshooting Guide

FGO server
KR
FGA build number
2170
Describe the bug
Android 13"Oneui 5.1" accessibility unavailable.

Video
Android 13"Oneui 5.1" accessibility unavailable.

Device model
Galaxy S22 Ultra
Android version
13
Screen size
1280x720
RAM
8GB

Install via the play store

I downloaded it through the Play Store.
It worked fine at first, but after a few days it just stopped at the servant selection screen.
After directly selecting a servant, you can run dungeons or skip the story.

Is the play button in the bottom left?

Everything has been resolved. I pressed the play button and confirmed that it was not recognized because of that.

Everything has been resolved. I pressed the play button and confirmed that it was not recognized because of that.

Everything has been resolved. I pressed the play button and confirmed that it was not recognized because of that.


Case Sidebar Data Display BUG

From @davidascher on June 18, 2018 16:40
Sender<EMAIL_ADDRESS>Comment: Case Sidebar Data Display BUG - only one method entered yet it appears four times in the sidebar of the reader view
Open #207 in Usersnap Dashboard

Download original image
Browser: Firefox 60 (Windows 10)
Referer: https://participedia.xyz/case/5313
Screen size: 1920 x 1080 Browser size: 1920 x 876
Powered by usersnap.com
Copied from original issue: participedia/usersnaps#194

closing via: https://github.com/participedia/frontend/issues/855


hreflang header implementation

Add hreflang tag to the header on all pages:

<link rel="alternate" href="https://www.flattenthecurve.com" hreflang="en-us" />
<link rel="alternate" href="https://www.flattenthecurve.com/es/" hreflang="es" />
<link rel="alternate" hreflang="x-default"
href="https://www.flattenthecurve.com" />

We were only missing the x-default link - and it's been added in 06b4ec2aa7c7bced0cf2be941fa058fdc95e09a0 & d4d5c5187ba124110acc28743b102fe82da83f93 👍

(The changes may not be live yet due to CloudFlare's cache)


CSS

CSS
User Story
As a boot camp student
I want the prework notes to be structured on a webpage
So that I can easily find and read the information
Acceptance Criteria
GIVEN a Prework Study Guide website
WHEN I view the study guide
THEN I see a dark blue header and footer, and four boxes with a shadow

Prework:
3.2.6:  Complete the Git Flow
CSS has been fulfilled


[SQL] az sql db create/update: Add --use-free-limit and --free-limit-exhaustion-behavior arguments

Related command

az sql db create --use-free-limit --free-limit-exhaustion-behavior AutoPause
az sql db update --free-limit-exhaustion-behavior BillOverUsage
Description

Add support for free limit parameters that will allow to create free limit database based on General Purpose Serverless database and allow to specify exhaustion behavior to either AutoPause until the end of the month or BillOverUsage to pay for usage above free limits.
Testing Guide

Create new azure sql database on GeneralPurpose serverless database with --use-free-limit and --free-limit-exhaustion-behavior. Later same parameters can be used to change --free-limit-exhaustion-behavior to BillOverUsage or change to billed version by specifying --use-free-limit False.
sql db create -g rgname --server servername --name dbname --edition GeneralPurpose --family Gen5 --capacity 2 --compute-model Serverless --use-free-limit --free-limit-exhaustion-behavior AutoPause
sql db update --free-limit-exhaustion-behavior BillOverUsage
sql db update --use-free-limit False
History Notes

[SQL] az sql db create/update: Add --use-free-limit and --free-limit-exhaustion-behavior arguments

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] The PR title and description has followed the guideline in Submitting Pull Requests.

[x] I adhere to the Command Guidelines.

[x] I adhere to the Error Handling Guidelines.

SQL


Develop 16 new parameter for player

you have to run cmake and build it at least one time, and commit the generated files by grpc and thrift

also, the version on the first line of thrift and grpc should be 1.1
and the thrift file and grpc file in sample projects should be updated (and codes should be generated)

I will create another PR to develop-16-new-parameter-for-player branch for adding the thrift and grpc generated files.


Documentation updates for Calico v3.6

[ ] Tests
[ ] Documentation
[ ] Release note

None required

Deploy preview for calico ready!
Built with commit 473f51826464b2b71538aca349e84dd79cc5d717
https://deploy-preview-2478--calico.netlify.com


write documentation on how to troubleshoot community build problems

I've learned a lot about this in the last few months. I should write as much of it down as I can.

an initial brain dump is now up at https://github.com/scala/community-builds/wiki . I'm sure I'll think of more additions over time, but the basics are there.


Cow: Watch techtipstation.com

Cow requests the watch of the watch_keyword techtipstation\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

techtipstation\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Makyen in Charcoal HQ


Update couchbaselabs/jsonx for meeting compliance

Signed-off-by: Shubham Sharma<EMAIL_ADDRESS>Description
Earlier couchbase/gocb.v1 depended on<EMAIL_ADDRESS>which did not have a license. This PR upgrades to<EMAIL_ADDRESS>which has an Apache license.
Issue reference
Please reference the issue this PR will close: #1480
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:

[X] Code compiles correctly
(NA) Created/updated tests
(NA) Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

Please update conflicting files.

@daixiang0, done!

/cc @daixiang0 can you please review this PR?


When first opening the project getting an error about NPM

When i try to open project after than build the library project, i'm getting about like this
"sass Styles:wwwroot/ --style compressed --load-path=Styles --update" exited with code 9009
You can fix it with install sass with npm following steps
run following command in your ThemeManager folder (not ThemeManager.App)
npm install -g sass

Its still not working.

What if I don't want to install npm and node on my machine, How to run the code in this case ?

In the MudBlazor main repo we have long abandoned NPM as a dependency and are using different means to get an scss compiler. This could be done here too but I don't have time to look into it.

I'm closing this issue.
The main branch contained code that was still in progress, but the code uploaded to NuGet was in the hotfix branch. Now we have swapped the branches, and the primary code is in the main branch, which does not contain any npm. The wip branch is not for public use.


RenderableView crash

Describe the bug
We saw the following crash reported in crashlytics:

I think it's related to this stack overflow post which has a suggested fix:
https://stackoverflow.com/questions/46764226/react-native-android-app-crashes-with-in-release-apk


There are no examples on how to use this action

In the README for this project, there is no information on how to use this action or detect-secret-additional-args.
We need to update the README with this info.

Solved by #11


SyntaxError - Chart.js:46

Hello,
I get this error on startup: Uncaught SyntaxError: export declarations may only appear at top level of a module Chart.js:46
Can you see it?
Thank you,
Gaston.

Yes, I saw this message. It is related to this line where there is the word export function. If I remove the export the script is not working.
I don't know why this is a syntax error.

It happens because the export directive is for modules and not for plain Javascript.

Add at the end of the page the following scripts:

<script src="_content/PSC.Blazor.Components.Chartjs/lib/Chart.js/chart.js"></script>
<script src="_content/PSC.Blazor.Components.Chartjs/Chart.js"></script>

The  is not neccesary because it is imported from:
     public ChartJsInterop(IJSRuntime jsRuntime)
       {
           moduleTask = new(() => jsRuntime.InvokeAsync<IJSObjectReference>("import",
               "./_content/PSC.Blazor.Components.Chartjs/Chart.js").AsTask());
       }

I removed it from my index.html and the error does not happen anymore.

Thank you so much!

Hi,
We are still seeing the same error on line 46 using version:

Was @gmlloves suggestion above incorporated in a later release or I am missing something in the suggested change.
Thanks

Confirm this issue still exists, albeit it displays as Uncaught SyntaxError: Unexpected token 'export' (at Chart.js:46:1)
Removing the second script src=... from index.html, as described by @gmlloves above, addresses it.
Not sure whether this issue can be reopened?

Hi,
I can confirm removing the second line works perfectly.
Thank you @skotl, and thank you @erossini for providing the wrapper!!

Thank you @skotl and @Ryan-ECPPro
I'm working on a new version of the components with more functionalities. Hopefully soon, few improvements.

I have tried removing the 2nd line but for some reason the first time it loads it always seems to fail then when I refresh it works as expected.
Either way I am not sure if this bug should be classed as closed as its not fixed in the latest release and requires a manual workaround, are you able to issue a hotfix for this and do a larger release with all your other changes further down the line?


[WIP] hasValidated property

refs #113
@offirgolan this is a result of the little bit of time I was able to spend on this, it doesn't work very well at the moment because I'm still getting used to the codebase but will see what all I can do tonight/later this week.

@offirgolan I've managed to get this working for everything but the hasMany validator; however, the current handling of belongsTo validators isn't ideal, and I may need some guidance as to a better way to accomplish this 😕

@acburdine super sorry for such a delayed response! Thank you so much for taking the time to put this together.
I feel as though this is overly complicated, but then again, my use-cases in the past have been very simple. Why is there a need to reset hasValidated when a value changes? Maybe hasValidated isnt the correct name for this.
//cc @jasonmit

@offirgolan The reason hasValidated is reset when the value changes is because of this comment.
Personally, my use case is for only showing the error once the input has focused out, which means whenever the validate or validateSync method is called. I'm not sure what a better name for it would be though 😕

Haha okay makes sense 😸 . Let me take some time to think about this and get back to you. I feel like this solution can either be simplified or can be split into a didValidate and a hasChanged sorta thing.

Im gonna go ahead and close this PR as it is pretty old. @acburdine thanks again for taking the time to put this PR together but as of right now, I think the simplest solution is to track this state on the app-side.


Feature Request: txnbuild: add ability to create TransactionParams from Transaction

What
Add ability to create TransactionParams from Transaction.
Why
So that we can load a Transaction, edit it, then resign it, etc.
As far as I can tell the txnbuild package does not contain functionality for this.
Since the way to provide parameters to a new Transaction is to use the TransactionParams type, it seems fitting that to modify a Transaction, which is largely immutable other than for signing, the method to do so would be to construct a TransactionParams from a Transaction.
There are plenty of use cases where different parties will sign a transaction, but then decide they need to modify it and resign it. SEP-8 is one example. Payment channels has a flow that will require it as well where a prior signed transaction stored as XDR will need reparsing, modifying, and resigning.

Hi @leighmcculloch Hope this feature is still relevant.?


Change is_callable insted method_exists in Object

What are you trying to fix with it?

@samdark I try to implement correct work in case when behavior has magic __set or __get.

Object can not have a behavior. It is covered correctly at Component.

@klimov-paul but canSetProperty and canGetProperty methods implement in Object class

So what?

If there is something, which troubles you, describe it by answering the following questions:

How to reproduce the issue?
What did you expected to see?
What did you seen instead?
Any extra comments.

I created behavior with overrided  method __get.
This behavior has to implement dynamic relation for ActiveRecord.
I try to call $model->vendor->title but get error Getting unknown property.
I want to get relation record by behavior.

If you have overridden __get() inside your behavior, you should as well override its canGetProperty() value accordingly.

@klimov-paul thanks


fix delete delay when update pod error

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@92012d2). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #271   +/-   ##
=========================================
  Coverage          ?   73.88%
=========================================
  Files             ?       20
  Lines             ?     1666
  Branches          ?        0
=========================================
  Hits              ?     1231
  Misses            ?      390
  Partials          ?       45

Continue to review full report at Codecov.

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


[!] [Onboarding] Fix code using old delegate method, resulting in crash

Sorry everyone... this needs to go in for 3.0.2!
In the clean up around Facebook's signup process, I removed methods we weren't using anymore / didn't do anything, but the email signup method still called it.
Not sure if I should changelog this, as it hasn't officially gone out yet?

I'd put it in the changelog for master ?

@mennenia Yeah this is going to go in 3.0.2 still 👍
@orta What does that mean? I’m confused about how the changelog works.

I meant upcoming, as this won't be the real 3.0.2 build

@alloy because it was still in the header >_< my bad

I’m going to merge this as-is.


torch.BoolTensor is supported since torch >= 1.2.0

Hi, first of all, thanks for sharing this code public!
I've discovered a problem with the README. It says it works with pytorch 1.0, but it won't because it is using torch.BoolTensor in model/layers/mesh.py. torch.BoolTensor is supported since 1.2.0.
I confirmed the test code for scripts/human_seg is working fine with pytorch 1.2.0. I hope this information helps other guys testing this code.

Hi @ycjungSubhuman ,
Thanks , I updated it :)


not showing author name

title: Alphonso mango production highest among all varieties
author:  Robert d. jr
date: 2023-07-22 01:56:00 +0600
categories: [Mango,fruits]
tags: [agriculture,food production,farmer] #TAG names should be lowercase
author name not showing
author name only shows when i set author name to cotes then it says Cotes Chung whats going on i can't understand
also im using a default git jekyll action the action script in the repo doesn't work for me both in jekyll-theme-chirpy and chirpy-starter for some reason.

hi @safinakib
to properly set author name for posts, remember to edit _data/authors.yml to be similar to https://github.com/cotes2020/jekyll-theme-chirpy/blob/master/_data/authors.yml
jekyll is confusing, really.
good luck!

sublimeclemency But what if there is more then one author, like if i want to make a reference post from a local newspaper as shown previously in that case the author is different what should i do then?

sublimeclemency thanks for the help.


Authentication and authorization of user for TuneIn purpose

DESCRIPTION
In this PR the changes are done to add a process of Authenticating and Authorizing the user before they modify and submit the TuneIn details. Both authentication and authorization of a user as of now are done using the APIs provided Azkaban which is a scheduler supported by Dr.Elephant.
So before users modify and submit the updated TuneIn details they need to authenticate themselves and then Dr.Elephant will query the scheduler to check if the respective user has Write access to the project whose properties they want to modify.
Login Page:

How Changes are tested
For the APIs for Authentication and Authorization, unit test cases are implemented in various scenarios.

LGTM . @ShubhamGupta29  please test on cluster (if not already done)

New PR #537


Change website icon to artifactory logo

Is currently some nextjs default I think:

Change to artiactory logo. Tidy HQ has this one but might be better with circle centered.

As an alternative, what about the one used on the webcam page?

That one does look pretty good! I should have checked here before rolling out the other one.
Do you have a source for that? Ill revisit another time.

From memory it's just been created from these:
https://space.artifactory.org.au/media/artifactory-logo.png
https://space.artifactory.org.au/media/artifactory-logo.svg

That did the trick. Has transparency so works well light and dark mode. Same favicon.ico are other relevant logo files used for webcams, wiki and websites now.


cockroach sql defaults for interactive vs. non-interactive sessions

Currently, only the interactive shell option defaults are documented: https://www.cockroachlabs.com/docs/stable/use-the-built-in-sql-client.html#sql-shell-options-changed-in-v1-1. These defaults are sometimes different for non-interactive sessions, i.e., executing from the command line or from a file.
cc @knz

Related issue: https://github.com/cockroachdb/docs/issues/2248

Closing this issue because it seems to be a dupe of #2397, which has been addressed by @rmloveland's #3031 (thanks!).


Is it possible to export the markdown output of a notion page?

Is it possible to export the markdown output of a notion page?
I can't seem to find an easy way to do this.

I'd love to be able to kick off an export as well! I can make another issue if needed, as not just markdown would be gold

@GregHilston I did figure out how to do it by taking a look at https://github.com/serokell/notion-to-markdown.
It didn't work out of the box though and I had to inspect the call being made by my Chrome browser because it looked like Notion may have changed things a bit since that code was posted.  Works great now though!  I am using both this library and the code from that one.
I am going to be writing about the approach I used and posting all code to get started on my blog: https://timothybramlett.com/Building_This_Blog_with_Notion.html
I may even be able to add the feature to this library is someone can point me in the right direction. :)

@TimothyBramlett  Understood. If you fixed https://github.com/serokell/notion-to-markdown, fork and pull request to that project or just keep your fork up to date!
I'd love to see what you did and use that on my end as well.
I'll keep my eyes peeled on your blog post, read through it now. If you hit me when you're finished, I'd love to see what you've come up with!
I'll be trying to integrate Notion into my dev experience as well, as I am also using a static site generator ha

@GregHilston Sounds good!  I will contact you here once I get the code up in the next few days.

@TimothyBramlett awesome! Excited to see what you write!!!

If you come up with a nice standardized way to do this (that you're planning on maintaining), let us know and I'll link to it from notion-py so others can find it -- thanks!

@TimothyBramlett @GregHilston hey did either of you ever find a way to do this? I'm looking at the linked code from serokell but also wondering if anyone else made progress on their own.

Hey @iansinnott I ended up abandoning my usage of Notion because of things like this, being locked down.
I've been loving writing pure markdown myself with LaTeX and its working perfectly. With VS Code or w/e editor one likes.

Thanks @GregHilston. I'm definitely feeling the pain of trying to use Notion as a CMS

@GregHilston, I came here to find a way to export all my Notion to a private GH repo. I don't like walled gardens any more than you do, but I like how Notion rips a page and puts it in Markdown. Best case, I would love to find a Chrome macro that elegantly converts the page to Markdown and feeds it to GH. :)
So, while I am not here to crosspost, I am working on a variant of kitabu that doesn't require use of a licensed product (i.e. free) and uses GH actions to compile directories of MD as books. It's called Verkilo, and it's pretty much just in alpha

@Merovex Very interesting! Do you have any links/writings I can read about your workflow?
I've pretty much kept up with exclusively writing markdown and latex in vm and using Github/Nextcloud to sync. Its worked great

That's something i need to do...document the process. Give me a week and I'll see what I can muster. ;)

@Merovex ;)


Webpack 5 support

Hi folks,
It seems mocha-webpack doesn't support beyond webpack 4. I don't know what's needed beyond bumping a version somwhere.
thanks!

Consider switching to instant-mocha for Webpack 5 support.

Webpack 5 support has also been added to mochapack - a fork of mocha-webpack by @jayaddison @skjnldsv and @sodatea and released in<EMAIL_ADDRESS>


Empty tag: Provides

specfile cannot parse https://src.fedoraproject.org/rpms/mingw-crt/blob/rawhide/f/mingw-crt.spec
It ends up with this TB:
The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/msuchy/projects/license-validate/./print-spec-changelog.py", line 7, in <module>
    specfile = Specfile(filename)
               ^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/specfile/specfile.py", line 48, in __init__
    self._spec = RPM.parse(str(self), self.sourcedir, self.macros)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/specfile/rpm.py", line 326, in parse
    raise RPMException(stderr=stderr) from e
specfile.exceptions.RPMException: line 71: Empty tag: Provides:

This is again caused by missing source files (standard-dlls-mingw32 in this case).

What we could theoretically do here is to generate a file containing some sort of a dummy value, but it would have to be a value that's syntactically correct in any place in a spec file, because shell expansions can appear anywhere. Let me think of something.


Add macros section to readme.md

These are the only 2 examples I  know of at the moment. I'm sure @kentcdodds knows more.

You can find more if you go to https://yarnpkg.com/en/package/?q=babel-macro

Thanks for the PR.
I'm not sure what we should do because there's already babel-macros and idx in other sections of the README. Should we merge them into a macro one?

Yep I would move it into a section and explain what a macro is or link to the new post

You'll find all the macros I'm aware of in the blog post :)


WIP master <- develop

Merge the develop branch into the master branch and deploy

Build log
Preview build with this PR (commit): https://312-280922552-gh.circle-artifacts.com/0/index.html


Fixed various links and removed deprecated/retired resources

There are numerous links that either don't work, are replaced, or are deprecated by their owners. Thus, keeping those links intact within this repo doesn't prove to be worthy. It's better to change or remove them accordingly. That's the main reason behind this PR.
Thanks!

Closing due to inactivity!


cannot redeclare block scoped variable postMessage()

🔎 Search Terms
"cannot redeclare block scope variable postMessage typescript"
🕗 Version & Regression Information
TS version: ^5.1.6
⏯ Playground Link
Can't use workers in Playground
💻 Code
const worker = new SharedWorker(new URL('./worker.js', import.meta.url))

/* ... */

worker.port.addEventListener('message', e => {
     if (!e.data?.type) {
          return
      }

      switch (e.data.type) {
          case 'get_tabs': {
               worker.port.postMessage({ //Error here
                   type: 'share_tab_id',
                   tab_id: tabId
               })
          }

    /* ... */

🙁 Actual behavior
I'm getting a Cannot redeclare block-scoped variable 'postMessage' error coming from TypeScript itself. I checked the file (lib.dom.d.ts) and it looks like the postMessage variable is getting declared twice

🙂 Expected behavior
Expect to have single declaration of postMessage and no error.
Additional information about the issue
I'm using a monorepo with NPM workspaces. Each module has a separate tsconfig.json and are built separately

It seems that two different lib.dom.d.ts are resolved, resulting in errors. But without knowing your setup it's difficult to say what you are doing wrong. You can use the --traceResolution compiler flag to get more information about the resolved files.

I don't understand how this is even possible -- it's legal to have ambient function declarations across multiple files. We'll definitely need a concrete repro since something very weird must be happening here.

@MartinJohns @RyanCavanaugh
I have a monorepo that uses NPM workspaces with roughly the following folder structure:

react-libs

node_modules
src
package.json
tsconfig.json
libs

react-audio-hook

src
package.json

tsconfig.json
react-context-menu

src
package.json
tsconfig.json

react-tab-state

src
package.json
tsconfig.json

The package.json in the topmost level looks like this:
{
  "name": "react-libs",
  "version": "0.1.0",
  "description": "Monorepo of React libraries",
  "main": "index.js",
  "private": true,
  "workspaces": [
    "libs/*"
  ],
  "scripts": {
    "start": "webpack-dev-server --config webpack.config.js",
    "build": "webpack"
  },
  "keywords": [
    "context",
    "context",
    "menu",
    "menu",
    "react",
    "component"
  ],
  "author": "JorensM",
  "license": "MIT",
  "devDependencies": {
    "@babel/plugin-syntax-jsx": "^7.22.5",
    "@babel/plugin-transform-react-jsx": "^7.22.5",
    "@babel/preset-env": "^7.22.10",
    "@babel/preset-react": "^7.22.5",
    "@babel/preset-typescript": "^7.22.5",
    "@testing-library/jest-dom": "^5.17.0",
    "@testing-library/react": "^14.0.0",
    "@types/jest": "^29.5.3",
    "@types/react": "^18.2.18",
    "@types/react-dom": "^18.2.7",
    "@types/uuid": "^9.0.2",
    "copy-webpack-plugin": "^11.0.0",
    "copyfiles": "^2.4.1",
    "cross-env": "^7.0.3",
    "css-loader": "^6.8.1",
    "jest": "^29.6.2",
    "jest-environment-jsdom": "^29.6.2",
    "mini-css-extract-plugin": "^2.7.6",
    "rimraf": "^5.0.1",
    "ts-loader": "^9.4.4",
    "typescript": "^5.1.6",
    "watch": "^1.0.2",
    "webpack": "^5.88.2",
    "webpack-cli": "^5.1.4",
    "webpack-dev-server": "^4.15.1"
  },
  "dependencies": {
    "rc-slider": "^10.2.1",
    "react": "^18.2.0",
    "react-dom": "^18.2.0",
    "uuid": "^9.0.0"
  }
}

The package.jsons in the libs folders look like this(all of them are the same):
{
  "name": "@printy/react-tab-state",
  "version": "1.1.0",
  "description": "Sync and persist state across tabs in React",
  "main": "dist/index.js",
  "types": "dist/types",
  "files": ["dist", "package.json", "README.md", "LICENSE"],
  "scripts": {
    "clean": "rimraf /dist",
    "copy-files": "copyfiles -u 1 src/**/*.js dist/",
    "build": "npm run clean && tsc && npm run copy-files",
    "test": "jest"
  },
  "keywords": [
    "react",
    "tabs",
    "tab",
    "state",
    "sync"
  ],
  "author": "JorensM",
  "license": "MIT",
  "repository": "github:Printy-Studios/react-tab-state",
  "devDependencies": {
    "@testing-library/react": "^14.0.0",
    "jest": "^29.6.2",
    "jest-environment-jsdom": "^29.6.2",
    "@types/jest": "^29.5.3",
    "@babel/plugin-syntax-jsx": "^7.22.5",
    "@babel/plugin-transform-react-jsx": "^7.22.5",
    "@babel/preset-env": "^7.22.10",
    "@babel/preset-react": "^7.22.5",
    "@babel/preset-typescript": "^7.22.5",
    "@testing-library/jest-dom": "^5.17.0",
    "@types/react": "^18.2.18",
    "@types/react-dom": "^18.2.7",
    "mini-css-extract-plugin": "^2.7.6",
    "rimraf": "^5.0.1",
    "ts-loader": "^9.4.4",
    "typescript": "^5.1.6",
    "copyfiles": "^2.4.1",
    "cross-env": "^7.0.3",
    "css-loader": "^6.8.1"
  }
}

The tsconfig.jsons in the libs folders look like this(also all the same)
{
    "compilerOptions": {
      "rootDir": "./src",
      "declaration": true,
      "declarationDir": "./dist/types",
      "outDir": "./dist/",
      "noImplicitAny": true,
      "module": "es2020",
      "target": "es5",
      "jsx": "react",
      "allowJs": true,
      "moduleResolution": "node",
      "allowSyntheticDefaultImports": true
    },
    "include": ["src"]
}

When I run npm run build inside react-tab-state, I get the reported error.
The topmost folder holds a react app as well as the other modules(in libs) that each have their own tsconfig.json
You will notice that my libs don't have node_modules. That's because this is how NPM workspaces work - all the modules
share a single node_modules folder
If there's any more information you need or if you need me to upload my repo, let me know.
For now, here's also the code of react-tab-state though I doubt that it's related to the code itself.
Thanks!

@MartinJohns I ran the build command with --traceResolution, and when searching for lib.dom in the output, this is what I found:
======== Resolving module '@typescript/lib-dom' from 'C:/Jorens/Work/Dev/web/react-libs/libs/react-tab-state/__lib_node_modules_lookup_lib.dom.d.ts__.ts'. ========
Explicitly specified module resolution kind: 'Node10'.
Loading module '@typescript/lib-dom' from 'node_modules' folder, target file types: TypeScript, Declaration.
Searching all ancestor node_modules directories for preferred extensions: TypeScript, Declaration.
Directory 'C:/Jorens/Work/Dev/web/react-libs/libs/react-tab-state/node_modules' does not exist, skipping all lookups in it.
Scoped package detected, looking in 'typescript__lib-dom'
Directory 'C:/Jorens/Work/Dev/web/react-libs/libs/node_modules' does not exist, skipping all lookups in it.
Scoped package detected, looking in 'typescript__lib-dom'
Scoped package detected, looking in 'typescript__lib-dom'
File<EMAIL_ADDRESS>does not exist.
Directory 'C:/Jorens/Work/Dev/web/node_modules' does not exist, skipping all lookups in it.
Scoped package detected, looking in 'typescript__lib-dom'
Directory 'C:/Jorens/Work/Dev/node_modules' does not exist, skipping all lookups in it.
Scoped package detected, looking in 'typescript__lib-dom'
Directory 'C:/Jorens/Work/node_modules' does not exist, skipping all lookups in it.
Scoped package detected, looking in 'typescript__lib-dom'
Directory 'C:/Jorens/node_modules' does not exist, skipping all lookups in it.
Scoped package detected, looking in 'typescript__lib-dom'
Directory 'C:/node_modules' does not exist, skipping all lookups in it.
Scoped package detected, looking in 'typescript__lib-dom'
Loading module '@typescript/lib-dom' from 'node_modules' folder, target file types: JavaScript.
Searching all ancestor node_modules directories for fallback extensions: JavaScript.
Directory 'C:/Jorens/Work/Dev/web/react-libs/libs/react-tab-state/node_modules' does not exist, skipping all lookups in it.
Directory 'C:/Jorens/Work/Dev/web/react-libs/libs/node_modules' does not exist, skipping all lookups in it.
Directory 'C:/Jorens/Work/Dev/web/node_modules' does not exist, skipping all lookups in it.
Directory 'C:/Jorens/Work/Dev/node_modules' does not exist, skipping all lookups in it.
Directory 'C:/Jorens/Work/node_modules' does not exist, skipping all lookups in it.
Directory 'C:/Jorens/node_modules' does not exist, skipping all lookups in it.
Directory 'C:/node_modules' does not exist, skipping all lookups in it.
======== Module name '@typescript/lib-dom' was not resolved. ========


Option to use external profile picture source

Describe the feature you'd like
When using AzureAD authentication we would like the profile pictures to be the same as the user has configured in Office 365.
Describe the benefits this feature would bring to BookStack users
This would add a layer of personalisation between colleagues. Currently the profile picture is pretty useless.

Thanks for the request.
I'm going to close this as an effective merge with #2368 since they cover the same fundamental request here.


[Question] How do we query to filter based on 2+ array items on the front-end?

Considering a simple use case where I have the following records of Books loaded into Vuex store of the Books Service. Each book contains a list of tags.
Book 1 Coding Javascript Education
Book 2 Javascript Coding FeathersJS
Book 3 Javascript FeathersVuex FeathersJS Coding
How do I query for books that have Coding & FeathersJS tags?
query: {
    tag: {
         $in: ['Coding', 'FeathersJS']
    }
}

This gives results for the books that have the Coding or FeathersJS tags as expected. (Book1, Book2, Book3)
I am not sure how to query for books that contain both the tags.
On the backend with mongoose, I can use the $all operator to achieve this - but how do I go about doing this on the frontend?
Currently, my workaround was to have a custom getter on the service which executes the $in query and then loops through the results to find the items where both tags are present.
Is there a better way to do this? Did I miss something w.r.t querying?

MongoDB allows to query a array with exact equality but it that case it respect the specific order of the items in the array.
Did you try this?
query: {
    tag: ['Coding', 'FeathersJS']
}

Or you can use the $all operator like that:
query: {
    tag: { $all: ['Coding', 'FeathersJS'] }
}

but you might need to whitelist the $all operator at the level service.

@J3m5 Thanks a lot!! I just stumbled on it as well. Ended up digging around in the code, found out that sift is being used to filter the results and the whitelist option is sent as a parameter.
$all seems to work as expected after whitelisting it! :)
Can I safely whitelist $and or other mongodb operators as well? On the mongodb $all documentation page it says that the following queries are equivalent -
{ tags: { $all: [ "ssl" , "security" ] } }
{ $and: [ { tags: "ssl" }, { tags: "security" } ] }
However, even after whitelisting both, the results are not the same when passed to the find getter ($all works as expected but $and just returns everything without any filtering). Is that expected?

Can I safely whitelist $and or other mongodb operators as well?

It depends on what you want your users to be able to do with your data, but for $and I would say yes, but there might be a risk of data leak with the $populate operator for example.

However, even after whitelisting both, the results are not the same when passed to the find getter ($all works as expected but $and just returns everything without any filtering). Is that expected?

You should try this

If I add it to the additionalOperators=['$elemMatch'] in the 'service-module.getters.js' file and replace it with const additionalOperators = ['$elemMatch','$and'] - It starts working and let's me execute the { $and: [ { tags: "ssl" }, { tags: "security" } ] } query.
const FILTERS = ['$sort', '$limit', '$skip', '$select']
const OPERATORS = ['$in', '$nin', '$lt', '$lte', '$gt', '$gte', '$ne', '$or']
const additionalOperators = ['$elemMatch']
const defaultOps = FILTERS.concat(OPERATORS).concat(additionalOperators)

export default function makeServiceGetters() {
  return {
    list(state) {
      return state.ids.map(id => state.keyedById[id])
    },
    find: state => params => {
      params = { ...params } || {}

      // Set params.temps to true to include the tempsById records
      params.temps = params.hasOwnProperty('temps') ? params.temps : false

      const { paramsForServer, whitelist } = state
      const q = _omit(params.query || {}, paramsForServer)
      const customOperators = Object.keys(q).filter(
        k => k[0] === '$' && !defaultOps.includes(k)
      )
      const cleanQuery = _omit(q, customOperators)

      const { query, filters } = filterQuery(cleanQuery, {
        operators: additionalOperators.concat(whitelist)
      })

Why do the top-level $ operators get filtered out irrespective of the whitelist? Trying to get a better understanding. Not sure if there is any documentation/posts/issues that go into this..

It depends on what you want your users to be able to do with your data, but for $and I would say yes, but there might be a risk of data leak with the $populate operator for example.

Oh ok - Though I am not using any $populate, but it sounds like something that might cause future problems. Will try and simplify my stories for now and get back to this once I have a better understanding I guess.

I think it's because of this:
const customOperators = Object.keys(q).filter(
  k => k[0] === '$' && !defaultOps.includes(k)
)
const cleanQuery = _omit(q, customOperators)

The filtering doesn't take the whitelist into account, I've seen it before but I don't know why it's done because the cleanQuery function is there for that and it is recursive.

When the whitelist was implemented, it was not added in the filter.
So we need to know if this filtering is really necessary, if yes add the whitelist to the filtering and if not remove the whole filtering.

I think it's because of this:
const customOperators = Object.keys(q).filter(
  k => k[0] === '$' && !defaultOps.includes(k)
)
const cleanQuery = _omit(q, customOperators)

The filtering doesn't take the whitelist into account, I've seen it before but I don't know why it's done because the cleanQuery function is there for that and it is recursive.

Yeah I get what is happening in that flow - just don't understand why 😅
So I have no idea if this is a bug or if there are other concerns that led to removing all '$' operators from the top-level of the query except those specifically hard-coded in there.
Hopefully, someone else can shed some light on this!

I think that we can safely remove this code block because the filterQuery function doesn't keep the operator if it's not in the given operators list.

@J3m5 Oh perfect - This would make my life a lot easier for sure if it can be safely removed!

I would really appreciate a PR if this will benefit users.  I'm a bit strapped for time for the next week or so, but I can review PRs and do releases.  Thanks guys!

@kshitizshankar thanks for the details in your last comment.  I was able to make the PR and have published it as<EMAIL_ADDRESS> Please reopen this issue if you still find that there's a problem.


Replace versioneer overrides with manual modification of package source

This PR replaces setting the RAPIDS_PY_WHEEL_VERSIONEER_OVERRIDE environment variable for consumption within Python packages with instead directly modifying metadata in the package. It relies on each package to provide a script ci/release/apply_wheel_modifications.sh that can be executed at wheel build time to perform all the necessary version replacements.

changed the base branch to branch-23.04.
i will delete the main branch now.

I have no other comments aside from what Sevag mentioned.
But can you post some links in this PR that reference where this has been tested downstream so we can inspect the changes there?

Here is an RMM PR demonstrating that existing repos won't be broken by this change. It changes rmm to use this branch of the workflow without doing anything else
Here is the PR containing the intended changes, namely the replacing of versioneer with a few hardcoded versions and extra lines in update-version.sh.


mixing globalizer with templatitator

I want to use globalizer in an template file and found an issue. The reference has to be present in global and in the file where it used. If the reference is not global, i saw only an empty box in admin panel (not only the dropdown, also the other content). If it is not in cms file of used page, it recommended that it cannot read property of undefined.

Ok I have to go one step back, maybe I tried to much stuff yesterday. It has not to be defined twice, but it will not find the definition if it is only in global or the template file itself. it has to be defined at file of use, is that wanted?


Non root ssh create sudo can't get password

Sudo tty password
I saw this but i don't know if it relates
https://github.com/ehazlett/machine/commit/b43a72f91aad5f3067ba406e54534bdd4b834fb4
maybe I don't know how the allocate the tty
My issue is that when using the generic driver to create a machine I do:
docker-machine -D create --driver generic \
  --generic-ip-address=example_host.example.com --generic-ssh-user=john \
  --generic-ssh-key=/home/john/.ssh/id_rsa.pub example_host

machine is able to log into example_host.example.com as john with the correct
key file, however it then attempts to run
sudo hostname example_host && echo "example_host" | sudo tee /etc/hostname

To which sudo replies
sudo: no tty present and no askpass program specified

when sudo trys to ask for john's password
Here is the full debug:
Importing SSH key...
IP: example_host.example.com
Getting to WaitForSSH function...
Testing TCP connection to: example_host.example.com:22
Using SSH client type: external
About to run SSH command:
exit 0
&{/usr/bin/ssh [/usr/bin/ssh -o PasswordAuthentication=no -o IdentitiesOnly=yes -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -o ConnectionAttempts=3 -o ConnectTimeout=10 -i /home/john/.docker/machine/machines/example_host/id_rsa -p 22<EMAIL_ADDRESS>exit 0] []  <nil> <nil> <nil> [] <nil> <nil> <nil> ?reflect.Value? false [] [] [] [] <nil>}
SSH cmd err, output: <nil>:
Using SSH client type: external
About to run SSH command:
cat /etc/os-release
&{/usr/bin/ssh [/usr/bin/ssh -o PasswordAuthentication=no -o IdentitiesOnly=yes -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -o ConnectionAttempts=3 -o ConnectTimeout=10 -i /home/john/.docker/machine/machines/example_host/id_rsa -p 22<EMAIL_ADDRESS>cat /etc/os-release] []  <nil> <nil> <nil> [] <nil> <nil> <nil> ?reflect.Value? false [] [] [] [] <nil>}
SSH cmd err, output: <nil>: NAME="Ubuntu"
VERSION="14.04.1 LTS, Trusty Tahr"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 14.04.1 LTS"
VERSION_ID="14.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"

found compatible host: ubuntu
Using SSH client type: external
About to run SSH command:
sudo hostname example_host && echo "example_host" | sudo tee /etc/hostname
&{/usr/bin/ssh [/usr/bin/ssh -o PasswordAuthentication=no -o IdentitiesOnly=yes -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o LogLevel=quiet -o ConnectionAttempts=3 -o ConnectTimeout=10 -i /home/john/.docker/machine/machines/example_host/id_rsa -p 22<EMAIL_ADDRESS>sudo hostname example_host && echo "example_host" | sudo tee /etc/hostname] []  <nil> <nil> <nil> [] <nil> <nil> <nil> ?reflect.Value? false [] [] [] [] <nil>}
SSH cmd err, output: exit status 1: sudo: no tty present and no askpass program specified

Error creating machine: exit status 1
You will want to check the provider to make sure the machine and associated resources were properly removed.

Any ideas on what to do? I tried asking the irc

I'm working on fixing this

I'm still working on this, Heres the repo if you want to use my version while I wait / hope to get my changes merged in https://github.com/pdxjohnny/docker-machine

My version works now so if you want to use that go ahead I'll leave this open until it gets merged in

hello @pdxjohnny could you get your changed merged in ? I could see the commit but not PR

https://github.com/docker/machine/pull/1586
I tried to it probably needs to be updated though

For people coming here in relation to docker multi-networking blog post
The only temporary fix is to let your user explicitly allow sudo to be used without a password.
edit /etc/sudoers and add YOURUSERNAME   ALL=(ALL) NOPASSWD:ALL

+1

I think https://github.com/docker/machine/pull/3085/files is sufficient to close this?

When you have such kind of problems, always check logs of target machine. In my case problem was - target machine was not able to - yum update.


feat: implements of getbit and setbit

This PR is related with #517

Do some modifications for update function merged days before to improve reusability of code
Add SetBit and GetBit

SetBit

If set to a non-exist key, it will create this key and corresponding value. The value will composed of offset bits of \x00 and 1 bit of the give byte.
If set to a exist key, and the value have a bigger size than the given offset. It will modify the corresponding bit.
If set to a exist key, but the value have a smaller size than the given offset. It will add some \x00 and modify the right bit to the given byte

GetBit

If get with a non-exist key, it will throw a key not found error.
If get with a exist key and the value have a bigger size than the given offset. It will return the corresponding bit
If get with a exist key but the value have a smaller size than the given offset. It will return \x00. (This is same with GETBIT of redis)

Hi, just a reminder. Don't forget update doc and example 😁.

Hi, just a reminder. Don't forget update doc and example 😁.

Hi, I've update documents and examples. How do you think about them


Track ipc contract genesis artifacts

Introduction
This PR builds on top of the previous PR: to track the ipc contract artifacts at genesis and actual deployment.
The high level idea is instead of scaning the contract byte code at init_chain, the genesis creation scans the artifacts and prepares the genesis such a way that makes the deployment a bit easier.
The gateway and registry contracts and all the facets are scanned to detect all the libraries used behind the scene. The bytecode and link references are collected into a hashmap with contract name as the key. This hashmap will be serialized and written to the genesis json.
The pending issue is to version the rust abi bindings, perhaps using rust crate version control instead of putting it in genesis.

Closing in favour of https://github.com/consensus-shipyard/ipc/pull/1016.

Actually closing now ;-)


Frame data

Is it possible to receive the frame data for streaming rather than saving it to a file?

This feature will be added as soon as possible. Don't worry. Have a nice day.

I am waiting for frame data feature for streaming it. Thanks a lot. Best regards.