Found JS Errors when running JS fiddle code examples in safari

Logs: TypeError: pc.addStream is not a function. (In 'pc.addStream(displayVideo(stream))', 'pc.addStream' is undefined)
Fixed js error when using safari due to deprecated RTCPeerConnection.addStream() method.
Updated js fiddle examples to use the addTrack() method instead.
https://developer.mozilla.org/en-US/docs/Web/API/RTCPeerConnection/addStream
Description
Reference issue
Fixes #...

Merged, thank you so much for your contributions @jamiegood ! Hope you stay involved, we need all the help we can get :)
63112a4ed409faa923a67c62b8cc2c75dc571590


After Migration Assistant of a .dmg Disk Utility backup from my old Mac (with Yosemite 10.10) to my new Mac (with Sierra 10.12) I get this on any brew command (I tried list, update, doctor, config).
$ brew list
Error: You have not agreed to the Xcode license. Please resolve this by running:
  sudo xcodebuild -license accept

Since even brew list and brew config throw this, I cannot find out which formula has an Xcode dependency.
So either this message should indicate the dependency tree, or the commands that can research the dependency tree should not throw this error.

What is your issue?

@bfontaine sorry, I pressed the enter key on a new Mac and somehow it submitted instead of putting a new line in the description box.

This seems to be printed independently of the formulae you have installed: https://github.com/Homebrew/brew/blob/9cce3414fbd39d146d97911dbb3bf07fffaa1080/Library/Homebrew/brew.sh#L167

Is it possible to "undo" the sudo xcodebuild -license accept in order to test brew.sh script alterations?

If you've got Xcode installed you need to accept the license. As noted, this is not a formula-level requirement.


[Lifecycle] Helm: Update container image repo with the correct location

Description
This PR fixes #2962
Notes for Reviewers
Replaced the image repo with the right address as directed in the comments. :)
Signed commits

[X] Yes, I signed my commits.

@nakul-shahdadpuri will you execute these commands in order to sign-off on your commit? https://github.com/layer5io/meshery/pull/2973/checks?check_run_id=2609990531
Thanks!

On it .

The correction is reflecting now. Fine for me .
Name:         meshery-67d7ddbc8-w72r9
Namespace:    meshery
Priority:     0
Node:         aks-k8sstaging-29265774-vmss000001/<IP_ADDRESS>
Start Time:   Wed, 19 May 2021 11:21:58 +0530
Labels:       app.kubernetes.io/instance=meshery
              app.kubernetes.io/name=meshery
              pod-template-hash=67d7ddbc8
Annotations:  <none>
Status:       Running
IP:           <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  ReplicaSet/meshery-67d7ddbc8
Containers:
  meshery:
    Container ID:   docker://5cbba99eea2f01265ff70f5445f72b3684468bd5d57a393d5306fe055e200b7c```
    Image:          layer5/meshery:stable-latest
    Image ID:       docker-pullable://layer5/meshery@sha256:5314eea136c1b41f058be22235e17e8bf2bc797246309607383824e989a65183
    Port:           8080/TCP
    Host Port:      0/TCP
    State:          Running
      Started:      Wed, 19 May 2021 11:23:09 +0530
    Ready:          True
    Restart Count:  0

yay, @nakul-shahdadpuri! 🎈


[ACR] Fix for acr task credential issue

Description
Contains fix for regression on acr task credentials command

ACR

Please specify the affected command in the PR title.
You can refer to the doc submitting-pull-requests to write the PR title

Could you add some test cases for this change?


parser/serializer for files.xml

Write a parser and serializer for files.xml <-> FilesXml.
Don't expose them via the FilesXml (maybe put them in an internal package, such that they're still accessible if needed), but use them in functions like read (parse xml to object) and save (serialize object to xml).
Make sure that files.xml -> FilesXml -> files.xml results in the same xml as with which you started.

Does this imply a refactoring of FilesXml in the deposit-api? It currently serializes files in a folder to a scala.xml.Elem written to  files.xml by [DepositDir.createXMLs].
DepositDir.createXMLs: https://github.com/DANS-KNAW/easy-deposit-api/blob/fb3ba7db33526f7869fd8fe07b9dfef308bbdae0/src/main/scala/nl.knaw.dans.easy.deposit/DepositDir.scala#L179


Some Exports missing - breaks other flowbite packages

Describe the bug
I realized in one of my new projects that this library is broken for releases > v1.4.3 as some exports are missing like
 export { default as ChevronRightSolid } from "./ChevronRightSolid.svelte"

Working setup:
"dependencies": {
"flowbite": "^2.3.0",
"flowbite-svelte": "^0.44.24",
"flowbite-svelte-blocks": "^1.1.0",
"flowbite-svelte-icons": "^1.4.3",
"flowbite-typography": "^1.0.3"
}
Not working setup
flowbite-svelte-icons >1.4.3
Reproduction
https://github.com/themesberg/flowbite-svelte-icons/compare/v1.4.3...v1.4.4 @shinokada
Version and System Info
v1.4.4

Use ChevronRightOutline.
The upstream repo removed it.
Find all icons at https://flowbite-svelte-icons.codewithshin.com/

Then I guess the flowbite-svelte-blocks is broken as its still referencing the older one.

I just updated flowbite-svelte-blocks. Run:
pnpm i -D flowbite-svelte-blocks@latest


docs: fix magic command usage in ai sample time series forecasting

Related Issues/PRs
None
What changes are proposed in this pull request?
Change magic command usage in sample notebook time series forecasting:

use !pip instead of %pip, since installing only the driver node is enough under this scenario
move package installation part forward just like other sample notebooks.

How is this patch tested?

[x] I have written tests (not required for typo or doc fix) and confirmed the proposed feature/bug-fix/change works.

Does this PR change any dependencies?

[x] No. You can skip this section.
[ ] Yes. Make sure the dependencies are resolved correctly, and list changes here.

Does this PR add a new feature? If so, have you added samples on website?

[x] No. You can skip this section.
[ ] Yes. Make sure you have added samples following below steps.

Find the corresponding markdown file for your new feature in website/docs/documentation folder.
Make sure you choose the correct class estimators/transformers and namespace.
Follow the pattern in markdown file and add another section for your new API, including pyspark, scala (and .NET potentially) samples.
Make sure the DocTable points to correct API link.
Navigate to website folder, and run yarn run start to make sure the website renders correctly.
Don't forget to add <!--pytest-codeblocks:cont--> before each python code blocks to enable auto-tests for python samples.
Make sure the WebsiteSamplesTests job pass in the pipeline.

AB#1981866

/azp run

Codecov Report

Merging #1654 (5a0b5d1) into master (3a160b3) will decrease coverage by 79.50%.
The diff coverage is n/a.

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


Flysystem Adapters Fix

The other filesystems need fixing too.

Eh All the adapters are out of the main repository.

No they're not. Rackspace isn't. Sftp isn't. Dropbox isn't.

http://flysystem.thephpleague.com/upgrade-to-1.0.0/

I thought you meant out as in came from, rather than removed from. Yeh, I know what's been going on. I've contributed to most of them, and spent part of the last two days getting my laravel flysystem wrapper ready. :)

So I guess dependency for flysystem needs to be updated over here.

#55. This whole issue is caused by using g a version constraint with no upper bound.

ye and also we still need to add adapters. So I guess added suggestions to install required adapters. And changed classes.

Done.

Please squash to one commit.

Done

The commit name is wrong, lol. Otherwise, :+1: from me. :)

Lol I renamed commit name.

Oh noes, now we've got a merge commit. Did you forget to force push?

Also, "Flysystem" is spelt like that, without an uppercase "S".

I did git push origin master -f I think it is suppose to be git push -f aargh now I have to fix this

ok Fixed.

:+1:

Thanks to both of you.

@ShawnMcCool This pull actually breaks the test. It seems travis wasn't even running them. I'm working on a fix...

@GrahamCampbell If you ever need a job reference, let me know.

lol

@GrahamCampbell just a heads up, i went ahead and fixed it all

@ShawnMcCool Great. :)


Parser edit functionality + changes to add command regex to allow whitespace in name

Coverage increased (+0.1%) to 84.211% when pulling cb2989e247d0378b88229b4781e54ed075a17eff on parser-edit into de7e5b55cf78ec65ab5e4b6f229fe1100616c116 on master.


feat: implement and test deploy syscall ctor stack trace

This change is

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 77.71%. Comparing base (a8679c0) to head (ae05d41).

Additional details and impacted files
@@                           Coverage Diff                           @@
##           dori/refactor-error-trace-generator    #1849      +/-   ##
=======================================================================
+ Coverage                                77.45%   77.71%   +0.25%
=======================================================================
  Files                                       60       60
  Lines                                     8589     8688      +99
  Branches                                  8589     8688      +99
=======================================================================
+ Hits                                      6653     6752      +99
  Misses                                    1494     1494
  Partials                                   442      442

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

