[ASTPrinter] Don't print inferred opaque result type witness

Opaque result type syntax is not usable except the declaration of itself. In other places, users need to let them inferred. If they are inferred associated types, they need to be referred by the name of the associated type.
rdar://problem/59817674

@swift-ci Please smoke test

@swift-ci Please smoke test


Tiled Upscale

Summary
Tiled upscaling is method of upscaling where an image is subdivided into multiple images, with an upscaling pass ran on each image and then masked back together to achieve an upscaled image with lower memory usage than upscaling the entire image in a single pass.
Similar to Ultimate SD Upscaler with Comfy/A111
Intended Outcome

InvokeAI supports tiled upscaling in the Linear UI & in nodes
User should have the ability to choose the number of tiles
User should have the ability to choose the scale factor (up to 8x)

It is also would be great if they also added StableSR support for Tiled Upscale.
StableSR requires an auxiliary model for it (such as webui_768v_139.ckpt), and provides excellent detail

There is a version of this now as part of my xygrid nodes. https://discord.com/channels/1020123559063990373/1133465385182699582
And has been discussed a fair bit in a embiggen thread in the nodes-chat forum on discord. Along with discussion of future updates of seam blending.
It would probably need a bit of work for it to be part of core but it might be as a starting point or at least provide some ideas for discussion.


PPT Support?

Pre-2007 powerpoint

Windows port of ppt/doc/xls to text http://blog.brush.co.nz/2009/09/catdoc-windows/


[gui error report] Error: Initializing daemon...

👉 Please describe what you were doing when this error happened.
Specifications

OS: win32 6.1.7601
IPFS Desktop Version: 0.31.0
Electron Version: 19.1.9
Chrome Version: 102.0.5005.167

Error
Error: Initializing daemon...
Kubo version: 0.23.0
Repo version: 15
System version: amd64/windows
Golang version: go1.21.1
Found outdated fs-repo, migrations need to be run.
Looking for suitable migration binaries.
Need 1 migrations, downloading.
Downloading migration: fs-repo-14-to-15...
Fetching with HTTP: "https://dweb.link/ipfs/QmZPedUiZNe6Gq9oDvoizuuCMVoeb7shwq9xKhysq7exMo/fs-repo-14-to-15/versions"
Fetching with HTTP: "https://dweb.link/ipfs/QmZPedUiZNe6Gq9oDvoizuuCMVoeb7shwq9xKhysq7exMo/fs-repo-14-to-15/versions"
Fetching with HTTP: "https://dweb.link/ipfs/QmZPedUiZNe6Gq9oDvoizuuCMVoeb7shwq9xKhysq7exMo/fs-repo-14-to-15/versions"
Error fetching: exceeded number of retries. last error was http.DefaultClient.Do error: Get "https://bafybeifegu2vs2zm2hup7dawh2mcxvy4zplwyqnwnr6fgymuyfcifqwydi.ipfs.dweb.link/fs-repo-14-to-15/versions": net/http: TLS handshake timeout
Fetching with IPFS: "fs-repo-14-to-15/versions"
Error fetching: context deadline exceeded
could not get latest version of migration fs-repo-14-to-15: 2 errors occurred:
	* exceeded number of retries. last error was http.DefaultClient.Do error: Get "https://bafybeifegu2vs2zm2hup7dawh2mcxvy4zplwyqnwnr6fgymuyfcifqwydi.ipfs.dweb.link/fs-repo-14-to-15/versions": net/http: TLS handshake

It has since upgraded itself...Thanks for the reply...
On Fri, 20 Oct 2023, 07:03 Nishant Arora, <
@.***> wrote:

Thanks for submitting this issue @aspiringdevper, looks like your instance
was unable to upgrade the ipfs repos because either the address was not
reachable. Restarting your instance might fix this. C
DuckDuckGo removed one tracker. More
https://duckduckgo.com/-g8jK5Ffs_bI0Tp3lqy6tYsuSTE6vd7fO0J2foHsSe_0LLk-M0NEYSgGejoyfMjc29w-S1980PGoHEwmNGj4S7pcWeBADHXfkN_oxtgizIuDxAM90F_FL5keBEGZz_ErqjCpEhsksZGZ5ningxwtmJGWmx-TxHYem3JIJOktOcimd4BS6jbCdYa903rLIAYgvRyvKGftvMVNQhvMnih3S8dvD1-dFMneP1ZlCFLNkRpXaX5HnPNNI1XOArUAZD9zbf0c7MHY7UxJxhNSr-6dIfT9EGeKA4axUc6YWJwQA6yIBdA2gKFMYwwW7eJlFn8kAbdC5GQ
Report Spam
https://duckduckgo.com/-g8jK5Ffs_bI0Tp3lqy6tYsuSTE6vd7fO0J2foHsSe_0LLk-M0NEYSgGejoyfMjc29w-S1980PGoHEwmNGj4S7pcWeBADHXfkN_oxtgizIuDxAM90F_FL5keBEGZz_ErqjCpEhsksZGZ5ningxwtmJGWmx-TxHYem3JIJOktOcimd4BS6jbCdYa903rLIAYgvRyvKGftvMVNQhvMnih3S8dvD1-dFMneP1ZlCFLNkRpXaX5HnPNNI1XOArUAZD9zbf0c7MHY7UxJxhNSr-6dIfT9EGeKA4axUc6YWJwQA6yIBdA2gKFMYwwW7eJlFn8kAbdC5GQ
Thanks for submitting this issue @aspiringdevper
https://github.com/aspiringdevper, looks like your instance was unable
to upgrade the ipfs repos because either the address was not reachable.
Restarting your instance might fix this.
Can you try again and see if it works?
—
Reply to this email directly, view it on GitHub
https://github.com/ipfs/ipfs-desktop/issues/2673#issuecomment-1771936845,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BDH3LXBWPCSSPDNK3AG2WI3YAHIG3AVCNFSM6AAAAAA57CWLNSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZRHEZTMOBUGU
.
You are receiving this because you were mentioned.Message ID:
@.***>


Handle lifting of relationships between entity types in the same hierarchy

Make InternalRelationshipBuilder.DependentEntityType() and InternalRelationshipBuilder.PrincipalEntityType() not try to invert the relationship
Add InternalRelationshipBuilder.RelatedEntityTypes() that handles inversion, as well as lifting of dependent or principal ends
This avoids ambiguity between lifting and inverting relationships between types in the same hierarchy
Make ForeignKeyPropertyDiscoveryConvention match shadow properties that weren't added by convention

:shipit:


Add new layers on top of BERT but ktrain gives error when trying to fit the model

Hi,
Firstly, thanks for the amazing ktrain.
I tried to add some new layers on top of BERT, but it gave me an error. Could you help me find out how to solve it? Thanks!
Specifically, It is a sentence-pair four-class problem.

I used ktrain to preprocess my text data:

Then, I used transformers and keras to build the model, adding some layers on top of BERT:

Then, I tried to use ktrain to fit the model, but it gave an error:

Hello:
The problem is with your Input layer, I think.    See this notebook for examples:
https://github.com/cerlymarco/MEDIUM_NoteBook/blob/master/Siamese_Dual_BERT/Siamese_Dual_BERT.ipynb
Also, TFBertForSequenceClassification already has a Dense layer on top of TFBertModel.


Fix encoding bug while reading rules.json.

In a Chinese Windows environment, files are by default read using the GBK encoding, which causes issues. This commit fixes the problem.

I will release a new version after adding some rules


My branch

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

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

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

[x] Follow steps from the guidelines for contributing to this repository.

@Srish-ty There are 2 PR's for the same issue. Delete one!!


Add a config entry to put google analytics key

Hi @adamcooke, any reason for closing this ticket?

Sorry. I thought I'd written one! I don't really plan on adding this directly because it also, for many, requires a bunch of extra work to handle cookie acceptance which I didn't want to handle.
Templates can be edited to add this though on a per install basis.

Thanks for the tip @adamcooke, a custom template will do its job.


Is there anyway to force the validator.validateAll() Promise to be rejected for unit testing

Versions:

VueJs: #3.0.1
Vee-Validate: 2.1.0-beta.9

Description:
In my unit:tests I would like to cover the .catch(e) error when the validateAll fails for any reason beside the form validation...  any flag in the validator that could be set to false in order to reject the promise ?
Steps To Reproduce:
sendMessage: function() {
  console.log("sendMessage()...");
  this.$validator
    .validateAll()
    .then(isValid => {
      console.log("VALIDATION RESULT: ", isValid);
      	...
        this.clear();
        return;
      }
      console.log("validation success, form submitted validForm: ");
      this.clear();
      return;
    })
    .catch(e => {
      // catch error from validateAll() promise
      console.log("error validation promise: ", e);
      this.validForm = false;
      this.clear();
      return;
    });
},

It used to be like this, still suggested here #1183 but so far I'm against it. Throwing on validation fail would hide actual dangerous errors from being reported. For example assume you have an async rule that throws due to no connectivity for example. Then your catch would need to inspect the error manually to tell if its a validation error or not.
Validation errors are more common (expected) than something else going wrong. You can read up a full discussion here on that issue #506
For now, if you prefer to throw on errors you can add a method to the prototype:
Validator.prototype.validateAllThrows = function (...args) {
  return this.validateAll(...args).then(result => {
    if (!result) throw new Error('Validation Error');
  });
};

Thanks a lot for clarifying it .   Got your point


Update info on wikis in the different repositories

There is a lot of information distributed across wikis for different repositories. Some information is outdated and some has been replaced by google sheets and others.
The goal of this issue is to:

[ ] Generate an inventory of repositories that have wikis with information and what information they provide
[ ] Specify what information we should provide and where
[ ] Update the wikis

@andrewhercules I'm inclined to let this go. I don't think wikis are regularly used, but they might have some legacy information that might eventually become relevant.
If you think there is value on improving their organisation please comment here. Otherwise, we could close this ticket

I'll check the wikis listed in the wiki spreadsheet but I suspect many are out-dated and no longer used.

Ticket closed as wiki in data_release repo reviewed and because content is outdated and superseded by recent updates, wiki has been hidden and repo archived.
Other GitHub repos have wikis with historical content that can be reviewed and archived as needed.


Add tcp_sink.

Added tcp_sink.

Hi, is there anything preventing this from being merged? Do you need any additional resources?

