Frequency refills

Add frequency and refills support to medications and substances to align with qdm spec.
Pull requests into Bonnie require the following. Submitter and reviewer should :white_check_mark: when done. For items that are not-applicable, note it's not-applicable ("N/A") and :white_check_mark:.
Submitter:

[x] This pull request describes why these changes were made.
[x] This PR is into the correct branch.
[x] JIRA ticket for this PR: https://jira.mitre.org/browse/BONNIE-1460
[ ] JIRA ticket links to this PR
[x] Code diff has been done and been reviewed (it does not contain: additional white space, not applicable code changes, debug statements, etc.)
[x] If UI changes have been made, google WAVE plug-in has been executed to ensure no 508 issues were introduced. NA
[x] Tests are included and test edge cases NA
[x] Tests have been run locally and pass (remember to update Gemfile when applicable) NA
[x] Test fixtures updated and documented as necessary ( see [internal wiki] (https://gitlab.mitre.org/bonnie/internal-documentation/wikis/testing#test-fixtures) ) NA
[x] Code coverage has not gone down and all code touched or added is covered.

In rare situations, this may not be possible or applicable to a PR. In those situations:

Note why this could not be done or is not applicable here:
Add TODOs in the code noting that it requires a test
Add a JIRA task to add the test and link it here:

Branch
Back End Coverage
Front End Coverage

master
[Paste Output Here]
[Paste Screenshot Here]

[New Branch]
[Paste Output Here]
[Paste Screenshot Here]

[ ] Automated regression test(s) pass

If JIRA tests were used to supplement or replace automated tests:

[ ] JIRA test links:
[ ] Justification for using JIRA tests:
[ ] JIRA tests have been added to sprint

Reviewer 1:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

If JIRA tests were used to supplement or replace automated tests:

[ ] JIRA tests have been run and pass
[ ] You agree with the justification for use of JIRA tests or have provided input on why you disagree

Reviewer 2:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

If JIRA tests were used to supplement or replace automated tests:

[ ] JIRA tests have been run and pass
[ ] You agree with the justification for use of JIRA tests or have provided input on why you disagree

Test with these branches.
https://github.com/projecttacoma/cql_qdm_patientapi/tree/frequency_refills
https://github.com/projectcypress/health-data-standards/tree/frequency_refills


Tuples

Create a dictionary with a tuple(classname,rollno) as key and name as value.
Create a set with a tuple and a tuple from a set.
Write a program where the 3 sides of a triangle are given in a 3 valued tuple. Find the area
Write a program that will create a multiplication table as a tuple. For example p3=(3,6,9,12,15,18,21,24,27,30)

students = {}
while True:
print("0-Exit,1-Add ,2-Search")
n = int(input("option\n"))
if n == 0:
break
elif n == 1:
classname = input("Enter class\n")
rollno = input("Enter roll no\n")
name = input("Enter name\n")
students[(classname, rollno)] = {"name": name, "class": classname, "rollno": rollno}
elif n == 2:
classname = input("Enter class\n")
rollno = input("Enter roll no\n")
print(students.get((classname, rollno)))


improving the build/installation process

Hi everybody!
I spent some time trying to figure out how HIE is built and I found a bunch of problems that might be pretty easy to fix.
This is me getting started on that and soliciting feedback.
My end-goal is to create a PR that makes the installation more pleasant for first time users, including some readme polish. Please note that I'm neither extremely experienced with makefiles, nor with other build tools or tricky dependency handling, so I'm not promising that I'll be extremely fast. I will track progress here.
The problems. Numbered so you can comment on them:

building everything seems robust-ish, but is very time intensive and uses up loads of harddisk.
building a targeted ghc version is broken in my opinion:

The submodules will use different resolvers. The redundancy in downloads and compilations is pretty nuts. Incorrect, they will use the resolver from the stack build command.
The selection of ghc version doesn't propagate to the other build commands.
The command to check the ghc version (GHC := $(shell stack path --compiler-exe)) will use the main stack.yaml instead of the targeted one. This will also attempt to download an entire resolver set, just to tell you its ghc version.

The resolvers in stack.yaml and stack-8.6.3.yaml are two different nightly ones, which I think could be aligned to use the same one, improving build-all.
It's unclear what I have to have on my system and what can get reused. If I have the latest cabal, no need to compile the whole thing.
happy gets compiled and installed with each version, effectively overwriting itself 7 times.

I really think installing one, maybe two specific versions is the right use-case for most intermediate users, especially those installing hie for the first time.
As an example, I managed to get an amazing fast install experience (for ghc 8.4.4) by doing the following:

remove the dependencies on cabal and submodules from hie-%: in the Makefile

not fully necessary, but nice in case we already have the right cabal version.

copy stack-8.4.4.yaml over stack.yaml
change the resolvers of submodules/HaRe and submodules/brittany to use the same one as HIE (and create a stack-8.4.4.yaml for the latter)

not necessary

make sure that cabal is installed. I happened to have it via ghcup so I have no idea if it even needed cabal update, I only did cabal new-update. It seems it's also not mandatory to install via stack.
make build-doc-8.4.4 at the end.
everything works in projects with 8.4.4. Amazing!

space cost: 200Mb. Would be 100Mb, but there is both hie-8.4 and hie-8.4.4. Does it need both? Who knows. md5 says they're the same thing. Would a symlink do?

Now the challenge is to make it equally nice without having to tweak any files.
I gotta run now, but I will update this post with goals and a todo list.
Chime in if you have comments!

Regarding 2) - not sure if changing resolver of submodules is actually ok, i think at least some code (ghc-mod probably) there relies on building with specific ghc, @alanz may tell better.
However propagating specific stack.yaml everywhere to reuse existing installations is probably a good thing to do to reduce time\space waste. Proper --stack-yaml parameter inferred from requested GHC version in stack invocations should remove a need in copying specific stack-x.y.z.yaml over stack.yaml. This will make a good first step.
Regarding 3) - i think most redundancies are handled by cache system of stack. At least for cabal - in my experience stack won't rebuild cabal if it is already installed. However, afaik, hie may require a specific version of cabal and globally installed one may not be suitable. So stack install cabal here is okay - it's either installs proper cabal or does nothing.
Regarding specific libraries (like libgmp), however, i'm not sure we can do anything better than case-by-case individual manually written checks based on user reports.

but there is both hie-8.4 and hie-8.4.4. Does it need both? Who knows. md5 says they're the same thing. Would a symlink do?
I think it will. Not sure about portability, though. Symlinks aren't widely used on Windows for some reason but in my experience they work okay, so we can give it a shot.

Thanks for the feedback @Anrock! I have a few questions for you at the end.

if I stay in the same overall LTS range, i.e. 12.* then it should be ok. I think the increasing LTS versions are supersets of the previous ones iirc? I don't know yet how to pass the choice of resolver to them.

I agree that copying over stack.yaml is not a solution, it was only my hack to prove that it's possible to massively reduce the amount of building that has to be done.

To be more slightly precise, stack will install cabal over the old one, but if it was already compiled with that resolver, then it just copies the artifact it already has anyway. So yes, only one compilation. But we could make it zero, maybe by checking cabal --version somehow.

To your last point a question: I now have three executables: hie, hie-8.4, and hie-8.4.4. What would happen if I install all versions? wouldn't several hie-8.4.* just keep pointlessly overwriting hie-8.4? To me that means that hie-8.4 cannot be used anywhere. Or could you explain to me how those 3 are needed?
IMHO in a perfect world we would only have hie-8.4.4 and have hie-wrapper do the rest.
I also got aware of https://github.com/haskell/haskell-ide-engine/pull/991, so I will limit the scope of my attempt to really just list here what I think is broken with build-all, and attempt to fix that.
Will report back with an overview of my understanding of make build-all

@2mol
2) Probably. as i said i'm not sure. For example, at the moment, hie always builds cabal-<IP_ADDRESS> which is available, i believe, only for GHC 8.6.
3) That may work, yeah.

wouldn't several hie-8.4.* just keep pointlessly overwriting hie-8.4?

They would.

To me that means that hie-8.4 cannot be used anywhere.

Why, tho?

Or could you explain to me how those 3 are needed?

You mean hie, hie-8.4 and hie-8.4.4? This is a common practice/convention in *nix world for having multiple versions of same library installed simultaneously.
Basically you have a whatever large set of libfoo-x.y.z.so files anywhere and a chain of symlinks, like /usr/lib/libfoo.so -> /usr/lib/libfoo-x.so -> /usr/lib/libfoo-x.y.so -> /whatever/libfoo-x.y.z.so. Then by manipulating symlinks to point to different lib files user is able to select "default" version of libfoo and build systems can look for dependencies in semi-standart way, like "i need any version of libfoo, so i just link with /usr/lib/libfoo.so" or "i need at least libfoo-2.4, so i link with /usr/lib/libfoo-2.4.so" and symlink chain will ultimately resolve to some conrecte file at the end.
Hie follows this convention, but copies binaries instead of symlinking, for some reason. And hie-wrapper here is "build system" from example.

building a targeted ghc version is broken in my opinion:

The submodules will use different resolvers. The redundancy in downloads and compilations is pretty nuts.

In a multi-directory project, stack will build the submodules with the resolver specified in the root. Otherwise you would not be able to use a version 8.6.3 compiled module with say a GHC 8.4.4 compiled one.

The selection of ghc version doesn't propagate to the other build commands.

The actual compilation step is driven by
## Builds hie for GHC version % only
hie-%: submodules cabal
	stack --stack-yaml=stack-$*.yaml install happy
	stack --stack-yaml=stack-$*.yaml build
	stack --stack-yaml=stack-$*.yaml install                                \
		&& cp '$(STACKLOCALBINDIR)/hie' '$(STACKLOCALBINDIR)/hie-$*'    \
		&& cp '$(STACKLOCALBINDIR)/hie-$*' '$(STACKLOCALBINDIR)/hie-$(basename $*)'
.PHONY: hie-%

So each of the invocations of stack uses exactly the same stack yaml file.

Even the command to check the ghc version (GHC := $(shell stack path --compiler-exe)) will use the main stack.yaml instead of the targeted one. This will also attempt to download an entire resolver set, just to tell you its ghc version (!)

This bit is done on the assumption that all was being built, so the specific version being used is not important, as it will be installed anyway. And the original purpose is to make sure that the cabal executable is available in the path, so that ghc-mod / cabal-helper can use it while trying to determine the project type.

Thanks @alanz, I appreciate you chiming in.

And for say the hie-8.6.3 one, the logic is that GHC 8.6.3 should be backward compatible with 8.6.2, and with 8.6.1

Ah, that makes sense, very good to know! That solves my comment to @Anrock about me thinking that 8.4 couldn't really be used.
But I don't fully understand: why then compile 8.6.1 if you could just compile 8.6.3 and use that for every version below it? I guess I really should look into the code for hie-wrapper at some point.
Either way, what do you think about switching to symlinks? My understanding is that the build for Windows is anyway done with a powershell batch file. So we could avoid copying the binaries, no?

