Add files via upload

@Eminentdio file/lib/domains/ng/edu/ui.txt: this request has an incorrect file path format, please ensure that you are familiar with     this repository rules located at the bottom of this page and change     your request accordingly. If you don't know how to change request, close it and open a new one.     If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message.

@Eminentdio First stage of verification passed, official domain is ui.edu.ng as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@Eminentdio Thank you for your patience while waiting for a review and processing your request. Pull request merged.


Porblem with parsing multiple or, and logical operators

Description
Right so I wanted to chain multiple Or and And operators it works when I swith them but shows error when using only one kind.
(a<b) && (a<5) && (b<10) not okay
(a<b) && (a<5) || (b<10) okay
Steps to Reproduce

https://cortexjs.io/mathlive/demo/
insert \left(0<b\right)\land\left(a<b\right)\land\left(a<-1\right)

4. insert \left(0<b\right)\land\left(a<b\right)\lor\left(a<-1\right)
5.

6. insert \left(0<b\right)\lor\left(a<b\right)\lor\left(a<-1\right)
7.

8. Try to solve it with parenthesis does not help insert \left(0<b\right)\lor\left(\left(a<b\right)\lor\left(a<-1\right)\right)
9.

Actual Behavior
From the steps above you can see when parsing multiple And and Or operators I get 'unexpcted-argument'.
Expected Behavior
Chaining multiple And statements and Or statements should be possible.
Environment
MathLive version If using the cortexjs.io site, the version is displayed
at the bottom of the page. If using the library, the version is available as
MathfieldElement.version
From the bottom of the site.
MathLive version
0.95.5
Updated
September 22, 2023
Operating System macOS, Windows, iOS. Include the version
OS Win11
Browser Safari, Chrome, Edge, Firefox, etc... Try several browsers and note
if there are differences between browsers.
Tried several browsers does not have an impact on the result.

Right so I went in to the code a bit and found some things.
https://github.com/cortex-js/compute-engine/blame/0851acb75817f4318d430f7d2b828acb01fd0899/src/compute-engine/compute-engine.ts#L265
Functions: null, // (Anything^n) -> Anything
NumericFunctions: null, // (Numbers^n) -> Numbers
RealFunctions: null, // (ExtendedRealNumbers^n) -> ExtendRealNumbers
LogicOperators: null, // (Booleans, Booleans) -> Boolean
Predicates: null, // (Anything^n) -> Booleans

LogicOperators: null, // (Booleans, Booleans) -> Boolean

The definition in the comment is strange. Why logic operators have only two parameters and not varying number of them?
Went a little deeper:
https://github.com/cortex-js/compute-engine/blob/0851acb75817f4318d430f7d2b828acb01fd0899/src/compute-engine/library/domains.ts#L34
Functions: ['FunctionOf', ['VarArg', 'Anything'], 'Anything'],
NumericFunctions: ['FunctionOf', 'Numbers', ['VarArg', 'Numbers'], 'Numbers'],
RealFunctions: [
'FunctionOf',
'ExtendedRealNumbers',
['VarArg', 'ExtendedRealNumbers'],
'ExtendedRealNumbers',
],
LogicOperators: [
'FunctionOf',
'Booleans',
['OptArg', 'Booleans'],
'Booleans',
],
Loking in this file the only domain that uses 'OptArg' is LogicOperators.
What is the difference between 'OptArg' and 'VarArg'? From the name I would assume that varArg is any number of arguments and OptArg is max number of arguments is specified, but the definition does not say so.
From guide-domain: A value of  or Nothing.
$$ \bot\land\bot\land\bot $$
Tried this:

Should be parsed as ['And', False, False, False] so all three params are from the same domain. But I guess the bug is somewhere else.
After I went looking where I get 'unexpcted-argument' error.
Getting the error here:
https://github.com/cortex-js/compute-engine/blob/0851acb75817f4318d430f7d2b828acb01fd0899/src/compute-engine/boxed-expression/validate.ts#L362
somehow here few lines above
https://github.com/cortex-js/compute-engine/blob/0851acb75817f4318d430f7d2b828acb01fd0899/src/compute-engine/boxed-expression/validate.ts#L272
it did not get all the OptArg and did not iterate over them.
So I went in to my code and did this for And, Or operators
const scopeMap: RuntimeIdentifierDefinitions = this.computeEngine.context.parentScope.ids;
        if (scopeMap != null) {
            for (const operator of ['Or', 'And']) {
                const operatorDefinition = scopeMap.get(operator);
                if (operatorDefinition != null && 'signature' in operatorDefinition) {
                    const signature = operatorDefinition.signature;
                    signature.optParams = [];
                    signature.restParam = signature.params[0];
                }
            }
        }

Just have to set optParams to empty array and restParam set to the same value as the first param which is Boolean.
@arnog
Was there any reason for the OptArg in logic-operators definition?

OK, that's some great detective work. You basically got it right. There's some info about OptArg/VarArg here https://cortexjs.io/compute-engine/guides/domains/#constructing-new-domains
Basically, OptArg indicates an optional argument (1 or zero), while VarArg indicate an argument that can be repeated zero or more times.
The issue is indeed the definition of LogicOperators. It should use VarArg, not OptArg.
I would also recommend avoiding modifying the "built-in" definitions, but you can override them by providing a new definition that will "shadow" them in the current scope.

Fixed in aa49d8b


Document that 0.9.14 requires SSE4.1

Expected Behavior 🌈
Document that 0.9.14 requires SSE4.1
Current Behavior 💥
Document that 0.9.14 requires SSE4.1
Relevant log output 📝
No response
Steps to Reproduce 🔍
Document that 0.9.14 requires SSE4.1
Context (Environment) 🌎
Document that 0.9.14 requires SSE4.1
Possible Solution 🛠
No response
Version 📦
v0.4.x
Anything else? 📌
No response

This issue should be in umh.docs.umh.app

yes


Improved the Load More Posts button UI

Load More Posts btn UI before :

Btn UI after :

I have successfully resolved the issue number #346 . I have added the before and after screenshots as well.
Now in light & dark mode the button and its text is visible while hovering.

kindly resync your fork , add issue number to PR


Redesign URL Class for Vichan

8chan's API is just about exactly the same as any Vichan engine's API. But in order to make it possible for people to set their own Vichan URLs, the url.py Class needs to be redesigned.

Perhaps this sort of thing would become a pyvichan, separate from the py8chan library, as there are clear differences between 8chan's implementation and that of others. Also, URLs would need to be defined by the constructor.


Mcs 1026 config template

Includes a lot of new features:

New python run_eval.py script
Using mako templating engine
Use single templates for mcs config and ray config files
Create general stats and timing estimates
Orchestrate variable number of clusters
Orchestrate custom permutations of scene folders and metadata levels

This incorporates tickets: 744, 1027, 1026
Questions/Issues:

Terminology and naming - I am unsure how to name things an it is evident in the code
Documentation - documentation is messy and probably not clear
Setting variable and varsets - Is this clear? easy? necessary?  I like the idea of hierarchical variable sets, but is there a more intuitive way?
.tmp_pipeline_ray folder accumulates folders with each run and requires a manual clear

More work:

Merge CORA PR when it comes in and validate (will be in this PR prior to final merge)
Better error capturing and output parsing (MCS-1049)
Better status and timing (MCS-1049)
Json or yaml status capture that is rerun-able (MCS-1049)

I'm confused about what is still needed and what the preferred way of running things is.  There was pipeline_ray.py, but then a script run_eval.sh to set things up for it;  we are transitioning to run_eval.py, which is fine, but if it is the preferred way of running an eval, then it should be clear.  At this point, there are too many ways of doing it.