crates/blockifier/src/execution/errors.rs line 399 at r3 (raw file):

            extract_entry_point_execution_error_into_stack_trace(
                error_stack,
                depth,

Why is it not depth+1 here, as in the cases above?
Code quote:
                depth,

crates/blockifier/src/execution/errors.rs line 464 at r3 (raw file):

            extract_entry_point_execution_error_into_stack_trace(
                error_stack,
                depth,

Why is it not depth+1 here, as in the cases above?
Code quote:
                depth,

crates/blockifier/src/transaction/account_transactions_test.rs line 482 at r4 (raw file):
Previously, dorimedini-starkware wrote…
@avi-starkware FYI: this is the test for the same stack trace in the DeployAccount case (non-syscall deployment)

Thanks!

crates/blockifier/src/execution/errors.rs line 399 at r3 (raw file):
Previously, dorimedini-starkware wrote…
the above recursive calls are to extract_syscall_execution_error_into_stack_trace, which is indeed a new depth.
extract_entry_point_execution_error_into_stack_trace extracts the VM portion of the same frame.
Not a perfect setup ATM (why the different behavior on this syscall?), but IMO we shouldn't really redesign until we have a way to test regression against a reconstructed traceback (i.e. the output text should include source code quotes).

Okay. I didn't even see it's a different function.


plugin_not_installed on ios

When you use any functionality, you receive the error message
plugin_not_installed

Please see the example project and follow the installation guide


fix(tekton): add favorite trigger support

PR summary
Add support for favorite triggers in Tekton pipeline
Also includes some minor documentation updates
PR Checklist
Please make sure that your PR fulfills the following requirements:

[x] The commit message follows the Angular Commit Message Guidelines.
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] New tests
[ ] Build/CI related changes
[ ] Documentation content changes
[ ] Other (please describe)

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Does the change of types from Map to List for several parameters not count as a breaking change?

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


Make Claims a concrete type

Currently, claims are represented by a map of string -> string. The historical reason for this was because we didn't know everything we wanted in it. Given how this data has essentially remained unchanged for over a year (and possibly longer), I propose we create a concrete type for claims and start using that instead of a hashmap

This is related to https://github.com/wasmCloud/wasmCloud/issues/508 right?

Closing in favor of https://github.com/wasmCloud/wasmCloud/issues/1093, which includes the dependency chain of types and explains why updating the control interface isn't straightforward today


support for "floating words"

http://logics.emap.fgv.br:10035/repositories/wn30#query/r/floating-words-verbs

excellent.
first  examples of results of this query show:
word-sindicar
http://logics.emap.fgv.br:10035/repositories/wn30#node/<http://arademaker.github.com/wn30-br/instances/word-sindicar>
word-partidarizar
http://logics.emap.fgv.br:10035/repositories/wn30#node/<http://arademaker.github.com/wn30-br/instances/word-partidarizar>
word-metralhar
http://logics.emap.fgv.br:10035/repositories/wn30#node/<http://arademaker.github.com/wn30-br/instances/word-metralhar>
word-burocratizar
http://logics.emap.fgv.br:10035/repositories/wn30#node/<http://arademaker.github.com/wn30-br/instances/word-burocratizar>
actions should be very different:
for burocratizar they don't seem to have the verb with the same root
bureaucracy in english  and red_tape is not a verb, but can be made into
one.
for sindicar the verb syndicate exists, but the meaning is different, so we
need a new synset, but related
for metralhar we simply need to add it to the synset 01136835-v 'shoot
with a machine gun';V2;
On Tue, Jan 20, 2015 at 4:31 AM, Fabricio Rosario<EMAIL_ADDRESS>wrote:

http://logics.emap.fgv.br:10035/repositories/wn30#query/r/floating-words-verbs
—
Reply to this email directly or view it on GitHub
https://github.com/fcbr/cl-wnbrowser/issues/23.

--
Valeria de Paiva
http://www.cs.bham.ac.uk/~vdp/
http://valeriadepaiva.org/

em um pré-proc eu poderia usar http://mymemory.translated.net/en/Portuguese/English/hostilizar para gerar sugestões de synsets

para gerar sugestões de synsets
??? synsets ou glosas?

2015-01-20 13:45 GMT-08:00 Alexandre Rademaker<EMAIL_ADDRESS>
em um pré-proc eu poderia usar
http://mymemory.translated.net/en/Portuguese/English/hostilizar para
gerar sugestões de synsets
—
Reply to this email directly or view it on GitHub
https://github.com/fcbr/cl-wnbrowser/issues/23#issuecomment-70740299.

--
Valeria de Paiva
http://www.cs.bham.ac.uk/~vdp/
http://valeriadepaiva.org/

stats on floating words again, please?

O problema aqui é suporte da interface a localizar as palavras de nominalizações que ainda não estão em nenhum synset. hoje não temos na interface maneira fácil de localizar estas palavras.


phrase pull by specific tag

Hey,
I know that phraseapp pull uses the yml, but sometimes I want that based on the YML configuration, pull only this specific tag (appended to the YML one) without pulling all strings or changing the YML for this, using the same files and not dividing by features.
If we divide by files, it will be a complicate configuration and number of files, as there are several teams with several features working at the same time, so isn't scalable.

This client has been deprecated and the issue moved to the new CLI v2 repo to keep track of the issue

It would be beneficial to have this feature implemented, esp. for a large project with a lot of locales and tags

Is there any update on this issue? We want to use it to generate different translation file depending on the tag given in Phrase.
To enable that, the cli or yaml file needed to have some options for that.
Example: phrase pull --tag Community

We have decided to close all GitHub issues and, instead, handle them through our Customer Support. We think this shift will allow us to offer proper prioritization of issues as well as a more appropriate response time that would be expected from Phrase products.
We apologize for any inconveniences this may cause. If you believe your issue is still relevant or has a high priority, please contact<EMAIL_ADDRESS>and we can take more direct action toward finding a solution.

@egze so, you've closed the public issues tracker, and moved issues handling to the private Customer Support area?
That's quite disappointing 👎


Favor nextest over tarpaulin

Tests run a little faster, but installation takes longer. Ends up taking longer overall!


fix: Ignore includeNotFoundErrors in order to keep visiting the AST

PR Checklist

[x] The PR title follows our guidelines: https://github.com/NativeScript/NativeScript/blob/master/CONTRIBUTING.md#commit-messages.
[] There is an issue for the bug/feature this PR is for. To avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it.
[x] You have signed the CLA.
[x] All existing tests are passing: https://github.com/NativeScript/ios-runtime/blob/master/CONTRIBUTING.md#contribute-to-the-code-base
[ ] Tests for the changes are included.

With llvm 7.0.1 metadata generation may be interrupted by includeNotFound error. Since in 4.0.1 'includeNotFound' errors are ignored for some reason (even though the 'suppressIncludeNotFound' setting is false) here we set this explicitly in order to keep the same behavior

run ci


How to share an image publicly?

Hi.
I'd like to get images published for a Linux distro into Azure in as-close to an official capacity as possible. What does this require? Ideally we would get a platform image similar to other Linux distros that are offered by default to users.
What's the best way to pursue this? Is there public documentation on platform image onboarding? Azure Marketplace doesn't quite seem right since we aren't trying to offer a paid image/service/etc.
Alternatively, if this is not an option, how can a Shared Image Gallery image be shared publicly so that our users may replicate official images without requiring the manual creation and management of storage accounts?
Thanks!

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

ID: 0d150ace-bd6d-8111-79b5-0ce7cb76a378
Version Independent ID: 13a828ae-ae92-9ea7-5f37-5a69eeeb87b7
Content: Azure Shared Image Gallery - Azure Windows Virtual Machines
Content Source: articles/virtual-machines/windows/shared-image-galleries.md
Service: virtual-machines-windows
GitHub Login: @axayjo
Microsoft Alias: akjosh

@colemickens The following document explains how to publish a Virtual Machine image to Azure Marketplace: Virtual Machine Offer Publishing Guide. Please let us know if you have any additional questions.

Okay, thanks, I had misread that page before and took it to only apply to paid offers, but I now see that a freely licensed image would fall under BYOL.
Thanks Mike!

Thanks for sharing the update.


[IMPORTANT] CVE patches

CVE-2024-53269: Happy Eyeballs: Validate that additional_address are IP addresses instead of crashing when sorting.
CVE-2024-53270:  HTTP/1: sending overload crashes when the request is reset beforehand
CVE-2024-53271:  HTTP/1.1 multiple issues with envoy.reloadable_features.http1_balsa_delay_reset

/docs

needs a docs fix
/wait

docs changes look correct to me - i think this must be an existing issue that i saw


Drop older PHP versions

We need to release the new version, which will be the last version that supports older versions (mainly PHP 5.3, potentially PHP 5.4 too). Then the next version will be able to drop the support for older versions.
Once it happens, #104 will become relevant again.

Massive :-1: for this. This tool is to support monitoring code coverage, and disallowing it for 5.3 (or even 5.4) is a big drawback.

You can still use the legacy version as long as we maintain the legacy version, no?

And you never know how long it would be.
And then, what is the real benefits of dropping it?

@keradus
You can casually add this library as a dependency to your project.
But yeah, you may be right. Since we're going to provide a phar file very soon, it (having legacy deps) shouldn't be a big problem.

Legacy deps isn't a problem for other repo since, for example for Symfony's components, one can install 2.3 as well as 3.0 ;) You have just changed it.
So still, it should be allowed to run tool (phared or not) on PHP 5.3.3 ;)

Ok, so I'll drop this plan.

Thank you @tmatsuo


⚠ SceneTime has degraded performance

In d8f628c, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 4178 ms

Resolved: SceneTime performance has improved in 477c885 after 6 minutes.


cliprange_vf is missing

https://stable-baselines.readthedocs.io/en/master/modules/ppo2.html#stable_baselines.ppo2.PPO2
there is a cliprange_vf param in the docuementation.
but I can't find it in code.
https://github.com/openai/baselines/blob/master/baselines/ppo2/ppo2.py#L21
also, the clipping code is using the same cliprange param as the ratio using.
https://github.com/openai/baselines/blob/master/baselines/ppo2/model.py#L69

@shtse8  baselines is no longer maintained. I recommend stable-baselines. https://github.com/hill-a/stable-baselines


Drop-down menu

When I leave that button, the drop-down menu also disappears, which makes it impossible for me to select the contents of the menu