In a multi-directory project, stack will build the submodules with the resolver specified in the root. Otherwise you would not be able to use a version 8.6.3 compiled module with say a GHC 8.4.4 compiled one.

Also something I didn't know! Some of my original points are therefore not valid and my step-by-step thing can be simplified. I started measuring compilation times and disk usage, to avoid being too wrong about how much can be improved :)

@2mol I think we would have to experiment to confirm whether the GHC 8.6.3 binary does in fact work for GHC 8.6.1 projects.
I do know there was a breaking AST change from GHC 8.2.1 to 8.2.2, which could cause an issue.
And I have no problem with symlinks, it perhaps makes it clearer what is going on, to anyone inspecting the bin directory.
We just need to make sure they are actually supported on all platforms using hie.

I think building them concurrently would help alot. Idk if Makefile supports them but Gradle does for sure.(Gradle is also much better in general than Makefile when making build system.)

Ok, tested out the first simple idea to make the single build faster. You can see the change in #1013. More progress to follow.
@alanz symlinks should be totally fine on mac and linux, and I can test on both
@ingun37 I think compiling already uses up all my cores, so I'm not sure if we can gain much by building concurrently. But I'd be happy to be proven wrong.

I suppose, since the Makefile does not exist anymore and #1168 has been merged, this can be closed now.


ckeditor default widget does not implement any attrs to style parent

I wanted to style the default widget to be width: 100%; but the template file doesn't include the attrs.class or attrs.style in the container element. Instead, those attrs get propagated down to the hidden textarea.
I understand that the current implementation has a use, but there should be a way to style the parent element without overriding the entire template or using the .django-ckeditor-widget css class.

Hi
An example of a possible configuration would be very useful. Or maybe even a pull request. It's not completely clear to me what your proposal or issue is.

In the template file, Currently all attrs are added to the main editor by including django/attrs.html. If i were to, for example, want to set the width of the parent to 100%, i currently need to do that by writing css for its class (which would apply to ALL editors on the page), or override the widget template myself (seems a bit overkill for just some style). My suggestion is to add something to the default widget template to make this easier.
Some suggestions:

Having a {{attrs.parent_class}} in the parent's classlist
Implementing a seperate kwarg like container_attrs in the widget code
Implementing a seperate arg or kwarg to set the classname or id of the parent to css only that specific widget.


how can I config authority with subdomains

My IdentityServer and ApiResource  in the same project, and develop in sub domain like

a.myids.com
b.myids.com
c.myids.com
d.myids.com

I  have reference this code, but only can config one IdentityServer address, how can I change the Authority property dynamic, follow current requestContext Uri?
{
    public void ConfigureServices(IServiceCollection services)
    {
        services.AddAuthentication(JwtBearerDefaults.AuthenticationScheme)
            .AddJwtBearer(options =>
            {
                // base-address of your identityserver
                options.Authority = "https://demo.identityserver.io";

                // if you are using API resources, you can specify the name here
                options.Audience = "resource1";

                // IdentityServer emits a typ header by default, recommended extra check
                options.TokenValidationParameters.ValidTypes = new[] { "at+jwt" };
            });
    }
}

These options must have a TokenValidationParameters property of type TokenValidationParameters which has a property named IssuerValidator where you can put your own validation delegate. Also there is ValidIssuers property where you can a list of all valid issuers.


Add script for genestack-uploader doc generation

In genestack-uploader I remove string the whole upload stops and and brake lines to fit screen.
I docs long lines produce horizontal scroll, I want to avoid this situation.

I add hidden comments to this scripts.
This scripts were commited to repo for use in track. I will remove them.


Feature Request - Support for Sound Effect in the SDK

Requesting addition of sound generation in the SDK -
Reference -
https://elevenlabs.io/docs/api-reference/sound-generation

Hi, it should be in the python and node SDK. Here's the tutorial, I'll add it to the reference docs shortly
https://elevenlabs.io/docs/api-reference/how-to-use-text-to-sound-effects
Let me know if you have any issues with it


K8s metadata - change metadata url in settings

Currently the URL to data.json includes branch name and that gets cached, so it doesn't immediately reflect the changes after pushing to repository.
Workaround:
Editing the URL to different branch, or changing the metadata-refresh-interval-minutes, would reload everything. This way new data will be loaded

The bug fix is validated with the rancher testing image v2.3.2
Saw the versions in the list is updated to the expected ones after either

editing the URL to a different branch
or
changing the v3/settings/metadata-refresh-interval-minutes


Modified create_ssl_listener option as per Mixlib-CLI.

Made changes in code for --[no-]create-ssl-listener option as per Mixlib-CLI's magic and also modified RSpecs to accommodate the changes.

It'd be nice if we could avoid having to add and remove the config setting in so many tests, but otherwise :+1:

@btm I have removed multiple add and delete entries for config[:create_ssl_listener] variable from the specs. Please have a look and let me know if any issues still persist.


Update pekko-stream, pekko-stream-testkit to 0.0.0+26721-bed33cd4-SNAPSHOT

About this PR
📦 Updates

org.apache.pekko:pekko-stream
org.apache.pekko:pekko-stream-testkit

from 0.0.0+26669-ec5b6764-SNAPSHOT to 0.0.0+26721-bed33cd4-SNAPSHOT
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.apache.pekko" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.apache.pekko" }
}]

labels: library-update, early-semver-build-metadata, semver-spec-build-metadata, version-scheme:semver-spec, commit-count:1

Superseded by #37.


microbit V2 cannot be flashed

The microbit V2 and therefore a possible Calliope mini update can be seen (and maybe connected), but flashing is not possible.

UUID seems to be: 0000FE59-0000-1000-8000-00805F9B34FB - Secure DFU Service


Fix POP restart from omuse provided data

POP internally has two versions of the prognostic variables: old and current. Previous implementation only exposed the current one in getter, and setter functions duplicated the data in both old and current POP arrays. New implementation uses suffixes _old and _cur to get/set old and current respectively, while a _all suffix is implemented to keep the previous behavior:channel.copy_attributes(["xvel_cur"])

will copy ONLY  the current data between two instances.channel.copy_attributes(["xvel_old"])

will copy ONLY  the old data between two instances.channel.copy_attributes(["xvel_all"])

will copy the current data into both old and current between two instances.
when restarting a POP instance from data provided through the Omuse mechanism described above, one need to specify:p.parameters.ts_option = "amuse"
p.parameters.pressure_correction = False

to ensure a smooth restart.

@Sbte can you get a look at this ? It should include the changes we discussed the at IMAU the other day.

It seems like a lot of code duplication to me. Would it be possible to add an extra oldtime argument to all Fortran setters and getters, such that they can be implemented in Python as something like
def set_node_barotropic_vel_oldtime(self, i, j, vx, vy):
    return self.set_node_barotropic_vel(i, j, vx, vy, True)

def set_node_barotropic_vel_curtime(self, i, j, vx, vy):
    return self.set_node_barotropic_vel(i, j, vx, vy, False)

def set_node_barotropic_vel(self, i, j, vx, vy):
    return self.set_node_barotropic_vel(i, j, vx, vy, True)
    return self.set_node_barotropic_vel(i, j, vx, vy, False)

def get_node_barotropic_vel_oldtime(self, i, j):
    return self.get_node_barotropic_vel(i, j, True)

def get_node_barotropic_vel_curtime(self, i, j):
    return self.get_node_barotropic_vel(i, j, False)

def get_node_barotropic_vel(self, i, j):
    return self.get_node_barotropic_vel(i, j, False)

Not sure if this is possible, but it avoids the code duplication.

Also, please squash the fixes into earlier commits. You can easily do this with git rebase -i and then use fixup.

@Sbte I agree, way too much duplication but I can't seem to make a more generic version work within the Amuse interface stuff. I'd rather go with this for now so you can use it, and revisit later when I have a better grasp of how to make that work.

Yeah, that's probably a good idea. I'll test it next week and then merge it if it works.

Note that this way of handling the _all attributes also duplicates them in the data files, which is not optimal.

Model time does not seem to be stored anywhere. Is that fixable in a reasonable amount of time? If not I don't think it matters.

Handling of time is cumbersome in POP. If you really need to sync time, the easiest way is to set it to your desired value in the namelist input file.

After commit 21f01c0, all the _all variables have been removed, reducing code duplication and extra disk space. The current time variable are accessible without extension:
channel.copy_attributes(["xvel"])

Both xvel and xvel_old have to be copied to mimic the previous behavior. For ssh the guess pressure also have to copied (on top of ssh and ssh_old):
channel.copy_attributes(["ssh_guess"])

@Sbte Let me know if you think this is ready to merge or if you see something else to update.


Refactoring, linting, and alternative release action

I finished my version of the release action. Life got busy, I was delayed. It looks like you created your own in the meantime. I merged them, as well as doing some cleanup, refactoring, and linting.
Minor changes overall. But I figured I might as well make a pull request anyway.
Instead of using an external action like softprops/action-gh-release@v1 I used the built-in gh command. Reducing the number of external dependencies in the build process. (I believe the gh cli as well as github-script deprecate a lot of common third-party actions.)
I also added a cleaning step to the cargo xtask dist command to clean the target/dist directory before creating the new zip files in it. Probably not relevant since the CI should run in a clean environment, but might as well.
In the line of reducing dependencies, I removed the clap crate, and switched from reqwest to ureq using the native Windows TLS support for HTTPS. I also modified the crates/common crate to have feature gates, to let cybercmd compile without having to directly depend on everything xtask needs, meaning it won't rebuild those crates in the release profile.

I made some minor comments, but generally looks good. I did a release with your previous changes, but I didn't push it to Nexus yet, because I don't like the fact that users will end up with 2 redscript config files. I think it'd be worth investigating adding some kind of backwards compat for the old TOML to make it as easy as possible for end-users and avoid weird scenarios like redscript being invoked twice.

I think I've fixed all the issues you commented on.
If I have time today I'll implement the legacy parsing as a separate pull request, so you can properly distribute the redscript toml with redscript.


Cs quiz kunal

Summary of changes
Question added related to B-tree in cs fundamentals quiz
Checklist

[x] I have read and followed the contribution guidelines.
[x] I have read through the Code of Conduct and agree to abide by the rules.
[x] This PR is for one of the available issues and is not a PR for an issue already assigned to someone else.
[x] My PR title has a short descriptive name so the maintainers can get an idea of what the PR is about.
[x] I have provided a summary of my changes.

closes #XXXXX

closing due to inactivity. 👍


wrong attestation app package name: UnknownPackage

Recent remote attestations failed. Tried creating a new verification pairing as auditee and after the QR code was scanned the app displayed:
Error encountered generating attestation:
wrong attestation app package name: UnknownPackage

Error persisted after force stopping and clearing the app cache. Error disappeared after restarting the device, so perhaps a bug in PackageManager (call to pm.getKeyAttestationApplicationId?). The device is a Pixel 3 XL running GrapheneOS RQ2A.210305.006.2<IP_ADDRESS>.

It could be an issue communication with the secure element. I think it must be an upstream bug and it's highly unlikely that you're going to run into it again. I don't think we'll be able to figure out what's wrong. I've had issues with the older generation Titan M which required rebooting the device before including with timestamps.