I think that run_eval.py should be in the top level, rather than aws_scripts; remove run_eval.sh
configs/*.ini files should go away?   hard to know what is still needed and not needed if they are still there
what is still needed in aws_scripts?
does pipeline_ray.py need to be at the top level?   Will people be running that, or is it something that is now a sub-process to run_eval.py?
it's confusing to have have both a config file and a command-line parser; I would vote to just have a config file.

I need more time to digest/try out run_eval.py, but I like the templating and wanted to leave a few thoughts regarding some of the points mentioned at the top:

Regarding documentation: I think this probably needs its own ticket. There is a LOT of information here + in confluence regarding Ray/the pipeline/how we run the evals. I do think nailing down how exactly we want to run everything like Clark was saying will help with this a little bit.
For cleaning things up after a run, like in .tmp_pipeline_ray: would it make sense to have a line that cleans up files of a certain type/pattern after the 'ray down' call in ray_eval.py? Maybe something else to clean up everything once all jobs have finished?

I'm confused about what is still needed and what the preferred way of running things is. There was pipeline_ray.py, but then a script run_eval.sh to set things up for it; we are transitioning to run_eval.py, which is fine, but if it is the preferred way of running an eval, then it should be clear. At this point, there are too many ways of doing it.

I think that run_eval.py should be in the top level, rather than aws_scripts; remove run_eval.sh
configs/*.ini files should go away?   hard to know what is still needed and not needed if they are still there
-- Nope, they are still needed;  used in run_eval, line 206
what is still needed in aws_scripts?
does pipeline_ray.py need to be at the top level?   Will people be running that, or is it something that is now a sub-process to run_eval.py?
it's confusing to have have both a config file and a command-line parser; I would vote to just have a config file.

For your points:

Moved the run_eval.py script around and removed a bunch of stuff in autoscaler.  I need to check and see if this will work with the video creation configs.
The {team}-aws.ini are still around.  They would probably not be hard to remove, but i'd prefer to leave that for future work.
aws_scripts is gone
moved pipeline_ray into a ray_script folder
We should talk more about the config file and command line.  The goal here was the config is "what to run" and the command line was "how to run it".  The goal was to allow us to share the config with minimal changes.  This does get confused a little with the idea of name tagging clusters, number of clusters and number of workers.  I also added the capability from the command line parser to run a single run kind of like the old shell script.  I should probably move that to another python file entirely.

I need more time to digest/try out run_eval.py, but I like the templating and wanted to leave a few thoughts regarding some of the points mentioned at the top:

Regarding documentation: I think this probably needs its own ticket. There is a LOT of information here + in confluence regarding Ray/the pipeline/how we run the evals. I do think nailing down how exactly we want to run everything like Clark was saying will help with this a little bit.
For cleaning things up after a run, like in .tmp_pipeline_ray: would it make sense to have a line that cleans up files of a certain type/pattern after the 'ray down' call in ray_eval.py? Maybe something else to clean up everything once all jobs have finished?

The only reason I don't want to clean up the files after a run is that is where I am saving the resume configuration file in the next ticket as well as you can inspect the yaml to make sure it is correct.  It should probably be renamed if it isn't going to be that temporary.  Thoughts?


getting error when trying to lunch "my image" elasticsearch:6.2.2

Expected behavior
when i click on "Create" button under the section "My Images", i expect the container to start
Actual behavior
upon clicking "Create" on my image, i see error message "(HTTP code 404) no such image - no such image: docker.elastic.co/elasticsearch:6.2.2: No such image: docker.elastic.co/elasticsearch:6.2.2"
Information about the Issue
i've pulled docker image via docker pull docker.elastic.co/elasticsearch/elasticsearch:6.2.2
as instructed on https://www.elastic.co/guide/en/elasticsearch/reference/current/docker.html
then opened kitematic app, clicked "+ New" navigated into "My images" and clicked "Create" next to my elasticsearch:6.2.2 box
Steps to reproduce the behavior

pull docker image via docker pull docker.elastic.co/elasticsearch/elasticsearch:6.2.2
open kitematic
click "+ New"
click "My Images" (top right)
locate elasticsearch box and click "Create"
see error "(HTTP code 404) no such image - no such image: docker.elastic.co/elasticsearch:6.2.2: No such image: docker.elastic.co/elasticsearch:6.2.2"  7.

Thank you for providing detailed information on this. The usual 'Observe no latest tags' is provided for users that didn't provide these steps and don't understand that they're pulling from a different registry.
Keep in mind that support for other registry has been an on-going discussion in Kitematic. WRT the "download", it's actually what docker does as well when you do a docker run .. - If you look through the Engine API, you'll notice that run isn't an API endpoint:
https://docs.docker.com/engine/api/v1.36/#tag/Container
You have to Pull, Create, and finally Start the container; this is what Kitematic does and why there's always a "download" triggered.
I'll see if I can isolate why this isn't working and provide a solution, if possible.


Feature: Possible to also have cv2_waitKey?

When cv2.imshow is used in an application, invariably there is usually also a call to cv2.waitKey. Do you think there would be any way to support this too remotely somehow?

Thank you for your interest.
However, i think there is no way to take a key event in Jupiter.
Do you know some ways?

I'm no expert, but Jupyter seems to work okay with input() reading from stdin, so one of the solutions presented here (https://stackoverflow.com/questions/983354/how-do-i-wait-for-a-pressed-key) for capturing a single character from stdin could potentially work? (using e.g. termios or ncurses?) A crude backup solution would be to use input(), which would require an enter after every keypress, but would at least fundamentally allow the code to run at all)

They are not designed for Jupyter. So they were not working.
I proposed a new idea.
I present a button for waitKey. So by clicking the button, it simulates the key press.
Please install v1.3.1 by pip install opencv_jupyter_ui==1.3.1

Hey, the button is a cool idea. For many cases that will already be enough!
In my case, my code is going through the frames of a video, and I use different keys to control whether to play/pause and/or step frames. At the moment the button can only send 255 as a return value. Do you think that maybe with the incorporation of some kind of text field or so at least 'normal' characters like a-z, 0-9, space etc could be returned?

It is imposible in Jupyter to get a single key and textbox is not a good idea too.
I have designed multiple customizable keys. Please upgrade to version 1.4.1
pip install opencv-jupyter-ui==1.4.1

I can confirm that this works for me and completely covers my use case now. You can close this issue if you agree that this is totally dealt with now. Thanks!

Thank you,
I have updated.
Would you please mark the answer as useful (if it is really) in StackOverflow to help more people see this project ;)

in Jupyter it is not possible to get a key
however i think it would be nice to have the possibility to define custom
keys as button
i will add this
On Mon, 18 Jul 2022, 10:27 Philipp Allgeuer, @.***>
wrote:

Hey, the button is a cool idea. For many cases that will already be enough!
In my case, my code is going through the frames of a video, and I use
different keys to control whether to play/pause and/or step frames. At the
moment the button can only send 255 as a return value. Do you think that
maybe with the incorporation of some kind of text field or so at least
'normal' characters like a-z, 0-9, space etc could be returned?
—
Reply to this email directly, view it on GitHub
https://github.com/modaresimr/opencv_jupyter_ui/issues/1#issuecomment-1186913551,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACIO4RVX6WGUAG3FLARYGXTVUUIPVANCNFSM53N7HWTQ
.
You are receiving this because you commented.Message ID:
@.***>


Layered Scaling feature

Description

Related issues

Checklist
You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[ ] I have read the contributing guidelines and the code of conduct.
[ ] I have followed the documentation style.

Additional information

At the moment only sending data upwards is supported in the kafka bridge @Ferdinand to check.
only remaining this. looks good to me :)


XLIFF and tracing back to source

How do I trace back from a XLIFF entry to it's source in the code?  The XLIFF "id" is some generated number that does not appear to have any reference to the object ID.  If a translator asks me what the context of a caption is how to do I find it?
Example below "id="Codeunit<PHONE_NUMBER>" comes from an Codeunit with the Object ID of 9095101.
        <trans-unit id="Codeunit<PHONE_NUMBER> - NamedType<PHONE_NUMBER>" maxWidth="999" size-unit="char" translate="yes" xml:space="preserve">
          <source>WIP %1</source><target state="translated">WIP %1</target>
          <note annotates="general" from="Developer" priority="2">%1 is a description</note>
          <note annotates="general" from="Xliff Generator" priority="3">Codeunit - Label</note>
        </trans-unit>

Go to the may update of the Developer Preview

Correct, this was fixed in the recent preview release.


Fixes #133, fixes #145

Adds additional flags to support setting assembly attributes.
Allow adding DLL's to the file list when creating standalone executable

Forgot to add the DLR?

Yeah


OSX: Resolve the compatibility issue with 10.12 Sierra

QTKit is being deprecated, forcing the developers to download the 10.11 SDK and install it themselves under Sierra.
Maybe that issue is already fixed inside the latest WebRTC revision.

I've successfully compiled their latest version, an update is required.

Resolved, also made the libwebrtc-chromium-deps repository lighter since it doesn't contain the Linux sysroot by default.


chore(release): v0.24.0

Version bump in package.json for release v0.24.0

:tada: This PR is included in version 0.24.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Optimize Docker image

I optimized the Docker image so that the image size is reduced to around 340MB (from around 800MB).
Changes made to the build process:

Use latest Alpine base image (alpine:3.12)
Disable pip cache
Remove build-time dependencies right after pip install
Disable yarn's update checker (reduce build time by a few seconds)
Delete yarn cache right after yarn install
Use dockerignore so that certain files/directories (resources/ and everything in gitignore) will not be included in the container image

Looks great. tested locally, seems all good. Thanks for the contribution.


TypingMode

Proposal
Some of our typing rules depend on the "mode" we're in. Most notably, whether we should force "unknowable" trait goals to be ambiguous during coherence and whether to define or reveal opaque types.
This is currently handled via ParamEnv::reveal, InferCtxt::intercrate, and InferCtxt::defining_opaque_types and never changes during the lifetime of a InferCtxt. Going forward we intend to add yet another mode to the type system: only reveal opaques defined by some body, but without being able to define them. This is necessary during places such as opaque type well-formedness checking. We currently

either treat them as opaque, and get an inconsistent state as HIR typeck only succeeded because it was able to observe the hidden type,
or we allow redefining all the opaques from the body, this causes ambiguity errors in case we end up using an opaque without actually reconstraining it. This is the reason why we've needed #124598 for bootstrap with the new solver

We currently also frequently accidentally forget parts of our typing mode, e.g. when calling nested queries which only take a ParamEnvAnd, dropping both the defining_opaque_types and intercrate.
I intend to change this by moving all of this information into a new typing_mode field on the InferCtxt and then change queries currently taking a ParamEnv to instead take a struct TypingEnv<'tcx> { typing_mode: TypingMode<'tcx>, param_env: ty::ParamEnv<'tcx> }.
I've started to already implement this in https://github.com/rust-lang/rust/pull/131856 and am continuing this work in https://github.com/rust-lang/rust/pull/132460. Given that this is ending up being quite involved and a nightmare to revert, I want to make sure the full Types Team is aware of this effort.
See https://rust-lang.zulipchat.com/#narrow/channel/364551-t-types.2Ftrait-system-refactor/topic/.60TypingMode.60 for more details, might extend this MCP tomorrow, have to leave for today 😅
Mentors or Reviewers
@compiler-errors
Process
The main points of the Major Change Process are as follows:

[x] File an issue describing the proposal.
[ ] A types team member or contributor who is knowledgeable in the area can second by writing @rustbot second.

Finding a "second" suffices for internal changes. If however, you are proposing a new public-facing feature, such as a -C flag, then full team check-off is required.
Types team members can initiate a check-off via @rfcbot fcp merge on either the MCP or the PR.

[ ] Once an MCP is seconded, the Final Comment Period begins. If no objections are raised after 10 days, the MCP is considered approved.

You can read more about Major Change Proposals on forge.
Comments
This issue is not meant to be used for technical discussion. There is a Zulip stream for that. Use this issue to leave procedural comments, such as volunteering to review, indicating that you second the proposal (or third, etc), or raising a concern that you would like to be addressed.

@rustbot second
Very very in favor of this work, and have discussed at length the approach and final state of the type system after this change. I'm volunteering to review this work.


Header undefined?

Current Behavior
I'm trying to upgrade the @shoutem/ui package to use the navigation from this library, since NavigationExperimental was recently deprecated. I'm trying to use the propTypes from the header and am getting the following error: undefined is not an object (evaluating _reactNavigation.Header.propTypes

Expected Behavior
Why is Header undefined? I import it like this:
import  {Header as NavigationHeader} from 'react-navigation';
then I use NavigationHeader.propTypes in the propTypes of a header component that's effectively extending this one.
Your Environment

software
version

react-navigation
1.0.0-beta.7

react-native
0.42.0

node

npm or yarn

Hey @JulianKingman did you ever figure out a solution for this? I'm not familiar with how flow works but the Header component doesn't have propTypes, but it doesn't really explain the error you received.
I'm going to close this (cleaning up issues) but if it's still an issues please re-open.

This issue is moot.


Cannot NULL permission

Trying to NULL a permission attached to an account and getting action exception.
./cleos.sh get account eos42freedom
permissions:
     owner     1:    1 EOS8QoCJ5TcopvKTVW5trtRKeynK5KCdTJiwwcFfdn8FVWxrfnhnN
        active     1:    1 EOS5rgA6SenKsWJysTRwS6nek8uHbT7PjsDMY76sZkHEW74Htnc5p
           claim     1:    1 EOS8WLaXgcZdctUr8DAErtgp5g9qp6PZQxDRHybUer4L4U9m6BCMt

./cleos.sh set account permission eos42freedom claim NULL
Error 3050000: action exception

Can you start your nodeos with --verbose-http-errors option and paste the result of running the above command here?

./cleos.sh set action permission eos42freedom eosio claimrewards NULL
executed transaction: f07ad3c329ddef7269142768a35e53656cf28682d7c6b23db83e4fc17596407a  120 bytes  1142 us
#         eosio <= eosio::unlinkauth            {"account":"eos42freedom","code":"eosio","type":"claimrewards"}
warning: transaction executed locally, but may not be confirmed by the network yet

I double checked the authority link was  unlinked.
./cleos.sh set action permission eos42freedom eosio claimrewards NULL
Error 3040000: transaction exception
Ensure that your transaction satisfy the contract's constraint!
Error Details:
cannot unlink non-existent permission link of account 'eos42freedom' for actions matching 'eosio::claimrewards'

./cleos.sh set account permission eos42freedom claim NULL
Error 3050000: action exception
Error Details:
Cannot delete a linked authority. Unlink the authority first

We once had the same issue. I checked your transaction, you once set linked to a wrong action:
72d4e5d604f529c8ef188e6f1904dc0f03c356d912051f648daadc908bacc2f1
account: eos42freedom, code: eosio, type: claimrewar, requirement: claim
Once we unlined the wrong action, we could delete the permission.
But we have a new problem now. We cannot claim rewards when we set a new permission and I don't know why.

thanks very useful :). Many people are having the same issue & some it does work, but still uses the active permission.

@ankh2054 Will you create the claim permission again? If so, please let me know if you can claim rewards by that permission successfully. Thank you.

I’ve tried again but still not working for me, always uses the active permission. Not sure why.

cleos push action eosio claimrewards '{"owner":"BP-ACCOUNT"}' -p BP-ACCOUNT@claimer
this works and the claimer permission is able to claim correctly. #4379


[ZEPPELIN-5934] Check notebook folder permissions before allowing to rename, remove or restore it

What is this PR for?
Users who are able to see notes in some directory can rename, move to trash and remove from trash that directory without being owner or having write permissions for notes in that directory.
This is resolved in first commit.
Secondly, after renaming directory to the name of already existing directory, old notes in target directory become unaccessible (in fact those notes are removed in file system, but still visible in UI as they are present in NoteManager registry).
This addresses 2nd point in ZEPPELIN-5333.
Fixed in 2nd commit.
What type of PR is it?
Improvement
What is the Jira issue?

ZEPPELIN-5934
ZEPPELIN-5333.

How should this be tested?

I've tested this manually by creating some note in directory, giving read permission to it for some other user, and checking whether that user can move to trash, remove, rename or restore directory with that note.
I've checked and it does not seem like there are available infrastructure in NotebookServiceTest or in NoteManagerTest to cover multi-user scenarios.

Sorry, I made this PR on top of 0.10.1 version, and it seems like something has been changed in this filed in master branch since then.
Now I have local fix of this issue for master branch. I'll update the PR as soon as I have successful run of tests.

Issues in my last comment were resolved in the latest commit.

BTW, there are no tests for the features. Could you please add tests for your feature?


logic bug in dynamic template substitution

Issue Summary
Passing dynamic or substitution wont work for dynamic templates because of the logic bug found here
https://github.com/sendgrid/sendgrid-nodejs/blob/0c83ae9a7151f466383df35a897a3426c5cdb06b/packages/helpers/classes/mail.js#L243-L247
after 2 days trying to find why substitution is failing I decided to look in the code.
The current work-around is to supply both substitutions and dynamicTemplateData in which case the library will delete substitutions, leaving dynamicTemplateData

Hello @codmajik,
Thanks for reporting this! I've added this to our backlog for further investigation.
With Best Regards,
Elmer

Hello, I'd love to take on this one if no one is currently working on it?

It's all yours @mateoholman, thanks!

@thinkingserious I'd love to get this fixed, but I need a bit of guidance on how the library should behave.
Can you summarize what the behavior here should be? It seems like the logic in question is trying to prevent the a user of this library from using the wrong property in the wrong context (substitutions vs dynamicTemplateData), as opposed to just sending the data along that the user has passed in.
It seems like the intended logic is, if the user is using a dynamic template (a template id that starts with a 'd'), then they should be using the dynamicTemplateData property, otherwise, for legacy templates, they should be using substitutions. It's not clear to me in which contexts the dynamicTemplateData property is supposed to be nested inside personalizations, but the library appears to expect it in both forms.
I'm not sure this library needs this logic, which seems intended to prevent the user from making a logical mistake, which presumably the api will respond with an error anyway. As a general principle, I don't think this library should be deleting or materially changing the structure of data the user has told the library to pass along to the api. That's unexpected and leads to very difficult to track down bugs.
Also, it seems that there is a related bug here in the typescript definition file that only accepts the dynamicTemplateData property inside the personalizations, but not at the top level, which seems to be what the javascript implementation expects: https://github.com/sendgrid/sendgrid-nodejs/blob/95dfe0652abb29eeae41b4530f12d5d7be95d3ed/packages/helpers/classes/mail.js#L90-L92.
I'm happy to fix this in a PR, I'm just not sure what the behavior here should be.

@thinkingserious it looks like the typescript issue has been resolved here: https://github.com/sendgrid/sendgrid-nodejs/commit/2d55dc44b6028a6bcc2e26400ce187a905a8c754. Any plans to update the package with this change?

@thinkingserious ping

@mateoholman, @ajsharp,
Are either of you working on this one?
@ajsharp,
I'm hoping to get a release out soon (Node.js is next in our queue), but I don't have a specific date.

Fixed by #939


feat: multiviewer border and additional box properties

About the Contributor
This pull request is posted on behalf of Companion
Type of Contribution
This is a: Feature
Current Behavior

New Behavior

Testing Instructions

Other Information

Status

[ ] PR is ready to be reviewed.
[ ] The functionality has been tested by the author.
[ ] Relevant unit tests has been added / updated.
[ ] Relevant documentation (code comments, system documentation) has been added / updated.

Codecov Report
Attention: Patch coverage is 67.64706% with 33 lines in your changes missing coverage. Please review.

Project coverage is 83.35%. Comparing base (1b9a6eb) to head (10b8633).

Files with missing lines
Patch %
Lines

...tings/MultiViewerWindowOverlayPropertiesCommand.ts
60.00%
16 Missing :warning:

...commands/Settings/MultiViewerBorderColorCommand.ts
64.00%
9 Missing :warning:

...s/Settings/MultiViewerWindowSafeAreaTypeCommand.ts
72.41%
8 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #169      +/-   ##
==========================================
- Coverage   83.62%   83.35%   -0.27%
==========================================
  Files         191      194       +3
  Lines        6057     6157     +100
  Branches      956     1008      +52
==========================================
+ Hits         5065     5132      +67
- Misses        960     1025      +65
+ Partials       32        0      -32

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Apply minor style changes to perfdash config validation

As a followup from previous PR, this fixes minor style issues in the
config validation logic:

use of named return values
comment was not formatted properly
typo in comment

/ok-to-test
/lgtm
/approve
Thanks!


Revert "Merge pull request #1536 from ericldelaney/task/stable/FACT-1595/update_debugging_tests"

This reverts commit 38cd262d544d59b133913b1ebca8dc1b4215366e, reversing
changes made to 986c5eef2d51e963ac9e12ab564a12034ce04a13.

Yeah... this feels silly and wrong 👍

👍

CLA signed by all contributors.


Geekbench: Updating supported versions

Just to confirm -- these versions have been confirmed to be working with the existing implementation. Or should there be additional changes to make the workload work with these new versions?
Either way, could please add a commit message body stating which it is.

Correct, the updated versions are working and tested with the existing implementation.

Great! Please add that to the commit message.


Nextjs v13 Installing Dependencies Failed

Describe the bug
Hello,
I am creating a Nextjs Project from scratch which has the Nextjs version v13 which is failing to Install the Dependencies, please look into this matter.
I'm building the Project in Nextjs v13 from scratch in my local system where it's working perfectly fine but StackBlitz have some issue for installing the dependencies.
Link to the blitz that caused the error
https://stackblitz.com/edit/nextjs-pmcz3s?file=package.json
Steps to reproduce
there's no steps to reproduce
Expected behavior
The expected behavior is to install the dependencies properly & run the start command to run the Nextjs App
Parity with Local

[X] I have run the project in my local machine and I could not reproduce the issue.

Screenshots
No response
Platform
Browser name  = Chrome
Full version  = <IP_ADDRESS>
Major version = 108
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36
performance.memory = {
  "totalJSHeapSize": 85975618,
  "usedJSHeapSize": 77458466,
  "jsHeapSizeLimit":<PHONE_NUMBER>
}
Hash = 0478c85eccde42845cdffe4745a763e1f3cb6e82

Additional context
No response

Hey there 👋 Thanks for the bug report, but the link you provided doesn't work for me. I am getting a 404. Can you please provide a working link and add some more information as to what the issue is with a list of steps to reproduce?

Hey there 👋 Thanks for the bug report, but the link you provided doesn't work for me. I am getting a 404. Can you please provide a working link and add some more information as to what the issue is with a list of steps to reproduce?

https://stackblitz.com/edit/nextjs-jb2zpq?file=package.json

Hi @dhavalveerarediff! We found out that the latest release<EMAIL_ADDRESS>is broken on WebContainer. Version 13.0.6 still works. We will have to look into why that is. In the mean time, we made sure that our starter project that you can create from the dashboard is updated to pull in a working version (13.0.6).

@SamVerschueren @d3lm , please look at the attached image, now this way StackBlitz is crashing the page, and the Project URL => StackBlitz Project

@SamVerschueren @d3lm = looks like currently StackBlitz doesn't have a stable Code particularly for Nextjs v13

Hi @dhavalveerarediff . The SBOX_FATAL_MEMORY_EXCEEDED error is because Chrome runs out of memory. This could happen if you have quite some Chrome tabs open, and maybe also quite some StackBlitz projects? The link that you shared does seem to work for me.
We found the issue with Next.js and tracking this internally.

I was too fast with answering. We did fix this for the latest Next.js versions. So it also works with the latest version https://stackblitz.com/edit/nextjs-vjwqlx. Closing this issue.


Regulation with --pcr-synchronous fails on PCR loopback

Hello,
I'm using the following command to stream a low-bitrate ts carrying timed data:
tsp -v -I file --infinite input.ts -P pcradjust -P continuity --fix -P regulate -p 1 --pcr-synchronous --wait-min 1 -P fork -b 1 "socat -b 188 UDP-SENDTO:<IP_ADDRESS>:51083,bind=<IP_ADDRESS> -" -P fork -b 1 "socat -b 188 UDP-SENDTO:<IP_ADDRESS>:51084,bind=<IP_ADDRESS> -" -O drop
The ts contains a single program with a single PID. The data packets are 188-byte length. The ts packet sequence is basically PAT - PMT - PES in a loop.
I observed that regulation fails after about 26.5 hours, which seems to indicate a problem on PCR loopback. The ts is streamed as if there were no regulation.

I forgot to say I'm using a self-compiled version 3.17-1189.

Hi @mlaurendeau
26.5 hours is exactly one complete PCR round. So, yes this is related.
If fact, the code in class PCRRegulator does take care of the PCR value looping back to zero. But there is a bug when the PCR reaches its initial value again, after returning to zero once. This is why the problem appears exactly after 26.5 hours, a complete round, and not when the PCR loops back to zero, somewhere between 0 and 26.5 hours.
Thank you for having detected and reported the problem. I will fix this bug. Sorry for the inconvenience.

Hi @mlaurendeau
The bug has been fixed in commit 9e765f83319738a7aac2641ff932f2e943e27372. I haven't tested it over 26.5 hours however. Could you please confirm if this is correct for you?

Version 3.18 has been released. Please open a new issue in case of problem with it.

Hi @lelegard
Sorry for not answering earlier, I had a vacation. I launched a test before my vacation. The issue is no more happening. Thanks for the fix!


#persisted? should not call the database

I'm working on a Neo4j adapter for rails_admin and one thing that I just ran across is that it does a lot of calls to #persisted?.  In neo4j this causes a lot of calls to the database.  I think that the difference comes down to the #destroyed? method.  In ActiveRecord this is just a check on the instance variable to see if it's been set as destroyed.  In neo4j it also checks (!new_record? && !exist?) and it's the #exist? that makes the call to the DB.  I'm find with two methods, but we should sort this out.  Curious for all opinions, but particularly @subvertallchris

I always use the presence of "_persisted_obj" to do a quick check and
reserve "persisted?" for those times that I want to be SURE a node still
exists in the database, which is... basically never. I'm totally fine with
changing it, since nobody really seems to expect its current behavior.
On Sunday, July 5, 2015, Brian Underwood<EMAIL_ADDRESS>wrote:

I'm working on a Neo4j adapter for rails_admin and one thing that I just
ran across is that it does a lot of calls to #persisted?. In neo4j this
causes a lot of calls to the database. I think that the difference comes
down to the #destroyed? method. In ActiveRecord this is just a check on
the instance variable to see if it's been set as destroyed. In neo4j it
also checks (!new_record? && !exist?) and it's the #exist? that makes the
call to the DB. I'm find with two methods, but we should sort this out.
Curious for all opinions, but particularly @subvertallchris
https://github.com/subvertallchris
—
Reply to this email directly or view it on GitHub
https://github.com/neo4jrb/neo4j/issues/857.

Good to know, thanks ;)  Since it's an API change I would think it would need to at least be version 5.1, but maybe it should have to wait until 6.0 technically?

Let's just put it in 5.1. It's not a breaking change and I can't see anyone
complaining about it.
On Monday, July 6, 2015, Brian Underwood<EMAIL_ADDRESS>wrote:

Good to know, thanks ;) Since it's an API change I would think it would
need to at least be version 5.1, but maybe it should have to wait until 6.0
technically?
—
Reply to this email directly or view it on GitHub
https://github.com/neo4jrb/neo4j/issues/857#issuecomment-118884803.

I could definitely see it as a breaking change since people might be depending on the behavior.  One thing that I thought of is to have a temporary configuration option to change the behavior in earlier versions and then change that later.  We could also have a time bomb-style check so that when it processes the configuration option it fails if (for example) the version is >= '6.0.0' so that we know to refactor it back

Believe it or not...
# from a project at work
..........*....................................................................................F.......................

Failure/Error: expect(rando_user.destroyed?).to be_truthy
       expected: truthy value
            got: false

So I guess it might be a breaking change after all! ;-)

I put this in as described, by the way.  It's possible to use the _active_record_destroyed_behavior configuration variable to get the ActiveRecord behavior today.  That should raise an error, though and fail the tests when we up the version of the gem to 6.0 so that we know to remove the check.


Installation via Poetry v1.4.0 fails

Description
The 1.4.0 release of Poetry introduced a controversial breaking change that changes the installer package Poetry uses. The new installer flat-out rejects installation of certain wheels with malformed metadata in RECORD. One of these wheels is pydata_sphinx_theme. This is the output from poetry install -E all:
  ["In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/__init__.py didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/assets/scripts/index.js didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/assets/styles/_admonitions.scss didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/assets/styles/_api.scss didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/assets/styles/_base.scss didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/assets/styles/_markdown.scss didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/assets/styles/_navbar.scss didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/assets/styles/_versionmodified.scss didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/assets/styles/index.scss didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/bootstrap_html_translator.py didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/_templates/copyright.html didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/_templates/edit-this-page.html didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/_templates/last-updated.html didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/_templates/navbar-icon-links.html didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/_templates/navbar-logo.html didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/_templates/navbar-nav.html didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/_templates/page-toc.html didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/_templates/prev-next.html didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/_templates/sidebar-ethical-ads.html didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/_templates/sidebar-nav-bs.html didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/_templates/sphinx-version.html didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/_templates/version-switcher.html didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/docs-navbar.html didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/docs-sidebar.html didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/footer.html didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/icon-links.html didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/layout.html didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/search-field.html didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/static/.gitignore didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/static/scripts/pydata-sphinx-theme.js didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/static/styles/pydata-sphinx-theme.css didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/static/styles/theme.css didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/static/vendor/fontawesome/5.13.0/LICENSE.txt didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/static/vendor/fontawesome/5.13.0/css/all.min.css didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/static/vendor/fontawesome/5.13.0/webfonts/fa-brands-400.eot didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/static/vendor/fontawesome/5.13.0/webfonts/fa-brands-400.svg didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/static/vendor/fontawesome/5.13.0/webfonts/fa-brands-400.ttf didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/static/vendor/fontawesome/5.13.0/webfonts/fa-brands-400.woff didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/static/vendor/fontawesome/5.13.0/webfonts/fa-brands-400.woff2 didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/static/vendor/fontawesome/5.13.0/webfonts/fa-regular-400.eot didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/static/vendor/fontawesome/5.13.0/webfonts/fa-regular-400.svg didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/static/vendor/fontawesome/5.13.0/webfonts/fa-regular-400.ttf didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/static/vendor/fontawesome/5.13.0/webfonts/fa-regular-400.woff didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/static/vendor/fontawesome/5.13.0/webfonts/fa-regular-400.woff2 didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/static/vendor/fontawesome/5.13.0/webfonts/fa-solid-900.eot didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/static/vendor/fontawesome/5.13.0/webfonts/fa-solid-900.svg didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/static/vendor/fontawesome/5.13.0/webfonts/fa-solid-900.ttf didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/static/vendor/fontawesome/5.13.0/webfonts/fa-solid-900.woff didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/static/vendor/fontawesome/5.13.0/webfonts/fa-solid-900.woff2 didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/static/webpack-macros.html didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme/theme/pydata_sphinx_theme/theme.conf didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme-0.8.1.dist-info/LICENSE didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme-0.8.1.dist-info/METADATA didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme-0.8.1.dist-info/WHEEL didn't match RECORD", "In /home/dlq/.cache/pypoetry/artifacts/5e/51/c0/f6facc1d51b1bbc97a5abce1b4e7219c054be65cbd3d6a2a39f0e20d4a/pydata_sphinx_theme-0.8.1-py3-none-any.whl, hash / size of pydata_sphinx_theme-0.8.1.dist-info/entry_points.txt didn't match RECORD"]

  at /local~/.local/share/pypoetry/venv/lib/python3.9/site-packages/installer/sources.py:289 in validate_record
      285│                         f"In {self._zipfile.filename}, hash / size of {item.filename} didn't match RECORD"
      286│                     )
      287│
      288│         if issues:
    → 289│             raise _WheelFileValidationError(issues)
      290│
      291│     def get_contents(self) -> Iterator[WheelContentElement]:
      292│         """Sequential access to all contents of the wheel (including dist-info files).
      293│

Steps to reproduce
First, install the latest version of Poetry. Then, in your terminal:
poetry new poetry-demo
cd poetry-demo
poetry add pydata_sphinx_theme # <= verify this fails

Did some digging. Poetry 1.4.0 now defaults to using the installer installer instead of pip. The breaking change was added in https://github.com/pypa/installer/pull/147, which first included in a release of 0.7.0, 2 days ago.

The next release will hopefully include a CLI for verifying wheel RECORDs: https://github.com/pypa/installer/pull/161#pullrequestreview-1347621353

It looks like the default install procedure doesn't even validate the record; python -m installer <path-to-wheel> passes just fine locally, and I don't see WheelFile#validate_record() (failing method in question) being called anywhere else besides tests. This bug is basically exclusive to Poetry builds because of they call WheelFile#validate_record() explicitly as a pre-install step: https://github.com/python-poetry/poetry/pull/7671/files#diff-6e4b362f2ca86526a481a87d23c626c3bc2e06998bac8c35c71ae4988f9fe3ef

Finally managed to reproduce this bug locally. First, build the wheel locally from the repo root:
pip install sphinx_theme_builder
stb package

Then, run this script from the repo root:
import os
from installer.sources import WheelFile

WHEEL_RELPATH = 'dist/pydata_sphinx_theme-0.13.2.dev0-py3-none-any.whl'

wheel_abspath = os.path.join(os.path.dirname(__file__), WHEEL_RELPATH)

with WheelFile.open(wheel_abspath) as source:
    source.validate_record()

Cut a PR upstream to fix this: https://github.com/pradyunsg/sphinx-theme-builder/pull/39

despite the setting installer.modern-installation: false that we read in the poetry issues that is a workaround.

Interesting, for me this workaround was successful (in a private repo). Are you sure the setting was successfully propagated through the snok/install-poetry action?

This should be fixed in 1.3.2. 🎉 I will verify this later when I have time.

Oh wait, 1.3.2 isn't published on PyPi yet 😂

0.13.2 is out, is it solving this issue ?

@12rambau Yes, I have locally verified that this issue is fixed in 1.3.2. 🎉
Was a little too quick on the draw earlier 😅


a

Overview
Brief description of what this PR does, and why it is needed.
Demo
Optional. Screenshots, curl examples, etc.
Notes
Optional. Ancillary topics, caveats, alternative strategies that didn't work out, anything else.
Testing Instructions

How to test this PR
Prefer bulleted description
Start after checking out this branch
Include any setup required, such as bundling scripts, restarting services, etc.
Include test case, and expected output

Why are you renaming the file? This change does not conform to GitHub's policy file names https://docs.github.com/en/code-security/getting-started/adding-a-security-policy-to-your-repository


Questions about CPU usage and event multiplexing

Hi, we are considering using this library in a project and would like to clarify some things first

Our first choice would be to use a single thread as shown in this example, but I have concers about the CPU usage: this strategy seems to be based on polling both the asio event loop ( io_context ) and the grpc completion queue with with a zero timeout to prevent the call to AsyncNext from blocking. If that is the case, the loop is likely to consume 100% of one CPU core, which might be prohibitive to our customers. On the other hand if it uses a small timeout to avoid too high CPU usage, it might add latency since both event loops cannot run at the same time. Is this analysis correct?

Can I perform multiple concurrent calls to RPC::request (as shown here) on the same context or should I wait the completion of last one to perform a new request?

Thanks.

Hi, thanks for considering this library :).

Correct, without timeout this would consume 100% CPU. In agrpc::run I therefore use a backoff policy going from the default of 250ms down to 0ms depending on most recent activity on either context. If a context has just processed them work in their poll call -> reduce timeout to 0ms, if not -> gradually increase back to 250ms. I am personally not a big fan of this API either, but users seem to like the convenience of running io_context and GrpcContext on the same thread (and thereby avoiding any need for synchronization). I feel that it needs more real-world testing though. I have some performance numbers for unary rpcs in the [README].(https://github.com/Tradias/asio-grpc#performance) (look for cpp_asio_grpc_io_context_coro).
Yes you can, otherwise it wouldn't be an asynchronous API, right? 😁

Thanks

Yes you can, otherwise it wouldn't be an asynchronous API, right?

In some low-level libraries like Boost.Beast the user is responsible for synchronizing reads and writes.

In some low-level libraries like Boost.Beast the user is responsible for synchronizing reads and writes.

For a single streaming RPC you can only have one outstanding read/write at a time. But of course, you can have multiple clients, each doing their RPC and won't need to sync reads/writes between all clients.


NodeMCU v2 Amica

Hello Martin, I don't know why but this project is not working at this board (https://www.seeedstudio.com/NodeMCU-v2-Lua-based-ESP8266-development-kit-p-2415.html). The LED from the ESP-12 keeps blinking all the time and I can't even debug it because the serial monitor stays busy all the time. Also, the AP MyAP does never show up.

 On both NodeMCUs I tried flashing from your firmware, because I don't know how to build from scratch. Maybe if you could explain how to build the binaries step by step on Youtube using Windows/Linux, it would be really helpful. Thanks a lot! I hope I've been helping you a lot lately.

Obviously, your board is rebooting all the time without really starting the repeater firmware at all. According to http://www.esp8266.com/viewtopic.php?p=2096#p2112 "rst cause:2" means reset pin is pulled. Are you pressing the button?
Just tested it: for me the lastest firmware downloads, boots, and works fine on a Wemos D1 Mini. Don't have a NodeMCU at hand, but if should be fairly compatible to the Wemos.
The download procedure on Linux is just the following:

Make sure you have the esptool.py on your PATH
Stop any serial terminal program that might use the serial port
connect the Wemos via USB to the Computer
"cd" to the directory where you have the firmware binaries
sudo esptool.py --port /dev/ttyUSB0 write_flash 0x00000 0x00000.bin 0x10000 0x10000.bin
(no button or any electical signal on any GPIO port required)
Wemos starts directly after the download finished - just to be sure, press reset once
connect to the serial port via a terminal program. I use "minicom -D /dev/ttyUSB0 -b 115200"
You should see some debug output and the serial console...

I am not pressing the reset button. Are you connecting the TX/RX of Wemos
after installing the firmware or just using 5V/3.3V VIN? My device is a
Wemos D1 Mini v1. Is your Wemos v1 or v2? Because some pins change from one
version to another.
On Jan 14, 2017 9:51 AM, "martin-ger"<EMAIL_ADDRESS>wrote:

Obviously, your board is rebooting all the time without really starting
the repeater firmware at all. According to http://www.esp8266.com/
viewtopic.php?p=2096#p2112 "rst cause:2" means reset pin is pulled. Are
you pressing the button?
Just tested it: for me the lastest firmware downloads, boots, and works
fine on a Wemos D1 Mini. Don't have a NodeMCU at hand, but if should be
fairly compatible to the Wemos.
The download procedure on Linux is just the following:

Make sure you have the esptool.py on your PATH
Stop any serial terminal program that might use the serial port
connect the Wemos via USB to the Computer
"cd" to the directory where you have the firmware binaries
sudo esptool.py --port /dev/ttyUSB0 write_flash 0x00000 0x00000.bin
0x10000 0x10000.bin
(no button or any electical signal on any GPIO port required)
Wemos starts directly after the download finished - just to be
sure, press reset once
connect to the serial port via a terminal program. I use "minicom
-D /dev/ttyUSB0 -b 115200"
You should see some debug output and the serial console...

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/martin-ger/esp_wifi_repeater/issues/7#issuecomment-272622278,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAZLEmBXFgPIeita9J0z0_92J8QulWJWks5rSMTDgaJpZM4LjkkJ
.

I meant that I don't know how to build the binaries from the ESP SDK and your other library. So sorry because I was so tired that I forgot to include the params "-fs 32m -ff 80m" to esptool. Will test again as soon as possible with Amica. Thanks!

This is my Wemos : http://www.ebay.de/itm/272271662681 I guess it is compatible to V2.
I connect nothing but USB for downloading and testing. USB provides power supply and serial link.

Okay, thank you very much. It's working on NodeMCU v2 Amica with the command that you sent to me:
esptool.py --port /dev/ttyUSB0 write_flash -fs 32m -ff 80m 0x00000 0x00000.bin 0x10000 0x10000.bin
Thank you very much!

I'm sending this message right now with the help from your outstanding project, which is working with a NodeMCU Amica v2 which is connected to an ESP-01, which is connected to a Linksys Repeater, which is connected to a Linksys Main AP, which is connected to a D-Link Modem, which is connected to the WWW, which has its own creator Sir Tim Berners-Lee.

That sounds great - obviously, it works... :-)

Please help me out. I have two node mcu and 3 ESP01. I was able to upload and run the firmware successfully in one of the nodemcu but the other one shows error when connected to COM port shows chksum errors. Also the firmware fails to upload on all 3 ESP-01. I am posting the screenshot for NodeMCU.


Ss/marathon networking update

Description
https://jira.mesosphere.com/browse/DCOS-15434
Urgency

[X] Blocker
[ ] High
[ ] Medium

Requirements

Test all commands and procedures.
Build content locally and test for formatting/links.
Add redirects to dcos-website/redirect-files.
Change all affected versions (e.g. 1.7, 1.8, 1.9, and 1.10).
See the contribution guidelines.

This PR updates code snippets for new marathon networking configuration and updates the Marathon API docs.


Get new & noteworth + popular node IDs from config

Purpose
Tests break if you set POPULAR_LINKS_NODE and/or NEW_AND_NOTEWORTHY_LINKS_NODE locally
Summary of Changes
Use the values from the ember config, which has the proper defaults in it
Side Effects
N/A
Feature Flags
N/A
QA Notes
No QA needed
Ticket
None
Reviewer Checklist

[ ] meets requirements
[ ] easy to understand
[ ] DRY
[ ] testable and includes test(s)
[ ] changes described in CHANGELOG.md

Pull Request Test Coverage Report for Build 1448

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 61.355%

Totals

Change from base Build 1446:
0.0%

Covered Lines:
2221

Relevant Lines:
3432

💛  - Coveralls


Automated Package Upgrade

:tada: This PR is included in version 25.3.239 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add support for  elements

This pull-request adds two additional selectors to consider <summary> elements.

This considers the first summary element directly within a details element focusable, provided it doesn’t have a negative tabindex attribute.

details > summary:first-of-type:not([tabindex^="-"])

This consider the details element focusable provided it does not have a summary element and does not have a negative tabindex attribute.

details:not(:has(> summary)):not([tabindex^="-"])

Find more information about this in the HTML specifications.

@mxmason for review. :)


Reference to figure.

Description
Add reference (DOI) to figure in docs.
Status

[x] Ready to go

Codecov Report

Merging #66 (797641f) into main (298c244) will not change coverage.
The diff coverage is n/a.


fix typo in gatekeeper_version variable

s/gatekeeeper/gatekeeper

Hello @tariq1890,
Can you please sign the OCA agreement so we can merge your PR?
Thanks.

It also needs to be rebased. Might be easier to recreate the PR.

Discussed separately and will close - thanks @tariq1890!


Add the option to continue a paused stream

Hitting a key while streaming pauses the stream.  There should be a way to resume.

v1.2.13


Reference error _ is not defined.

Hello guys. I installed loadash and d3 libraries. Below is the dependenies copied from my package.json file.
 "dependencies": {
    "d3-dtree": "^2.4.1",
    "d3": "^4.5.0",
    "lodash": "^4.0.0"
  }

Can you tell me what went wrong with my installation ?

same issue here, did you make it work @mohankoppuravuri ?

same issue here, did you make it work @mohankoppuravuri ?

Hi , I have downloaded d3-tree package instead of using npm. I have loaded d3 and loadash as npm package. In my downloaded dTree.js , I have added :
import _ from "lodash"; import * as d3 from "d3";
Then everything worked. Note that d3 should be older version , if no it gives error, mine is "d3": "^5.16.0".


don't include both QuickReplies.html and quickReplies.html

See https://github.com/dart-lang/pub/issues/2072
In general, I would discourage checking the doc/api/ folder into source control, and I would also discourage you from having it in your folder when publishing as it gets included in the package on pub..
The problem in this case is probably (just guessing), that you renamed quickReplies to QuickReplies (or maybe you have two types with same name, only one is lowercase) and suddenly you have two files with the same name (except one is lowercase, the other is uppercase)... Such packages won't work on Windows, since the filesystem is case insensitive (case preserving).

Note: if you think you actually generated documentation producing both QuickReplies.html and quickReplies.html, then please make a small test-case that reproduces this and file an issue with: https://github.com/dart-lang/dartdoc

See https://github.com/dart-lang/dartdoc/issues/1196

Greetings, I have already made the update. I have deleted the doc folder and fixed some problems with the lower case, so that the same problem does not occur. =)

Cool, thanks :)


Twilio configuration done and app can call and hang up

Please review

 Need to configure Twilio

@kelajatu Please merge


[FEATURE] IMPLEMENT SIGN UP/ SIGN IN USING GOOGLE.

Problem
The project currently lacks a "Sign up with Google" feature. This limits the ease of user onboarding, as many users prefer signing up with their Google accounts for faster and more secure access, rather than manually creating a new account.
Solution
I want to work on adding a "Sign up with Google" feature to the application. This would integrate Google's OAuth 2.0 authentication, allowing users to register or log in with their Google accounts, streamlining the registration process and improving user experience.

We don't want to take on any authentication features at this moment.


Why not work on localhost

Hello everyone,
My app is: vue 3.3.4, flowbite 1.8.1, tailwindcss 3.3.3, vite 4.4.5, typescript 5.0.2
In my app, flowbite only work on http://<IP_ADDRESS>:8080. It not work on http://localhost:8080.
It seems that Javascript not work on localhost.
For example, with dropdown:

http://<IP_ADDRESS>:8080: when click button, the dropdown is shown is normal
http://localhost:8080: when click button, nothing happen

I don't know what the problem is. This is my codes:
postcss.config.js:
module.exports = {
  plugins: {
    tailwindcss: {},
    autoprefixer: {},
  },
};

tailwind.config.js
/** @type {import('tailwindcss').Config} */
export default {
  content: [
    './index.html',
    './src/**/*.{vue,js,ts,jsx,tsx}',
    './node_modules/flowbite/**/*.js',
  ],
  theme: {
    extend: {},
  },
  plugins: [require('flowbite/plugin')],
};