@Brooooooklyn
it seems that the issue is related to #148 ,any idea to fix it?

I'll take a look at it soon

@Brooooooklyn thanks :)


Add frame index to output with metadata.

🚀 The feature
Currently, VideoDecoder.get_frame_at() returns a Frame which has the decoded data as a tensor, the pts in seconds and the duration in seconds. We should also return the frame index.
Motivation, pitch
No response

I did some digging on how to implement this.
Ideally, we would always return the frame index whenever we return a frame and its metadata. Doing that is not as simple as just plumbing some values through, because in the C++, we return a DecodedOutput object whenever we want to return any decoded frame. We can easily add a field in that object for the frame index, but the challenge is that we return this object in situations where we don't (currently) know the frame index, such as getNextFrameNoDemux(). (That is the core of the implementation for the Python core.get_next_frame() function; see the entry point.)
The simplest solution I can think of is to build up a reverse pts-to-index mapping when we scan a file. That would easily enable getNextFrameNoDemux() to cheapy look up the appropriate index for a pts value. (We always know the pts value, because it's part of what FFmpeg gives us when we decode the frame.)
Of course, the challenge here is that we have several entry points that do not currently assume we have scanned the file, and core.get_next_frame() is one of them. We should preserve that. This feature is then connected to our desire for an approximate mode (which we need to create an issue for). In getNextFrameNoDemux(), when we're in exact mode (meaning that we have scanned the file), we can just use the revert pts-to-index mapping. When in approximate mode, we would just do whatever math we do elsewhere.
However, this maybe means we should implement an approximate mode first, before trying to address this issue.

Issue tracking approximate seeking: #427


Support ingest lineage from Flink sql.

One very common use case for Apache Flink is to implement ETL  pipelines  using Flink sql. We could extract lineage metadata from Flink sql and ingest into datahub to explore Flink etl flow.

Hi @wangqinghuan!
We are now managing feature requests through our new portal to improve visibility & prioritize work into our public roadmap. If this request is still relevant, please create a new issue so we can gauge current interest from the Community & prioritize work accordingly.
We'll close out this issue in the meantime. Feel free to reach out to me on DataHub Slack with any questions!


Implement GUI based test for OpenEBS Upgrade using Director

@AmitKumarDas  Till now with the latest release of the director will install the latest EE version of OpenEBS. How can I implement the above test case?
For eg: Director 1.10-ee will install openebs 1.10-ee and so on.

Closing this issue since it will be done through API


Add phpcs support for JavaScript

This is no longer needed.  With recent versions of syntastic it's possible to call checkers for "foreign" filetypes like this: php/phpcs.  You can use that with :SyntasticCheck, you can add it to syntastic_*_checkers etc.

Hey @lcd047, ah no worries, sorry I didn't realise. Should syntax_checkers/css/phpcs.vim be deleted then, since it's available in syntax_checkers/php/phpcs.vim?

No, nothing should be either added or deleted until the async API is finished.

@lcd047 ok, no worries.


Transactional replay

Also, Mutator should disallow transactional writes to non-transactional bases, and vice-versa.


Distinct Pagination (Plugin)

I don't think that the paginator should be running a DISTINCT on a COUNT call. On large tables, this can really slow things down. It should be up to the schema to make sure that the ID is distinct (IMO). If this doesn't make sense, I think the paginator needs some more fetchOptions or something that allow you to disable the COUNT query or allow you to override either the column or the query.

+1 because id attribute is unique, no need to count distinct id.

Any way to use count instead of countDistinct? Maybe make it configurable?


Documentation - Steam Input - getDigitalActionData return keys

Describe the bug
Steam.getDigitalActionData(input_handle, digital_action_handle) returns a two-value Dictionary. In documentation, the keys for the values are state and active. In code, the keys are bState and bActive.
Desktop (please complete the following information):

OS: Windows 11
Version: Build 22621

Version of Godot:
Which version are you using? 4.0.3 Stable Mono
Version of GodotSteam:
GDExtension 4.2.4
Additional context
The actual code appears to work fine, this is merely a documentation error.
Similar documentation errors may exist elsewhere in the SteamInput section; I haven't had a chance to check yet.

Hey there!  So I looked at the code and it is actually wrong there.  The docs are right and the keys should have been state and active instead.  I will fix these in the next GDExtension patch!
Thanks for reporting  this!

Glad to help. Since this will be a breaking change, will there be a blog post of some sort pointing it out?

Yeah, always need to point out things like that.  Saves on people asking what happened.

OK, this is now changed in my local copy and mentioned in the patch notes. It will be noted in the release notes and added to my usual post-patch posts!  Thank you again!


Migration Instructions for cache-manager v6.0.0 with NestJS

I'm facing difficulties migrating to cache-manager v6.0.0 in my NestJS application. Previously, I could type the injected cache manager as Cache, but this type is no longer available in the latest version. Here's a simplified version of the service I’m trying to update:
import { CacheKey, CacheTTL } from "@nestjs/cache-manager";
import { Injectable } from "@nestjs/common";
import axios from "axios";
import { Cache } from "cache-manager";

const CACHE_DURATION = 10 * 60 * 1000; // 10 minutes in milliseconds
const exampleCacheKey = "example-service/cache-key";

@Injectable()
export class ExampleService {
  private readonly cacheManager: Cache;

  constructor(private readonly cache: Cache) {
    this.cacheManager = cache;
  }

  @CacheKey(exampleCacheKey)
  @CacheTTL(CACHE_DURATION) // Cache for 10 minutes
  async getCachedData(): Promise<number> {
    const cachedValue = await this.cacheManager.get<number>(exampleCacheKey);
    if (cachedValue !== undefined) {
      return cachedValue;
    }

    const { data } = await axios.get("https://api.example.com/data");
    const valueToCache = data.someProperty;
    await this.cacheManager.set(exampleCacheKey, valueToCache, CACHE_DURATION);

    return valueToCache;
  }
}

Hi @liuliu-dev - this is brand new and you will need to use the v5 version of cache-manager until they update this library.

you can try using https://www.npmjs.com/package/nestjs-cache-manager-v6

@zhx47 - this looks great. Have you tried to do a pull request against @nestjs/cache-manager with the changes?

@zhx47 - this looks great. Have you tried to do a pull request against @nestjs/cache-manager with the changes?

PR has been submitted and is awaiting review

Yep! Currently, @nestjs/cache-manager supports 5.7.6 as you can see in the package.json
    "cache-manager": "5.7.6",
    "cache-manager-redis-store": "^3.0.1",

Here is the readme for v5: https://github.com/jaredwray/cacheable/blob/main/packages/cache-manager/READMEv5.md
In version 5 cache-manager had its own stores that it supported. In v6 we now are using Keyv as our backend stores.

what worked for me was
 "cache-manager": "^5.7.6",
 "cache-manager-ioredis-yet": "^2.1.2",
 "@nestjs/cache-manager": "^2.2.2",


Minecraft Font not displaying

I just discovered this awesome GRUB theme. Thank you so much!
Everything works fine expect the custom Minecraft font does not load. For all the text GRUB continues to use the base font. I could not find any working solutions so far.
I am using Fedora37 with UEFI-boot.

Hmm, can you cat /boot/grub/grub.cfg | grep pf2  and see if these files actually exist in the file system?
If they do and it doesn't work, you could try to copy them to /boot/grub/fonts, maybe that'll work?

Thanks, I think the problem could originate from my usage of efi-booting. Therefore, my main path is nos /boot/grub/ but /boot/efi/EFI/fedora/ where my grub.cfg and my themes and fonts folder is located.
Here, all fonts are present:
[root@fedora]/boot/efi/EFI/fedora/fonts# pwd
/boot/efi/EFI/fedora/fonts
[root@fedora]/boot/efi/EFI/fedora/fonts# ls -al
total 2384
drwx------. 2 root root    4096 May  3 12:39 .
drwx------. 5 root root    4096 May  3 12:30 ..
-rwx------. 1 root root    6524 May  3 12:38 Minecraft24.pf2
-rwx------. 1 root root    8402 May  3 12:13 Minecraft.pf2
-rwx------. 1 root root   12482 May  3 12:39 Monocraft22.pf2
-rwx------. 1 root root 2394108 May  3 12:13 unicode.pf2

I changed my grub theme default in /etc/default/ to GRUB_THEME="/boot/efi/EFI/fedora/themes/minegrub-theme/theme.txt" and the paths should work fine:
[root@fedora]/boot/efi/EFI/fedora# cat grub.cfg | grep pf2
    font="/root/usr/share/grub/unicode.pf2"
loadfont ($root)/EFI/fedora/themes/minegrub-theme/Minecraft24.pf2
loadfont ($root)/EFI/fedora/themes/minegrub-theme/Minecraft.pf2
loadfont ($root)/EFI/fedora/themes/minegrub-theme/Monocraft22.pf2

If you have any other idea, I would be glad to hear it: otherwise it is not too big of a problem and I like the theme anyway :)

Hey, sorry for the late response, sadly I don't know what causes this. You could maybe press C to open the console while in the grub menu and loadfont /EFI/fedora/themes/minegrub-theme/Monocraft22.pf2 the fonts manually, then close and reopen the console and see if the font changed.
I wouldn't know what to to in either situation tbh, but maybe it helps to find the cause of the problem.
I faintly remember having this problem with my other grub theme (which consisted to 90% of fonts), but sadly i cannot remember how i fixed it.
Also, thanks! I'm happy you enjoy it despite the issue :D

https://github.com/AdisonCavani/distro-grub-themes/issues/101#issuecomment-1423353475


Migration file continues to be created

Describe the bug
Migration file will be created forever after migrate up
Stack trace
...