Going to close this because I don't think there's much we can do especially for an older generation device. I don't think it's a PackageManager issue but rather the secure element is not giving the OS the value that it has stored on it for the key for some reason. It's basically not something we could even begin to debug or fix. If the OS was providing the wrong value to it then it wouldn't be resolved by a reboot and wouldn't be allowing usage of the key either.

Also, by clearing the app cache, do you mean clearing data for the app completely?

Thanks for clarifying - that explanation makes more sense. I'll post back if it unexpectedly fails again.

Also, by clearing the app cache, do you mean clearing data for the app completely?

Kept the app data, just clicked the clear cache button in app info after force stopping. The attestation pairing fingerprint remained the same.


Secret Store Http Client

Describe the proposal
I know you are working to improve the dapr client as statedt in #197, but since the Secrets API endpoint has been merged (https://github.com/dapr/dapr/pull/1059 & https://github.com/dapr/dapr/pull/1085) a Secret Store http client should be provided

@cmendible Thanks for adding the secrets api, This add s a new SecretsClient, I would wait and add the api api refactoring which is being done for DaprClient.

@cmendible Thanks for adding the secrets api, This add s a new SecretsClient, I would wait and add the api after refactoring which is being done for DaprClient, the calls would go over gRPC

Ohhh I see, so the http will be deprecated?
I just submitted #241 so I guess it will be a no go. If there is anyway I can help just let me know.

Ohhh I see, so the http will be deprecated?
Yes, non-actor calls from .net sdk will go over gRPC/
I just submitted #241 so I guess it will be a no go. If there is anyway I can help just let me know.
Please modify the issue, to add it to DaprClient api over gRPC. This is the branch we will be working in https://github.com/dapr/dotnet-sdk/tree/one_client, currently it has an interface and a class please feel free to app secret api to this branch.


Standalone content-tag implemented via conditional exports in package.json

Alternative to: https://github.com/embroider-build/content-tag/pull/41
Changes:

there are now two wasm-pack builds, one targeting noed, and one "browser" or "standalone" (as browser targets tend to be "standalone" / runnable anywhere) -- if we didn't need to support CJS, we could get away with only the standalone build
the root package.json is now the package.json that is published

now has name, description, etc
files entry includes the pkg directory
has exports with conditional/subpath entries to target node/browser separately since wasm-pack generates very different output for each target (there isn't a need for this if they went for full async-only API, but :shrug: )

To test that the browser changes actually work, vite has been added to devDependencies as well as an index.html

I tried to automate browser testing with vitest's browser mode: https://vitest.dev/guide/browser#browser-option-types -- but the browser mode does not support the same work around that vite has for https://github.com/vitejs/vite/issues/9731 -- which is setting resolve-alias for "package-name": "." (current directory) so that vite can resolve the "self's" exports.  So we currently don't have automated browser testing atm.  We could set up qunit instead of vitest, but we currently need to handroll a reporter to the CLI, because vite/vitest haven't given us those APIs to build custom reporters. GlimmerVM is already doing this, so it "just" needs to be extracted.
This is the error:[plugin:vite:import-analysis] Failed to resolve import "content-tag" from "test-browser/process.test.js". Does the file exist?
/home/nvp/Development/OpenSource/emberjs/content-tag/test-browser/process.test.js:2:48
1  |  import { __vi_inject__ as __vi_esm_0__ } from 'vitest'
2  |  import { __vi_inject__ as __vi_esm_1__ } from 'content-tag'
   |                                                 ^
3  |
4  |

Due to not being able to correctly test with vitest, I added publint and @arethetypeswrong/cli to help me be more confident that the package.json was correctly configured so we don't have to rapid publishes to fix bugs with package.json config.
@arethetypeswrong/cli reported some issues which are resolved now.
One being this issue which is resolved by using node newer than 16 -- which... we don't declare node support at all, and node 16 is EOL'd so it seems fine to bump the CI's node.

yes, if this did the same thing meaning npm run build the two would be in
sync
On Fri, Dec 1, 2023, 22:58 NullVoxPopuli @.***> wrote:

@.**** commented on this pull request.
In .github/workflows/ci.yml
https://github.com/embroider-build/content-tag/pull/44#discussion_r1412642100
:

     cache: 'npm'

run: npm ci

run: ./build.sh

the release workflow already run npm run build, so this is covered
—
Reply to this email directly, view it on GitHub
https://github.com/embroider-build/content-tag/pull/44#discussion_r1412642100,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABHPNIYA6WWEOZLJLNEWL23YHJOHRAVCNFSM6AAAAABADKFMUKVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTONRQGY3TGMJTGM
.
You are receiving this because you commented.Message ID:
@.***>


Support the full syntax for dependency version ranges

Right now, coursier goes so far as to process single version intervals, as I can see in Parse.scala. However, Maven also supports multiple intervals like [v1,v2],[v3,v4],..., as shown in this design document.
I'm getting a message Ignoring unparsed versions: Vector([1.0.3,1.1),[1.1.1,1.2)) in a real world project where one of my dependencies ends up bringing "org.webjars.bower" % "dgrid" % "1.0.0", which has such a range dependency.

I don't see a straightforward way of implementing that without breaking binary compatibility before 1.0... Although a quick workaround could be to just keep the last interval in the list, in a first time.

I would be fine with that temporary solution for my concrete use case, although it would make sense to support those less common cases sooner rather than later.


[Keyboard Manager] Support remapping a single key to a shortcut

Summary of the new feature/enhancement

E.g. remmap CapsLock key to Ctrl + Win + Space

+1

another scenario is being able to map the HOME key to alt+ left arrow, same key stroke as on the mac.

Yes, I think it's quite useful!

Another (my) scenario is to use Right Alt as language switcher (Win + Space)

Great suggestion, we've got this from many users and I'll be closing this and tracking the suggestion here: #3290

Love it, hoping we can get this in for our V1.  Since this is a duplicate issue, I'll be closing this and tracking the suggestion here: #3290


Add eventtype when labelling the PR

Signed-off-by: Chmouel Boudjnah<EMAIL_ADDRESS>

Codecov Report

Merging #76 (3b94b06) into main (0ea3403) will increase coverage by 3.11%.
The diff coverage is 60.00%.

@@            Coverage Diff             @@
##             main      #76      +/-   ##
==========================================
+ Coverage   69.47%   72.59%   +3.11%
==========================================
  Files          10       10
  Lines         688      686       -2
==========================================
+ Hits          478      498      +20
+ Misses        160      137      -23
- Partials       50       51       +1

Impacted Files
Coverage Δ

pkg/pipelineascode/pipelineascode.go
70.49% <60.00%> (-0.48%)
:arrow_down:

pkg/cmd/pipelineascode/pipelineascode.go
66.17% <0.00%> (+32.35%)
:arrow_up:

Continue to review full report at Codecov.

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


Allow enabled or visible in customer group scope.

Closes #1165

@alecritson should this not target 0.5 as it's a fix?


Fixing issue 458

There was a regression.
But also some weirdness: Range.setStart(startNode, startOffset) + setEnd(endNode, endOffset) does not behave the same as Range.setStart() + window.getSelection().extend(endNode, endoffset)
I now do the selection.extend() for all non-collapsed selections.

There is still a rendering issue when the ContainerSelection reaches into the next paragraph at char 0.
It is a Fragmenter bug.


iOS: stop recycling web views

This won’t add any UI latency if implemented correctly. We will use slightly more processing. The pay off is that if we have a web view with an incorrect dynamic text size, it will be used only once and not keep coming back. This doesn’t fix our text size bug, but should make it more tolerable.

We are going to handle this a different way.  See issue #1878


Clarify Solid 0.9 compat for ESS/pod.inrupt.com

Link to https://docs.inrupt.com/ess/latest/security/authorization/#additional-information

This site does state that ESS v1.2 (not released yet apparently) is (translated) "In accordance with the Solid Specifications", so maybe they anticipate the WAC requirement will be dropped in post-0.9 Solid, or there is some other piece of the puzzle we don't fully understand yet.
We could add a column for 'ACP-based Solid' next to the 'Solid 0.9' column, to show that v0.9 is maybe not the only "flavour" of Solid. But let's first ask the spec editors team what their current stance on WAC vs ACP is.

See also https://github.com/solid-contrib/specification-tests/blob/main/protocol/requirement-comments.ttl#L8

And https://github.com/solid-contrib/specification-tests/blob/main/test-subjects.ttl#L23
This comment says ESS with WAC is supported by Inrupt, although if you read that in the context of https://docs.inrupt.com/ess/latest/security/authorization/#additional-information then it probably means it's supported in development, not in production.


Server Side Rendering

Hello,
I wanted to know if slim.js supports server side rendering. I have been looking at the documentation to see if this feature was available but I could not find any mention of it.
Thank you for your help and good job.
Linvi

@linvi
Hi.  It is based on native DOM API (which only runs in the browser). The whole point of using web components and custom elements is to extend the primitive elements exists on the browser (i.e. span, div, etc.) and create new ones with code-behind and logic.
You could generate code in the server and load only the components in use.
If you could please specify how your servers works and what are the requirements I could point out how to make it work with custom elements / web components.
slim.js is an extension of the native API that provides essentials that does not exists (and probably never will) on the browser: Data binding, Plugins, Extensions - to the native API.
10x.

Hello,
I am aware that web components are based on browser rendering but I was just wondering how to render web components for robots that unlike google do not execute javascript.
I am planning on using node in the backend to execute the javascript necessary by the web component.
Your input would be greatly appreciated.
Thanks,
Linvi

You can use aria-* attributes that helps robots understand what is going on the website.
Robots (as google says) can read web-components. They do not care about div vs. span but they do care about metadata and aria-* attributes.

Thank you for the feedback, I will read more about the subject.
Cheers,
Linvi


dotnet run error

Problem encountered on https://dotnet.microsoft.com/en-us/learn/dotnet/hello-world-tutorial/install
Operating System: macos
Hey all! I am new to coding and am using VScode. I ran into an error trying to establish the "Hello World!" introductory code. After the initial install I was able to get the code correctly, but then after using cd a couple times and trying to create new folders I have not been able to get a working code and even tried to get the Hello World code and still cannot.  Fix the build errors and run again.
I have been trying to reverse text as an exercise and the code that inputted was this
"
public class Class1 System.string Reverse(string input){
if (string.IsNullOrEmpty(input)){
return input;
}
}
StringBuilder reversed = new StringBuilder(input.Length);
for (int i = input.Length - 1; i >= 0; i--){
    reversed.Append(input[i]);
}
    {return reversed.ToString();}

Console.WriteLine(Racecar);

"
Thanks in advance!

The problem is that your code isn't formatted correct. Here is something to get you started.
public class Class1
{
    public static string Reverse(string input)
    {
        if (string.IsNullOrEmpty(input))
        {
            return input;
        }

        StringBuilder reversed = new StringBuilder(input.Length);
        for (int i = input.Length - 1; i >= 0; i--)
        {
            reversed.Append(input[i]);
        }
        return reversed.ToString();

    }
}
Console.WriteLine(Class1.Reverse("Racecar"));

I'm gonna close the issue, but good luck on learning to code!


sentiment analysis using nltk

How can I do sentiment analysis using nltk?
Does nltk 3.1 has inbuilt sentiment analyzer?
If not, I heard it now supports stanford corenlp integration, if this is true then how can it be achieved?
I think it is more like a stackoverflow question but since 3.1 is new I thought this might be better place.

The documentation for the new sentiment analysis functionality is still a bit rudimentary, but have a look at:

New corpora in http://www.nltk.org/howto/corpus.html#categorized-corpora
Brief examples in http://www.nltk.org/howto/sentiment.html
Longer examples in http://www.nltk.org/api/nltk.sentiment.html#module-nltk.sentiment.util

@anupamme I suggest that if you want to pursue this question further, it would be best to do it on the NLTK user mailing list.


Not all keys are supported

Expected Behavior
Not all keys are supported, i.e.
;:'"[{]}?/ aren't being detected or used in the keylogger.
Current Behavior
No output of the above keys.
Steps to Reproduce
Use the keylogger
System Information

Version: Latest
Platform: Windows 7 x64

Bug has been fixed in 44eb1210e6f2f10340b3d201b97bd0c05465f1d8


TODOs

[x] Favourites and Recents.
[x] Message of the day.
[x] Donation button.
[x] Signed release apk.
[ ] CI Setup.
[ ] Contributors guide.
[ ] Auth & Library sync.
[ ] Chat.
[x] Better video player Okay-ish video player.
[ ] Responsive for large screens / landscape orientation.
[ ] Screen Cast.
[x] OSS info inside the app.
[x] Design and add icons for the app.
[ ] Make season += 1
[ ] Things to do on no network

[x]  Favourites and ~Recents~.
[x]  Message of the day.
[x]  Donation button.
[x]  Signed release apk.
[ ]  CI Setup.
[ ]  Contributors guide.
[ ]  Auth & Library sync.
[ ]  Chat.
[x]  ~Better video player~ Okay-ish video player.
[ ]  Responsive for large screens / landscape orientation.
[ ]  Screen Cast.
[x]  OSS info inside the app.
[x]  Design and add icons for the app.
[ ]  Make season += 1
[ ]  Things to do on no network
[ ]  forward/backward button on video player


[WİP]: dynamic window title #2810

I made a small development for the dynamic window text, I would be grateful if you have any advice on this subject.
interacted with the refine component on an example 🚀

Hello. this PR does not meet all the features of the issue

Hello. this PR does not meet all the features of the issue. We expect a callback where it can return a new title according to users' needs and it should also be managed manually with a hook. Also, It should work with all router provider packages.
If you have any further ideas or feedbacks, we can discuss on issue #2810 🙏

i'll be there in pursuit 🚀


Enable thread safety for GenericTransformation and ConvexShapeContact.

I did not work on the constraint solver as it is a tough work and I think it is not necessary for now.


MASTER_ADDR setting for mnist example

When launching the public pytorch examples for jobsets (doc link), I had to change the MASTER_ADDR value from pytorch-workers-0-0.pytorch-workers -> pytorch-workers-0-0.pytorch.train.svc.cluster.local for the pods to connect.
Is this something specific to my installation? Or do the examples need to be updated?
Exact error log from resnet.yaml
[W socket.cpp:558] [c10d] The IPv6 network addresses of (pytorch-workers-0-0.pytorch-workers, 3389) cannot be retrieved (gai error: -2 - Name or service not known).

Setup
I launched the jobset into specific namespace named train.
kubectl apply -f jobset.yaml -n train --server-side
We are using the v0.5.2 of jobset
kubectl apply --server-side -f https://github.com/kubernetes-sigs/jobset/releases/download/v0.5.2/manifests.yaml
I have verified that the the headless service resource exists on jobset creation. I have verified that that the jobset-controller-manager is in a healthy state.

Oh it looks like the example docs might be out of date.
The public docs) have MASTER_ADDR=pytorch-workers-0-0.pytorch-workers, but the github example correctly has MASTER_ADDR=pytorch-workers-0-0.pytorch.
Setting MASTER_ADDR=pytorch-workers-0-0.pytorch now works.