I also attached the video show my problem
https://github.com/themesberg/flowbite/assets/70369658/1ad01cf5-3977-48ce-85ec-61921d0fb23b

If I had to guess, I would say it has something to with either your browsers' security settings or system settings.
Maybe you can provide more information on how you start the project and on what system it is running.

Seems to be a local configuration error - given that Tailwind CSS and Flowbite is installed correctly then the project should work and CSS and the UI components should be functional.


Release v1.0.7 appears to be tagged incorrectly

Hi, the tag for release 1.0.7 is a bit inconsistent compared to previous releases.
It's tagged as 1.07 which both drops the v and drops the minor/patch separator.
This isn't a blocking issue as using "1.07" in go mod works fine, but it did catch me out when trying to upgrade as the release is labelled v1.0.7

I couldn't figure out how to update it, so I just made a new release that goes with the previous convention. Thanks for catching that!


Design evolution for FancyZones

Hello folks !
I've installed the Power Toys preview and am particularly excited about them.
My suggestion is specifically related to FancyZones and their potential use. First of all, as of now (09/06/2019) the tool only supports one screen use which issue I suspect you are going to solve in later versions.
This, moreover, is not my main concern. Due to the fact that I mostly use my box professionally, I was looking for a way in the past, to open, at start up, a specific number of windows in a specific layout per desktop (I heavily use the rather handy multi virtual desktops feature) in a shared two monitors physical setup, for which ever activity I am involved at any given moment. The only way one can achieve something like that, is by simply leaving his/her box on sleep mode so that he/she doesn't loose the preferable tools arrangement he/she already had been working with, or maybe use a Powershell script to this effect.
For example for an e-learning session I need several tools/windows open at a specific location of choice on my desktop which is shared between my two screens such as a browser, a VS-Code and a CLI window on my left monitor and some others on my right etc.
In short, I think that there is a clear need for a hierarchical design, which would implement a layout per virtual desktop and (physical) screen ... If at the same time, you enrich the "custom layout" feature with the option for a user to define which specific apps/windows would want to (optionally) open as defaults : that would be perfect ladies and gents !
In essence the scenario that am describing means that one could set up his/hers working environment of choice : in a click of a button, or now that am thinking about it, maybe without even one !
Maybe a top level "layout" object, should be included in the design, to accommodate the rest of the hierarchy ie
When I open my PC, I want three (3) virtual desktops (always in a shared two monitor setup), each one of which would have it's own predefined layout and would open specific default apps/windows at specific location on and per screen ...