Thanks for PR and sorry for the huge delay in merging it. Just merged it and released new version 2.0.6 to PyPi.


Improve filler value check w.r.t. finite types

Description:
Consider the following two unions:
const decimal ZERO = 0.0;
const decimal ONE_TWO = 1.2;
const decimal TWO_THREE = 2.3;

type DEC ZERO|ONE_TWO|TWO_THREE;

function testFiniteTypeArrayFill5(int index) returns DEC[] {
    DEC value = 1.2;
    DEC[] ar = [];
    ar[index] = value;
    return ar;
}

and
type LiteralsAndType 1|2|int;

function testUnionArrayFill4(int index) returns LiteralsAndType[] {
    LiteralsAndType value = 1;
    LiteralsAndType[] ar = [];
    ar[index] = value;
    return ar;
}

Both of the above cases result in compile errors saying there's no implicit initial value for the type. However, these actually do have implicit initial values. The check for implicit initial values need to be improved to consider finite types defined using constants and union types which have finite type constituents.

This is still valid after the change to panic at runtime if the list does not have a filler value - now fails at runtime.

@MaryamZi, @pubudu91 I'm trying to understand the issue here,
With regard to the first example, what is the filler value should be?
How do we identify a filler value in such cases?


💡 Updating documentation comments

Checklist

[x] I checked the Contributing Guidelines before creating this request.
[ ] New extensions are written in Swift 5.0.
[ ] New extensions support iOS 8.0+ / tvOS 9.0+ / macOS 10.10+ / watchOS 2.0+, or use @available if not.
[ ] I have added tests for new extensions, and they passed.
[x] All extensions have a clear comments explaining their functionality, all parameters and return type in English.
[ ] All extensions are declared as public.
[ ] I have added a changelog entry describing my changes.

Travis CI build failed caused by Could not set up API to Code Review site for Danger 😅

@cHaLkdusT The danger one maybe is my fault 😅 I'll take a look at it soon :)

🙈🙉🙊


Consider providing the necessary semantics for denoting tab bars for accessibility

Presently, there seems to be no way to mark up custom tab bars with accessibility semantics. As a result, developers resort to simulating them by "stuffing" the accessibility lable with announcements such as:
"Notifications, tab 1 of 3"
Etc.
iOS, Android and web provide ways to denote tab bars to match native accessibility APIs for these platforms. SOme useful resources below:

iOS: iOS accessibility tabBar trait, real-life implementation.
Android: setRoleDescription API
Web: ARIA tabpannel pattern

/CC @goderbauer

When we expose this API in Flutter we should also use it for Flutter's implementation of the Tab bar, which currently also simulates the announcement via labels.
@chunhtai Have you by any chance looked at these more specific tab bar a11y APIs before?
cc @jmagman (iOS) @GaryQian (Android) @yjbanov (web)

no I will have not looked into this before. will have to test if the mentioned APIs work as expected

@hangyujin Can you take a look at this?

That's correct. The drawback of conveying tabs in the label is that the iOS Switch Control focus indicator does not navigate to them... well, only to the selected tab as it has a "programmatically determined state". The rest of the tabs do not have a "programmatically determined role" and so switch control is treating them as text nodes.

Providing control types in the label also has the following side effects: they will be fully spelled out on the Braille display regardless of the user configuration. Tangentially, assistive technology has no way of modifying the presentation of such controls to the user since they are forced as part of the label.
FWIW, these APIs are used in both Material iOS and material Android components.

For Android, it seems like this may be able to be solved be adding setting a role description of "Tab" on the AccessibilityNodeInfo. The role description is part of the AccessibilityNodeInfoCompat wrapper class, but it can be manually added to AccessibilityNodeInfo using info.getExtras().putCharSequence("AccessibilityNodeInfo.roleDescription", roleDescription);: AccessibilityNodInfoCompat source. The index announcements such as "1 of 3" should come from the CollectionInfo and CollectionItemInfo. Based on my glance at the AccessibilityBridge for Android, it doesn't look like these are implemented for anything other than scroll views. I think there may be another issue out there for these two properties on Android.
iOS is going to be a little different. It needs the tabbar trait on the parent view with the actual tab controls having the button trait. The parent view with the tabbar trait needs to also be hidden from assistive technology with the child views exposed. The index announcements such as "1 of 3" will be automatically added by VoiceOver.

I composed a list of necessary role we should add
http://flutter.dev/go/semantics-roles
it looks like sooner or later we would need to add tar bar role

/cc @chunhtai. We closed above linked issues in favor of the design document which contains all the widgets for which there were separate issues filed. Please let me know if this is fine or we need to keep them tracking separately.

@darshankawar and @chunhtai - The team at Disney prefers that these all be tracked individually we can communicate incremental progress for each missing role and their associated ARIA properties and keyboard support.

Thanks for the feedback @jcollins-disney
I will reopen them so as to track them separately.

hi darshankawar. We are also interested by this issues. Do you have any information about the roadmap of this ? And do you know where in the Flutter repo we could make a PR to work on one of this topics ?

Do you think we should add role by role or add WE could add a property to add any aria role we pass for web for example ? Could you indicate where the aria mapping is done ?

the mapping i have outlined in this doc http://flutter.dev/go/semantics-roles
The idea is to have an enum like

enum SemanticsRole {
   tabBar,
   tab,
   tabList
   list,
   listItem,
  ...
}

// And then you can do

Semantics(
  role: SemanticsRole.tabBar
)

Ok like the button role ? And then where the mapping for the web component is done ?


Fix a private-in-public error

Not sure if this crate is abandoned or not, but it was broken by a bugfix in rustc (see https://tools.taskcluster.net/task-inspector/#VPC0Q4iFQKO1tX2H-Ubm1w/0 and rust-lang/rust#34537 for more details).
Here's a fix (I also fixed one deprecation warning).

Thanks


Transformer?

Just a suggestion, encoder-decoder are not transformer models. Perhaps add a transformer section too.

Transformer models in this repository refer to deep learning networks.
See architecture for more details on encoder-decoder: https://en.m.wikipedia.org/wiki/Transformer_(machine_learning_model)


Fix LS signature help does not work for unclosed parenthesis

Purpose

Fix LS signature help does not work for unclosed parenthesis

Fixes #16065
Check List

[x] Read the Contributing Guide
[ ] Required Balo version update
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[x] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[x] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

Merging #16209 into jballerina will increase coverage by 0.18%.
The diff coverage is 75.62%.

@@               Coverage Diff                @@
##             jballerina   #16209      +/-   ##
================================================
+ Coverage         31.28%   31.46%   +0.18%
- Complexity         3539     3565      +26
================================================
  Files              1012     1012
  Lines             35014    35121     +107
  Branches           4395     4416      +21
================================================
+ Hits              10953    11051      +98
+ Misses            23073    23068       -5
- Partials            988     1002      +14

Impacted Files
Coverage Δ
Complexity Δ

...langserver/sourceprune/AbstractTokenTraverser.java
100% <100%> (ø)
9 <0> (+1)
:arrow_up:

...alang/langserver/BallerinaTextDocumentService.java
64.61% <100%> (+0.23%)
37 <1> (ø)
:arrow_down:

...ang/langserver/signature/SignatureTreeVisitor.java
75.6% <35.29%> (-7.28%)
28 <0> (ø)

...nalang/langserver/signature/SignatureHelpUtil.java
76.56% <75.7%> (+13.85%)
69 <17> (+31)
:arrow_up:

...lang/langserver/sourceprune/LHSTokenTraverser.java
82.95% <84.61%> (-10.88%)
25 <0> (-5)

...lang/langserver/sourceprune/RHSTokenTraverser.java
89.28% <0%> (-1.79%)
25% <0%> (-1%)

...erinalang/langserver/common/utils/FilterUtils.java
77.33% <0%> (-0.67%)
55% <0%> (-1%)

...ballerinalang/langserver/common/LSNodeVisitor.java
14.03% <0%> (+0.58%)
24% <0%> (+1%)
: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 7426a5c...99639b0. Read the comment docs.


MobileNet config files missing for kMaX-DeepLab

Hi!
I would like to use the MobileNet checkpoints from Simple training strategy section located here:
https://github.com/google-research/deeplab2/blob/main/g3doc/projects/imagenet_pretrained_checkpoints.md
but I can't find a corresponding configuration file here (I only see ResNet and ConvNeXt config files):
https://github.com/google-research/deeplab2/tree/main/configs/coco/kmax_deeplab
May I use the config file kmax_meta_r50_os32.textproto wit the MobileNet checkpoint? If I use ResNet-50 do I have to use this configuration file?
Best regards,
Rubén.

Hi,
Thanks for your interests. We have not tried kMaX with MobileNet backbones, but you may try it by modifying the kmax_meta_r50_os32.textproto and replace the backbone section with MobileNet.
Best,

Thank you. I will try.


feat: AppImage build

Thanks for the project!

I'm working on this feature, I will make pull request ASAP


chore(ui): minor ui changes to support flexibility to components

Describe your changes:
Fixes:

Add support for additional props for gaining more control over components like:

TagsSuggestions
UserAndTeamSelectable
DomainSelectable
TierCard

I worked on ... because ...

Type of change:

[ ] Bug fix
[ ] Improvement
[ ] New feature
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] My PR title is Fixes <issue-number>: <short explanation>
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] For JSON Schema changes: I updated the migration scripts or explained why it is not needed.

Thanks for the changes @chirag-madlani , can we add the test and also check the collate side.

Thanks for reviewing, Pushed unit tests and yes it's verified with Collate side.


Test grafana dashboards

Add syncjenkins container to docker-compose setup.
This allows for easier local setup spin up.

Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

It will help us expedite review of your Pull Request if you tag someone (e.g. @username) to look at it.

R: @pabloem @huygaa11

CC: @swegner


[Breaking Change Request] Remove support for Analyzer based DDC

Intended Change
Remove support for running the Analyzer based DDC from versions of the Dart SDK >= 2.7.0.

Default all invocations of dartdevc to use Kernel based DDC and begin ignoring the -k and --kernel arguments.
Delete the versions of dart_sdk.js compiled by Analyzer based DDC that are distributed with the SDK.

dart-sdk/lib/dev_compiler/amd/dart_sdk.js
dart-sdk/lib/dev_compiler/common/dart_sdk.js
dart-sdk/lib/dev_compiler/es6/dart_sdk.js