To Reproduce
Steps to reproduce the behavior:

Modified entity

  @Property()
  @Unique()
  email: string

=>
  @Property({ columnType: 'varchar(255) binary' })
  @Unique()
  email: string

mikro-orm migration:create run
migrate up

  const orm = await MikroORM.init({ ...options, ...{ dbName } })
  try {
    const migrator = orm.getMigrator()
    await migrator.up()
    await orm.close()
  } catch (err) {
    await orm.close()
    throw err
  }

mikro-orm migration:create run again

Expected behavior
No changes required, schema is up-to-date
Additional context
Add any other context about the problem here.
Versions

Dependency
Version

node
14.16.1

typescript
4.0.5

mikro-orm
4.4.4

your-driver
mysql5.7

Already fixed in v5 via #1641, no plans to backport any schema diffing issues as it is pretty much impossible.


create virtual environment for running python script for RDStoRedshiftSqoop sample

This may be worthwhile so that we have more control over the environment we are running in.

This was added in the master readme.md file and is applicable to all samples.


bump: sbt, scripted-plugin 1.7.0 (was 1.5.8)

Updates

org.scala-sbt:sbt
org.scala-sbt:scripted-plugin

from 1.5.8 to 1.7.0.
GitHub Release Notes - Version Diff
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.scala-sbt" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "org.scala-sbt" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #188.


Tags in the tags dropdown cannot be clicked

The tags in the tags dropdowns cannot be clicked - it's impossible to add a tag to a tiddler by clicking.
The culprit is this line:
.tc-tiddler-frame img, .tc-tiddler-frame a:not(.tc-tiddlylink):not(.tc-tiddlylink-external):not(.tc-btn-invisible) {
...
}

Which is a mistake

This is now fixed


Sell items

Hi, is it posiible to sell item to the shop? Or could it be possible?
Thanks

You just set the price to negative value.


Merged HEAD on stash-plugin

This pull-request merges the last version of the stash-plugin, to solve #8 .
Stash containes some webhook functionality, which is not included
Thiss pull-request fixes #8

Let me know if you want this pull-request squashed.

One of the tests seems to fail:
Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 16.075 sec <<< FAILURE! - in InjectedTest
index.jelly(org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyCheck)  Time elapsed: 0.028 sec  <<< ERROR!
org.apache.commons.jelly.JellyException: Could not parse Jelly script : file:/.autofs/homes/users/u0044579/projects/external/jenkins-mattermost-plugin/target/classes/index.jelly
	at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
	at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)
	at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
	at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
	at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
	at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source)
	at org.apache.xerces.impl.XMLDocumentScannerImpl$TrailingMiscDispatcher.dispatch(Unknown Source)
	at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
	at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
	at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
	at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
	at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
	at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
	at org.apache.commons.jelly.parser.XMLParser.parse(XMLParser.java:350)
	at org.apache.commons.jelly.JellyContext.compileScript(JellyContext.java:525)
	at org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyCheck.runTest(JellyTestSuiteBuilder.java:92)

Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 41.972 sec - in jenkins.plugins.mattermost.workflow.MattermostSendStepIntegrationTest

Results :

Tests in error:
  JellyTestSuiteBuilder$JellyCheck.runTest:92 » Jelly Could not parse Jelly scri...

Tests run: 29, Failures: 0, Errors: 1, Skipped: 0

[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:10 min
[INFO] Finished at: 2016-07-14T13:52:24+02:00
[INFO] Final Memory: 47M/886M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.16:test (default-test) on project mattermost: There are test failures.
[ERROR]
[ERROR] Please refer to /.autofs/homes/users/u0044579/projects/external/jenkins-mattermost-plugin/target/surefire-reports for the individual test results.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

When I checkout your PR and run mvn install, I get the following error:
[...]
Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 16.075 sec <<< FAILURE! - in InjectedTest
index.jelly(org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyCheck)  Time elapsed: 0.028 sec  <<< ERROR!
org.apache.commons.jelly.JellyException: Could not parse Jelly script : file:/.autofs/homes/users/u0044579/projects/external/jenkins-mattermost-plugin/target/classes/index.jelly
	at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
	at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(Unknown Source)
	at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
	at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
	at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
	at org.apache.xerces.impl.XMLScanner.reportFatalError(Unknown Source)
	at org.apache.xerces.impl.XMLDocumentScannerImpl$TrailingMiscDispatcher.dispatch(Unknown Source)
	at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
	at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
	at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
	at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
	at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
	at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
	at org.apache.commons.jelly.parser.XMLParser.parse(XMLParser.java:350)
	at org.apache.commons.jelly.JellyContext.compileScript(JellyContext.java:525)
	at org.jvnet.hudson.test.JellyTestSuiteBuilder$JellyCheck.runTest(JellyTestSuiteBuilder.java:92)

Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 41.972 sec - in jenkins.plugins.mattermost.workflow.MattermostSendStepIntegrationTest

Results :

Tests in error:
  JellyTestSuiteBuilder$JellyCheck.runTest:92 » Jelly Could not parse Jelly scri...

Tests run: 29, Failures: 0, Errors: 1, Skipped: 0

[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:10 min
[INFO] Finished at: 2016-07-14T13:52:24+02:00
[INFO] Final Memory: 47M/886M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.16:test (default-test) on project mattermost: There are test failures.
[ERROR]
[ERROR] Please refer to /.autofs/homes/users/u0044579/projects/external/jenkins-mattermost-plugin/target/surefire-reports for the individual test results.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException

OK, silly typo :-) I expected it to be something on my side ...

Yea. Silly typo :)
I guess a failed attempt at committing from idea ;) ctrl-k -> k

Like having ':wq' in a Word document ;-)
Anyway, compiled and deployed to our Jenkins setup. Will test it for a few days and if all is well I will merge the PR after the weekend...

Took another week, but I'm building the release now (and if all goes well, it should be distributed around the world today)


[bug] Using navigator.appVersion for OS type is not reliable enough

Describe the bug
I see you use  navigator.appVersion.includes function to get the operating system type but navigator.appVersion returns "5.0 (X11)" on Firefox 103.0.1 on Linux Mint.
https://github.com/tauri-apps/tauri/blob/679abc6a9a662a10a1c8f358364fdcb9d288f020/tooling/api/src/helpers/os-check.ts#L8
Reproduction
No response
Expected behavior
Linux Mint, Firefox 103.0.1
Platform and versions
Linux Mint
Stack trace
No response
Additional context
No response

I don't really understand? Firefox is irrelevant for Tauri apps. And this code seems to work alright in (webkitgtk) Tauri windows themselves


Re-instate swipeToNavigate for Mac

Per this PR - original setting was
   "workbench.editor.swipeToNavigate": true
I realise that the setting was removed per this but that's a long time ago and it looks like it can be supported with this Electron event
This is a really nice feature of Mac navigation and is supported across a number of apps - including Electron-based, like Slack.

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_smiling_face: This feature request received a sufficient number of community upvotes and we moved it to our backlog. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


Add ability to hide link to extension options page

PR #16 also contains a fix for the Twitter home feed


Assist dev team to get BI hooked to Postgres (ideally replica)

This may not even be possible with our current setup but the dev team would like to hook up their BI tool to the replica instance in staging/production. This probably means to the 172.x.x.x address and will likely require assistance from the CDC firewall team

@jsutantio @adegolier from Jeremy: "sent the request, part of the issue is we do not have a CDC security engineer officially assigned to PRIME - the person we go through is on loan from another group inside the CDC. He was supposed to leave at the end of April but I think will be able to help. Their organization is a real mess."

@jsutantio @adegolier create a Ticket CHG0035387 for CDC to open the firewall from Power BI to Postgres, will provide an update based on the tickets progress

@jsutantio @adegolier As mentioned in chat CDC team has cancelled the Ticket CHG0035387 since they requested to provide non-NAT internal IP address instead of <IP_ADDRESS>
created a new ticket CHG0035441 with the IP of  FQDN from CDC VM where Power BI is installed

@arnejduranovic FYI

@jsutantio @adegolier @arnejduranovic change request CHG0035441  has been updated to closed, could you please check to see if you are able to connect to Postgres from PowerBI

CDC has created a VM with PowerBI installed on the machine, created a new request CHG0036556 to CDC to create connectivity from PowerBI to staging environment.


feat: add default deploy manifest

closes https://github.com/polywrap/wrapscan-registry/issues/2

hey @dOrgJelli I'll take over this PR if it's okay with you. I'll merge it up with the branch in #1813 and continue the work from there.


Add geospatial item to chart

Good morning,
I have now added most properties to an entity and put them on the chart. However, I cannot figure out how to do this for the geospatial entities. Please can you help with this.
The Source is already a Geospatial object, so I expect that this can be easily added as a target property.
My function in ToolView.tsx
const targetProperties: { [key: string]: data.PropertyValue } = {};
        for (const propertyType of entityType.propertyTypes) {

          const sourceProperty = event.properties.find((c: { typeId: any; }) => c.typeId === propertyType.analyzeId);
          if ( sourceProperty ) {
            console.log('Source', sourceProperty);
            console.log('Property', propertyType);
            if ( sourceProperty.value && (propertyType.logicalType === 'singleLineString' || propertyType.logicalType === 'suggestedFromList')){
              console.log('match');
              targetProperties[propertyType.id] = sourceProperty.value;
            } else {
              if ( propertyType.logicalType === 'geospatial'){
                debugger;
                //data.createGeoPoint();
                targetProperties[propertyType.id] = sourceProperty.value;
              }
            }
          }
        }

The error