@PAvramidis i'm going to reword your ask here, is this correct?  I'm reading this and it sounds like FZ is a part of it but not FZ itself.
As an end user, i want a "setup my computer".

on launch / whenever i can execute the command
It will setup virtual desktops in correct order
It will rename my virtual desktops correctly.
it will launch applications
it will launch windows
it will move applications to appropriate FZ / Window / Virtual Desktop
As an end user, i'm ok with the load time impact this will take knowing that some applications will take longer and when chained with other apps, depending on HW, it can become a bit lengthy (example loading 4 visual studios, photoshop, teams, and others at launch)

if what i stated above is correct, this is 🔥🔥🔥. cool idea.

ping @PAvramidis

closing due to @PAvramidis not responding


Ensure NSLock/NSThread don't have stored properties with CoreFoundation types

This PR attempts to resolve the NSLock/NSThread subclassing issues by ensuring that their stored properties use types from the Glibc module (which is a public import) instead of CoreFoundation (which is @_implementationOnly imported)

@swift-ci please smoke test

@swift-ci please build toolchain Linux platform

@swift-ci please test Linux platform

@swift-ci please build toolchain Linux platform

@swift-ci please test Windows platform

@swift-ci please test

@swift-ci please test Windows platform


Duplicate service name checks should be case insensitive.