Rationale
The Analyzer based DDC is pure technical debt now. None of our supported build systems rely on this implementation and it is unused. It slows down development of the Analyzer team as they must keep it updated when they make breaking API changes.
Expected Impact
The exact number of users affected by this change is unknown but we expect it to be low based on the large groups that we know will not be.
Projects known to break

Projects with a dependency on build_web_compilers: < 2.0.0

Projects that will not be affected

Flutter web projects (never used Analyzer based DDC)
Web projects created by stagehand: ^3.3.2 (published for Dart v2.4 on Jul 3, 2019)
Web projects that depend on AngularDart: ^6.0.0-alpha+1
All Google internal web applications (already migrated to Kernel based DDC)

Migration Steps
The migration path is simple, update your package to depend on build_web_compilers: ^2.0.0 (the latest as of this writing is v2.7.0).

The typical dependency on build_web_compilers does not include any API usage so there should be no breaking changes.

@Hixie @matanlurey @dgrove - Please review and approve.

@devoncarew - it came to my attention that this may affect flutter dartpad as well - I believe you were already aware, but let us know if there is any need to wait or if we can move forward.

Flutter does not use the analyzer based DDC and should not be affected by this chagne.

At this point I am swamped with unforking flutter web. I think @RedBrogdon is going to have to take point on looking into getting us off of DDC for normal Dart compilation purposes.

@devoncarew there is now =)

LGTM in principle, modulo practical short term concerns.

Closing the loop: Speaking with @RedBrogdon in person we have confirmed the change migrating flutter pad from "DDC" to "DDK" https://github.com/dart-lang/dart-services/pull/467 has been deployed and the tracking issue has been closed https://github.com/dart-lang/dart-pad/issues/1341.
I'll prepare a change that includes the deletion, thanks everyone! 😄

@nshahan what is the status of this?

We pushed it back until D28 but It's underway. I have landed the first change that removes the ability to run the analyzer based DDC and stops running our test suite. https://dart-review.googlesource.com/c/sdk/+/127067/12
I have some other changes in progress that will actually delete the source files.

Thanks for following up. The code for analyzer based DDC has been deleted.
https://github.com/dart-lang/sdk/commit/c561a9eacc1b3d0a93980ef5119f77bf88511a15


Include CloudTrail configuration and CloudWatch alarms

These will trigger notifications when

Root account has activity
Unauthorized API calls are made

👍


kernel: sparse fixes

Fix some issues identified with sparse.
 My bet is that most of these are false positive and would be better addressed in sparse.

checkpatch fails because of sparse output in commit messages:
1: T1 Title exceeds max length (74>72)
5: B1 Line exceeds max length (193>72)