Hi @sdorresteijn88
Have you had a look at the  app.IValueFactory that has  helper functions for creating a data.IGeoPoint object from either a pair of latitude and longitude values or from a  data.IGeoPointData object.

Cheers

Hi @Anthony-Johnson-i2 ,
I have seen this in the connectors indeed. But I didn't get it to work in the plugin.
import {
  chart,
  data,
  records,
  schema,
  toolview,
} from '@i2analyze/notebook-sdk';
.....
targetProperties[propertyType.id] = data.createGeoPoint(sourceProperty.value.coordinates[1], sourceProperty.value.coordinates[0]);

This gives an error and I don't know what to import.

Using the value factory is the correct approach - however, note that data is just a typing namespace, there's no code (or at least very little) shipped with the @i2analyze/notebook-sdk, it mostly just Typescript types. Instead, the value factory can be found on the mutations object that is passed to you in the runXMutations call, e.g.
api.runTrackedMutation((application, mutations) => {
  const geoPoint = mutations.valueFactory.createGeoPoint(lat, long);
  ...
});

Hi @sdorresteijn88  (Steven)
With Tim's  last reply to you  did you manage to get this figured out?
If so, are you happy for this issue to be closed?
Cheers

Morning @Tim-Mawson-i2 and @Anthony-Johnson-i2,
Thank you very much for your reply. That's the solution indeed, thanks a lot!


Featrue :单据添加自定义TAB

Codecov Report

Merging #480 (584902a) into v2.6.x_develop (a9678af) will decrease coverage by 0.02%.
The diff coverage is n/a.

@@                Coverage Diff                 @@
##           v2.6.x_develop     #480      +/-   ##
==================================================
- Coverage           62.69%   62.67%   -0.03%
==================================================
  Files                 441      441
  Lines               27226    27232       +6
==================================================
- Hits                17070    17067       -3
- Misses              10156    10165       +9

Impacted Files
Coverage Δ

itsm/ticket/permissions.py
35.06% <0.00%> (-1.75%)
:arrow_down:

itsm/ticket/views/ticket.py
47.13% <0.00%> (-0.28%)
:arrow_down:

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 a9678af...584902a. Read the comment docs.


Zooming not working on variant tracks

Variants not being updated when zooming. Below is zoomed into an inton, but the variants are still shown based on their position in the full gene model

Seems to be fixed


fix(tabs): added controllerAs for tab controller

it fixes #5019

This needs tests.

@wesleycho  Done


Error: The argument type 'BuildContext?' can't be assigned to the parameter type 'BuildContext' because 'BuildContext?' is nullable and 'BuildContext' isn't.

Describe the bug
When I run a newly created Getx project, I get this error. This is just a simple default counter app.
`Failed to build iOS app
Error output from Xcode build:
↳
** BUILD FAILED **
Xcode's output:
↳
Writing result bundle at path:
/var/folders/v3/y_zty5cn46n2bg3tpcf2kyjr0000gn/T/flutter_tools.RmZjKi/flutter_ios_build_temp_dirdafpks/temporary_xcresult_bundle
: Error: The argument type 'BuildContext?' can't be assigned to the parameter type 'BuildContext' because 'BuildContext?' is nullable and 'BuildContext' isn't.
../…/src/extension_navigation.dart:77

'BuildContext' is from 'package:flutter/src/widgets/framework.dart' ('../../../../../DevSDKs/flutter/packages/flutter/lib/src/widgets/framework.dart').
package:flutter/…/widgets/framework.dart:1
assert(debugCheckHasMaterialLocalizations(context));
^
Failed to package /Users/nirmal/Documents/Developments/Personal/TestingProjects/Flutter/mvvm_api.
Command PhaseScriptExecution failed with a nonzero exit code
note: Building targets in dependency order
warning: Run script build phase 'Thin Binary' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'Runner' from project 'Runner')
warning: Run script build phase 'Run Script' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'Runner' from project 'Runner')
Result bundle written to path:
/var/folders/v3/y_zty5cn46n2bg3tpcf2kyjr0000gn/T/flutter_tools.RmZjKi/flutter_ios_build_temp_dirdafpks/temporary_xcresult_bundle`

**Reproduction code
import 'package:flutter/material.dart';
import 'package:get/get.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});
  @override
  Widget build(BuildContext context) {
    return GetMaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: const MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({super.key, required this.title});

  final String title;

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  int _counter = 0;

  void _incrementCounter() {
    setState(() {
      _counter++;
    });
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text(widget.title),
      ),
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            const Text(
              'You have pushed the button this many times:',
            ),
            Text(
              '$_counter',
              style: Theme.of(context).textTheme.headline4,
            ),
          ],
        ),
      ),
      floatingActionButton: FloatingActionButton(
        onPressed: _incrementCounter,
        tooltip: 'Increment',
        child: const Icon(Icons.add),
      ),
    );
  }
}

Flutter Version:
Flutter (Channel stable, 3.3.10, on macOS 13.1 22C65 darwin-arm)
Getx Version:
^4.6.5
Describe on which device you found the bug:
iPhone 14 Pro (iOS 16.1)

This is not all code for reproduction. All works ok with part of code you provided, so maybe something wrong wit your MyHomePage. Show all code.

This is not all code for reproduction. All works ok with part of code you provided, so maybe something wrong wit your MyHomePage. Show all code.

My bad. Update the comment.

Code is fully working. I even create new project and ran it on my env - it similar to yours, except iOS on emulator (mine 16.0), my flutter version is also same as yours. Did you tried this on different emulators or android, for example? Just wondering.

Code is fully working. I even create new project and ran it on my env - it similar to yours, except iOS on emulator (mine 16.0), my flutter version is also same as yours. Did you tried this on different emulators or android, for example? Just wondering.

I tried, but I'm getting errors there as well. Error is like this.
Launching lib/main.dart on sdk gphone64 arm64 in debug mode...
lib/main.dart:1
: Error: The argument type 'BuildContext?' can't be assigned to the parameter type 'BuildContext' because 'BuildContext?' is nullable and 'BuildContext' isn't.
../…/src/extension_navigation.dart:77
- 'BuildContext' is from 'package:flutter/src/widgets/framework.dart' ('../../../../../DevSDKs/flutter/packages/flutter/lib/src/widgets/framework.dart').
package:flutter/…/widgets/framework.dart:1

    assert(debugCheckHasMaterialLocalizations(context));
                                              ^

FAILURE: Build failed with an exception.

* Where:
Script '/Users/nirmal/Documents/DevSDKs/flutter/packages/flutter_tools/gradle/flutter.gradle' line: 1159

* What went wrong:
Execution failed for task ':app:compileFlutterBuildDebug'.
> Process 'command '/Users/nirmal/Documents/DevSDKs/flutter/bin/flutter'' finished with non-zero exit value 1

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 28s
Exception: Gradle task assembleDebug failed with exit code 1

I found the solution. I ran flutter pub cache repair command, everything is working fine


[5.8] Get the available user instance.

Helper function to get the available user instance.
If You need to get current user, you can used user() function directly to get user instance.

You've pushed this PR to the 5.7 branch.

You need to rebase your branch,


Testing on Android (Chrome)

[ ] Is palava.tv usable in general?
[ ] Are there WebRTC connection bugs?
[ ] Are there any unpleasant layout bugs?
[ ] Any ideas for improvements on this platform?

@janlelis tried using this with a friend just right now (who's only got an Android Tablet with Chrome installed) and we didn't see each other (both were being told the other one is "disconnected"). He's happy to provide more information if necessary

@pascalwengerter This is probably related to the missing TURN support (see https://github.com/palavatv/signaltower/pull/30, and https://palava.tv/info/about "Important" section), which is the most important issue right now to make palava more reliable


Fix incorrect rendering of right eye on radv

I'm not too familiar with the spec regarding multiview, so perhaps this could be a radv bug.
Sometimes the error isn't noticeable until you tweak the eye separation.
This error occurs with both a Vega 64 and a RX 580.

Can you please check this with current code? The multiview sample had a bug that made it use a wrong render pass that could have caused this issue too.

With the current code in master, the right eye still renders incorrectly.
After applying this PR's change, it renders correctly.

Seems the Vulkan spec requires the framebuffer's layer count to be 1 when multiview is used.
A fix is at https://gitlab.freedesktop.org/mesa/mesa/merge_requests/20


Feature request: scatter/gather implementation for plain ed25519 signatures

In constrained memory systems, it can be very handy to ed25519 sign messages that are readily available and complete, however not available in one contiguous memory. With the current sign() signature, such messages need to be copied into contiguous memory.
An example for this situation is my solokey eddsa support POC https://github.com/solokeys/solo/pull/478.
For illustration, I added a sign2() function in https://github.com/enrikb/salty/tree/feature/scatter-gather-message (just copy and paste of the regular sign()).
Of course, this can also be done for verify(), and also more sophisticated versions like working on a vector of message fragments are possible, following the POSIX readv()/writev() pattern (but maybe not needed that much?).
What do you think about such an API enhancement?

How often do you really have messages in embedded systems that are long enough to make this a necessity?
I have a preference for keeping the API surface simple, but if the use case is valid we can try and do something about it for sure!
In which case spontaneously I think we might want to go all the way and have sign et al. accept a kind of "resettable iterator" (or "clonable iterator") over bytes (a standard iterator won't work since we need it twice). Of course in the C-API it won't look as nice :)
What do you think?

I played around with this a bit (https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=ae7a21ba8cc33631c981872f92408947), and I think at this point I'd favor something like:
fn sign_non_contiguous(message: &[&[u8]]) -> Signature

The hope with this IntoIterator stuff was to find a trait bound that lets the user pass in either a slice or a slice of slices, but either my type fu isn't strong enough or it's not possible. E.g., &T does not implement IntoIter<Item=&T> (which it "could", considering &T as an array of one &T element, but maybe this is a trait coherence issue).

Another attempt: https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=0acfb27e1ca7a1d81994ebc603bf5e88
I'm not happy with having to use .as_ref() on references to byte arrays of known length. I think with const generics we could implement the trait for all [u8; N] (but we don't have them yet), or maybe there's some way to as for AsRef<SliceOrSliceOfSlices>, but I haven't managed.
Maybe the pragmatic choice is to add the _non_contiguous methods separately :)