Rancher Version: v1.0.0-rc2
Steps to Reproduce:
Create a service with name - test1 and activate it.
Create a service with name - TEST1 and activate it.
resolution on  for test1/TEST1 , resolves containers from both the service - "test1" and "TEST".
resolution for containers under test1/TEST1 to returns the same ip address.

Tested with latest build from master:
Duplicate service name checks is now case insensitive.
Create a service with name - test1 and activate it.
Create a service with name - TEST1.
Service creation fails with error - "Validation failed in API: name is not unique"


Converted gguf file is removed if '-sq' option is set

Describe the bug
When using ilab convert -sq to skip quantization, no gguf is generated. Reason is that it is removed by this code.
    # quantize to 4-bit GGUF (optional)
    if not skip_quantize:
        gguf_model_dir = f"{model_dir_fused_pt}/{model_name}.gguf"
        gguf_model_q_dir = f"{model_dir_fused_pt}/{model_name}-Q4_K_M.gguf"
        run_quantize(gguf_model_dir, gguf_model_q_dir, "Q4_K_M")

    ctx.obj.logger.info(f"deleting {model_dir_fused_pt}/{model_name}.gguf...")
    os.remove(os.path.join(model_dir_fused_pt, f"{model_name}.gguf"))

To Reproduce
Steps to reproduce the behavior:

Use ilab train to train a model
Use ilab convert -sq to convert.

Expected behavior

There is a non-quantized gguf file generated.
Screenshots

Device Info (please complete the following information):

Hardware Specs: Apple M1 Pro Chip
OS Version: Mac OS 14.5
Python Version: Python 3.11.4
InstructLab Version: ilab, version 0.15.1

Additional context

@shenghu since you pointed out the portion of the code responsible for the behavior, would like to send a PR to address this? Thanks!

@leseb OK, I'll submit one.

@shenghu are you still planning on work on this?

Related to #2133


Is it possible to body tracking from other device?

Hello.
I wonder if I can process body tracking from mkv which recorded by common camera(not azure kinect) or pre-made ply(point cloud).
Thank you for reading.

I suspect you will have challenges

The depth data will need to be somehow transformed from your other camera into a format that is the same as Kinect Azure: pixels, pov, focal length, etc. The neural net and supporting code was trained for specific hardware.
There might also be licensing issues. I recommend you read your license for the Body Tracking SDK.

If it is legally allowed, sounds like a good project for you to try. Code it and tell us your experience.


AI gpt

https://www.youtube.com/watch?v=u8-sYdnlEa4

https://dw9ne0o7jcasn.cloudfront.net/AWSMachineLearning/AWSCertifiedMLSlides.pdf