Fixed in #604
Thanks @song-william!


CronManager initial setup

AS A Service Manager
I WANT TO initiate repetitive requests and have full control over them
SO THAT I could do it from one place
AS AN Architect
I WANT TO have all repetitive requests managed by one tool
SO THAT these functionalities wouldn't get lost in a sea of custom source code
Acceptance Criteria

[ ] Documentation with sample usage

Acceptance tested by @1ahmedyasser


Update E2E tests

Description

[x] Disable DEBUG logging in testcontainers
[x] Use 2.2.0 tag for localstack

Test Steps

Checklist:

[x] I have tested my changes. No regression in existing tests.
[x] I have modified and/or added unit-tests to cover the code changes in this Pull Request.

Related Issue
#86
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Not super critical but it would be helpful to update your checklist within description on why you're making the changes. I'm guessing because of noise and to avoid breaking changes w localstack.


Updates to pyflyte init templating

TL;DR
This PR removes the cookiecutter templating system for pyflyte init, and instead uses gitpython, without templating.
This is part of a wider effort to replace our Dockerfile / docker_build.sh systems with the much simpler ImageSpec.
This PR depends on https://github.com/flyteorg/flytekit-python-template/pull/40
This is a breaking change
All templates are now imagespec based, and cookiecutter is no longer used to generate custom readme titles or directory names.
Type

[ ] Bug Fix
[x] Feature
[ ] Plugin

Are all requirements met?

[x] Code completed
[x] Smoke tested
[ ] Unit tests added
[x] Code documentation added
[ ] Any pending items have an associated Issue

Complete description
As discussed as part of the larger Flyte example improvement with newly introduced imagespec.

cc @eapolinario / @neverett do you think you want to check this one in?


add an optional argument for glib path

#39

Oops, I meant to split the PRs but this also includes a fix for #23

Oops, I lost track of this! I totally meant to answer sooner.
In brief, I really thank you for taking the time to do this, but I can't maintain it (nor even meaningfully test it), which is why I didn't accept #39 in the first place.
I do want the fix for #23, and will be cherry-picking that, but as far as glibc, I won't touch it.
Thanks again, sorry I didn't accept the whole thing.


Unable to connect to an Azure-hosted Postgres instance

I'm experimenting with connecting OpenFGA to an Azure managed Postgres instance by running the OpenFGA docker container locally, and passing the postgres:// connection URI as the OPENFGA_DATASTORE_CONNECTION_URI env var. I've verified that I can connect to the Postgres instance through other means, but when I make a cURL request to create a new store in OpenFGA I get the following error:
ERROR   grpc error      {"error": "rpc error: code = Unknown desc = rpc error: code = Code(4000) desc = Internal Server Error", "request_url": "/stores"}
github.com/openfga/openfga/pkg/logger.(*ZapLogger).ErrorWithContext
        /home/runner/work/openfga/openfga/pkg/logger/logger.go:80
github.com/openfga/openfga/server.New.func1
        /home/runner/work/openfga/openfga/server/server.go:134
github.com/grpc-ecosystem/grpc-gateway/v2/runtime.HTTPError
        /home/runner/go/pkg/mod/github.com/grpc-ecosystem/grpc-gateway/v2@v2.10.3/runtime/errors.go:81
go.buf.build/openfga/go/openfga/api/openfga/v1.RegisterOpenFGAServiceHandlerClient.func12
        /home/runner/go/pkg/mod/go.buf.build/openfga/go/openfga/api@v1.1.16/openfga/v1/openfga_service.pb.gw.go:1639
github.com/grpc-ecosystem/grpc-gateway/v2/runtime.(*ServeMux).ServeHTTP
        /home/runner/go/pkg/mod/github.com/grpc-ecosystem/grpc-gateway/v2@v2.10.3/runtime/mux.go:386
github.com/rs/cors.(*Cors).Handler.func1
        /home/runner/go/pkg/mod/github.com/rs/cors@v1.8.2/cors.go:231
net/http.HandlerFunc.ServeHTTP
        /opt/hostedtoolcache/go/1.18.3/x64/src/net/http/server.go:2084
net/http.serverHandler.ServeHTTP
        /opt/hostedtoolcache/go/1.18.3/x64/src/net/http/server.go:2916
net/http.(*conn).serve
        /opt/hostedtoolcache/go/1.18.3/x64/src/net/http/server.go:1966

Steps to reproduce:

Populate .openfga.env with:

OPENFGA_DATASTORE_ENGINE=postgres
<EMAIL_ADDRESS>OPENFGA_GRPC_TLS_ENABLED=false
OPENFGA_HTTP_TLS_ENABLED=false

Run docker run --env-file ./openfga.env -p 8080:8080 openfga/openfga run
Run curl -X POST 'localhost:8080/stores' \ --header 'Content-Type: application/json' \ --data-raw '{  "name": "openfga-demo" }' in a separate terminal