But the case for the necessity of this API increase still needs to be made by you :)

I have to admit that my wish was maybe driven by an attempt to over optimize. I don't know how tight (stack) memory e.g. on the solokey actually is, just saw one or two comments like 'let's do it like this to save on stack memory'. And being used to the usual init/update/finalize pattern of hashing functions, I thought it might be useful to have something at least close to it for ed25519 signatures, if the non-contiguous message parts can be accessed twice during the signature generation.
I am quite new to Rust, so I had expected that a general/generic solution for multi part messages like you describe above might come at virtually no cost. However, if it makes the common case much 'uglier' like needing all the as_ref()'s, users won't like it and that's not a good option.

I'll leave this open for sure. If I understand correctly, "baby const generics" (https://github.com/rust-lang/lang-team/issues/37) might be released soon, and should make a nice shared API possible.

Looking at https://doc.rust-lang.org/std/io/trait.Write.html#method.write_vectored, maybe such a method could be called sign_vectored.

Sounds like a good match.

Another option: https://docs.rs/iterate/1.0.0/iterate/macro.iterate.html


Pascal case option for export

Is it possible to add support for more case options on export? Specific use case is Pascal case support for typography export on Android

Yes, it's possible. But unfortunately I don't have time to do it. If you know Swift, then feel free to open a PR.


Update app service plan only when necessary

Update app service plan only when necessary, for #1008

Codecov Report

Merging #1022 into develop will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             develop    #1022   +/-   ##
==========================================
  Coverage      38.61%   38.61%
  Complexity       626      626
==========================================
  Files            112      112
  Lines           4695     4695
  Branches         728      728
==========================================
  Hits            1813     1813
  Misses          2735     2735
  Partials         147      147

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 dca749a...30983bb. Read the comment docs.


Create places

Should have attributes and relations corresponding to everything in the Linked Places JSON-LD spec.

[ ] Names (any number of names)
[ ] Geometries (spatial information like lat/long, polygon, eventually: elevation)
[ ] Has and belongs to many Sites (parent, child, sibling)
[ ] Relations to people, organizations, collections, sources, controlled vocabularies
[ ] Timespans
[ ] Types
[ ] Links
[ ] Relations
[ ] Descriptions
[ ] Depictions (imagery, in our case, likely IIIF media)

Closing in favor of https://github.com/performant-software/core-data-cloud/issues/26.


Remove Staff/hidden projects from all statistics

Staff/hidden tasks that are not visible to the public still show up on the main statistics page, which could be a bit confusing.

This will be dealt with when we move over to the pybossa-analyst plugin


All files seem to remain unmodified  (class conversion)

I'm using
\Documents\GitHub> jscodeshift -t react-codemod/transforms/class.js <path to my directory>

but it just does not seem to do anying  - I just get
Processing 281 files...
Spawning 3 workers...
Sending 50 files to free worker...
Sending 50 files to free worker...
Sending 50 files to free worker...
Sending 50 files to free worker...
Sending 50 files to free worker...
Sending 31 files to free worker...
All done.
Results:
0 errors
281 unmodified
0 skipped
0 ok

I'd appreciate any guidance

Try this:
jscodeshift -t react-codemod/transforms/class.js  <path to my directory> --extensions jsx

It worked for me

Thanks for responding, but sadly I'm having no luck.  So a file I would expect to be tranformed.
const MyComponent = React.createClass({
  render() {

    return pug`
      div
        p  Hello
    `;
  },
});

export default MyComponent;

running
 jscodeshift -t ../react-codemod/transforms/class.js --remove-runtime-prototypes=false src\components\mycomponent.js

gives me
Processing 1 files...
Spawning 1 workers...
Sending 1 files to free worker...
All done.
Results:
0 errors
1 unmodified
0 skipped
0 ok
Time elapsed: 1.212seconds

However,  if I add import React from 'react'; to the top of the file then it works.
Trouble is that we declare React as a global variable so do not import  it separately in each file.
I will change the title of this issue - if anyone can suggest anything......