https://www.databricks.com/sites/default/files/2023-01/mlops_for_dummies_databricks_special_edition.pdf

https://huyenchip.com/2023/04/11/llm-engineering.html


Bump websocket package to 1.0.31

This PR bumps the websocket package in protoo-server to  1.0.31 so that it includes Fix infinite loop in error handling.
Also adds package-lock to control installed dependency versions.

I will update the version but I don't want package-lock.json in the repo. That's just for apps, not for libraries.
Thanks for reporting, will release a new version with updated versions.

Done in 4.0.4.


readme: update installation instructions for Arch Linux

dra has been moved to the community repository: https://archlinux.org/packages/community/x86_64/dra/

Hi @orhun!
This is very cool! Thank you for you work 🔝
Out of curiosity how does a package get promoted inside the community packages?

Hi @orhun!
This is very cool! Thank you for you work top

Hey, nps! 🐻

Out of curiosity how does a package get promoted inside the community packages?

If you're asking "when" as in "how" then I would say it is up to the maintainer to decide if they want to maintain it in the official repositories (as a binary package) and make it easily available for a wider user base. I usually move packages to community when I see that they are mature enough and might be beneficial for the users.
If you're asking "how", then there is a technical packager wiki page for Arch Linux maintainers which goes into detail.

Yes, I actually meant "when" 😅.
But the "how" part was also nice to understand how arch packaging works 🚀


Both with and without -m, I get an error from onyo (source code from 2022-08-, but no crashes nor commits:
I edited one of my templates, to have something to commit.
(onyo) aghisla@juvuzela in ~/source/onyo-testrepo on git:master!
❱ onyo git commit                                                           1 !
ERROR:onyo:
Onyo expects a clean onyo working tree before running commands. Please commit or .gitignore all changes and check the syntax of asset files.

The Onyo working tree is not clean.
Changes not staged for commit:
	 .onyo/templates/laptop.template
Please commit all changes or add new files to .gitignore
(onyo) aghisla@juvuzela in ~/source/onyo-testrepo on git:master!
❱ onyo git commit -m"Commented the vendor model type keys in laptop template, duplicates of the asset creation questions."
ERROR:onyo:
Onyo expects a clean onyo working tree before running commands. Please commit or .gitignore all changes and check the syntax of asset files.

The Onyo working tree is not clean.
Changes not staged for commit:
	 .onyo/templates/laptop.template
Please commit all changes or add new files to .gitignore

But I seem to get the same error with onyo git status and a few more commands. What should I check next?

You have found another bug in onyo git, that must have been introduced after Tobias filed this bug.
Onyo runs some checks before executing commands (similar to onyo fsck). One of these checks is ensuring that the git repo is clean.
You have created the template file, and thus there is an untracked file.
It seems this check is also done for onyo git, which somewhat defeats the purpose of the command.

True. I wonder if it should be just simply removed, or if there would be value to run the checks in the end to get output describing the situation after the onyo git commands.

Closing as wont-fix with the merging of #201


Update DG for StatusCommand

Codecov Report
Base: 71.76% // Head: 71.76% // No change to project coverage :thumbsup:

Coverage data is based on head (b30e705) compared to base (90cd1ea).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##             master      #88   +/-   ##
=========================================
  Coverage     71.76%   71.76%
  Complexity      479      479
=========================================
  Files            83       83
  Lines          1544     1544
  Branches        168      168
=========================================
  Hits           1108     1108
  Misses          384      384
  Partials         52       52

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Great work creating the activity diagram and sequence diagram for StatusCommand. UML has been implemented here nicely.


Display message box for all errors it bit + Its best practices

How can I display error message to end user for all errors I get from server responses?
Is there any best practice for this?
Thanks in advance.

You can achieve this by extending Logger class.

Relation between this issue & Enhanced Rad Grid Row commit was made by a mistake


Export more types to enhance TypeScript support

While using PptxGenJS with TypeScript, I wanted to do something like this:
function addChartToSlide(slide: Slide, chartData: ChartData): void {
  ...
}

With the existing type definitions, type inference works as expected but the Slide type (among others) are not exported and thus are not able to be referenced from client code, making it more difficult to write correct type definitions.
This PR exports all the types defined within the PptxGenJS namespace, while retaining the current behavior (export the PptxGenJS class as the default export).

Great work and thanks for the contribution @ntietz !

Thanks for creating and maintaining this and being responsive!


Patreon embedded video not found anymore

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm reporting that yt-dlp is broken on a supported site
[X] I've verified that I have updated yt-dlp to nightly or master (update instructions)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched known issues and the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[X] I've read about sharing account credentials and I'm willing to share it if required

Region
Worldwide
Provide a description that is worded well enough to be understood
Today it seems that Patreon changed their embedding or embedded videos. The program fails on all embedded videos and creators I got access to. So it looks like a site change.
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
[debug] Command-line config: ['-vU', '--cookies-from-browser', 'firefox', 'https://www.patreon.com/posts/fairy-tail-30-85954582']
Extracting cookies from firefox
[debug] Extracting cookies from: "C:\Users\Black\AppData\Roaming\Mozilla\Firefox\Profiles\i7jxqj1d.default-release-1663947917890\cookies.sqlite"
Extracted 2322 cookies from firefox
[debug] Encodings: locale cp932, fs utf-8, pref cp932, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version<EMAIL_ADDRESS>from yt-dlp/yt-dlp-nightly-builds [95e82347b] (win_exe)
[debug] Python 3.8.10 (CPython AMD64 64bit) - Windows-10-10.0.19045-SP0 (OpenSSL 1.1.1k  25 Mar 2021)
[debug] exe versions: ffmpeg N-109468-gd39b34123d-20221230 (setts), ffprobe N-109468-gd39b34123d-20221230
[debug] Optional libraries: Cryptodome-3.19.1, brotli-1.1.0, certifi-2023.11.17, mutagen-1.47.0, requests-2.31.0, sqlite3-3.35.5, urllib3-2.1.0, websockets-12.0
[debug] Proxy map: {}
[debug] Request Handlers: urllib, requests, websockets
[debug] Loaded 1798 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp-nightly-builds/releases/latest
Latest version<EMAIL_ADDRESS>from yt-dlp/yt-dlp-nightly-builds
yt-dlp is up to date<EMAIL_ADDRESS>from yt-dlp/yt-dlp-nightly-builds)
[Patreon] Extracting URL: https://www.patreon.com/posts/fairy-tail-30-85954582
[Patreon] 85954582: Downloading API JSON
ERROR: [Patreon] 85954582: No supported media found in this post
  File "yt_dlp\extractor\common.py", line 718, in extract
  File "yt_dlp\extractor\patreon.py", line 289, in _real_extract
  File "yt_dlp\extractor\common.py", line 1196, in raise_no_formats