Commit bea9a91309:
4: B1 Line exceeds max length (81>72)```

I can wrap the lines if that's preferred

Just for the record, commit message line length test is the only one that fails.


DASH generateStaticMpd method working not properly

Since shaka-packager renamed flag --generate_static_mpd to --generate_static_live_mpd from version v2.4.0
The method $options->generateStaticMpd() no longer working anymore

Thank you for the report. I have just fixed the bug and now you can update the package:
composer update aminyazdanpanah/php-shaka


Define mapsControllers#index, #show

mapsController#index is in promises (declarative syntax)
We will have to render in maps/index.ejs
mapsController#show is written in async, await. The foundMap is retrieved from api via req.params.id
We will render in maps/show.ejs
Variables in maps/show.ejs
type: foundMap.data,
name: foundMap.data.names[5].name,
locations: foundMap.data.locations

Variables in locations/show.ejs
location: foundLocation.data,
name: foundLocation.data.name,
url: foundLocation.data.url,
region: foundLocation.data.region


Trading type

Added both market and limit orders with best price calculation.
My offers now displays all outstanding offers with the ability to cancel them.

Thanks I’ll update this with a new PR.
Sent from my iPhone

On Jun 5, 2018, at 11:33 PM, Nick DiZazzo<EMAIL_ADDRESS>wrote:
@ndizazzo commented on this pull request.
In BlockEQ/View Controllers/Trade/MyOffersViewController.swift:

@@ -19,30 +21,103 @@ class MyOffersViewController: UIViewController {
}

 func setupView() {

   let offersCellNib = UINib(nibName: OffersCell.cellIdentifier, bundle: nil)

   tableView.register(offersCellNib, forCellReuseIdentifier: OffersCell.cellIdentifier)

   let offerNib = UINib(nibName: OffersCell.cellIdentifier, bundle: nil)

   tableView.register(offerNib, forCellReuseIdentifier: OffersCell.cellIdentifier)

If you conform your OffersCell to ReusableView, NibLoadableView, this can be simplified to tableView.registerCell(type: OffersCell.self)
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.


[Bug]: Etterna Rebirth reliably crashes on "Game Start" on OSX Monterey (12.0.1)

Is there an existing issue for this?

[X] I have searched the existing issues

Contact Details
Reply to the issue, or<EMAIL_ADDRESS>Version Info
Latest available release
What operating system are you seeing the problem on?
macOS
Bug Behavior
The game crashes 100% of the time on pressing Game Start on OSX 12.0.1.
Expected Behavior
The song list should have loaded.
Reproduction Steps

open Etterna from the dock
click "Accept" on the crash logs upload popup
press Enter on "Game Start"
the game crashes and writes a .dmp file to /Applications/Etterna/CrashFiles/completed

Anything else?
Here's a zipfile of three recent crash dumps.
EtternaCrashes.zip
The only thing in Songs is a years-old zenius-i-vanisher dump of In The Groove 1.
All other menus seem to work perfectly; I'm able to modify inputs, navigate the main menu, etc just fine.
A random person on Reddit seems to have had my exact issue two years ago, but left no further context; they were also on a much older version of OSX than I am (unsurprisingly).
I do not know if this has worked before because I've been out of rhythm games for a while and, since leaving and returning, Stepmania stopped working on OSX. So I need new software. :)

the crash reason given for one of these is interestingly related to the notefield preview
https://crash.etterna.dev/crash-reports/88fc97af-a43d-4390-a38b-c5a2a46472f7
do you have any songs installed?

The only thing in Songs is a years-old zenius-i-vanisher dump of In The Groove 1.

I can try pulling new songs from somewhere else if we think it's just a very old format thing?

you could try switching themes
main menu - options - display options - appearance options - theme -> Til Death or Rebirth

Ah, well! Rebirth was what was already selected (and what was crashing), but Til Death gets me to the song selection screen just fine.
Computers! The worst!

hmmmmm

I'm fine if you close this, because I do at least have a workaround now, but I also understand as a fellow software-screamer-atter if you want to keep it open to debug. :p

there are known mac crashes on rebirth and notefieldpreview crashes which both need to be discovered and covered so i will leave this opened until i look at what may have precisely caused it and attempted to cover it up

tried somethin maybe it will be fixed next release 911061a5b1f3f2851965290b9283233682429067


Adds the new account-id type

We've got a new field type for Visualization configuration fields. The CLI supports the new field type, but the UI doesn't yet so this PR is not quite ready to merge. Just getting into place for after we update the Custom Visualizations UI.
Description
Add a short description about the purpose of this PR here.
Reviewer Notes
If there are links or steps needed to test this work, add them here.
Related Issue(s) / Ticket(s)
If there are any related GitHub Issues or JIRA tickets, add links to them here.

issue

Screenshot(s)
If relevant, add screenshots here.
Use Conventional Commits
Please help the maintainers by leveraging the following conventional commit
standards in your pull request title and commit messages.
Use chore

for minor changes / additions / corrections to content.
for minor changes / additions / corrections to images.
for minor non-functional changes / additions to github actions, github templates, package or config updates, etc

git commit -m "chore: adjusting config and content"

Use fix

for minor functional corrections to code.

git commit -m "fix: typo and prop error in the code of conduct"

Use feat

for major functional changes or additions to code.

git commit -m "feat(media): creating a video landing page"

@JuliaNocera This is approved to merge, but it's in a draft state. However, I suggest we actually just get rid of this list in the guide, now that we have reference document, and link to the reference doc. That way we only have to update one doc and others can just link to the source-of-truth.

@JuliaNocera This is approved to merge, but it's in a draft state. However, I suggest we actually just get rid of this list in the guide, now that we have reference document, and link to the reference doc. That way we only have to update one doc and others can just link to the source-of-truth.

@alexronquillo that sounds like a great idea! I'll get that added in here then :)


Could not find method compile() for arguments [com.google.android.gms:play-services-maps:+]

FAILURE: Build failed with an exception.

Where:
Build file '/.../platforms/tempPlugin/nativescript_google_maps_sdk/build.gradle' line: 105

What went wrong:
A problem occurred evaluating root project 'nativescript_google_maps_sdk'.

Could not find method compile() for arguments [com.google.android.gms:play-services-maps:+] on object of type org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.

BUILD FAILED in 5s
Failed to build plugin nativescript-google-maps-sdk :
Error: Command ./gradlew failed with exit code 1

package.json:
{
"name"<EMAIL_ADDRESS>"main": "main.js",
"version": "7.0.6",
"author": "NativeScript Team<EMAIL_ADDRESS>"description": "NativeScript Application",
"license": "SEE LICENSE IN ",
"publishConfig": {
"access": "public"
},
"keywords": [
"nativescript",
"mobile",
"angular",
"{N}",
"template"
],
"repository": "",
"bugs": {
"url": "https://github.com/NativeScript/NativeScript/issues"
},
"dependencies": {
"@angular/animations": "~10.1.0",
"@angular/common": "~10.1.0",
"@angular/compiler": "~10.1.0",
"@angular/core": "~10.1.0",
"@angular/forms": "~10.1.0",
"@angular/platform-browser": "~10.1.0",
"@angular/platform-browser-dynamic": "~10.1.0",
"@angular/router": "~10.1.0",
"@nativescript/angular": "~10.1.0",
"@nativescript/core": "~7.0.0",
"@nativescript/datetimepicker": "2.0.4",
"@nativescript/firebase": "11.1.3",
"@nativescript/geolocation": "^7.0.0",
"@nativescript/theme": "~3.0.0",
"@nstudio/nativescript-floatingactionbutton": "^3.0.4",
"@nstudio/nativescript-tracking-transparency": "^1.0.0",
"nativescript-advanced-webview": "^6.0.0",
"nativescript-google-maps-sdk": "3.0.2",
"nativescript-phone": "^3.0.2",
"nativescript-ui-listview": "^9.0.4",
"nativescript-ui-sidedrawer": "^9.0.3",
"reflect-metadata": "~0.1.12",
"rxjs": "^6.6.0",
"zone.js": "~0.11.1"
},
"devDependencies": {
"@angular/compiler-cli": "~10.1.0",
"@nativescript/android": "7.0.1",
"@nativescript/ios": "7.0.5",
"@nativescript/types": "~7.0.0",
"@nativescript/webpack": "~3.0.0",
"@ngtools/webpack": "~10.1.0",
"typescript": "~4.0.0"
},
"private": "true",
"readme": "NativeScript Application"
}

I have been using this plugin for almost a year now, and have enjoyed using it, but just today after I tried to rebuild the app from scratch, first it complained gradle needs java 11, after switching to java 11, then I am experiencing the same error for this plugin (A problem occurred evaluating root project 'nativescript_google_maps_sdk') . Any help will be appreciated, thanks!

@pvcoelho Just found workaround on this, the error is because this plugin has one dependency defined as
compile "com.google.android.gms:play-services-maps:$googlePlayServicesVersion"
but "compile" is obsolate or removed from gradle 7+, just replace "compile" with "implementation", and that fixed error for my project, you can apply the workaround in file "\node_modules\nativescript-google-maps-sdk\platforms\android\include.gradle"; Need to confirm with plugin author(s) to see if "implementation" is the right replacement or "compileOnly" or "runtimeOnly" is.

Has there been update in getting a permanent fix in for this issue?


delete fast start unit test

Description
Now that fast-start syncs assets by default, this isn't testing anything. Retire the test

Landing to fix tree


Hosting react site on node.js and redirect all pages to index.html

Hi, I'm trying to build a single page progressive web app with full clientside routing. This seemed to work out of the box.
I am hosting my react.js app with node.js on google app engine, and configured it like instructed at:
https://github.com/facebook/create-react-app/blob/master/packages/react-scripts/template/README.md#other-solutions
https://github.com/facebook/create-react-app/blob/master/packages/react-scripts/template/README.md#other-solutions
My site:
https://nodejs-static.appspot.com/
The static files such as js and css are perfectly reachable:
https://nodejs-static.appspot.com/static/css/main.c17080f1.css
As you can see everything loads fine. But if you go into a sub path like:
https://nodejs-static.appspot.com/haha/haha
It will still load the index page (good right?) but whenever it tries to load the js and css files, it will just return the index.html instead of css/js.
https://nodejs-static.appspot.com/haha/static/css/main.c17080f1.css
How do you guys usually prevent this from happening so that it loads the correct js/css on sub paths?
It would be easiest if the create-react-app would give an option for my index.html to just load the css/js/favicon/manifest.json directly from the root of my site regardless on which path it would be (eg: nodejs-static.appspot.com/first or nodejs-static.appspot.com/first/second or nodejs-static.appspot.com/first/second/third)
I have multiple domain names for the site I want to build (for multiple languages) so I wouldn't want to hardcode it.

I found out that simply removing the homepage attribute in my package.json would make the scripts appear like:

Which makes it always load the JS and CSS from the root.


Ticket creation fails when field 'components' cannot be set

Hi,
creating a ticket fails with the error message
Field 'components' cannot be set. It is not on the appropriate screen, or unknown.
Due to Jira permissions I do not have the permission to edit the corresponding screen to allow the field 'components' to be set. Uncommenting the lines
issue.Fields.Components = make([]*jira.Component, 0, len(r.conf.Components))
for _, component := range r.conf.Components {
    issue.Fields.Components = append(issue.Fields.Components, &jira.Component{Name: component})
}

from notify.go solves the problem but it should probably be configurable whether jiralert attempts to set 'components'.

I've wrapped the offending code in an if len(r.conf.Components) > 0 block, so it will now no longer set an empty list of components. I'll try to make a new release soon, but I'm trying to get the other 2 issues solved as well.

Closing as fixed, let me know if you still have problems. Fix is part of release 0.6.

Everything is working fine now. Thanks a lot!


Replace mocha, chai and sinon with jest

mocha, chai, sinon -> jest
nyc (istanbul) -> jest --coverage
coveralls -> codecov
Update path-to-regexp from v2.1.0 to v2.2.0, see changelog

Codecov Report

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

@@           Coverage Diff           @@
##             master   #151   +/-   ##
=======================================
  Coverage          ?   100%
=======================================
  Files             ?      5
  Lines             ?    147
  Branches          ?     44
=======================================
  Hits              ?    147
  Misses            ?      0
  Partials          ?      0

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 dd8ef59...4fa1be6. Read the comment docs.


Feature/move to bcrypt

Not sure what happened here, I wanted this go to our forked Repo.  Sorry about this.

np


chore: update dependencies

Here's the polished version:
Upgrading Dependencies
Due to changes in the dependencies, the following adjustments are required:

Update .env file and remove NODE_ENV to make it compatible with<EMAIL_ADDRESS>Replace import 'windi.css' with import 'virtual:windi.css'
Replace import path from 'path' with import path from 'node:path'

Hey @zhangyuhan2016,
thanks for you work 👏


create a 'divide' operation

This PR creates a "divide" operation, similar to the JOSM gridify plugin. It lets you divide an area into a grid of smaller areas. This is useful for mapping parking spaces, terraced houses, and camp pitches.
You can try it out here. Select an area and press K.
Closes #6988
https://user-images.githubusercontent.com/16009897/157165940-b2f6e20a-c885-4f74-8814-716f912a6c74.mp4

More Examples

Remaining issues:

[ ] needs an icon
[ ] needs a different shortcut instead of K
[ ] Since this operation is only useful for a small number of features it should possibly be hidden by default?

Nifty, this will tempt me to start nanomapping the individual modules of solar panels. 😉
I wonder if it would be possible to replace the two prompts with something more interactive. Perhaps you hit the shortcut key, then move the mouse along the long and short axes to control the number of divisions. It’d be similar to how you can scrub the mouse cursor while rotating a feature, except that this gesture would snap to widths that evenly divide the area. For things like parking spaces, it’d be more convenient to eyeball the right width than to count the divisions manually.

Since this operation is only useful for a small number of features it should possibly be hidden by default?

If we expect this operation to be used somewhat less frequently than, say, the merge operation, how about keeping it available in the context menu for all areas but avoid assigning a keyboard shortcut? It’s becoming ever more difficult to assign memorable single-key shortcuts without modifiers, especially in locales that translate them. Currently, operations’ availability depends on the selected geometry type, but it would be more difficult to communicate to the user that this operation depends on certain tags.

Probably out of scope for this PR, but may be worth considering as a follow up: Would be nice if this supported use of custom dividing line (something like: draw way across area, select both, perform divide operation). Useful for thinks like drawing a footprint and splitting into non-uniform buildings or building parts, or splitting land use to re-tag a section.

Would be nice if this supported use of custom dividing line (something like: draw way across area, select both, perform divide operation). Useful for things like drawing a footprint and splitting into non-uniform buildings or building parts, or splitting land use to re-tag a section.

Vector drawing tools have a similar operation. It isn’t the most discoverable, but it makes a lot of sense once you’re made aware of it, similar to how iD supports punching holes in polygons using the merge operation. In that case, you could even hook it up to the split operation, so you can select an area and a line that cuts across it, but don’t select a vertex, then split the area along the line. It would be quite outside the scope of this PR, but it might be worth considering how to make the UX for this feature consistent with what might be possible for that other feature.

This is looking superb! It'd be nice if it could split based on the bbox instead of the actual nodes, but that can be implemented after this :)
A case where splitting with bbox would be useful:

It would be nice if we could also do this with ways, for if we know there's windows/doors or extensions along a building wall.

It's been 2 years... anything going on?


Fix #5177 by setting MRUBY_CONFIG early

Fix #5177
I'm not sure this is the intended way.
I've just split the two steps:

Calculating MRUBY_CONFIG
Loading MRUBY_CONFIG

... so Rakefile could hook between the 2 steps.

Thank you for the great report!
Basically I agree with the patch. I have a few comments.

After setting MRUBY_CONFIG, we can use load MRUBY_CONFIG, so I don't think load_config method is needed.
mruby_config_path method is usually called only once, so I don't think the result cache is needed. If the result cache is used, we can write @mruby_config_path || = (...), so I don't think _mruby_config_path method is needed either.

Thank you for your detailed feedback.
Tonight I'll fix it (when I get home).
It will be a honor for me to have a PR of mine accepted in mruby! 👍

Dear @shuujii ,
I've just applied your suggestion.
Please tell me if there's something more I should do.


Add CDK instance constraint overlays

Ensure that all CDK instances end up in the same availability zone.

We can close this now in favor of #80, right?

@johnsca: Yep, closing in favor of #80


38 page size change

Fixes issue #38 by clearing all live monitoring when changing the page size. Fixes issue #44 by respecting inactive checkboxes.
To test the second fix, search *. Change page size to 20 and toggle to page 12 (PVs 241-260). This is a page with some active and some inactive checkboxes. Page 11 has all active checkboxes and page 13 has all inactive checkboxes, for further testing.

looks great!


kubectl exec and kubectl logs -f hang

examples: kubectl exec -it pod1 bash, kubectl logs -f pod1

Thanks! Confirmed: These are the features Kui is missing to support.

splitting this out into two separate issues


dpad_y and left_y Data Values Swapped

When running the best_default_program in tank mode, we've found that tank mode works with the right motor being controlled with the right stick like intended, but the left motor is being controlled by the dpad, not the left stick. We've identified that the problem can be found in line 97,
motor_left.throttle = map_range(gizmo.axes.left_y, 0, 255, -1.0, 1.0)

We've found that this problem can be fixed by changing line 97 to look like this,
motor_left.throttle = map_range(gizmo.axes.dpad_y, 0, 255, -1.0, 1.0)

Changing left_y to dpad_y makes the left stick control the left drive motor like intended. We've found that in circuitpython_gizmo.py in lines 75-80 some data values need to be switched to make the original best default code work as intended,
self.left_x = data[0]
self.left_y = data[1]
self.right_x = data[2]
self.right_y = data[3]
self.dpad_x = data[4]
self.dpad_y = data[5]

The data values 5 and 1 need to be switched to make the code work as intended as the data values currently are switched resulting in the problem.

Please check whether the Mode light on your gamepad is on (just below the Logitech logo button, next to the button labeled "MODE"). The Mode button toggles swapping the Dpad and left joystick. When the green light is on, the two inputs will be swapped, so pressing the Dpad will show up as moving the left joystick, and vice-versa. You can verify this behavior by connecting your gamepad to a computer and going to https://hardwaretester.com/gamepad.
The lines you've referenced in the CircuitPython library are correct as is. They must match the order the inputs are packed in the system processor firmware. That happens here:
gizmo.cpp line 607:
  cstate.Axis0 = cstateJSON["AxisLX"];
  cstate.Axis1 = cstateJSON["AxisLY"];
  cstate.Axis2 = cstateJSON["AxisRX"];
  cstate.Axis3 = cstateJSON["AxisRY"];
  cstate.Axis4 = cstateJSON["AxisDX"];
  cstate.Axis5 = cstateJSON["AxisDY"];


add sphinx_autodoc_typehints and list (default) napoleon settings

Changes
add sphinx-autodoc-typehints with default config
will move type-hints from function arguments to parameter field (if no explicit parameter type given in docstring)
similar behavior possible with "sphinx.ext.autodoc.typehints" setting autodoc_typehints = "description" (formatting not as nice)
Related Issues
Closes # (add issue numbers)
Checks

[x] updated CHANGELOG.md
[x] updated tests
[x] updated doc/
[x] update example/tutorial notebooks

So if I got this correctly, we can remove all type hints from the docstrings?

So if I got this correctly, we can remove all type hints from the docstrings?

We could but beware that currently pandas/xarray somehow seem to be broken with intersphinx. E.g. xr.DataArray won't link correctly in and form typehints but xarray.DataArray put manually into the docstring will somehow...
But I like the look and formating with this


Future Request: Swift support

Is this app going to be translated to Swift?
I think it would be a best practice since everything is going swiftly..

https://github.com/istornz/iPokeGo/issues/10


Fix spelling and gremlin characters

This PR:

Fixes spelling in the text content

Note: I've changed all instances of "screenreader" to be "screen reader"

Replaces common gremlin characters (like " instead of “, and ' instead of ’).

Note: gremlin characters are characters that can be harmful because they are invisible or looking like legitimate ones

Relates to #49
I used the VS Code extension Code Spell Checker to help identify spelling mistakes, and Gremlins tracker for Visual Studio Code to help identify gremlin characters.

Note: all automated tests pass on this branch when using localhost instead of the IP address.


Update dependencies for examples

Resolves #51
The examples all now run correctly.
lustre_http v0.5.2 has been tagged, which now enables examples 05 and 06 to build without crashing the compiler.
For consistency, I also updated the required version of lustre_ui to its latest version.

Ah thank you so much, this is very handy!


Improper examples

It's may unappropriate to use Hong Kong as a country in this example:https://react.dev/learn/choosing-the-state-structure#avoid-deeply-nested-state

You're right.
According to Wikipedia:
Hong Kong is a city in South China

Merged the fix to remove it. Fwiw, I don't think the intent was to claim it's a country. For example, Hawaii and Bora Bora are listed, which are not countries either.

Hey all!
FWIW, renumbering all the items created a nightmare of a conflict arbitration for translators. Many locales had translated place names, and changing IDs for all entities post-HK was a major PITA to resolve conflict-wise.
Please consider translation work when touching code bits in doc pages: make sure your changes are as narrow as possible.
Thanks!


[DO NOT MERGE] Auto PR to update dependencies of istio

This PR will be merged automatically once checks are successful.
none

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-suite-rbac-no_auth.sh
0d1894dd5fa9dc578d7aeddad0040318dfd77bb9
link
/test e2e-suite-rbac-no_auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-suite-rbac-no_auth.sh
0d1894dd5fa9dc578d7aeddad0040318dfd77bb9
link
/test e2e-suite-rbac-no_auth

prow/e2e-suite-rbac-auth.sh
0d1894dd5fa9dc578d7aeddad0040318dfd77bb9
link
/test e2e-suite-rbac-auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@istio-testing: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-suite-rbac-no_auth.sh
0d1894dd5fa9dc578d7aeddad0040318dfd77bb9
link
/test e2e-suite-rbac-no_auth

prow/e2e-suite-rbac-auth.sh
0d1894dd5fa9dc578d7aeddad0040318dfd77bb9
link
/test e2e-suite-rbac-auth

prow/e2e-cluster_wide-auth.sh
0d1894dd5fa9dc578d7aeddad0040318dfd77bb9
link
/test e2e-cluster_wide-auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ayj @linsun any idea why this fails on release-0.2?


Update Java Routing Demo README

We need to update the Java Routing Demo for 2016 Developer Summit README with the workflow to start developing with the demo in Eclipse and IntelliJ IDEA.  This can be added once we release ArcGIS Runtime Java Quartz Beta 2.

Closing as demo moved out of repo


Add github workflow to push development helm charts to quay.io

The goal of this PR is to make it easier for developers and users to test images prior to releases being tagged. A common source of trouble is using images built in CI with the wrong version of the helm chart. This usually occurs when someone is testing an image from CI with the latest release of the chart. Typically this results in a failed install because the older chart is incompatible with the newer image.
This can simplify the testing of new changes by building a chart whenever an image is built, updating the chart to use the images built in CI. This means you can just install the chart, no need to even modify your values.yaml to use the CI images.
This was tested in a separate branch since workflow_dispatch only will work for workflows in the default branch. The CI ran passed here: https://github.com/cilium/cilium/actions/runs/4834815876. Normally it will only run after the image build CI workflow finishes, and or if triggered manually.
Once the chart is pushed, you can use it with helm like so:
helm template -n kube-system oci://quay.io/cilium-charts-dev/cilium --version 1.13.90-dev.426-ft-main-chancez-push-dev-charts-76b0a5c283
helm install cilium -n kube-system oci://quay.io/cilium-charts-dev/cilium --version 1.13.90-dev.426-ft-main-chancez-push-dev-charts-76b0a5c283 --dry-run

You can view the chart repo here: https://quay.io/repository/cilium-charts-dev/cilium?tab=tags

Okay, I updated it to use a few more variables in case we want to reuse this elsewhere. CI run: https://github.com/cilium/cilium/actions/runs/4835002365/jobs/8616858840

/test

There's nothing to test in this PR @michi-covalent

i'm keeping it simple. if the button is not green, i don't merge ✅

test-1.26-net-next: hit https://github.com/cilium/cilium/issues/15455

/test-1.26-net-next

is the button green? yes. am i merging it? definitely.


Purge game

This game is inspired by the sokoban game.
In order to win the purge game, you need to Cover the purple with green.

Hey Novicee, there is a bug with the movement code. I think you're trying to have multiple players. If not, the last level is impossible. I have some code to fix that if you want. Just tell me if you want it.

Hey Novicee, there is a bug with the movement code. I think you're trying to have multiple players. If not, the last level is impossible. I have some code to fix that if you want. Just tell me if you want it.

@Omay238 go ahead! :flags:

Alright. The code I used is this:
onInput("s", () => {
  let players = getAll(player);
  for (let i of players) {
    i.y += 1;
  }
});
onInput("d", () => {
  let players = getAll(player);
  for (let i of players) {
    i.x += 1;
  }
});
onInput("w", () => {
  let players = getAll(player);
  for (let i of players) {
    i.y -= 1;
  }
});
onInput("a", () => {
  let players = getAll(player);
  for (let i of players)
    i.x -= 1;
  }
});

Replace your current movement code with that, and then it should work. It just loops through all the player objects, then moves them accordingly.

Alright. The code I used is this:
onInput("s", () => {
  let players = getAll(player);
  for (let i of players) {
    i.y += 1;
  }
});
onInput("d", () => {
  let players = getAll(player);
  for (let i of players) {
    i.x += 1;
  }
});
onInput("w", () => {
  let players = getAll(player);
  for (let i of players) {
    i.y -= 1;
  }
});
onInput("a", () => {
  let players = getAll(player);
  for (let i of players)
    i.x -= 1;
  }
});

Replace your current movement code with that, and then it should work. It just loops through all the player objects, then moves them accordingly.

@Omay238 should I remove the 'j' input completely..?

Oh, the 'j' is ok. Just replace WASD with that code.

Ok, I just noticed. I have a typo in that code. The new code is this:
onInput("s", () => {
  let players = getAll(player);
  for (let i of players) {
    i.y += 1;
  }
});
onInput("d", () => {
  let players = getAll(player);
  for (let i of players) {
    i.x += 1;
  }
});
onInput("w", () => {
  let players = getAll(player);
  for (let i of players) {
    i.y -= 1;
  }
});
onInput("a", () => {
  let players = getAll(player);
  for (let i of players) {
    i.x -= 1;
  }
});```