Hi @thisisxvr! I think the problem here is that your Postgres instance does not have the required tables created yet. The ability to create the tables using the cli is in an upcoming PR (https://github.com/openfga/openfga/pull/56).
For the moment, the schema can be found https://github.com/openfga/openfga/blob/main/storage/postgres/migrations/20220617_initialize_schema.up.sql, so if you can execute this file on your instance, everything should work okay.
Please let me know if you have anymore questions!

@craigpastro You are correct; I ran the schema and it worked. Thanks for the quick response!


HTTPS support

Is there a way we can access kibana endpoint over HTTPS?  And proxy forward request to ES endpoint over HTTPS?

Hello @hardik-k-shah, all requests ARE forwarded as httpS already


Smooth scrolling editor

when we use ctrl d , we will jump file
sometimes we will from bottom jump top of file, or anywhere,
then , we will hard to understand file jump specific process,
and Easy to get lost the focus
so provide Smooth scrolling  is possibility ? thanks.

@zhangenming smooth scrolling is available via the setting editor.smoothScrolling.


react-native-pdf-view

I can not see PDF file on Android and IOS

Same issue , Android works with older version of react native but does not work with react 30 (The example app in the repo)

I needed to set flex: 1. Does that work for you guys?

+1

I get blank screen on android 4.4.4 any recomendation for fixing this bug?

+1 Can't work on 37.

Example app has been updated for RN 0.42

Don't forget to make libRNPDFView.a in your linked librairies


Understanding citation changes

Quinn noticed that the data errors went from 800->200. Can we get a report of the old errors and the new errors to follow up on the changes?

validation-errors.csv
@Vensberg
Here's a document that shows the error list, and whether the error shows up on stage, test, or both stage and test. Would this work for you?

@UcDust , perfect.


A function to replace the select part for one column

Motivation
When I have a larger struct, from which I want to have most columns as is, but let's say I want to have one of the existing columns with a function call like upper case, or COALESCE(), then I am forced to call .select_only() and repeat all the other columns.
Proposed Solutions
So I would like to have a function, which allows me to write the desired select piece, without being forced to do anything on the other columns.
This could be achieved by having all columns in the selection being mapped by the alias, and you could replace the selection for that alias with something new.
e.g.:
  fn column_instead<S: Into<SimpleExpr>>(mut self, expression: S, alias: &str) -> Self {
    …
  }

Hey @mohs8421, interesting!! I have a counter proposal!
How about we allow user to supply the list of selected column at the very beginning?
let cols = cake::Column::iter()
    .map(|col| {
        let expr = col.into_simple_expr();
        match col {
            cake::Column::Name => Func::upper(expr).into(),
            _ => expr,
        }
    });

cake::Entity::select(cols)
    .all(db)
    .await?;

that way you would still need to know more about the way sea-orm works internally, if you reduce your proposal to not use map with a callback, but with a filter, that would be easier, or is it possible to offer both by having the select definition like
fn select<S: IntoSimpleExpr>(cols: Vec<S>)…


Make WF example simpler

I just noticed that for the simple WF simulator used to demonstrate recapitation, we do some fiddly editing of the node flags, when (in this simple case) it's easier to just find all the nodes at time 0 and simplify with respect to those (which will automatically set the correct flags).

@mergifyio rebase

darn here I thought I had learned something about those CI errors...


A/B test on auto play for kids

Play next episode within the series
Play next preview/ countdown
Put it behind unleash
Sticky to device ID (determine what this should be)
Method to link to npaw data

[ ] Cancel autoplay if the user interacts with the page
[ ] Analytics: log when autoplay and when cancelling autoplay

@mulundapm How should this be linked to npaw data?

@mulundapm We can use the Session ID to link the did-autoplay-next and npaw events

This can be tested in the newest version on TestFlight.

Should autoplay next episode if the user doesn't touch the screen.
Autoplay should be cancelled if the user interacts with the screen


flutter run  ios跑不起来

Compiler message:
/Users/bing/flutter/.pub-cache/hosted/pub.flutter-io.cn/dio-2.2.2/lib/src/dio_http_headers.dart:55:8: Error: The method 'DioHttpHeaders.add' has fewer named arguments than those of overridden method
'HttpHeaders.add'.
void add(String name, value) {
^
org-dartlang-sdk:///third_party/dart/sdk/lib/_http/http.dart:694:8: Context: This is the overridden method ('add').
void add(String name, Object value,
^
/Users/bing/flutter/.pub-cache/hosted/pub.flutter-io.cn/dio-2.2.2/lib/src/dio_http_headers.dart:70:8: Error: The method 'DioHttpHeaders.set' has fewer named arguments than those of overridden method
'HttpHeaders.set'.
void set(String name, Object value) {
^
org-dartlang-sdk:///third_party/dart/sdk/lib/_http/http.dart:703:8: Context: This is the overridden method ('set').
void set(String name, Object value,

看下你得dio版本
我的是^2.1.7

close


Chart[Network Node]: Update Open Telemetry configuration to support optional remote write pushing of metrics and logs

depends on #216

:tada: This issue has been resolved in version 0.8.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Develop a code of conduct for the repository

Create a code of conduct that outlines the expectations for behavior and interaction within the repository's community.

I would like to work on this. Please assign this to me

Hey @1sh22
Sure. I assign this issue to you.

Hey @saharepiyush01
Sure I assign this issue to you
Please follow the contributing guidelines
Thanks

Hey @saharepiyush01 this issue has been resolved by @1sh22
You can go for some other issue
Looking forward to your contribution:)

ok then I will try some other thankyou


Issue #28 : do not crash test when there is no schema ns

Coverage remained the same at 98.397% when pulling 54c866e7cfa0bfea475a3b72c5e38f065cf35408 on hfiguiere:issue-28 into 80ea7728b21db4fa48b68f0a0066d78a06a35577 on python-xmp-toolkit:master.

Coverage remained the same at 98.397% when pulling 54c866e7cfa0bfea475a3b72c5e38f065cf35408 on hfiguiere:issue-28 into 80ea7728b21db4fa48b68f0a0066d78a06a35577 on python-xmp-toolkit:master.


Feature request: base class for event args

Many (in my experience, most) event handlers use event args without data. So this is boilerplate:
public class AsyncEventArgs : EventArgs, IDeferralSource
{
  internal DeferralManager DeferralManager { get; } = new DeferralManager();
  public IDisposable GetDeferral() => DeferralManager.DeferralSource.GetDeferral();
}

So would you kindly consider adding it to the library? Would make calling code mush cleaner.
If someone needs eventargs with data, then just subclass AsyncEventArgs. Which would also be cleaner.

Yes, absolutely! I just read a blog post last week where someone used a base class for this, and thought it would be a good idea.
The only real question is how the internal member should be exposed. Possibly keep it internal and just add event-raising helpers...

Good point, I didn't think about that! Internal and helpers, probably, but I'm not sure.
I always prefer to hide things away at first, and expose them later if I need to.

This issue was moved to StephenCleary/AsyncEx#87


Add missed changelog

Q
A

Is bugfix?
❌

New feature?
❌

Breaks BC?
❌

Fixed issues
-

thanks you


Trim carriage returns from TCP input

Description of Changes
Fixes a bug in the TCP input where it doesn't trim carriage returns from the message, causing downstream syslog parsing issues. Additionally, a number of small clean-ups for the TCP and UDP inputs.
Notes:

TCP input now uses a scanner, which is reduces copies, reduces allocations, and makes the logic simpler
UDP reuses the buffer it's reading into, reducing allocations
Debug message noise is reduced by only erroring when we get an unexpected error (an error when we haven't told the listener to close)
Adds a benchmark for the TCP and UDP inputs
Adds a Makefile task bench
Adds a FakeOutput to the testutil package, which has much less overhead than the mock output, so it can be used for benchmarking. Additionally, seems like it'll be simpler to use in most test cases that don't need special behavior.
The functions in testutil now use a TestingT interface, which is also implemented by testing.B so we can use testutil functions in benchmarks
Cleaned up UDP and TCP tests so that we can do simple array-driven tests.

Please check that the PR fulfills these requirements

[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)
[x] Add a changelog entry (for non-trivial bug fixes / features)
[ ] CI passes

Log Files
Logs / Second
CPU Average (%)
Memory Average (MB)

1
1000
3.551841
28.312769

1
5000
6.8794727
35.73734

1
10000
10.120906
41.01118

1
50000
38.552593
112.03152

1
100000
70.82805
172.09442

10
100
4.1035595
28.980064

10
500
7.982939
36.55819

10
1000
13.552083
43.048492

10
5000
46.56985
109.94572

10
10000
81.69222
195.79755


Update to 2.8.4, add release docs, version alpha.3

This PR updates cairo to 2.8.4, adds some release docs and updates the version to alpha.3 to prepare for another release.
It also removes a possible panic in case linking fails and renames from_jit and to_jit to from_ptr and to_ptr

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

Project coverage is 88.11%. Comparing base (0b73f1c) to head (25092a0).

Files with missing lines
Patch %
Lines

src/values.rs
88.37%
5 Missing :warning:

src/executor.rs
90.00%
1 Missing :warning:

src/ffi.rs
0.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #835      +/-   ##
==========================================
- Coverage   88.11%   88.11%   -0.01%
==========================================
  Files         123      123
  Lines       34974    34973       -1
==========================================
- Hits        30819    30818       -1
  Misses       4155     4155

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


Digger apply always creates a new plan an applies it

Working with digger I realized that any "digger apply" comment will always create a new plan and apply that one. No matter if a plan already exists.
Steps to reproduce:

Run a digger project
Create a PR
Optional (approve the PR)
Comment "digger apply" -> This will directly apply creating a new plan
Comment "digger plan"
Comment "digger apply" -> Check the action logs and a new plan will appear

Looking closer at the action definition there is no plan download step before running digger/terraform apply. This means that currently digger does not guarantee the integrity of what is reviewed to what is applied. I think this is a pretty serious issue and should be priorized.

Since this issue really bugs me out I had a look at the code and -auto-approve is hardcoded there: https://github.com/diggerhq/digger/blob/develop/pkg/core/terraform/tf.go#L106

I confirmed this issue in my setup too and we are working on the fix now

fixed in https://github.com/diggerhq/digger/pull/610, will be included in the next release


[Feature Request] Using Move in a Layer 2 setup

🚀 Feature Request

Motivation
Scalability of blockchain system has always been a huge concern for the community. As a result, blockchain systems usually relies on a so-called layer 2 sctructure to offload some computation to a less decentralized system in order to get greater throughput. A question then arise, if Move and MoveVM can provide any unique value to the Layer 2 scaling solution? Specifically, how we might put Move ecosystem in the famous 2x2 matrix in the Layer 2 scaling.
Pitch
There are following questions we would like to understand about Move:

How easy would it be to construct a zero-knowledge based solution for Move, either via:
a.  Using existing zk based VM such as MidenVM to execute Move contracts, now that the Move team is working on a cross compiler from Move to Yul
b. Build a VM plugin for MoveVM to support generating traces of MoveVM execution to generate zero knowledge proof of execution correctness?

Moreover, is current zk proof generation process efficient enough for executing Move codes? Can we bring Move to a Validium based roll up solution?

Will the unique account structure of Move bring any unique value to the Plasma framework based solution??

Plasma based protocols are known to be more friendly to a UTXO based scheme as UTXO is naturally easier to prevent double spending on the child network. Moreover, generic smart contracts execution are usually considered not feasiable on Plasma. It would be nice if we have deeper understanding of this issue. Specifically, is it because of the limitation of EVM's state model or it's more of a generic issue that's going to plague the scale-up of Move based ecosystem as well.
Related work
StarCoin has started their optimisitc rollup proposal for a Move ecosystem.
There's also a zk based solution for Move that's been developed here.

On question 2, what intrigues me is the following statement I found in the discussion:

The Plasma framework effectively relies on something I call “state objects.” Each of these objects are pieces of state that can only be modified under certain conditions.

Was wondering if the unique resource model of Move can bring any unqiue value to this known issue.

A couple of thoughts on rollups for Move:

Optimistic: my inclination would be to look into Arbitrum Nitro, which alleges to provide fraud proofs for arbitrary WASM code. Engineering an optimisitic rollup is very challenging, whereas compilation from Move bytecode to WASM is probably not so bad, and might be useful elsewhere. In particular: designing fraud proofs for the verifier seems very difficult, but if you compile the verifier to WASM this problem goes away.
ZK: I know @bobbinth is thinking about supporting Move while designing Miden--definitely something to keep up-to-date on

Moreover, is current zk proof generation process efficient enough for executing Move codes?

Probably not, but it's also incredibly slow for producing execution proofs for existing transaction types or other langs, which is something that the ZK zealots are not always very transparent about...

Will the unique account structure of Move bring any unique value to the Plasma framework based solution??

I think it's possible. However, I think Plasma-based designs have fallen out of favor due to more fundamental design problems that Move can't address. Understanding these problems requires going pretty far into the weeds, but this podcast has an approachable explanation of some of them.

Yes, I'd love to support Move on Miden VM - so, would be very interested in understanding what would be needed from Miden VM side for this. A few notes:

We are currently working on the v0.2 release of Miden VM (in the next branch). This will support everything described in the latest Miden assembly specs. One notable thing that is absent from the v0.2 release is storage, which is slated for v0.3 release.
There is a project for transpiling Yul to Miden assembly called Scribe. If there is work being done on compiling Move into Yul, than it might be possible to do: Move → Yul → Miden assembly. Although, direct compilation Move -> Miden assembly would probably be a better approach.
In terms of performance, Miden VM currently runs at 10K cycles/sec on a single CPU core (this includes ZK proof generation time). This scales pretty well with additional CPUs. For example, on 16 cores it can run at about 100K cycles/sec, and we are working on further improvements to make it faster.

CC @wrwg on the Move -> Yul -> Miden path

Yes, the Move-to-Yul path is expected to be ready (basically) in Q1.

Optimistic: my inclination would be to look into [Arbitrum Nitro](https://medium.com/offchainlabs/arbitrum-nitro-sneak-preview-44550d9054f5), which alleges to provide fraud proofs for arbitrary WASM code. Engineering an optimisitic rollup is very challenging, whereas compilation from Move bytecode to WASM is probably not so bad, and might be useful elsewhere. In particular: designing fraud proofs for the verifier seems very difficult, but if you compile the verifier to WASM this problem goes away.

It is possible to support dispute_resolution in MoveVM, like AVM.


Mysql issue

Hi There,
Do you know why im getting this pls ?
[Doctrine\DBAL\Exception\ConnectionException]
An exception occured in driver: SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Name or service not known
[Doctrine\DBAL\Driver\PDOException]
SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Name or service not known
[PDOException]
SQLSTATE[HY000] [2002] php_network_getaddresses: getaddrinfo failed: Name or service not known
[PDOException]
PDO::__construct(): php_network_getaddresses: getaddrinfo failed: Name or service not known

your database settings are incorrect. Did you use the Docker Compose file included in the repo?

Yeap ... did you try your repo ? something wrong with abe -> mysql ( python ).
Thank you very much for answering me :+1:

Indeed, lots of stuff was broken due to new docker images and a jsonrpc client release. Fixed those. But these were not related to the mysql issue. This seems to work perfectly here.
could you provide a:

docker-compose ps
docker-compose logs mysql

Awesome .!!!  \o/

Sorry disturbing you again .. I got this any idea ? pls ... appreciated your help :-)
PHP Fatal error:  Uncaught TypeError: Argument 3 passed to JsonRPC\Client::__construct() must be an instance of JsonRPC\HttpClient, array given, called in /src/otc/comp/vendor/kunstmaan/libphp-multichain/src/be/kunstmaan/multichain/MultichainClient.php on line 49 and defined in /src/otc/comp/vendor/fguillot/json-rpc/src/JsonRPC/Client.php:66
Stack trace:
#0 /src/otc/comp/vendor/kunstmaan/libphp-multichain/src/be/kunstmaan/multichain/MultichainClient.php(49): JsonRPC\Client->__construct('http://mulichai...', 3, Array)
#1 /src/otc/comp/src/Multichain/Console/Shared/MultichainCommands.php(23): be\kunstmaan\multichain\MultichainClient->__construct('http://mulichai...', 'multichainrpc', 'this-is-insecur...', 3)
#2 /src/otc/comp/src/Multichain/Console/Command/CreateAddressCommand.php(31): Multichain\Console\Command\CreateAddressCommand->connectMultichain()
#3 /src/otc/comp/vendor/symfony/console/Command/Command.php(256): Multichain\Console\Command\CreateAddressCommand->execute(Object(Symfony\Component\Console\Input\ArgvInput), Objec in /src/otc/comp/vendor/fguillot/json-rpc/src/JsonRPC/Client.php on line 66

make sure you do a git pull and a composer update, this error was fixed by my changes yesterday


update dataset at "on_train_epoch_start", but "training_step" still get old data

Bug description
I use trainer.fit(model, datamodule=dm) to start training.
"dm" is an object whose class inherited from pl.LightningDataModule, and in the class, I override the function:
def train_dataloader(self):
    train_dataset = MixedBatchMultiviewDataset(self.args, self.tokenizer,
         known_exs=self.known_train,
         unknown_exs=self.unknown_train,
         feature=self.args.feature)

    train_dataloader = DataLoader(train_dataset,
         batch_size = self.args.train_batch_size,
         shuffle=True, num_workers=self.args.num_workers,
         pin_memory=True, collate_fn=self.collate_batch_feat)

    return train_dataloader

at the model's hook on_train_epoch_start, I update the dataset:
train_dl = self.trainer.train_dataloader
train_dl.dataset.update_pseudo_labels(uid2pl)

loop = self.trainer.fit_loop
loop._combined_loader = None
loop.setup_data()

in the training_step, the batch data is still old data, but trainer.train_dataloader.dataset is new:
def training_step(self, batch: List[Dict[str, torch.Tensor]], batch_idx: int):

    self.mv_model._on_train_batch_start()

    logger.info(self.trainer.train_dataloader.dataset.unknown_feats) # new
    logger.info(batch) # old

What version are you seeing the problem on?
v2.3
How to reproduce the bug
No response
Error messages and logs
# Error messages and logs here please

Environment

Current environment
#- PyTorch Lightning Version (e.g., 2.4.0):
#- PyTorch Version (e.g., 2.4):
#- Python version (e.g., 3.12):
#- OS (e.g., Linux):
#- CUDA/cuDNN version:
#- GPU models and configuration:
#- How you installed Lightning(`conda`, `pip`, source):

More info
No response

hey, thanks for filing the issue. Can you provide a minimal runnable reproduction?


Prepend zero on open.

Fixes #35.

Thanks for your contribution @khamasaki.

No problem, thanks for the merge.


gnome-disks does not see any drives

Version
Version 10.0.19044 Build 19044
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>
Distro Version
21.10
Other Software
No response
Repro Steps
Simply run:
$ gnome-disks&

Expected Behavior
I expected to see the Linux system disk and all mounted disks, at a minimum. For example, this is what a machine natively running the same version of Ubuntu shows. Note that the removable Voyager S3 drive is included (attached via USB).

gnome-disks is useful for backing up images of drives, which can be mounted via loopback. Much better than trying to make a tar from a WSL/WSL2 instance!
Actual Behavior
No disks are shown.

Diagnostic Logs
No response

Thanks for reporting this @mslinn.
This is actually by-design given that WSL2 run in a VM, and block devices aren't accessible from inside the VM (unless you specifically attach them with wsl --mount)
See: https://docs.microsoft.com/en-us/windows/wsl/wsl2-mount-disk

I believe it would be helpful to be able to access the virtual file system as a drive. Administration would be much easier.


Define what "small pieces of state" means

Hi, in the very beginning of the article purpose of durable entities is "define operations for reading and updating small pieces of state".  Could you please clarify what "small" means in this context? Is there any specific criteria to measure how suitable certain entity is for durable entities use case? Are there any limitations or what? Please, add some info about this, if there are any real constraints/guidelines etc. Thanks.

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

ID: 87e12177-bb3a-d00c-99a5-422e00f9b03f
Version Independent ID: 2fa1cf0d-2a5f-2fb0-ef25-bccfac3279fd
Content: Durable entities - Azure Functions
Content Source: articles/azure-functions/durable/durable-functions-entities.md
Service: azure-functions
GitHub Login: @cgillum
Microsoft Alias: azfuncdf

Hi @ironpercival Thanks for your feedback. We will review and update as appropriate.

Hi @ironpercival I have assigned this to content author for further review and update as appropriate.

Durable entities seem to be API sugar around an orchestration that doesn't end. My understanding is that orchestration state is mediated through storage account queues, so "small pieces of state" probably mean "fits in a queue message minus any overhead from the entity/orchestration context".


Webcam doesn't work anymore

Camera is not working anymore in any app.
In the Settings menu Bluetooth & devices > Cameras > HP Webcam 1300, the preview is only showing grey:

Any idea what's happening?

have the same problem. after running bloatynose (great tool, thank you very much!)  camera shows nothing anymore. which setting i have to recover to make it working again?

Simply reactivate app access to the camera. The feature is no longer available with the rebranding and Winpilot anyway.


Won't download on Windows 10

It won't download and keeps bringing up an error message. I've tried running it as an administrator, but it still comes up with the error message. It's was working earlier, but stopped so I re-downloaded it. That's when the error message came up when installing.

NWJS inst compatible with windows 10 right now

Without more information I cant help you, closing


Add frog hopping multiplayer javascript game

Describe the project you want to add with tech stack
I'd add a frog hop javascript game, which is a multiplayer game in which the user would have to attack the enemy's frogs while defending their own. The user would also have the option to choose their opponent as either computer or another player fromg ame settings.
Expected behavior

User starts the game.
User selects either the green frogs or the yellow frogs
Post selection, the remaining frogs are assigned to the second player/computer
User chooses a frog and moves it into the empty spaces.

The one having surviving frogs at the end wins.

Screenshots (optional)

@pranjay-poddar @MohitGupta121 @TusharKesarwani please assign me this


Resources parsed from MPD files dont contain signature for request resulting in a HTTP 403 (DiscoveryPlus)

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

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

Checklist

[X] I'm reporting a bug unrelated to a specific site
[X] I've verified that I'm running yt-dlp version 2022.11.11 (update instructions) or later (specify commit)
[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 the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Provide a description that is worded well enough to be understood
➜  2021.12.17 git:(stable) ./bin/youtube-dl -Uv --no-geo-bypass --cookies discoveryplus.com_cookies.txt https://www.discoveryplus.com/video/homestead-rescue/hardcore-homesteading
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-Uv', '--no-geo-bypass', '--cookies', 'discoveryplus.com_cookies.txt', 'https://www.discoveryplus.com/video/homestead-rescue/hardcore-homesteading']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8
[debug] youtube-dl version 2021.12.17
[debug] Git HEAD: 3748bed37
[debug] Proxy map: {}
It looks like you installed youtube-dl with a package manager, pip, setup.py or a tarball. Please use that to update.
yoooo im here using common downloader
[DiscoveryPlus] homestead-rescue/hardcore-homesteading: Downloading JSON metadata
[DiscoveryPlus] 846793: Downloading JSON metadata
hello there: ext: mpd format_id: dash
[DiscoveryPlus] homestead-rescue/hardcore-homesteading: Downloading MPD manifest
urlh.geturl:https://dplus-northamerica.media-edge.prod-vod.h264.io/82a6a9c8-8581-42f8-b83d-f7aec5daccf5/dash_clear_fmp4/edge-cache-token=Expires=9999999999&KeyName=media-edge-key-prod-northamerica-200d417&Signature=[REDACTED]/master.mpd
Traceback (most recent call last):
  File "/youtube-dl/2021.12.17/./bin/youtube-dl", line 33, in <module>
    sys.exit(load_entry_point('youtube-dl==2021.12.17', 'console_scripts', 'youtube-dl')())
  File "__init__.py", line 475, in main
    _real_main(argv)
  File "__init__.py", line 465, in _real_main
    retcode = ydl.download(all_urls)
  File "YoutubeDL.py", line 2070, in download
    res = self.extract_info(
  File "YoutubeDL.py", line 810, in extract_info
    return self.__extract_info(url, ie, download, extra_info, process)
  File "YoutubeDL.py", line 817, in wrapper
    return func(self, *args, **kwargs)
  File "YoutubeDL.py", line 838, in __extract_info

This bug is related to #4147 but that fix didnt quite resolve the issue.  The signature and expiration from the .mpd file is getting dropped when parsing the xml and appending the resources to the base_url.  I'm not sure what the proper fix is, but I was able to fix it with this kludge of a hack:
    def _extract_mpd_formats(self, mpd_url, video_id, mpd_id=None, note=None, errnote=None, fatal=True, data=None, headers={}, query={}):

[...]
        mpd_base_url = base_url(urlh.geturl())

        mpd_base_url = urlh.geturl().replace("master.mpd", "")

Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
➜  2021.12.17 git:(stable) ./bin/youtube-dl -Uv --no-geo-bypass --cookies discoveryplus.com_cookies.txt https://www.discoveryplus.com/video/homestead-rescue/hardcore-homesteading
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-Uv', '--no-geo-bypass', '--cookies', 'discoveryplus.com_cookies.txt', 'https://www.discoveryplus.com/video/homestead-rescue/hardcore-homesteading']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8
[debug] youtube-dl version 2021.12.17
[debug] Git HEAD: 3748bed37
[debug] Proxy map: {}
It looks like you installed youtube-dl with a package manager, pip, setup.py or a tarball. Please use that to update.
yoooo im here using common downloader
[DiscoveryPlus] homestead-rescue/hardcore-homesteading: Downloading JSON metadata
[DiscoveryPlus] 846793: Downloading JSON metadata
hello there: ext: mpd format_id: dash
[DiscoveryPlus] homestead-rescue/hardcore-homesteading: Downloading MPD manifest
urlh.geturl:https://dplus-northamerica.media-edge.prod-vod.h264.io/82a6a9c8-8581-42f8-b83d-f7aec5daccf5/dash_clear_fmp4/edge-cache-token=Expires=9999999999&KeyName=media-edge-key-prod-northamerica-200d417&Signature=[REDACTED]/master.mpd
Traceback (most recent call last):
  File "/youtube-dl/2021.12.17/./bin/youtube-dl", line 33, in <module>
    sys.exit(load_entry_point('youtube-dl==2021.12.17', 'console_scripts', 'youtube-dl')())
  File "__init__.py", line 475, in main
    _real_main(argv)
  File "__init__.py", line 465, in _real_main
    retcode = ydl.download(all_urls)
  File "YoutubeDL.py", line 2070, in download
    res = self.extract_info(
  File "YoutubeDL.py", line 810, in extract_info
    return self.__extract_info(url, ie, download, extra_info, process)
  File "YoutubeDL.py", line 817, in wrapper
    return func(self, *args, **kwargs)
  File "YoutubeDL.py", line 838, in __extract_info

Is your problem is with yt-dl or yt-dlp? You seem to have pasted your issue https://github.com/yt-dlp/yt-dlp/issues/5663 without regard to the issue template here.
Also...

How is issue 4147 (from either repo) related?
Since the site serves the manifest with the signature, why "redact" it?
For yt-dl, just use -v to get the verbose log.

Sorry for the sloppy issue.
Here's how youtube-dl (from homebrew) fails currently:
youtube-dl -Uv --no-geo-bypass --cookies cookies.txt https://www.discoveryplus.com/video/homestead-rescue/hardcore-homesteading
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-Uv', '--no-geo-bypass', '--cookies', 'cookies.txt', 'https://www.discoveryplus.com/video/homestead-rescue/hardcore-homesteading']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8
[debug] youtube-dl version 2021.12.17
[debug] Git HEAD: 3748bed37
[debug] exe versions: ffmpeg 5.1, ffprobe 5.1, rtmpdump 2.4
[debug] Proxy map: {}
It looks like you installed youtube-dl with a package manager, pip, setup.py or a tarball. Please use that to update.
[DiscoveryPlus] homestead-rescue/hardcore-homesteading: Downloading JSON metadata
[DiscoveryPlus] 846793: Downloading JSON metadata
[DiscoveryPlus] homestead-rescue/hardcore-homesteading: Downloading MPD manifest
WARNING: [DiscoveryPlus] Unknown MIME type image/jpeg in DASH manifest
WARNING: [DiscoveryPlus] Unknown MIME type application/mp4 in DASH manifest
[debug] Default format spec: bestvideo+bestaudio/best
[debug] Invoking downloader on 'https://dplus-northamerica-cloudfront-gcs.prod-vod.h264.io/82a6a9c8-8581-42f8-b83d-f7aec5daccf5/dash_clear_fmp4/x-discovery-token=Expires=[99999]&KeyName=primary&Signature=[REDACTED]/master.mpd'
[dashsegments] Total fragments: 630
[download] Destination: Hardcore Homesteading-846793.fdash-video=9861000.mp4
[download] Got server HTTP error: HTTP Error 403: Forbidden. Retrying fragment 1 (attempt 1 of 10)...
[download] Got server HTTP error: HTTP Error 403: Forbidden. Retrying fragment 1 (attempt 2 of 10)...
[download] Got server HTTP error: HTTP Error 403: Forbidden. Retrying fragment 1 (attempt 3 of 10)...
[download] Got server HTTP error: HTTP Error 403: Forbidden. Retrying fragment 1 (attempt 4 of 10)...
[download] Got server HTTP error: HTTP Error 403: Forbidden. Retrying fragment 1 (attempt 5 of 10)...
[download] Got server HTTP error: HTTP Error 403: Forbidden. Retrying fragment 1 (attempt 6 of 10)...
[download] Got server HTTP error: HTTP Error 403: Forbidden. Retrying fragment 1 (attempt 7 of 10)...
[download] Got server HTTP error: HTTP Error 403: Forbidden. Retrying fragment 1 (attempt 8 of 10)...
[download] Got server HTTP error: HTTP Error 403: Forbidden. Retrying fragment 1 (attempt 9 of 10)...
[download] Got server HTTP error: HTTP Error 403: Forbidden. Retrying fragment 1 (attempt 10 of 10)...
ERROR: giving up after 10 fragment retries
  File "/opt/homebrew/bin/youtube-dl", line 8, in <module>
    sys.exit(main())
  File "/opt/homebrew/lib/python3.9/site-packages/youtube_dl/__init__.py", line 475, in main
    _real_main(argv)
  File "/opt/homebrew/lib/python3.9/site-packages/youtube_dl/__init__.py", line 465, in _real_main
    retcode = ydl.download(all_urls)
  File "/opt/homebrew/lib/python3.9/site-packages/youtube_dl/YoutubeDL.py", line 2068, in download
    res = self.extract_info(
  File "/opt/homebrew/lib/python3.9/site-packages/youtube_dl/YoutubeDL.py", line 808, in extract_info
    return self.__extract_info(url, ie, download, extra_info, process)
  File "/opt/homebrew/lib/python3.9/site-packages/youtube_dl/YoutubeDL.py", line 815, in wrapper
    return func(self, *args, **kwargs)
  File "/opt/homebrew/lib/python3.9/site-packages/youtube_dl/YoutubeDL.py", line 847, in __extract_info
    return self.process_ie_result(ie_result, download, extra_info)
  File "/opt/homebrew/lib/python3.9/site-packages/youtube_dl/YoutubeDL.py", line 881, in process_ie_result
    return self.process_video_result(ie_result, download=download)
  File "/opt/homebrew/lib/python3.9/site-packages/youtube_dl/YoutubeDL.py", line 1692, in process_video_result
    self.process_info(new_info)
  File "/opt/homebrew/lib/python3.9/site-packages/youtube_dl/YoutubeDL.py", line 1970, in process_info
    partial_success = dl(fname, new_info)
  File "/opt/homebrew/lib/python3.9/site-packages/youtube_dl/YoutubeDL.py", line 1915, in dl
    return fd.download(name, info)
  File "/opt/homebrew/lib/python3.9/site-packages/youtube_dl/downloader/common.py", line 366, in download
    return self.real_download(filename, info_dict)
  File "/opt/homebrew/lib/python3.9/site-packages/youtube_dl/downloader/dash.py", line 75, in real_download
    self.report_error('giving up after %s fragment retries' % fragment_retries)
  File "/opt/homebrew/lib/python3.9/site-packages/youtube_dl/downloader/common.py", line 165, in report_error
    self.ydl.report_error(*args, **kargs)
  File "/opt/homebrew/lib/python3.9/site-packages/youtube_dl/YoutubeDL.py", line 628, in report_error
    self.trouble(error_message, tb)
  File "/opt/homebrew/lib/python3.9/site-packages/youtube_dl/YoutubeDL.py", line 590, in trouble
    tb_data = traceback.format_list(traceback.extract_stack())

The issue was referring to and my confusion with cross posting the issue came from google searching the stack trace and finding a related issue on yt-dlp: https://github.com/yt-dlp/yt-dlp/issues/4187
It was fixed with this commit: https://github.com/metayan/yt-dlp/commit/65dd00c13c2eece13e1e73a556400111608befb5
Backporting this commit fixed my issue. I opened a pull request for the backport #31490

That's all much clearer, thanks.


FX Order not saved correctly when modified in reaper

https://kdrive.infomaniak.com/app/share/795671/c884b237-c14b-4d49-bfd6-c8f86286b499

Fixed in 862419f88f462bbac407f37cfade98bd8050709f


Support Request: How to change bot device type from electric outlet to press button

Describe Your Problem
My bots display as electric outlets instead of press buttons. I'd like them to display as press buttons
Relevant log output
No response
Config for homebridge-switchbot
{
    "name": "SwitchBot",
    "credentials": {
        "openToken": "xxx",
        "notice": "Keep your token a secret!"
    },
    "platform": "SwitchBot"
}

Screenshots

Device & Model
switchbot bot
Node.js Version
v16.13.1
NPM Version
v8.3.0
Homebridge Version
v1.3.9
Homebridge SwitchBot Plugin Version
v1.7.0
Homebridge Config UI X Plugin Version
No response
Operating System
Raspbian GNU/Linux Bullseye (11)

There is a StatefulProgrammableSwitch that might work. But I have recently added other device types to the device config that you can look at. What are you using the Bot for?

I am using the bot to press a button in the RFID remote of a garage door. The command should always be PRESS. When the door is open, it closes. When it is closed, it opens with the same press. The second bot does the same thing in another door. I want to control them via a Homepod mini by a single command like PRESS DOOR ONE. Currently, I must previously know the status of the “electric outlet” to say TURN ON DOOR ONE or TURN OFF DOOR ONE even if the actual status of the door is the opposite. Thank  you for your response.

I am using the bot to press a button in the RFID remote of a garage door. The command should always be PRESS. When the door is open, it closes. When it is closed, it opens with the same press. The second bot does the same thing in another door. I want to control them via a Homepod mini by a single command like PRESS DOOR ONE. Currently, I must previously know the status of the “electric outlet” to say TURN ON DOOR ONE or TURN OFF DOOR ONE even if the actual status of the door is the opposite. Thank  you for your response.

My recommendation would be to use Device Type = Door and Garage Door that I have for options for boys. And use switch mode.

The problem is that the device 'remembers' the status. Right now the garage door is closed but the device status is displayed in Home app as 'open'. So, when I say "Hey Siri, open door" it does nothing because it thinks it is already open. Updating this status to match the real world wouldn't work, because often we open/close the door manually using a different RFID remote. It is the same problem for "electric outlet", "door" and "garage door".
There is another problem I don't know how to fix. When I say "Hey Siri, open door" to the Homepod mini, she says "You must go on in your personal device" and then I must confirm the operation in the iPhone. I understand this problem is not related to your plugin, you're doing a great work.

@jdefelice Set mode on not to press in the device settings.

Done! Both switchbots work as expected now! Thank you!
Next step for me will be to get working IR control for TV On/Off and TV Speaker On/Off.
Thanks again!
I will post here my configuration, as it might be useful for other readers:
{
"name": "SwitchBot",
"credentials": {
"openToken": "(my token)",
"notice": "Keep your token a secret!"
},
"options": {
"devices": [
{
"deviceId": "(Mac Address for Switchbot 1)",
"configDeviceName": "Cancela",
"configDeviceType": "Bot",
"bot": {
"mode": "press",
"deviceType": "garagedoor"
}
},
{
"deviceId": "(Mac Address for Switchbot 2)",
"configDeviceName": "Porton",
"configDeviceType": "Bot",
"bot": {
"mode": "press",
"deviceType": "garagedoor"
}
}
]
},
"platform": "SwitchBot"
}


Great lib

Just a heads up that in unity 2018 the type is found in:
asm.GetType("UnityEditor.Experimental.EditorResources");

Not UnityEditorInternal.EditorResourcesUtility where it used to be looking.

great man


Enable/Disable Data Network doesn't work on Android 5.0+

For now this app use hidden API setMobileDataEnabled of ConnectivityManager on Android 2.3+. However, this hidden API is removed on Android 5.0+, so it doesn't work.
I also found an issue on stackoverflow that discuss this:

In Android L 5.xx the hidden API setMobileDataEnabled method is
removed and it can no longer be used. You can verify this in android
lolipop source code under
/frameworks/base/core/java/android/net/ConnectivityManager.java.
If you still insist to perform it, you can use code snippet answered
by Kushal but getDataEnabled is a system api, which normal user
applications cant access. There is also one more system api available
setDataEnabled under TelephonyManager.
(/frameworks/base/telephony/java/android/telephony/TelephonyManager.java)

Also a possible solution here: http://stackoverflow.com/questions/26539445/the-setmobiledataenabled-method-is-no-longer-callable-as-of-android-l-and-later
For now this setting application cannot enable/disable data network, so I suggest adding description of this issue in document network_connection first.

Related: https://github.com/appium/appium-android-driver/issues/98

Should be fixed by https://github.com/appium/io.appium.settings/pull/7. Please try it and see if it works for you. Data connection handling has been implemented exactly the way it is described by http://stackoverflow.com/questions/26539445/the-setmobiledataenabled-method-is-no-longer-callable-as-of-android-l-and-later, which means it won't work on non-rooted devices running Lollipop+ anyway.


[Viborg] Parking data available

See http://portal.opendata.dk/dataset/parkering-viborg the JSON file to use is the one called "Ledige parkeringspladser".

I would like to be assigned to this task.


Convergence error when using run_time_response function

When running the run_time_response function lsim, the integrator is not converging, resulting in NaN values:

Hi there!
I have marked this issue as stale because it has not had activity for 45 days.
Consider the following options:

If the issue refers to a large task, break it in smaller issues that can be solved in
less than 45 days;
Label the issue as wontfix or wontfix for now and close it.

Currently, we are not able to reproduce this issue.
I will close it for now and if we come across this error again we can reopen it.


virtcontainers: Initial import

This is a virtcontainers 1.0.7 import into Kata Containers runtime.
virtcontainers is a Go library designed to manage hardware virtualized
pods and containers. It is the core Clear Containers framework and will
become the core Kata Containers framework, as discussed at
https://github.com/kata-containers/runtime/issues/33
Some additional pointers:
virtcontainers README, including some design and architecure notes:
https://github.com/containers/virtcontainers/blob/master/README.md
virtcontainers 1.0 API:
https://github.com/containers/virtcontainers/blob/master/documentation/api/1.0/api.md
Fixes #40
Signed-off-by: Samuel Ortiz<EMAIL_ADDRESS>

Thanks @sameo. There are a few bits I think we can remove:

Drop the .ci/ as we already have that at the top-level
(we can make changes to those top-level scripts specifically for vc if required potentially later).
I'd consider removing NEWS entirely as it's something else (to forget) to maintain and can be handled via a normal release PR + tag.
Drop .pullapprove.yml + OWNERS as we already have the former at the top-level. We could move OWNERS to the top-level, but again it will need updating with who is in the current top-level .pullapprove.yml so I'd vote we just zap it.
Drop CONTRIBUTING.md and CODE_OF_CONDUCT.md as we have those at the top-level too.

The name "vircontainers" is confusing here since there will be a single unified runtime.
And how to update vircontainers/ when the repo vircontainers is updated?

IMO, I hope there will be two repos.
kata-containers/libkata: a repo  like "vircontainers" or runv/hypervisor.
kata-containers/runkata: the cli repo like cc-runtime or runv/cli.
sandbox, agent, network, hypervisors and persistence as #32 described should be in different packages under kata-containers/libkata.
both vircontainers and runv can be refactored as it.

The name "vircontainers" is confusing here since there will be a single unified runtime.

If you're thinking about something like libkata, I'd disagree. We really want this library to not be kata specific. It's always been a design requirement as a driving function for building properly architectured software.

And how to update vircontainers/ when the repo vircontainers is updated?

See #40 for more details, but the idea is that the virtcontainers repo would be frozen, and kata-containers/runtime/virtcontainers/ becomes the single point of development for virtcontainers. There will be a transition period where we'd have to manually update, but we want to make it as short as possible.

IMO, I hope there will be two repos.
kata-containers/libkata: a repo like "vircontainers" or runv/hypervisor.

A few objections here:

I'd prefer not to call it libkata at that point.
We already have a lot of repos, I was hoping we could refrain ourselves from creating more as virtcontainers is going to be the biggest runtime dependency.
virtcontainers and runc/hypervisor are not comparable.
runc/hypervisor is not a repo.

kata-containers/runkata: the cli repo like cc-runtime or runv/cli.

The only reason why we have not put virtcontainers under clearcontainers/cc-runtime is to make it clear it was not designed to be a Clear Containers/Intel dependent component. Kata Containers is a more neutral organization and it's ok to move it there, but I believe both virtcontainers and the runtime cli should live under the runtime repos:

gitub.com/kata-containers/runtime/virtcontainers (or some more relevant name if there's a consensus about name changing)
github.com/kata-containers/runtime/cli for the actual cli implementation on top of virtcontainers.

We should not forget that a big part of what we build is an OCI compatible runtime and that is mostly defined by the CLI level compatibility.

gitub.com/kata-containers/runtime/virtcontainers (or some more relevant name if there's a consensus about name changing)
github.com/kata-containers/runtime/cli for the actual cli implementation on top of virtcontainers.

This is so good to me. As a core part of kata-runtime, it makes sense to put it directly under runtime/ .
So many repos is starting to make me headache 😛
This is a good start, though there are still many further modifications need to do. LGTM as a first step

@sboeuf @jodh-intel comments addressed

Thanks @sameo
About the CI, we are removing it from virtcontainers since we already have it in the repo. But we need to port what was done in virtcontainers into the kata runtime CI. Particularly, the testing of a PR affecting virtcontainers with Clear Containers. Any PR related to virtcontainers should be tested both for Clear Containers and Kata Containers.

As my comments in #40.
I think we should agree on APIs before merging this PR though I don't want to put a -1 here. I am not saying I don't like the code. I don't like to merge code before the APIs are seriously discussed.

Dope! :) looks good to me

LGTM

So it sounds like there are 2 somewhat conflicting goals:

virtcontainers is a generic library that can be reused outside of the kata runtime
Reduce the maintenance burden of managing 2 repos, in particular the need to keep the vendored dependency in runtime up to date.

Is that an accurate summary? One strategy is to move forward with the approach you have here, but in my experience we'll need to put some strict import restrictions in place (through presubmit tests) that prevent virtcontainers from gradually fusing with the runtime. The alternative approach would be to make it a separate repo, which is a much stronger separation, and automate the task of keeping the runtime repo up-to-date. Either way, I think some automation is required.

@tallclair that's a very clear description of the problem, and that's also the reason why virtcontainers is currently living in its own repo, decoupled from Intel Clear Containers. Unfortunately, the decision of moving this library to the kata-runtime repo has been taken in order to prevent from contributors from confusion...

Adding do-not-merge until everybody agreed.

would you prefer having a separate repo for virtcontainers over moving it under the runtime repo directly?

Both are ok for me. But I prefer putting virtcontainers under runtime directly.

@sameo I would prefer a separate repo.

So to summarize the current state (please correct me if I misunderstood) we have:
@jessfraz is ok with this
@WeiZhang555 is ok with this
@sameo is ok with this (obviously)
@tallclair gives us a fair warning but does not have a strong preference for where it should live.
@gnawux would prefer to see the API discussion going further but does not want to NACK this PR at that point.
@sboeuf is ok with the PR but would prefer to see the virtcontainers code live in a different repo.
@devimc, @amshinde, @jodh-intel, @egernst and @grahamwhaley (All of them are virtcontainers contributors, whatever that means...) have ACKed this PR.
If that's a fair depiction of the current status, I'd like to consider removing the do-not-merge tag and proceed with that PR. Please speak up if you disagree.

@sameo we are going to have the meeting in hours, let's discuss in the meeting. I don't think it is good to merge code before we have an agreement on APIs.

For ALL APIs(related functions, structures, interfaces ...), please add the document // unstable.

We don't need to keep ALL APIs always as they were when the time they were important.
We don't want the initial API block our future progress.
On the other hand, // unstable should be also added when the new APIs are added or current ones are updated. // unstable will be kept until some milestones.

LGTM

Updated to import virtcontainers 1.0.8.
@laijs I will add a specific document explicitly stating that all APIs are alpha (i.e. not stable).

LGTM.
Codes are so many and it's hard to review, but let's trust virtcontainers and use it as our fundamental code base, and keep improving it in following iterations.
We all know these APIs are alpha, and we shouldn't release a 1.0 tag until all requirements we agreed are satisfied . Even without document we still have Github records, that's one nature advantage of a github project :-)

Ok, let the wheel run.