@DeeLindesay try adding --explicit-require=false as a jscodeshift arg. That seemed to work for me. From the code ( https://github.com/reactjs/react-codemod/blob/master/transforms/class.js#L1159 ), it needs either that or ReactUtils.hasReact (which checks for the import), or else it skips the file.

Thank you.  That definitely gets me onto the right track.


tf.Tensor documentation in TF2

System information

TensorFlow version: 2.0 alpha
Doc Link: https://www.tensorflow.org/versions/r2.0/api_docs/python/tf/Tensor

Describe the documentation issue
The documentation of tf.Tensor in the 2.0 section is still about the tf.Tensor as a symbolic tensor that contains the result of a  tf.Operation and it states that the only way to get its value is to use a tf.Session to run the node.
This is no more the truth in tf2:

tf.Session is no more available
tf.Tensor holds the value of the computation and we can extract it using .numpy().

We welcome contributions by users. Will you be able to update submit a PR (use the doc style guide) to fix the doc Issue?
Yes, I can submit a PR if needed - in the PR I can remove any reference to tf.Session and replace the introduction, explaining what is a tf.Tensor in Tensorflow 2.0.

I just want to confirm that whether  we have to remove tf.session() from class Tensor description or from complete ops.py wherever it is ,eigther in description or in function.


ci(dev-to-prod): auto update prod during initial development

:tada: This PR is included in version 1.0.0-alpha.18 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Update scalafmt-core to 3.8.3

About this PR
📦 Updates org.scalameta:scalafmt-core from 3.8.1 to 3.8.3
📜 GitHub Release Notes - Version Diff
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.scalameta", artifactId = "scalafmt-core" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scalameta", artifactId = "scalafmt-core" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:n:3

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

I don't like the fact that _ got replaced by * in Scala 2 sources. Must be something wrong with the config.

Closed in favour of #39


Problems with model_id always defaulting to 1 when being persisted.

Hello,
I experimentally started using the package last night and was attempting to proof of concept what I wanted to accomplish by using artisan tinker... unfortunately I didn't get very far because I realized whenever I create a new model it persists model_id 1 to the database the first time it is persisted.
example using a simple model in a table that has some rows already:
TestModel::create(['name' => 'test', 'content' => 'ha ha']);
will immediately output this as it gets created:
=> TestModel {
     id: 14,
     name: "test",
     content: "ha ha",
     model_id: 14,
     is_current_version: 1,
     created_at: "2016-05-23 22:35:04",
     updated_at: "2016-05-23 22:35:04",
     deleted_at: null,
   }

So everything looks good right?
well the database row that actually got inserted looksl like this:
id: 14, name: test, content: ha ha, model_id: 1, version: 1, is_current_version: 1  etc
as you can see it just inserts 1 as the model_id.  I mean this makes sense to me since you wouldn't know the ID of the model until after it is persisted... so it would require a second save to update the model_id...
It works the same way when I new up a model and save it the traditional way.  I'm wondering is this supposed to be how this behaves?  I'm using php 7, and mariadb 10.  I'm going to take a look at the code and if I can figure out a fix I'll attempt a pull request.
Please let me know if I am just trying to use it wrong or if I missed some part of setup (I looked over the readme several times to check).
Thanks!

So I've looked more into this and I've found that there is something strange going on when trying to update the model_id to the correct value.  Here is the bit of relevant code (part of Versioned)
        // If the model is brand new, we'll insert it into our database,
        // then set the model_id to the id of the newly created record.
        else {
            $this->{static::getIsCurrentVersionColumn()} = 1;
            $saved = $this->performInsert($query, $options);
            $this->{static::getModelIdColumn()} = $this->attributes[$this->primaryKey];
            $saved = $saved && $this->performUpdate($query, $options);
        }

so It sets the model_id column to the value of the primary key column (id), and then it tries to perform the update...  Well I followed the update through Model and did a var dump of the sql and bindings and this is what happens:
>>> $ag = \Aviago\Models\Agreement::create(['name' => '4', 'content' => '4']);
string(117) "insert into `agreements` (`name`, `content`, `is_current_version`, `updated_at`, `created_at`) values (?, ?, ?, ?, ?)"
array:5 [
  0 => "4"
  1 => "4"
  2 => 1
  3 => "2016-05-24 15:08:55"
  4 => "2016-05-24 15:08:55"
]
string(200) "update `agreements` set `name` = ?, `content` = ?, `is_current_version` = ?, `updated_at` = ?, `created_at` = ?, `id` = ?, `model_id` = ? where `model_id` = ? and `agreements`.`is_current_version` = ?"
array:9 [
  0 => "4"
  1 => "4"
  2 => 1
  3 => "2016-05-24 15:08:55"
  4 => "2016-05-24 15:08:55"
  5 => 45
  6 => 45
  7 => 45
  8 => 1
]

As you can see from above... the UPDATE that takes place after the initial insert is wrong... it tries to update WHERE model_id = 45... which will never happen since that is the value we are trying to update in the first place.  It should be trying to use the primary key to update the model_id...  I'm still not sure how to fix this yet, but I'm hoping this helps someone pinpoint how to make the perform update work we want.

Hi there, I will look into this as soon as I can.  It might take me a few days, just to set expectations.  If you figure out more in the meantime, please update this issue.   Patches are also welcome if you figure out a solution.

@sbarre I committed a fix to this issue sometime ago and was wondering if you ever had a chance to review and accept my pull request.
Thanks


GSOD on Insider 17056 + WSL + golang 1.9 PPA

This bug-tracker is monitored by developers and other technical types.  We like detail!  So please use this form and tell us, concisely but precisely, what's up.  Please fill out ALL THE FIELDS!
If you have a feature request, please post to the UserVoice.
Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues. Instead, send dumps/traces to<EMAIL_ADDRESS>referencing the GitHub bug number. Ideally, please configure your machine to capture minidumps, repro the issue, and send the minidump from "C:\Windows\minidump".

Your Windows build number: Microsoft Windows [Version 10.0.17056.1000]

What you're doing and what's happening:  (Copy&paste specific commands and their output, or include screen shots)

Per https://github.com/golang/go/wiki/Ubuntu
$ sudo add-apt-repository ppa:gophers/archive
$ sudo apt update
$ sudo apt-get install golang-1.9-go
Add /usr/lib/go-1.9/bin to $PATH
$ go --version

What's wrong / what should be happening instead:

Green screen of death

Strace of the failing command, if applicable:  (If some_command is failing, then run strace -o some_command.strace -f some_command some_args, and link the contents of some_command.strace in a gist here)

I can try, but since I GSOD I can't capture it. Even my history gets eaten.
See our contributing instructions for assistance.

I'm not able to reproduce this in 1803.


Remove deprecated comment

Currently working on refactoring the changes that I added in https://github.com/stackernews/stacker.news/pull/749/commits/4b95addfcdd0e5488cc1f66998136a5a680db3d0 since I noticed this warning printed in the console in 310011f0:

index.js:86 Warning: Cannot update a component (LNbitsProvider) while rendering a different component (RawWebLNProvider).


Rule that detects unused ports

I think it would be useful to have a rule that checks whether a port is unused. This can crash people's applications, and is also a common problem that beginners run into but do not understand.
If this gets added, I think the package's documentation (in the README and in the elm.json at least) should change to say it's a general review package for rules, one way or another.
Thanks for making this package :heart:

Here's a related issue for reference: https://github.com/elm/compiler/issues/1988

I did some research into what counts as unused as part of developing the rule, here are the findings for the record.
Findings

It does not matter whether the port is returned directly or via other function calls.
Being exposed from a module has no effect on its own.
A port is only made available when:

An outgoing port is returned from an application's update.
An incoming port is returned from an application's subscriptions.

When there are no available ports, app.ports is undefined.
There is no difference with or without --optimize.


feat: add route Handle example

What type of PR is this?

feat: A new feature
What this PR does / why we need it (English/Chinese):

en: add example for Handle
zh: 添加路由注册 Handle 方法的使用示例
Which issue(s) this PR fixes:

Fixes(https://github.com/cloudwego/hertz/issues/392)

LGTM


Fix Georgia trend

After Georgia was flipped, trend number should be flipped too

The algorithm needs to be fixed. Just changing the number in the text file solves nothing.

You're right, should be fixed now though

Fixes #210 by the way

Nice work, @rachetfoot


Slow docbuild

Weirdly, it's only on CI. Locally it's fine

[ ] Figure out why

Maybe start a repo fresh; pkgtemplates mayb.
See if fast there. And if so, gradually add things until it's this repo, see when it becomes slow
Another thing to try: don't use the pkgtemplates sanctified action; rather call the commands that you use locally urself, in the worfklow .yml

(Re

https://github.com/JuliaDocs/Documenter.jl/issues/2002#issuecomment-1367304615

..and the local timings below that)

So adding caching (7c4b7ad) did not help:
https://github.com/tfiers/PkgGraph.jl/actions/runs/3925498405/jobs/6710464373#step:6:1524
(12 minutes for "ExpandTemplates: expanding markdown templates")
Though, the caching might not happen since we do
https://github.com/tfiers/PkgGraph.jl/blob/7c4b7adf05161b5eff4f11b2355a944b01cfe080/.github/workflows/Docs.yml#L30-L32


nix-shell with private ssh too verbose

Issue description
nix-shell when invoked on ssh srcs is too verbose.
Steps to reproduce
Use nix-prefetch-git to manually pull a private source file using an ssh URL. Call nix-shell on a default.nix where src uses fetchGitPrivate, and src.url is of the form ssh://... to the pre-fetched source.
$ nix-shell
trace: Please set your nix-path such that ssh-config-file points to a file that will allow ssh to access private repositories. The builder will not be able to see any running ssh agent sessions unless ssh-auth-sock is also set in the nix-path.

Note that the config file and any keys it points to must be readable by the build user, which depending on your nix configuration means making it readable by the build-users-group, the user of the running nix-daemon, or the user calling the nix command which started the build. Similarly, if using an ssh agent ssh-auth-sock must point to a socket the build user can access.

You may need StrictHostKeyChecking=no in the config file. Since ssh will refuse to use a group-readable private key, if using build-users you will likely want to use something like IdentityFile /some/directory/%u/key and have a directory for each build user accessible to that user.

trace: Please set your nix-path such that ssh-config-file points to a file that will allow ssh to access private repositories. The builder will not be able to see any running ssh agent sessions unless ssh-auth-sock is also set in the nix-path.

Note that the config file and any keys it points to must be readable by the build user, which depending on your nix configuration means making it readable by the build-users-group, the user of the running nix-daemon, or the user calling the nix command which started the build. Similarly, if using an ssh agent ssh-auth-sock must point to a socket the build user can access.

You may need StrictHostKeyChecking=no in the config file. Since ssh will refuse to use a group-readable private key, if using build-users you will likely want to use something like IdentityFile /some/directory/%u/key and have a directory for each build user accessible to that user.

Technical details
nix-shell's man page specifies the following verbosity levels:
       0
           “Errors only”: only print messages explaining why the Nix invocation failed.

       1
           “Informational”: print useful messages about what Nix is doing. This is the default.

       2
           “Talkative”: print more informational messages.

       3
           “Chatty”: print even more informational messages.

       4
           “Debug”: print debug information.

       5
           “Vomit”: print vast amounts of debug information.

I believe the above output should only be displayed for verbosity=1.
PS
I'd be happy to help out with the resolution if this is accepted. Would be a good "dip my toes in" issue.

Unlikely relevant give 2.0 release


Bump mocha from 5.2.0 to 9.1.2

Summary 📖
This PR simply updates mocha from 5.2.0 to 9.1.2
After looking over the CHANGELOG  for mocha, it appears that a lot of the breaking changes will NOT affect this repo (since they were never really used). All tests pass successfully and look good on my end, and I have not seen any deprecation warnings.
NOTE: Mocha version 9 only works with Node 12 and above (Node 12 is currently it LTS). With this in mind, we should begin the transition of only supporting Node 12 and above.
Linked issue(s) 🔗
#17
Will also close #11
Involved parts of the project ⚙
None are affected, only tests are, all of which are currently passing.

@jankapunkt please re-review, I added the new mocha config file.

@HappyZombies @jankapunkt Are you guys cool with me merging these once they're approved?


Failure to build with py11

Expected Behavior
dlib should be able to build with python 3.11
Current Behavior
dib failed to build with newest version of python 3.11.
build.log
Steps to Reproduce
Attempt to build dlib with python 3.11. Provided log above to see the failure.

Version: 19.24
Where did you get dlib: dlib.net via https://src.fedoraproject.org/rpms/dlib/
Platform: Fedora Linux 36
Compiler: gcc 12.2.1

Python 3.11 is not out yet.  The latest release of python is 3.10.

I am aware that python 3.11 will get released on October 22. Fedora Project just used the unreleased python 3.11 on their build system exposing the failure. Additionally, Python 3.11 is in candidate release giving the opportunity address future changes.
In a meanwhile, is there a way to use external pybind11 as it seems the internal version in dlib failed to handle python 3.11?

You can just replace the code in dlib/external/pybind11.   But yes, if there end up being API breaks in python 3.11 when it's fully released we will update pybind11.  I'm fine with updating pybind11 now if you want to send a PR for it.

@luyatshimbalanga, could you try to build again from master (after #2660 or commit https://github.com/davisking/dlib/commit/65bce59a1512cf222dec01d3e0f29b612dd181f5)?

@arrufat The commit successfully built as highlighted by the build.log. Updating pybind11 solved the issue.

I am getting errors with installing dlib v 19.24.1 with python3.10


Arith example

new example of arithmetic.

We'll use this example to demonstrate how omo works with onchain contracts.


Deleted package detected

I'm a Cyber Security researcher and developer of PackjGuard [1] to address open-source software supply chain attacks.
Issue
During my research, I detected a deleted package in this repository.
Details
Specifically, the package creditpy mentioned in file README at line 10 does not exist on the public PyPI registry. A bad actor can hijack this package to propagate malicious code.
Impact
Not only your apps/services using https://github.com/ayhandis/creditpy repo code are vulnerable to this attack, but the users of your open-source Github repo could also fall victim.
You could read more about such attacks here<EMAIL_ADDRESS>Remediation
Please highlight this in file README and register a placeholder package for creditpy on public PyPI soon to remediate.
To automatically fix such issues in future, please install PackjGuard Github app [1].
Thanks!

PackjGuard is a Github app that monitors your repos 24x7, detects vulnerable/malicious/risky open-source dependencies, and creates pull requests for auto remediation: https://github.com/marketplace/packjguard

Hi Ashish, package has been re-uploaded again.


Handling of UTF-8 encoded strings that begin with the sequence U+00FE U+00FF

One of my randomized tests found the following when it created a string "þÿ". I suppose since hitting that string is 1/2^16 it took a while to pop up.
In [16]: as_bytes = 'þÿ abcdefgh'.encode('utf-8')

In [17]: as_bytes
Out[17]: b'\xc3\xbe\xc3\xbf abcdefgh'

# This is fine
In [18]: bytes(pikepdf._qpdf._new_string_utf8(as_bytes))
Out[18]: b'\xfe\xff abcdefgh'

# This is the problem
In [19]: str(pikepdf._qpdf._new_string_utf8(as_bytes))
Out[19]: '\u2061扣摥晧

_new_string_utf8() calls QPDFObjectHandle::newUnicodeString.
bytes() calls QPDFObjectHandle::getStringValue.
str() calls  QPDFObjectHandle::getUTF8Value.
"U+00FE U+00FF" in UTF-8 encodes to c3 b3 c3 bf. We pass that to newUnicodeString, and since all of our code points just happen to be PdfDocEncoding compatible, utf8_to_pdf_doc converts the string to one that begins with fe ff. All fine, this is the correct representation of those code points in pdfdoc.
The trouble is that when we call getUTF8Value, the presence of fe ff triggers that pdfdoc string to be interpreted as UTF-16, returning a corrupted result instead of encoding back to UTF-8. All of the code points get byte-packed, hence the Asian characters.

Yeah, I never thought about that case. This almost feels like it should be part of a puzzle. I guess I need to make sure the byte representation of a string created with newUnicodeString never starts with fe ff (or ff fe since qpdf, like many readers, recognizes UTF16-LE even though not supported in the PDF spec) unless it is stored as UTF-16. I think the same thing would happen with a string that started with ï»¿. Very tricky. I'll probably just hard-code the UTF-8 representations of the sequence of characters fe ff, ff fe, and ef bb bf and make sure to go straight to UTF-16-BE when I see those without attempting pdf doc encoding first. It will be an easy fix. In other words, go straight to UTF-16 when the string starts with any of these byte sequences:

c3 af c2 bb c2 bf
c3 be c3 bf
c3 bf c3 be

While this clearly is a qpdf bug that can be fixed, I'm reminded of this paragraph from the PDF spec, specifically NOTE 3:

For text strings encoded in UTF-16BE, the first two bytes shall be 254 followed by 255. These two bytes represent the Unicode byte order marker, ZERO WIDTH NO-BREAK SPACE (U+FEFF), indicating that the string is encoded in the UTF-16BE (big-endian) encoding scheme specified in Unicode.
...
NOTE 3
This mechanism precludes beginning a string using PDFDocEncoding with the two characters thorn ydieresis, which is unlikely to be a meaningful beginning of a word or phrase.

Actually, a better fix is to make sure that anything that, when transcoding to PDF doc, starts with fe ff, ff fe, or ef bb bf is considered invalid because those are not valid sequences at the beginning of PDF doc encoded strings.

I have a fix in progres -- had about 20 minutes to work on it and will finish up tomorrow. Just mentioning this in case anyone's thinking of fixing with a PR (which isn't necessary since I already have most of the fix).


installation difficulties on linux

with solo user install and multi user install for powerline fonts i have 10-symbols.conf in multiple folders and i am getting lost about wich is effective. Also when you say "replacing PragmataPro with the name of the font you want to use in the terminal " you talk about one of the 4 fonts available in the .buid ?  I'm sorry it seems a stupid question but this is not obvious for me, and i have also to integrate it with Powerlevel9K that is not obvious too. I know when i'll succeed it i'll say it was obvious but now i'm lost and search a little help here after posting a lot of post in askUbuntu ^^
I'll delete this post as fast as i receive an answer that direct me a little as this is not a real issue .... sorry

I also find most of the instruction rather problematic for beginners. I ended up with conf.d files instead of directories. Instructions say what to do step by step but not how to do it and what command to use. Why bother with such instructions (copy this... copy that... run that... copy another) when all you need to do is:

git clone https://github.com/gabrielelana/awesome-terminal-fonts.git
./awesome-terminal-fonts/install.sh
update font name using simple editor like vim or nano
vi ~/.config/fontconfig/conf.d/10-symbols.conf
and replace PragmataPro with FontAwsome (if that's the one you want to use)
echo 'source ~/.fonts/*.sh' >> ~/.zshrc

...
vi ~/.config/fontconfig/conf.d/10-symbols.conf
and replace PragmataPro with FontAwsome (if that's the one you want to use)
...

you meant to write: ... and replace PragmataPro with FontAwesome. Thanks for the instructions, overlooked the handy install script :+1:

@blinkeye thanks, fixed


[SMALLFIX] Add example usage for IndexedSet

@gpang PTAL

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/Tachyon-Pull-Request-Builder/4807/
Test PASSed.

+1 LGTM

Thanks for the document improvement!
You probably need to reopen this PR to merge to master branch though, after #1464 is merged.

@uronce-cc Could you reopen this one to the master branch?

Reopened in https://github.com/amplab/tachyon/pull/1505


Fix deployment target into 8.0 for Carthage support

On trying to use BSImagePicker via Carthage, I faced with the build error:
Module file's minimum deployment target is ios9.0 v9.0: ******/Carthage/Build/iOS/BSImagePicker.framework/Modules/BSImagePicker.swiftmodule/x86_64.swiftmodule

It is because of deployment target written in Pods.xcodeproj .  This pull request resolves the error.

Pods.xcodeproj will be overwritten every time I do a pod update/install. So that is not the way to fix it :/

May this post_install hook be a solution?
https://github.com/CocoaPods/CocoaPods/issues/118

If you want to use the example project for carthage then this is probably a better way of doing it: https://guides.cocoapods.org/syntax/podfile.html#platform

It seems that @takasek 's pull request will work on Carthage.

It probably does, but as I said. Every time I do a pod update/install those changes will be reset.
I linked how you spec deployment_target in the Podfile, that is a fix that I would merge :)
(It will do the same thing as this PR, set deployment target...but the changes will persist after a pod update/install/etc).

If you want to use the example project for carthage

No, I just want to use not the example project but BSImagePicker itself.
To ensure Requirements: iOS 8, the deployment target of the project file in this repository should be altered.
When Carthage checks out and builds the libraries, their project file (*.xcodeproj) determines the deployment targets.
In BSImagePicker's case, _Pods.xcodeproj locks the deployment target into 9.0.  My project supports lower version than iOS 9.0, so I cannot use BSImagePicker so far.
It is why I pushed this pull request.

Your changes are commited to Example/Pods/Pods.xcodeproj/project.pbxproj. 🙂

Add platform :ios, '8.0' to Example/Podfiel.
Run pod update in the Example folder.

This should have the same effect as your commit, with the added benefit of not being reverted back to iOS 9 every time I or any other contributor runs pod update/install.

Alright, so I have done those changes in the hotfix/carthage_ios8 branch.
Could any of you test it and verify that it works? If so I'll merge it and tag a new version.

Your changes are commited to Example/Pods/Pods.xcodeproj/project.pbxproj. 🙂

Yes, because _Pods.xcodeproj is an alias for Example/Pods/Pods.xcodeproj/project.pbxproj .
https://github.com/mikaoj/BSImagePicker/blob/master/_Pods.xcodeproj
I got it.  Adding platform :ios, '8.0' to Example/Podfile is better solution than this PR. 👍

Thanks for bringing my attention to the problem @takasek @akio0911 🙂
It is fixed in version 2.3.1


[3.x] Massive Performance increase of opening the editor

Master branch version: https://github.com/godotengine/godot/pull/57766
In 3.4 there is a performance regression for me where Godot takes >15 seconds to open our project. I found that it Loads some of our 300+ GDScript files many many times in order to compute the EditorResourcePicker::get_allowed_types for Theme, Script, Material and some other simple base types. Then when I open a scene with a new Resource type in it, I get a very noticable lag spike.
Ultimately this lag spike was caused by the change in how EditorResourcePicker was caching it's get_allowed types. Specifically slow is EditorData::script_class_get_base, which would load every single class_name in our GDScript many times. In my testing, I found that even switching the order of 2 of the initialization lines in that previous code would allow the GDScript resources to be cached. I discovered that the old code was even parsing GDScript to find the base class, which seems strange considering that ScriptServer has a very fast answer to what the baseclass of a GDScript file is.
This code change rewrites EditorData::script_class_is_parent to be over 1000x faster by using ScriptServer to find the base class of a Script instead of loading and parsing GDScript.
I have confirmed that the new code produces the exact same result as the old code in our project of over 300 gdscript files, 100 .tres, including Scripted Resources, and many layers of class hierarchy.

Tagging @pycbouh as he worked on EditorResourcePicker

Tagging @willnationsdev as he has worked on some similar features previously.

Looks good to me. This change is probably even part of the massive exportable resources PR that's been waiting around forever. Still, better to add this in now if possible.

I guess this might also be relevant for the master branch?

@akien-mga: Quite possibly - I noticed alpha 1 is noticeably slower than 3.4 to open the same project. I was thinking it was a matter of Vulkan drivers, but it might be this?

@akien-mga: Quite possibly - I noticed alpha 1 is noticeably slower than 3.4 to open the same project. I was thinking it was a matter of Vulkan drivers, but it might be this?

No that wouldn't be related. This PR here fixes a performance issue that affects all Godot versions since class_name was introduced.

I can make the same change for master. Just wanted to get early feedback on this PR because I wasn't sure if I was missing something. I think there's a few function calls in editor_data.cpp that could be optimized through usage of ScriptServer.

Thanks!

Cherry-picked for 3.4.3.