@Omay238
Thanks for the help! Fixed the code :rocket:

This is a great thread you guys have going!
I played the game and it's fun! It feels like there are more than one way to solve each puzzle but that's not necessarily a bad thing. This variation of multiple players in Sokoban seems to be pretty popular. It's fun to see how each game is still different depending on the creator's level design. Nice work, you've earned your Sprig: https://sprig-order.hackclub.dev/

Thank you @leomcelroy :yellow_heart:
This was my first ever try and I got an inspiration from the sokoban game. :rocket:
Happy that I was able to build something new :relaxed:


relation "account_base_user" does not exist

Hi, I'm a newbie, but I am very interested in this project because I am looking for starlette with jwt authentication, and this is more than expected.
But I have some issues when I am using one of examples: createUser.
I installed postgres, and I also set up database connection in .env.
I just thought GINO will automatically create databases and its tables from models.py, but there is no db and no tables.
The below is what I am going through.
Am I missing something related to database?
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/graphql/execution/execute.py", line 674, in await_completed
    return await completed
  File "/usr/local/lib/python3.6/dist-packages/graphql/execution/execute.py", line 659, in await_result
    return_type, field_nodes, info, path, await result
  File "/usr/local/lib/python3.6/dist-packages/graphql/execution/execute.py", line 733, in complete_value
    raise result
  File "/usr/local/lib/python3.6/dist-packages/graphql/execution/execute.py", line 628, in await_result
    return await result
  File "/usr/local/lib/python3.6/dist-packages/ariadne/types.py", line 58, in resolve
    result = await result
  File "/usr/local/lib/python3.6/dist-packages/ariadne/utils.py", line 45, in async_wrapper
    return await func(*args, **convert_to_snake_case(kwargs))
  File "/usr/local/lib/python3.6/dist-packages/turbulette/validation/decorators.py", line 35, in wrapped_func
    return await func(obj, info, **kwargs)
  File "./eshop/account/resolvers/user.py", line 38, in resolve_user_create
    user_model.username == valid_input["username"]
  File "/usr/local/lib/python3.6/dist-packages/gino/api.py", line 137, in first
    return await self._query.bind.first(self._query, *multiparams, **params)
  File "/usr/local/lib/python3.6/dist-packages/gino/engine.py", line 748, in first
    return await conn.first(clause, *multiparams, **params)
  File "/usr/local/lib/python3.6/dist-packages/gino/engine.py", line 328, in first
    return await result.execute(one=True)
  File "/usr/local/lib/python3.6/dist-packages/gino/dialects/base.py", line 215, in execute
    context.statement, context.timeout, args, 1 if one else 0
  File "/usr/local/lib/python3.6/dist-packages/gino/dialects/asyncpg.py", line 184, in async_execute
    result, stmt = await getattr(conn, "_do_execute")(query, executor, timeout)
  File "/usr/local/lib/python3.6/dist-packages/asyncpg/connection.py", line 1681, in _do_execute
    ignore_custom_codec=ignore_custom_codec,
  File "/usr/local/lib/python3.6/dist-packages/asyncpg/connection.py", line 380, in _get_statement
    ignore_custom_codec=ignore_custom_codec,
  File "asyncpg/protocol/protocol.pyx", line 168, in prepare