Can be tested with with free video post, no account needed: https://www.patreon.com/posts/happy-holidays-94714289
It throws the same messages:
[debug] Command-line config: ['-vU', '--cookies-from-browser', 'firefox', 'https://www.patreon.com/posts/happy-holidays-94714289'] Extracting cookies from firefox [debug] Extracting cookies from: "C:\Users\Black\AppData\Roaming\Mozilla\Firefox\Profiles\i7jxqj1d.default-release-1663947917890\cookies.sqlite" Extracted 2328 cookies from firefox [debug] Encodings: locale cp932, fs utf-8, pref cp932, out utf-8, error utf-8, screen utf-8 [debug] yt-dlp version<EMAIL_ADDRESS>from yt-dlp/yt-dlp-nightly-builds [95e82347b] (win_exe) [debug] Python 3.8.10 (CPython AMD64 64bit) - Windows-10-10.0.19045-SP0 (OpenSSL 1.1.1k  25 Mar 2021) [debug] exe versions: ffmpeg N-109468-gd39b34123d-20221230 (setts), ffprobe N-109468-gd39b34123d-20221230 [debug] Optional libraries: Cryptodome-3.19.1, brotli-1.1.0, certifi-2023.11.17, mutagen-1.47.0, requests-2.31.0, sqlite3-3.35.5, urllib3-2.1.0, websockets-12.0 [debug] Proxy map: {} [debug] Request Handlers: urllib, requests, websockets [debug] Loaded 1798 extractors [debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp-nightly-builds/releases/latest Latest version<EMAIL_ADDRESS>from yt-dlp/yt-dlp-nightly-builds yt-dlp is up to date<EMAIL_ADDRESS>from yt-dlp/yt-dlp-nightly-builds) [Patreon] Extracting URL: https://www.patreon.com/posts/happy-holidays-94714289 [Patreon] 94714289: Downloading API JSON ERROR: [Patreon] 94714289: No supported media found in this post   File "yt_dlp\extractor\common.py", line 718, in extract   File "yt_dlp\extractor\patreon.py", line 289, in _real_extract   File "yt_dlp\extractor\common.py", line 1196, in raise_no_formats

as noted in the linked gallery-dl issue, this may be something that's only rolled out to certain regions, as I cannot reproduce the error

@bashonly good catch! It works fine without cookies. But need them to get access to private tiers sadly.

Hi,
I can reproduce this as of today (2024-01-12). For me, everything worked fine yesterday, and possibly even earlier today.
So it seems like it's a new video format for content behind a paywall on Patreon, possibly being rolled out in stages for different pages/creators.
Also, the same content I could download fine yesterday, I can no longer re-download, resulting in a "No supported media found in this post" error message. So the issue is not only for new content, but also affects old content, once the change has hit a certain Patreon creator (presumably).
Please let me know if I can add anything useful to the ticket :)

Hi,
I can reproduce this today (2024-01-13). The same command, with cookies was working okay aweek ago.
So, something's has changed on Patreon
I'm a paid user ..

I just manually compiled PR #8993 and it fixes the problem for me.
Anyone else with that problem, you can try his fork until the PR is merged. But you gotta compile it yourself.
Thank you for all your hard work :)

I managed to test it out with his fork.

Some videos are working now. I can manage to run it
Some files, I kept getting despite passing the params - 'cookies-from-browser': 'firefox'
2.1 I am also looking at the same page in patreon in FF and it looks fine

any clue?

I managed to test it out with his fork.
1. Some videos are working now. I can manage to run it

2. Some files, I kept getting despite passing the params - 'cookies-from-browser': 'firefox'
   2.1 I am also looking at the same page in patreon in FF and it looks fine
   ![image](https://private-user-images.githubusercontent.com/156088299/296554947-0fcf5cb6-62f0-439d-b934-09e6333a6aa5.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MDUyNDQxODMsIm5iZiI6MTcwNTI0Mzg4MywicGF0aCI6Ii8xNTYwODgyOTkvMjk2NTU0OTQ3LTBmY2Y1Y2I2LTYyZjAtNDM5ZC1iOTM0LTA5ZTYzMzNhNmFhNS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwMTE0JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDExNFQxNDUxMjNaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0yYjk1OGU1MmE3ZjdhYmQwY2JlY2M4MzBlOGUwOWIzY2E3NmRjMWQ2OGMxZTMwYzMzNzVkNDkzZDZhY2UyMGM3JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.vsioRu1VIjvuT-Da9ykn_usaGYZ15oDGo4VbpPR2Ii8)

any clue?

I assume you passed the command correctly? yt-dlp.exe --cookies-from-browser firefox "<URL>" <Other Params>
Maybe the PR did not fix all problems.

Yup, I'm pretty sure - I didn't compile it to a .exe. Instead,

I coded a simple .py that calls the actual .py and pass in the params
Went to-and-fro testing 2 videos from the paid channel
One works and the other won't - while both are loaded in FF in my laptop.

Pretty strange...
I'm not really competent in python programming yet to help on this >.>
It's the part that's calling www.patreon.com/api that returns a response that current_viewer_can_view:False (sorry if wrong URL, I'm not on that laptop now)

@tp2024sc I can upload my compiled version and put the link in a gist on my account. Just keep a look out for it and try that. Then we can see if your problem stemms from using the py directly or if its a problem with the PR. Maybe this helps the others?
Just drop a comment on the gist once you downloaded it, so I can get rid of it again. I don't know If I get in trouble in this repo for sharing builds.
My gists: https://gist.github.com/Ultraporing

Hi again,
Good news! I managed to get it working with the PR's source

I managed to compile a .exe from the fork src as well. I can download the 2 videos from the compiled .exe
.\yt-dlp --cookies-from-browser firefox --verbose

After 2 hrs, I finally figured out another way of telling it to get the cookies from FF

ydl_opts = { 'cookiesfrombrowser' : ('firefox', None, None, None), 'verbose': True }
Tried with 2 videos from the paid channel and I could download them!
Happy as a puppy and now I can go to sleep in peace!
Cheers

I could've really done with that executable forked from the working pull. Can someone reupload or something?

+1 Would also really appreciate that

@seagull @klairvoyage It probably was not ok that i shared the link to it. so I doubt they let me share it again. And since Github does not have a way to direct message people its kinda tough. Maybe contact me via Twitter / X dm and i see if I can help you with it.
So the Issue won't get flooded with this kind of requests :).

@Ultraporing enable actions on your fork and use the release workflow (choose your PR branch and check "pre-release"). It will build on a github runner and publish a release on your fork, and you can link to it here without any sketchiness

And then we don't have to pay Elon to message you...

I did not know that Elon now wants money for this... Jesus the dude. I'm barely on Twitter so I didn't notice.
Gimme a sec I set up the Fork.

Here you go, it complains not finding the version but who cares. It works, I just tested it myself: https://github.com/Ultraporing/yt-dlp/releases/tag/2<IP_ADDRESS>815

Thanks Tobias, you've gone above and beyond.


Confused...where is the source code?

I went to this github but it seems like there are just a bunch of .md's and that's it.  Where's the code? (Where's the beef, also?)

Check out https://github.com/NationalSecurityAgency/ghidra/wiki/Frequently-asked-questions#where-is-the-complete-ghidra-source-code


chore: create Nuxt 3 issue-sdk.bug.yml as example

Create the ISSUE template in Nuxt 3 SDK module as example

This will be implemented via a sync with the JS SDK using this GH Action -> https://github.com/BetaHuhn/repo-file-sync-action


Abort PR #2506 by customer request

Motivation and context
Editing positions in AAM is returned by a request of one of our customers
How has this been tested?
Manual testing
Checklist

[x] I submit my changes into the develop branch
[ ] I have added description of my changes into CHANGELOG file
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues (read github docs)
[ ] I have increased versions of npm packages if it is necessary (cvat-canvas,
cvat-core, cvat-data and cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
[x] I have updated the license header for each file (see an example below)

# Copyright (C) 2020 Intel Corporation
#
# SPDX-License-Identifier: MIT

Coverage decreased (-0.02%) to 61.801% when pulling c0c90745872b7f713deb0de2af84d64fb3b9493d on bs/enabled_ability_change_positions_aam into 76ff7eff03a2f16a72f84e8bc9f1e4862b91e6bb on develop.


pwd

Expected behavior
Actual behavior
Information about the Issue
Steps to reproduce the behavior

...
...

No information provided or steps to replicate - Closing


The collision detection isn't reliable

Often the collision system doesn't work and it doesn't detect it or it only runs the code for one person rather than both

It's been a year and a half since this issue, so I'll just state the following: I won't fix any bugs where the physics engine is the one at fault and not GMMaker itself. Then again, this issue is 1.5 years old, so there's a chance that this was actually a GMMaker issue, and thus it might have been resolved by now. If the issue persists and you can prove that GMMaker is at fault, feel free to reopen this issue.


Added a readme section and updated the mediabot nuget package reference

@waboum,
Thanks for your contribution.
To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla.microsoft.com.
It will cover your contributions to all Microsoft-managed open source projects.
Thanks,
Microsoft Pull Request Bot

@waboum, thanks for signing the contribution license agreement. We will now validate the agreement and then the pull request.
Thanks, Microsoft Pull Request Bot

Squashing and merging