graphql.error.graphql_error.GraphQLError: relation "account_base_user" does not exist

modles.py
from gino.json_support import ObjectProperty
from sqlalchemy import Column, DateTime, ForeignKey, Integer
from sqlalchemy.dialects.postgresql import JSONB
from sqlalchemy.sql.sqltypes import Float, String

from turbulette.db import Model
from turbulette.apps.auth.models import AbstractUser

class BaseUser(Model, AbstractUser):
    pass

class CustomUser(AbstractUser, Model):
    pass

resolvers/user.py
@mutation.field("createUser")
@convert_kwargs_to_snake_case
@validate(BaseUserCreate)
async def resolve_user_create(*_, **kwargs) -> dict:
    valid_input = kwargs["_val_data"]

    user = await user_model.query.where(
        user_model.username == valid_input["username"]
    ).gino.first()

    if user:
        message = f"User {valid_input['username']} already exists"

        # Make sure to call __str__ on BaseError
        out = str(ErrorField(message))
        logging.info(out)

        return ErrorField(message).dict()

    new_user = await user_model.create(**valid_input)
    auth_token = await get_token_from_user(new_user)
    return {
        "user": {**new_user.to_dict()},
        "token": auth_token,
    }

Okay, I fixed the issue since I found the content related to databases from here.
As the document mentioned, turbulette doesn't do much more from what gino does.
Once put database information into .env, just run turb cli commands as follows: (it shows how to use alembic as well)
turb makerevision <app>
turb upgrade <app>


use kebab-case naming convention

On many typos, the uppercase "I" can be confused with the lowercase "L", so pollId can be confusing.
By using kebab-case naming convention, poll-id and judgment-id are more explicit and easier to read.

That sounds good to me.
It seems that both naming convention are acceptable, but your point is more than fair.


PlatformIO: Fix ESP-IDF generation. (fix #734)

@PetteriAimonen please wait for the CI finish before merge

Thanks!

@PetteriAimonen could you please publish updated version to the PlatformIO registry?
Thanks in advance.


[WIP] P2Pool Overview

I'll give it a go on the P2Pool overview page

Closed issue. Reason: Lack of updates.


Added Substring function

Based on the changes of #207 added support of the function substring with syntax SUBSTRING(... FROM ... FOR ...)
See also:
http://sqlzoo.net/wiki/SUBSTRING(ansi)

Coverage decreased (-0.002%) to 83.565% when pulling 8711734ad3be3aeecb99cb1e18e239c5dcc4326f on conterra:substring into 3bc316df743ab09993d8d9e3588504ddde2d33de on JSQLParser:master.

Coverage decreased (-0.002%) to 83.565% when pulling 9025b6fdc3c734f69cf8fa7d09056564166753f7 on conterra:substring into 3bc316df743ab09993d8d9e3588504ddde2d33de on JSQLParser:master.

Coverage decreased (-0.002%) to 83.565% when pulling a9fcd459cd3ddd08a37b00a17d12d1987f9abc7d on conterra:substring into 3bc316df743ab09993d8d9e3588504ddde2d33de on JSQLParser:master.

Coverage decreased (-0.002%) to 83.565% when pulling 65e2bf2af1c688937035265bf75bba2d24f33ec6 on conterra:substring into 3bc316df743ab09993d8d9e3588504ddde2d33de on JSQLParser:master.

I see you already divided the first pull request. I will look into this.

already solved


Add multiple channels support

Allow bot to play music in multiple voice channels.
Requires investigation.

It is not possible using Discord Bot API


very slow using this api

usually we operate in web ui it only taks about 10 seconds to generate a pic, but while using api it takes about 6x times to generate the pic. any idea why ?

Well, it depends on the input parameters. What parameters are you using in automatic1111 frontend and what are you passing as parameters in the api call?
With the same parameters it should take the same time.

@mix1009 when is the next release to pypi?

Let's see guys... the speed issue is not because this repo is because how you use it. If you do not plqn to share the previous requested info better close this issue

@mix1009 when is the next release to pypi?

I'll release when there is code change. last commit was an README update.


Deploy Checklist: New Expensify 2023-07-17

Release Version: 1.3.42-4
Compare Changes: https://github.com/Expensify/App/compare/production...staging
This release contains changes from the following pull requests:

[x] https://github.com/Expensify/App/pull/18752
[x] https://github.com/Expensify/App/pull/19509
[ ] https://github.com/Expensify/App/pull/19850
[ ] https://github.com/Expensify/App/pull/20142
[x] https://github.com/Expensify/App/pull/20434
[ ] https://github.com/Expensify/App/pull/20762
[ ] https://github.com/Expensify/App/pull/21552
[x] https://github.com/Expensify/App/pull/21667
[x] https://github.com/Expensify/App/pull/21714
[ ] https://github.com/Expensify/App/pull/21851
[ ] https://github.com/Expensify/App/pull/21852
[x] https://github.com/Expensify/App/pull/22131
[ ] https://github.com/Expensify/App/pull/22154
[ ] https://github.com/Expensify/App/pull/22247
[x] https://github.com/Expensify/App/pull/22260
[ ] https://github.com/Expensify/App/pull/22321
[x] https://github.com/Expensify/App/pull/22329
[ ] https://github.com/Expensify/App/pull/22403
[ ] https://github.com/Expensify/App/pull/22431
[x] https://github.com/Expensify/App/pull/22432
[ ] https://github.com/Expensify/App/pull/22484
[x] https://github.com/Expensify/App/pull/22529
[x] https://github.com/Expensify/App/pull/22542
[x] https://github.com/Expensify/App/pull/22551
[ ] https://github.com/Expensify/App/pull/22559
[x] https://github.com/Expensify/App/pull/22564
[x] https://github.com/Expensify/App/pull/22565
[x] https://github.com/Expensify/App/pull/22566
[ ] https://github.com/Expensify/App/pull/22586
[x] https://github.com/Expensify/App/pull/22612
[x] https://github.com/Expensify/App/pull/22616
[x] https://github.com/Expensify/App/pull/22620
[ ] https://github.com/Expensify/App/pull/22623
[x] https://github.com/Expensify/App/pull/22628
[ ] https://github.com/Expensify/App/pull/22639
[ ] https://github.com/Expensify/App/pull/22642
[x] https://github.com/Expensify/App/pull/22643
[x] https://github.com/Expensify/App/pull/22653
[x] https://github.com/Expensify/App/pull/22672
[x] https://github.com/Expensify/App/pull/22680
[x] https://github.com/Expensify/App/pull/22686
[x] https://github.com/Expensify/App/pull/22690
[x] https://github.com/Expensify/App/pull/22693
[ ] https://github.com/Expensify/App/pull/22702
[ ] https://github.com/Expensify/App/pull/22717
[x] https://github.com/Expensify/App/pull/22730
[x] https://github.com/Expensify/App/pull/22731
[x] https://github.com/Expensify/App/pull/22740
[x] https://github.com/Expensify/App/pull/22743
[x] https://github.com/Expensify/App/pull/22746
[ ] https://github.com/Expensify/App/pull/22752
[ ] https://github.com/Expensify/App/pull/22757
[ ] https://github.com/Expensify/App/pull/22761
[x] https://github.com/Expensify/App/pull/22771
[x] https://github.com/Expensify/App/pull/22777
[ ] https://github.com/Expensify/App/pull/22781
[x] https://github.com/Expensify/App/pull/22782
[ ] https://github.com/Expensify/App/pull/22784
[ ] https://github.com/Expensify/App/pull/22786
[x] https://github.com/Expensify/App/pull/22787
[x] https://github.com/Expensify/App/pull/22801
[x] https://github.com/Expensify/App/pull/22814
[x] https://github.com/Expensify/App/pull/22817
[ ] https://github.com/Expensify/App/pull/22820
[ ] https://github.com/Expensify/App/pull/22827
[x] https://github.com/Expensify/App/pull/22835
[ ] https://github.com/Expensify/App/pull/22836
[ ] https://github.com/Expensify/App/pull/22838
[x] https://github.com/Expensify/App/pull/22845
[x] https://github.com/Expensify/App/pull/22848
[ ] https://github.com/Expensify/App/pull/22863
[ ] https://github.com/Expensify/App/pull/22866
[ ] https://github.com/Expensify/App/pull/22867
[ ] https://github.com/Expensify/App/pull/22869
[ ] https://github.com/Expensify/App/pull/22899
[x] https://github.com/Expensify/App/pull/22902
[x] https://github.com/Expensify/App/pull/22903
[x] https://github.com/Expensify/App/pull/22905
[ ] https://github.com/Expensify/App/pull/22908
[ ] https://github.com/Expensify/App/pull/22926
[ ] https://github.com/Expensify/App/pull/22956

Internal QA:

[x] https://github.com/Expensify/App/pull/22847 - @danieldoglas
[ ] https://github.com/Expensify/App/pull/22590 - @dangrous

Deployer verifications:

[ ] I checked the App Timing Dashboard and verified this release does not cause a noticeable performance regression.
[ ] I checked Firebase Crashlytics and verified that this release does not introduce any new crashes. More detailed instructions on this verification can be found here.
[ ] I checked GitHub Status and verified there is no reported incident with Actions.

cc @Expensify/applauseleads

:rocket: All staging deploys are complete, @Expensify/applauseleads please begin QA on version https://github.com/Expensify/App/releases/tag/1.3.42-0 :rocket:

If I already QAed the PR I was assigned for the previous Deploy Checklist, do I need to again? Is there a possibility it's broken now? Not sure on the process (or what happened here)

@dangrous I accidentally deployed the old checklist during the stress test, but cancelled that deploy.
So your PR was checked off, and in the process of being deployed, but didn't actually get deployed. So it was included in this checklist again.
I would QA it again just to be sure that it still works with the new items in this checklist. Sorry for the hassle!

@jasperhuangg similar question. Should we re-QA ALL of the PRs from previous checklist as well?

ah @mvtglobally I didn't think about this.. yes, I think it's best, otherwise regressions might get through. Thanks for asking.

@jasperhuangg As a heads up - this will increase the result turnaround time considerably since it's another 30 PRs to verify. We will keep you posted on the progress.

@isagoico that's fine, thanks for letting me know!

I checked off #23070 after cherry-picking the revert PR here

@Julesssss @jasperhuangg I see the build is upped. Can you pls share the CPs we need to test as I dont see them in checklist

Confirmed #22590 works well!

@aimane-chnaif Yep, the CP failed https://github.com/Expensify/App/actions/runs/5588876019/jobs/10216344982 trying to get that resolved

Checking #23083 off, not a blocker.
@mvtglobally I think if you have verified some PRs yesterday in the checklist, I dont think we have to be verifying them again, any reason for that @jasperhuangg?

I'm concerned that a new combination of PRs may cause regressions/blockers that we weren't previously aware of. I'd rather catch those bugs now rather than later.

Checking #23083 off, not a blocker.
@mvtglobally I think if you have verified some PRs yesterday in the checklist, I dont think we have to be verifying them again, any reason for that @jasperhuangg?

@mountiny I'm concerned that a new combination of PRs may cause regressions/blockers that we weren't previously aware of. I'd rather catch those bugs now rather than later.

Checking off https://github.com/Expensify/App/issues/23050 as it isn't reproducible in the latest release and shouldn't be a blocker

We are working on the full list Will be sharing update shortly

Checking off blocker 23106, not an issue

Checking off https://github.com/Expensify/App/pull/17452, was able to QA this myself successfully

Current summary
https://github.com/Expensify/App/pull/17452 is failing
https://github.com/Expensify/App/pull/20142 pending validation on all platforms
https://github.com/Expensify/App/pull/21594 CP pending validation on all platforms
https://github.com/Expensify/App/pull/21938 CP pending validation on all platforms
https://github.com/Expensify/App/pull/22154 CP pending validation on all platforms
https://github.com/Expensify/App/pull/22243 CP pending validation on all platforms
https://github.com/Expensify/App/pull/22248 CP pending validation on all platforms
https://github.com/Expensify/App/pull/22260 pending validation on all platforms
https://github.com/Expensify/App/pull/22329 pending validation on all platforms https://github.com/Expensify/App/pull/22403 is failing
https://github.com/Expensify/App/pull/22431 pending validation on all platforms
https://github.com/Expensify/App/pull/22473 CP pending validation on all platforms
https://github.com/Expensify/App/pull/22484 is failing
https://github.com/Expensify/App/pull/22484 pending validation on all platforms
https://github.com/Expensify/App/pull/22551 checking off https://github.com/Expensify/App/pull/22551#issuecomment-1636312128
https://github.com/Expensify/App/pull/22586 is failing
https://github.com/Expensify/App/pull/22616 pending validation on all platforms
https://github.com/Expensify/App/pull/22620 pending validation on all platforms
Continuing updating this comment....

Checking off https://github.com/Expensify/App/issues/23102 since we CP'd a fix to staging.

@mvtglobally I tested https://github.com/Expensify/App/pull/17452 myself and it works as expected, gonna remove it from your list

Current summary
https://github.com/Expensify/App/pull/20142 pending validation on all platforms
https://github.com/Expensify/App/pull/21594 CP pending validation on all platforms
https://github.com/Expensify/App/pull/21938 CP pending validation on all platforms
https://github.com/Expensify/App/pull/22154 CP pending validation on all platforms
https://github.com/Expensify/App/pull/22243 CP pending validation on all platforms
https://github.com/Expensify/App/pull/22248 CP pending validation on all platforms
https://github.com/Expensify/App/pull/22260 pending validation on all platforms
https://github.com/Expensify/App/pull/22329 pending validation on all platforms https://github.com/Expensify/App/pull/22403 is failing https://github.com/Expensify/App/issues/23052
https://github.com/Expensify/App/pull/22431 pending validation on all platforms
https://github.com/Expensify/App/pull/22473 CP pending validation on all platforms
https://github.com/Expensify/App/pull/22484 is failing https://github.com/Expensify/App/issues/23083 & pending IOS validation
https://github.com/Expensify/App/pull/22484 pending validation on all platforms
https://github.com/Expensify/App/pull/22551 checking off https://github.com/Expensify/App/pull/22551#issuecomment-1636312128
https://github.com/Expensify/App/pull/22586 is failing https://github.com/Expensify/App/issues/23049. Repro in PROD checking off
https://github.com/Expensify/App/pull/22616 pending validation on all platforms
https://github.com/Expensify/App/pull/22620 pending validation on all platforms
https://github.com/Expensify/App/pull/22628 is failing 6132992
https://github.com/Expensify/App/pull/22639 pending validation on all platforms
https://github.com/Expensify/App/pull/22653 pending validation on all platforms
https://github.com/Expensify/App/pull/22734 CP pending validation on all platforms
https://github.com/Expensify/App/pull/22755 CP pending validation on all platforms
https://github.com/Expensify/App/pull/22761 pending validation on all platforms
https://github.com/Expensify/App/pull/22777 is failing https://github.com/Expensify/App/pull/22777. Repro in PROD checking off
https://github.com/Expensify/App/pull/22784 CP pending validation on all platforms
https://github.com/Expensify/App/pull/22808 CP pending validation on all platforms
https://github.com/Expensify/App/pull/22817 CP pending validation on all platforms
https://github.com/Expensify/App/pull/22818 CP pending validation on all platforms
https://github.com/Expensify/App/pull/22820 pending validation on all platforms
https://github.com/Expensify/App/pull/22827 is failing https://github.com/Expensify/App/issues/23084 Repro in PROD checking off
https://github.com/Expensify/App/pull/22830 CP pending validation on all platforms
https://github.com/Expensify/App/pull/22845 pending validation on all platforms
https://github.com/Expensify/App/pull/22866 pending validation on all platforms
https://github.com/Expensify/App/pull/22869 is failing https://github.com/Expensify/App/issues/23082 Repro in PROD checking off
https://github.com/Expensify/App/pull/22898 CP pending validation on all platforms
https://github.com/Expensify/App/pull/22903 pending validation on all platforms
https://github.com/Expensify/App/pull/22908 & https://github.com/Expensify/App/pull/22917 Can we check off since this is PROD QA?
https://github.com/Expensify/App/pull/22928 CP pending validation on all platforms
https://github.com/Expensify/App/pull/23023 CP pending validation on all platforms
https://github.com/Expensify/App/pull/23053 CP pending validation on all platforms
https://github.com/Expensify/App/pull/23107 CP pending validation on all platforms

@mvtglobally

https://github.com/Expensify/App/pull/22908 & https://github.com/Expensify/App/pull/22917 Can we check off since this is PROD QA?

Checked them off!

sorry for the long summary @jasperhuangg  but I wanted to provide the actual feedback on all unchecked so we have a better visibility

https://github.com/Expensify/App/pull/22403 is failing https://github.com/Expensify/App/issues/23052

It seems the root cause of https://github.com/Expensify/App/issues/23052 is actually https://github.com/Expensify/App/pull/21852, so checking off https://github.com/Expensify/App/pull/22403

QA'd https://github.com/Expensify/App/pull/22243 successfully myself, checking it off

QA'd https://github.com/Expensify/App/pull/22755 successfully myself, checking it off

QA'd https://github.com/Expensify/App/pull/22734 successfully myself, checking it off

Checking off #23077 repro in prod

We CP'd a fix for https://github.com/Expensify/App/pull/23133, just retested on staging and it works now, checking it off

Current summary
Checked a bunch of the PRs. working on the last ones
https://github.com/Expensify/App/pull/20142 pending validation on all platforms
https://github.com/Expensify/App/pull/22154 CP pending validation on all platforms
https://github.com/Expensify/App/pull/22243 CP pending validation on all platforms
https://github.com/Expensify/App/pull/22248 CP pending validation on all platforms
https://github.com/Expensify/App/pull/22403 is failing https://github.com/Expensify/App/issues/23052
https://github.com/Expensify/App/pull/22431 pending validation on all platforms
https://github.com/Expensify/App/pull/22473 CP pending validation on all platforms
https://github.com/Expensify/App/pull/22484 is failing https://github.com/Expensify/App/issues/23083 & pending Android validation
https://github.com/Expensify/App/pull/22620 pending validation on all platforms
https://github.com/Expensify/App/pull/22628 is failing https://github.com/Expensify/App/issues/23144. repro in PROD
https://github.com/Expensify/App/pull/22639 pending validation on all platforms
https://github.com/Expensify/App/pull/22653 pending validation on all platforms
https://github.com/Expensify/App/pull/22761 pending validation on all platforms
https://github.com/Expensify/App/pull/22784 CP pending validation on all platforms
https://github.com/Expensify/App/pull/22808 CP pending validation on all platforms
https://github.com/Expensify/App/pull/22817 CP pending validation on all platforms
https://github.com/Expensify/App/pull/22818 CP pending validation on all platforms
https://github.com/Expensify/App/pull/22820 pending validation on all platform
https://github.com/Expensify/App/pull/22830 CP pending validation on all platforms
https://github.com/Expensify/App/pull/22845 pending validation on all platforms
https://github.com/Expensify/App/pull/22866 pending validation on all platforms
https://github.com/Expensify/App/pull/22898 CP pending validation on all platforms
https://github.com/Expensify/App/pull/22903 pending validation on all platforms
https://github.com/Expensify/App/pull/22928 CP pending validation on all platforms
https://github.com/Expensify/App/pull/23023 CP pending validation on all platforms
https://github.com/Expensify/App/pull/23053 CP pending validation on all platforms
https://github.com/Expensify/App/pull/23107 CP pending validation on all platforms

QA'd https://github.com/Expensify/App/pull/23107 myself and it works, checking it off

Cherry-picked this minor PR to staging and checked it off: https://github.com/Expensify/App/pull/23155

@jasperhuangg Regression is completed
Final summary
https://github.com/Expensify/App/pull/20142 is failing https://github.com/Expensify/App/issues/23170. repro in PROD. We are also blocked from validation on Native apps.
Also, I'm checking off https://github.com/Expensify/App/pull/22817 as it was reverted.

:shipit:


Couldn't connect to Docker daemon at http+docker://localunixsocket - is it running?

Hello,I have installed docker and docker compose according to the documentation. In the third step, I try to building the apss docker container. I entered 'make' command in the terminal, But error occur as follow:

I entered 'sudo docker-compose' command in the terminal to solve this problem. But error occur as follow:

So I come here to search for your help. Thank you.

Hello, the problem has a simple solution.
Just follow the [official docker installation instructions]("Post-installation steps for Linux | Docker Documentation" https://docs.docker.com/engine/install/linux-postinstall/) and you will be fine

Thank you for your answer. I have successfully built the apss docker container. In the next step, their still some problem as follow:

I don't know what cause this error. May be I set a wrong data-set path. If you think so, please offer me a example. Or others reason? Thank you


transformers.Trainer does not provide speedup compared to native pytorch loop

Hi,
I was working on exploring PEFT through this tutorial, however, it seems that the Trainer usage shown here is slower compared a native PyTorch loop provided in the this tutorial. I might be doing something wrong?
I am using an M1 device.
torch = "^2.0.0"
transformers = "^4.28.1"
datasets = "^2.12.0"
peft = "^0.3.0"
evaluate = "^0.4.0"
seqeval = "^1.2.2"
streamlit = "^1.22.0"

42 seconds vs 340 seconds.
from transformers import (
    AutoModelForSequenceClassification,
    Trainer,
    TrainingArguments,
)
import numpy as np

metric = evaluate.load("f1")
def compute_metrics(eval_pred):
    """Computes accuracy on a batch of predictions"""
    predictions = np.argmax(eval_pred.predictions, axis=1)
    return metric.compute(predictions=predictions, references=eval_pred.label_ids)

args = TrainingArguments(
    "finetuned-lora-food101",
    remove_unused_columns=False,
    evaluation_strategy="epoch",
    save_strategy="epoch",
    learning_rate=lr,
    per_device_train_batch_size=batch_size,
    gradient_accumulation_steps=4,
    per_device_eval_batch_size=batch_size,
    num_train_epochs=num_epochs,
    logging_steps=1,
    load_best_model_at_end=True,
    metric_for_best_model="f1",
    # push_to_hub=True,
    label_names=["labels"],
)

trainer = Trainer(

    model,
    args,
    train_dataset=tokenized_datasets["train"],
    eval_dataset=tokenized_datasets["test"],
    tokenizer=tokenizer,
    compute_metrics=compute_metrics,
    optimizers=(optimizer, lr_scheduler),
    data_collator=collate_fn,
)
trainer.train()

demo__transformer_peft.ipynb.zip

Hi,
I did some more testing and this seems top be an M1 issue, it does run on Colab.


Create a desktop filter component

One need to make this component using HTML and Tailwind CSS. I would suggest to use Tailwind Playgrounds to make things faster and quicker.
Hey I wanted to contribute more to this repo kindly assign this to me
Here is a reference to the component.
Add image here

After building the component please raise a PR with a screenshot of the component and add the component in path of the file.
If you need to use any icon please use it from Hero Icons
Good luck.

Choose one @abhijain2003

is this not one, ok then I would like to go with accessories

Ok go with it and update the image @abhijain2003

sure

just wanted to confirm is the location of this component will be Filter/Desktop/marketplace.html

marketplace-1.html @abhijain2003

sure


Is it possible to perform a cert rollover without a restart?

Question
Is it possible to rollover certs without an application restart? I know it's possible to register a validation key using the code below. But that will obviously require an app restart whenever a roll-over is required. I also see there are the ISigningCredentialStore and IValidationKeysStore interfaces that I can implement. If I do that, are these stores called frequently or are they only called on start up? Restarting isn't a big issue, but this would be a nice to have.
Minimal working example
services
    .AddIdentityServer()
    .AddSigningCredential(activeCertificate)
    .AddValidationKey(secondaryCertificate);

Found my answer.
https://github.com/damienbod/IdentityServer4AspNetCoreIdentityTemplate/issues/30


"post identity body world" fails with http-parser >= 2.9.3

Little surprised nobody has reported this earlier ...
Re-building http_parser.rb with the latest version of http-parser (2.9.4) I noticed the "post identity body world" check fails:
  1) HTTP::Parser should parse request: post identity body world
     Failure/Error: @parser << test['raw']

     HTTP::Parser::Error:
       Could not parse data entirely (116 != 122)
     # ./spec/parser_spec.rb:317:in `<<'
     # ./spec/parser_spec.rb:317:in `block (4 levels) in <top (required)>'

After a lengthy research I think the test is indeed flawed, i.e. in violation of RFC 7320 3.3.1. ("Transfer-Encoding").
The check sets Transfer-Encoding: identity and also Content-Length: 5
About the first, the RFC states:
   If any transfer coding
   other than chunked is applied to a request payload body, the sender
   MUST apply chunked as the final transfer coding to ensure that the
   message is properly framed.

...so this is not acceptable.
According to 3.3.3. ("Message Body Length"), combining Transfer-Encoding: and Content-Length: indicate "request smuggling" which "ought to be handled as an error" - which is what the http-parser library now does: It implemented a stricter check in commit https://github.com/nodejs/http-parser/commit/7d5c99d09f6743b055d53fc3f642746d9801479b.
Reproducer (could possibly be shorter):
require "http/parser"

parser = Http::Parser.new

parser.on_headers_complete = proc do
  p parser.http_version

  p parser.http_method # for requests
  p parser.request_url

  p parser.status_code # for responses

  p parser.headers
end

parser <<"POST /post_identity_body_world?q=search#hey HTTP/1.1\r\nAccept: */*\r\nContent-Length: 5\r\nTransfer-Encoding: identity\r\n\r\nWorld"

Solution: Please rewrite or disable that test.

Solution: Please rewrite or disable that test.

I confirmed it too.
I think the current implementation refers old RFC rfc2616 because

0.6.0 is released at December 11, 2013
rfc7230 is published at 2014.

So we should increment feature version (0.x.0) of this gem when we upgrade to http-parser 2.9.3 or later.
BTW because http-parser isn't maintained anymore, I'll also not actively maintain this after resolving major remaining issues.
From https://github.com/nodejs/http-parser
http-parser is not actively maintained. New projects and projects looking to migrate should consider llhttp.


Replace newlines with space

Currently failing tests because this method does not remove trailing space from the end of the title if the title ends with a newline.
Not sure what to do about that without chasing our own tail. Maybe we just don't strip newlines at all?
#66

Is there a "strip" filter we could use?

Shopify has one, but Jekyll does not.

Shopify has one, but Jekyll does not.

¡ABSURD! Is it in Liquid 3 only, maybe?

Looks that way

welp. time to upgrade :troll:
On Mon, Sep 21, 2015 at 12:08 PM, Pat Hawks<EMAIL_ADDRESS>wrote:

Looks that way
https://github.com/Shopify/liquid/commit/d2827bfa76801d0e8b104ab28703ce86164d5253
—
Reply to this email directly or view it on GitHub
https://github.com/jekyll/jekyll-feed/pull/67#issuecomment-142044936.

Will release a new beta. Maybe I can get some time this week...

Using the strip works for Jekyll 3.
Jekyll 2 will not have trailing whitespace removed, but calling a filter that doesn't exist doesn't break anything either with the relaxed Liquid parsing.

The other option would be to just add our own Liquid filter to collapse whitespace
  def collapse_whitespace(input)
    input.to_s.gsub(/\s+/, ' ').strip
  end

:question:

Any liquid filters we make here will be globally available, just a head's up.

Any liquid filters we make here will be globally available, just a head's up.

Is that to be avoided?

@pathawks Would you please add a test for this?

Test added :+1:


The unit test success rate for esm.sh is lower after refactoring

Hey, @ije nice try for esm.sh 's refactoring to transform node eval to ast parser.
Better for some package like: /@lume/element, /@lume/variable.
But bad for some packages too, here is the details:
Online Test for current esm.sh : 66.23%

Online Test for (esm.alibaba-inc.com) which is based on old version: 89.61%

Maybe we need node eval and ast parser both for named export & packaging.

@zhoukekestar i think the AST parser is ok, guess the main problem is that i updated esbuild to 0.11, the external module resolver needs to be updated too becuase i saw a lot require is not defined errors, i will fix it asap, thanks 🙏
btw the testing looks amazing, can you please share it for me?

Thanks for your hard working, the unit test is  very simple which is written in native JavaScript. I will open-source it if you need this so that we can deliver esm.sh with confidence.

i added a simple testing page, do you have interest in improving it? thanks

you can update it in here: https://github.com/postui/esm.sh/blob/master/embed/assets/testing.js

run the testing in http://localhost/?test

btw, i added a build queue instead of mutex lock that can use the multiple CPU units. in my computer(i7 8 cores) it got almost 7x build speed faster!

Great, that's awesome!

We just need check variable exist or not in most case. If esm.sh import works and has no-undefined variable, it's always works for me.

Some hack details maybe useful for you to pass all unit test:

named export solution PRed by @wleonardo
some npm packaged by webpack
some npm use browser entry directly. For example<EMAIL_ADDRESS>some necessary polyfill like: @jspm/core & entends it. For example: https://github.com/jspm/jspm-core/issues/13
some named export like arguments seems NO-SOLUTION for it, and may be the only way is use is.default.arguments. For example: https://github.com/postui/esm.sh/issues/28