RuntimeError in molopt/pretrain.py

Dear Wengong Jin
I'd like to ask your help about molopt during running pretrain.py
I have successfully done all of example in molopt with data/train.txt , data/vocab.txt, data/train.logP-SA.
However RuntimeError has occurred with my own training dataset , vocab generated with python ../jtnn/mol_tree.py <  my_dataset.txt and my own logP property file.
It seems to be wrong dimension during node aggregation.
What's your opinion about this issue ?
Best Regards, Minkyu Ha
( environment is same with you. python 2.7, cuda 8.0,  pytorch 0.3.1)
Model #Params: 4271K
Traceback (most recent call last):
File "pretrain.py", line 69, in
loss, kl_div, wacc, tacc, sacc, dacc, pacc = model(batch, beta=0)
File "/home/minkyuha/anaconda2/lib/python2.7/site-packages/torch/nn/modules/module.py", line 357, in call
result = self.forward(*input, **kwargs)
File "/home/minkyuha/new-jtnn/icml18-jtnn/jtnn/jtprop_vae.py", line 76, in forward
tree_mess, tree_vec, mol_vec = self.encode(mol_batch)
File "/home/minkyuha/new-jtnn/icml18-jtnn/jtnn/jtprop_vae.py", line 57, in encode
tree_mess,tree_vec = self.jtnn(root_batch)
File "/home/minkyuha/anaconda2/lib/python2.7/site-packages/torch/nn/modules/module.py", line 357, in call
result = self.forward(*input, **kwargs)
File "/home/minkyuha/new-jtnn/icml18-jtnn/jtnn/jtnn_enc.py", line 62, in forward
cur_h_nei = torch.cat(cur_h_nei, dim=0).view(-1,MAX_NB,self.hidden_size)
RuntimeError: invalid argument 2: size '[-1 x 8 x 420]' is invalid for input with 144900 elements at /opt/conda/conda-bld/pytorch_1523240155148/work/torch/lib/TH/THStorage.c:37

Hi @MinkyuHa , try increasing MAX_NB global parameter in jtnn_dec.py and jtnn_enc.py.
I increased it from 8 to 32. Note that this will increase GPU memory usage.

I've got the same issue.
However, increasing global parameter MAX_NB doesn't fit in my case.
Have anyone solve this issue in another way?


help

How can I write this example code in e73?

For the current state-of-the-art support for this chip you can rather have a look here or also here


Can change Content-Disposition string？

Describe the issue
Can change Content-Disposition string？
Vapor version
4.6.0
Operating system and version
Mac
Swift version
5.9.0
Steps to reproduce
1.upload file
2.then the file header Content-Disposition: form-data; filename="1721182375.png"; name="file"
now I want Content-Disposition: form-data; name="file"; filename="1721182375.png"
can I change name and filename？
Outcome
upload result  header Content-Disposition: form-data; filename="1721182375.png"; name="file"
I want Content-Disposition: form-data; name="file"; filename="1721182375.png"
Additional notes
M2 Mac

You can manually override the header in a request with request.headers.contentDisposition = .... There is nothing in the spec that requires a specific order so overriding it is not something Vapor supports


No Such file or deirectory

Hey there again, hope you r doing well, I just updated to hyprland 0.40.0-1 (latest on extra), hyprkool simply stopped working, when running "hyprkool" in the terminal i get the help message, but when running hyprkool daemon -m i get Error: No such file or directory (os error 2).
I updated the daemon and the plugin from hyprpm, but to no avail, and using the entore path to run the thingy has the same result, when running ~/.cargo/bin/hyprkool i get the help message, but when running ~/.cargo/bin/hyprkool daemon - m i get Error: No such file or directory (os error 2)

tested on these, only works on this one

hyprland changed a bunch of things in v0.40 and i haven't done the work to support that yet.
i'll push fixes for it in the near future. until then, hyprkool will only work with v0.39.
apologies for the inconvenience.

ok ok, lovely, thx

let's keep the issue open until it is fixed. :)


Automation/Reorganisation of Codebase

As we start adding more licenses (#18), it's going to be harder to add all of the license text into individual go files. We should have some script to automate this process
Automation is a necessity since the licenses are getting longer!
Also, the root directory will start getting crowded the more licenses we add to it (#18) ... we should move all the license go files to licenses/ to clean up the root directory.

@nikitavoloboev Do you have any ideas of what would be a nice interface for this?

Not sure but maybe we can take inspiration from other projects
There's a few like https://github.com/nishanths/license
I made this because I wanted simple & memorable API.

I see ... I'll take a look now


CHANGELOG 2.9

Telemetry:

DealDamage event now has variable Delt renamed to Dealt inside of payload.
{ "time": "2017-09-23T20:12:42-0700", "type": "DealDamage", "payload": {   "Team": "Left",   "Actor": "*Samuel*",   "Target": "*Reza*",   "Source": "Unknown",   "Damage": 80,   "Dealt": 69,   "IsHero": 1,   "TargetIsHero": 1 } }

Fixed misspelling on BuyItem variable RemainingGold: to RemainingGold

Rename Shared With variable from EarnXP to SharedWith

Kraken damage is now included in DealDamage

HealTarget is a new event. This is what it will look like:

Be aware that Buff_SpawnStage_Recharge is a game buff. It's the healing buff the hero gets when it goes to spawn location. I recommend skipping it when calculating the total healing a hero dealt.
[{ "time": "2017-09-23T19:45:15-0700", "type": "HealTarget", "payload": { "Team": "Right", "Actor": "*Vox*", "TargetActor": "*Vox*", "TargetTeam": "Right", "Source": "Buff_SpawnStage_Recharge", "Heal": 24, "Healed":  24, "IsHero": 1, "TargetIsHero": 1 } },

Some events are from actor unknown because they don't have an owner, but you can clearly see that it came from a jungle camp.
{ "time": "2017-09-23T19:45:15-0700", "type": "HealTarget", "payload": { "Team": "Unknown", "Actor": "Unknown", "TargetActor": "*Grumpjaw*", "TargetTeam": "Right", "Source": "Buff_JungleMinion_TreeEnt_Restore", "Heal": 32, "Healed":  32, "IsHero": -1, "TargetIsHero": 1 } },

Fountain is also included. Since it is overtime heal, it will be a series of event with each second heal
{ "time": "2017-09-23T19:44:21-0700", "type": "HealTarget", "payload": { "Team": "Left", "Actor": "*Lyra*", "TargetActor": "*Lyra*", "TargetTeam": "Left", "Source": "Buff_Item_FountainOfRenewal", "Heal": 59, "Healed":  59, "IsHero": 1, "TargetIsHero": 1 } },

Same thing for abilities overtime heal, like Lyra:
{ "time": "2017-09-23T19:44:20-0700", "type": "HealTarget", "payload": { "Team": "Left", "Actor": "*Lyra*", "TargetActor": "*Baptiste*", "TargetTeam": "Left", "Source": "Buff_Lyra_SpiritFlame", "Heal": 8, "Healed":  8, "IsHero": 1, "TargetIsHero": 1 } }]

Barriers, fortified health or any other buff that is not a direct Heal it is not included on this event.

Heroes:
*Churnwalker* Churnwalker

Skins:

Churnwalker_DefaultSkin

Perk:

Abilities:

HERO_ABILITY_CHURNWALKER_A_NAME Hook & Chain

HERO_ABILITY_CHURNWALKER_B_NAME - Torment

HERO_ABILITY_CHURNWALKER_C_NAME - Trespass

Damage Sources:

Ability__Churnwalker__DefaultAttack
Ability__Churnwalker__AltAttack
 Ability__Churnwalker__CritAttack
Ability__Churnwalker__A
Ability__Churnwalker__B
Ability__Churnwalker__C
Buff_Churnwalker_ChainTether

Skins:

Lyra_Skin_Autumn_CHN Moon Empress Lyra

Lyra_Skin_Autumn_JPN Moon Goddess Lyra

Lyra_Skin_Autumn_KOR Moon Queen Lyra

Baptiste_Skin_Scarecrow Baptiste Scarecrow

Baron_Skin_Heli Baron Fly Or Die

Items:

*Item_DragonsEye* DragonsEye

*Item_Spellfire* Spellfire

Echo Image change

TBD

DealDamage event now has variable Delt renamed to Dealt inside of payload.

This is a breaking change in the schema and will need to be supported for 4 more months… It's too late now, but always a :-1: from me for backwards incompatible schema changes that don't add or replace a different attribute with a different meaning. This was too minor of an issue to justify a schema change in my opinion.

I think any minor issue should be fixed now before they become more of a snowball that it is already.
We still in Alpha, this is still the best time.

Honestly, I agree with shutter -- this exact issue was raised months ago by Nathan, and we were told at the time (by genexp) that it was going to stay as it was, and the issue was closed.
And can we PLEASE stop invoking the "it's in alpha" as an excuse for wrecking code that has worked for months?

It's not an excuse to wreck code, its a reason to give us the possibility to make those small changes.
I believe we SHOULD have this fixed, not only that, but all other minor issue so when we get out of Alpha we can have a more perfect API.
I will see if I can get that reverted.

I'm glad @PierreAndreis is working hard to get some of the low hanging stuff patched.  (Thank you!!!)  That said, I get the pain here, and if you want I can actually revert this on the gamelocker side.  I can globally find replace "dealt" with "delt" in the telemetry as it's ingested.  Sound good?

@genexp I am a bit confused here. The little time SEMC gets to focus on fixing the API now we are reverting their fixes. Why? Things will break and that's the nature of choosing to work with alpha products. We should not be replacing fixed stuff with broken stuff.
Maybe create another field alongside the correct dealt and call this new field delt that has the same value. In the next update, 2.10 delt becomes deprecated. Everyone has time to accommodate to the change. But do not replace correct info with incorrect info, please. If SEMC fixes something we should celebrate not unfix it to be broken.

I will see if I can get that reverted.

For me, you don't need to revert. I will find the time to make the necessary changes. I am just worried about newcomers and the general pace of changes. So far, Telemetry had only two schemas (first version, then the version with hero bans — and some changes with the item, hero and ability names). Every time the schema changes, clients have to support both schemas. For almost half a year. Even if a dev starts next week, they gain nothing from a friendlier attribute name, because past data isn't rewritten [which is the real issue here].

when we get out of Alpha

Telemetry has been stable for months, the gamelocker major version is 6… I am not sure anymore what "this API is alpha" refers to, because my idea of an alpha stage is different. Irrelevant to the current issue though.

I'm glad PierreAndreis is working hard to get some of the low hanging stuff patched.

Agreed.
From an outside perspective… I find it troubling that you have to do it. It isn't officially your job. It's great that you do it, and you probably enjoy it, but you shouldn't need to. I want to critizise that it is very problematic and a sign of bad health that we need to rely on a community developer that happens to be employed by SEMC to communicate between MadGlory's customers and SEMC. What if you lose interest, get sick or want an advantage over other developers — I trust you to not be that guy, yet it's a possibility — that is just not right. There should be an official partner for us or a mail address (with you behind it?) for us to rely on for data level technical support. The critique is mostly targeted at @genexp.
It's all a definition of the seriousness of the API.
Is it for hobbyist, where everyone helps each other, the code breaks and everyone is more concerned about the technical challenged than getting the services running again?
Or is it a professional API, where consumers rely on uptime, support and well-communicated issued and changes, and can trust to be given the freedom to expand and commercialize?
For me, it's always been the latter, with thousands of pageviews every day, large scale applications, schema versioning, and plans for monetization of every consumer by MadGlory. Maybe I have been wrong the whole time (which could explain my frustration), but that makes the API lose all its attractiveness for me for any complex web application (as they currently exist).

Thanks Pierre.
Seeing that Delt isn't the only change, it's acceptable to introduce a new schema.


Align ScoreFeatureSet with the new PCA functions.

Codecov Report

Merging #54 (1a851bb) into master (5d93dde) will decrease coverage by 1.18%.
The diff coverage is 95.16%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##           master      #54      +/-   ##
==========================================
- Coverage   96.87%   95.70%   -1.18%
==========================================
  Files          89       89
  Lines        7593     7084     -509
  Branches      130      122       -8
==========================================
- Hits         7356     6780     -576
- Misses        185      253      +68
+ Partials       52       51       -1

Impacted Files
Coverage Δ

...clude/scran/dimensionality_reduction/SimplePca.hpp
95.52% <ø> (ø)

...e/scran/feature_set_enrichment/ScoreFeatureSet.hpp
83.11% <94.11%> (-15.78%)
:arrow_down:

...sts/src/feature_set_enrichment/ScoreFeatureSet.cpp
100.00% <100.00%> (ø)

... and 1 file with indirect coverage changes


Take pgroll JSON schema from a branch

Update and regenerate the schema JSON for pgroll using the alter-column-json-schema (https://github.com/xataio/pgroll/pull/261) branch.
https://github.com/xataio/pgroll/pull/261 makes changes to the schema for the 'alter column' operation and it would be good to test them in the migration editor before merge.

Closing as we won't merge this.


[FEATURE] Utility to upgrade old models to include new metadata

Ticket to track the model metadata update utility.
Thinking of shipping either a Colab notebook to get the job done similar to the previous utility to get from folder models to files

Haven't heard anyone asking for this recently, so closing.


Windows GSG: ruamel.yaml wheel not available for Python 3.12

I am following the Getting Started Guide for v3.5-rc3 on a fresh Windows machine.
As of Oct 15, I get python 3.12 when using the GSG instructions. (choco line says "python").
At the moment there are no wheel candidates for ruamel.yaml for 3.12 on WIndows.
The machine tries to build the native components of that package but cannot as the machine does not have the expected compiler.
If I change the choco line to install "python311" instead this problem goes away.
(Along with the windows-curses issues that is already reported in https://github.com/zephyrproject-rtos/windows-curses/pull/44 and expected to be fixed before the v3.5 release.)
I assume you will arrange to have a ruamel.yaml wheel available or change the GSG to use phython311.
(Instructing the user to install the native compiler seems like overkill for this problem.)

This is the second step for addressing https://github.com/zephyrproject-rtos/zephyr/issues/63977.

Thanks for reporting this @wmamills. We definitely want the Getting Started to work out of the box so your feedback is very helpful. As you can see in recent comments, we will be looking at hardening our CI so that to get a better chance to catch potential issue with 3.12.
In the meantime, I think the Windows wheels are now available (https://pypi.org/project/ruamel.yaml.clib/#files) -- would you mind trying again and reporting back?
Thanks!

We now test against Python 3.12 in our Continuous Integration on both MS Windows, macos, and Linux.

windows-curses 2.3.2 has been released with the wheels for Python 3.12.


Update cube.py

adding valve position

Coverage remained the same at 98.842% when pulling 3cff0e1c6ac8282c2263fc340d75446a9ea126bc on sutyagin:patch-1 into 9458b66cd8291355d5c8feee6b00c12d010ad6d9 on goodfield:master.

Coverage remained the same at 98.842% when pulling 3cff0e1c6ac8282c2263fc340d75446a9ea126bc on sutyagin:patch-1 into 9458b66cd8291355d5c8feee6b00c12d010ad6d9 on goodfield:master.

Coverage remained the same at 98.842% when pulling 3cff0e1c6ac8282c2263fc340d75446a9ea126bc on sutyagin:patch-1 into 9458b66cd8291355d5c8feee6b00c12d010ad6d9 on goodfield:master.


Enhancement: BO3Tools for Forge

It would be great if we could get BO3Tools for forge. Best would be if we could also use mod blocks aswell.
Currently we need to create a basic form in a bucket server with terraincontrol, world edit, and bo3Tools. And afterwards change the needed blocks in a text file to implement mod blocks.
For trees this is somewhat workable, but I cannot imagine doing this for custom structures especially with the multitude of different mod blocks available.
Probably need to force a way to disregard on the fly generated blocks: like those of flat colored blocks, malisis blocks's, ...

Hey, I don't maintain BO3Tools so you'll have to ask RutgerKok for that. Personally I use worldedit, mcedit and TCEE but I understand that for a lot of people that's not good enough. I agree we could use some better BO3 editing tools but at the moment my time is stretched to the limit just working on OTG :(.

Is TCCE available for 1.10.2?

TCEE is a windows application, you can grab the latest version from here: https://github.com/PG85/TCEE/tree/master/Build. You can use TCEE to convert schematics to BO3's, it doesn't allow you to set a center point for the BO3 like BO3Tools does though, so you would have to place corner blocks in your schematic with your object in between centered the way you want it, then after converting the schematic to BO3's you'd remove the corner blocks from the bo3's manually. Also, TCEE slices schematics to 16x16 BO3's automatically and turns the slices into branches. That's handy for big schematics like structures that you would want to spawn with CustomStructure(), but for trees and rocks etc you would want to use CustomObject() and a 32x32 single BO3 with no branches. I'll update TCEE asap so that it let's you choose to export a BO3 as a single 16x16 BO3, single 32x32 BO3 or multiple 16x16 BO3s with branches configured.
For now I'll close this issue, you can keep an eye on the TCEE repo for a new commit, hopefully I'll be able to get to it in the next few weeks (lots of other coding stuff to do that has prio, sorry).


PhysicsFromMesh entities have inverted normals when using trace functions

Physics objects created using Entity:PhysicsFromMesh seem to have inverted normals when tracing them using util.TraceLine (this probably goes for all derivatives of this trace function).

Thanks! Do you have an add-on or lua_run or whatever that can reproduce?


live-common 18

to be continued.
@machard I think you can take over this PR to add the small tasks for WalletConnect.

todo:

[ ] add hashes in sign message summary
[ ] hook into the lending approve flow if a transaction is an approve (need https://github.com/LedgerHQ/ledger-live-common/pull/1012/files)
[x] remove from experimental
[x] fix reconnexion issue

todo:

[ ] add hashes in sign message summary
[ ] hook into the lending approve flow if a transaction is an approve (need https://github.com/LedgerHQ/ledger-live-common/pull/1012/files)
[x] remove from experimental
[x] fix reconnexion issue

unfortunately the nano app display hashes that are different from the one we give to the eth lib :/

unfortunately the nano app display hashes that are different from the one we give to the eth lib :/


[BACKLOG-22705] PDI localization issues

Build Completed
:x: This pull request has errors. They will need to be addressed before it can be accepted. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -fn -f 'pom.xml' -pl 'ui,dbdialog,engine,core,plugins/pur/core' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install
mvn -B -fn -f 'integration/pom.xml' -pl '.' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'ui,dbdialog,engine,core,plugins/pur/core' -P '!assemblies' -amd build-helper:remove-project-artifact && mvn -B -f 'integration/pom.xml' -pl '.' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  core/src/main/java/org/pentaho/di/core/plugins/BasePluginType.java
  core/src/main/java/org/pentaho/di/i18n/GlobalMessageUtil.java
  core/src/main/java/org/pentaho/di/i18n/GlobalMessages.java
  core/src/main/java/org/pentaho/di/i18n/LAFMessageHandler.java
  core/src/main/java/org/pentaho/di/i18n/LanguageChoice.java
  core/src/test/java/org/pentaho/di/i18n/GlobalMessageUtilTest.java
  core/src/test/java/org/pentaho/di/i18n/GlobalMessagesTest.java
  core/src/test/resources/org/pentaho/di/foo/messages/messages_fr.properties
  core/src/test/resources/org/pentaho/di/i18n/messages/messages.properties
  core/src/test/resources/org/pentaho/di/i18n/messages/messages_fr_FR.properties
  core/src/test/resources/org/pentaho/di/i18n/messages/messages_ja.properties
  core/src/test/resources/org/pentaho/di/i18n/messages/test_ascii_messages_ja.properties
  core/src/test/resources/org/pentaho/di/i18n/messages/test_utf8_messages.properties
  core/src/test/resources/org/pentaho/di/i18n/messages/test_utf8_messages_de.properties
  dbdialog/pom.xml
  dbdialog/src/main/java/org/pentaho/ui/database/Messages.java
  dbdialog/src/test/java/org/pentaho/ui/database/MessagesTest.java
  engine/src/main/java/org/pentaho/di/job/entry/validator/ValidatorMessages.java
  integration/src/it/java/org/pentaho/di/blackbox/BlackBoxIT.java
  plugins/pur/core/src/main/java/org/pentaho/di/ui/repository/pur/repositoryexplorer/abs/controller/AbsController.java
  ui/src/main/java/org/pentaho/di/ui/core/PropsUI.java
  ui/src/main/java/org/pentaho/di/ui/core/database/dialog/XulDatabaseDialog.java
  ui/src/main/java/org/pentaho/di/ui/core/dialog/EnterOptionsDialog.java
  ui/src/main/java/org/pentaho/di/ui/spoon/SpoonPerspectiveManager.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes (click to expand)
org.pentaho.di.core.logging.LogChannel

Complexity Change: -1.6% :small_red_triangle_down:
Instruction Change: -1.9% :small_red_triangle_down:
Line Change: -1.4% :small_red_triangle_down:
Method Change: -2.5% :small_red_triangle_down:

org.pentaho.di.core.plugins.BasePluginType

Instruction Change: -0.1% :small_red_triangle_down:
Line Change: -0.2% :small_red_triangle_down:

org.pentaho.di.i18n.GlobalMessages

Branch Change: -8.3% :small_red_triangle_down:

org.pentaho.di.i18n.LAFMessageHandler

Method Change: -2.4% :small_red_triangle_down:

org.pentaho.ui.database.Messages

Complexity Change: -37.5% :small_red_triangle_down:
Instruction Change: -79.6% :small_red_triangle_down:
Line Change: -66.5% :small_red_triangle_down:
Method Change: -42.9% :small_red_triangle_down:

org.pentaho.di.trans.steps.constant.ConstantMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.memgroupby.MemoryGroupByMeta

Branch Change: -1.1% :small_red_triangle_down:
Complexity Change: -1.3% :small_red_triangle_down:

org.pentaho.di.trans.steps.symmetriccrypto.symmetriccryptotrans.SymmetricCryptoTransMeta

Branch Change: -3.3% :small_red_triangle_down:
Complexity Change: -1.8% :small_red_triangle_down:
Instruction Change: -0.3% :small_red_triangle_down:

org.pentaho.di.trans.steps.textfileinput.TextFileInputMeta

Branch Change: -0.5% :small_red_triangle_down:

org.pentaho.di.trans.steps.salesforceinsert.SalesforceInsertMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.ui.spoon.SpoonPerspectiveManager

Instruction Change: -0.1% :small_red_triangle_down:

Checkstyle violations
The code submitted is not complying with one or more of our guidelines. To perform these checks locally, please use this tool.
/home/buildguy/project/core/src/main/java/org/pentaho/di/i18n/GlobalMessageUtil.java

:heavy_exclamation_mark: ')' is not preceded with whitespace. at Line: 450 Column: 38

/home/buildguy/project/plugins/pur/core/src/main/java/org/pentaho/di/ui/repository/pur/repositoryexplorer/abs/controller/AbsController.java

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 132 Column: 72

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 133 Column: 85

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 134 Column: 96

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 135 Column: 114

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 137 Column: 91

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 138 Column: 104

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 157 Column: 108

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 158 Column: 120

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 159 Column: 82

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 160 Column: 94

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 206 Column: 78

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 207 Column: 79

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 208 Column: 108

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 214 Column: 76

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 215 Column: 79

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 217 Column: 118

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 237 Column: 78

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 238 Column: 79

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 239 Column: 108

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 245 Column: 76

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 246 Column: 79

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 248 Column: 118

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 324 Column: 82

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 327 Column: 94

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 333 Column: 108

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 351 Column: 88

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 354 Column: 106

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 360 Column: 120

Build Completed
:x: This pull request has errors. They will need to be addressed before it can be accepted. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
mvn -B -fn -f 'pom.xml' -pl 'ui,dbdialog,engine,core,plugins/pur/core' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install
mvn -B -fn -f 'integration/pom.xml' -pl '.' -P '!assemblies' -Dsurefire.runOrder=alphabetical -Daudit -amd clean install

Cleanup Commands
mvn -B -f 'pom.xml' -pl 'ui,dbdialog,engine,core,plugins/pur/core' -P '!assemblies' -amd build-helper:remove-project-artifact && mvn -B -f 'integration/pom.xml' -pl '.' -P '!assemblies' -amd build-helper:remove-project-artifact

Changed files
  core/src/main/java/org/pentaho/di/core/plugins/BasePluginType.java
  core/src/main/java/org/pentaho/di/i18n/GlobalMessageUtil.java
  core/src/main/java/org/pentaho/di/i18n/GlobalMessages.java
  core/src/main/java/org/pentaho/di/i18n/LAFMessageHandler.java
  core/src/main/java/org/pentaho/di/i18n/LanguageChoice.java
  core/src/test/java/org/pentaho/di/i18n/GlobalMessageUtilTest.java
  core/src/test/java/org/pentaho/di/i18n/GlobalMessagesTest.java
  core/src/test/resources/org/pentaho/di/foo/messages/messages_fr.properties
  core/src/test/resources/org/pentaho/di/i18n/messages/messages.properties
  core/src/test/resources/org/pentaho/di/i18n/messages/messages_fr_FR.properties
  core/src/test/resources/org/pentaho/di/i18n/messages/messages_ja.properties
  core/src/test/resources/org/pentaho/di/i18n/messages/test_ascii_messages_ja.properties
  core/src/test/resources/org/pentaho/di/i18n/messages/test_utf8_messages.properties
  core/src/test/resources/org/pentaho/di/i18n/messages/test_utf8_messages_de.properties
  dbdialog/pom.xml
  dbdialog/src/main/java/org/pentaho/ui/database/Messages.java
  dbdialog/src/test/java/org/pentaho/ui/database/MessagesTest.java
  engine/src/main/java/org/pentaho/di/job/entry/validator/ValidatorMessages.java
  integration/src/it/java/org/pentaho/di/blackbox/BlackBoxIT.java
  plugins/pur/core/src/main/java/org/pentaho/di/ui/repository/pur/repositoryexplorer/abs/controller/AbsController.java
  ui/src/main/java/org/pentaho/di/ui/core/PropsUI.java
  ui/src/main/java/org/pentaho/di/ui/core/database/dialog/XulDatabaseDialog.java
  ui/src/main/java/org/pentaho/di/ui/core/dialog/EnterOptionsDialog.java
  ui/src/main/java/org/pentaho/di/ui/spoon/SpoonPerspectiveManager.java

Unit Test Coverage
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.

:warning: Coverage Changes (click to expand)
org.pentaho.di.core.logging.LogChannel

Complexity Change: -1.6% :small_red_triangle_down:
Instruction Change: -1.9% :small_red_triangle_down:
Line Change: -1.4% :small_red_triangle_down:
Method Change: -2.5% :small_red_triangle_down:

org.pentaho.di.core.plugins.BasePluginType

Instruction Change: -0.1% :small_red_triangle_down:
Line Change: -0.2% :small_red_triangle_down:

org.pentaho.di.i18n.GlobalMessages

Branch Change: -8.3% :small_red_triangle_down:

org.pentaho.di.i18n.LAFMessageHandler

Method Change: -2.4% :small_red_triangle_down:

org.pentaho.ui.database.Messages

Complexity Change: -37.5% :small_red_triangle_down:
Instruction Change: -79.6% :small_red_triangle_down:
Line Change: -66.5% :small_red_triangle_down:
Method Change: -42.9% :small_red_triangle_down:

org.pentaho.di.job.entries.waitforsql.JobEntryWaitForSQL

Branch Change: -0.8% :small_red_triangle_down:
Complexity Change: -1% :small_red_triangle_down:
Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.step.StepMeta

Branch Change: -0.7% :small_red_triangle_down:
Complexity Change: -0.6% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:
Line Change: -0.3% :small_red_triangle_down:

org.pentaho.di.trans.steps.datagrid.DataGridMeta

Branch Change: -2% :small_red_triangle_down:
Complexity Change: -1.7% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.dimensionlookup.DimensionLookupMeta

Branch Change: -1.8% :small_red_triangle_down:
Complexity Change: -1.1% :small_red_triangle_down:
Instruction Change: -0.4% :small_red_triangle_down:
Line Change: -0.3% :small_red_triangle_down:

org.pentaho.di.trans.steps.excelwriter.ExcelWriterStepMeta

Branch Change: -1.3% :small_red_triangle_down:
Complexity Change: -0.7% :small_red_triangle_down:

org.pentaho.di.trans.steps.groupby.GroupByMeta

Branch Change: -2.1% :small_red_triangle_down:
Complexity Change: -2.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.pgbulkloader.PGBulkLoaderMeta

Branch Change: -1.8% :small_red_triangle_down:
Complexity Change: -0.9% :small_red_triangle_down:
Instruction Change: -0.2% :small_red_triangle_down:
Line Change: -0.3% :small_red_triangle_down:

org.pentaho.di.trans.steps.sort.SortRowsMeta

Instruction Change: -0.1% :small_red_triangle_down:

org.pentaho.di.trans.steps.sortedmerge.SortedMergeMeta

Instruction Change: -0.2% :small_red_triangle_down:

org.pentaho.di.trans.steps.symmetriccrypto.symmetriccryptotrans.SymmetricCryptoTransMeta

Branch Change: -3.3% :small_red_triangle_down:
Complexity Change: -1.8% :small_red_triangle_down:
Instruction Change: -0.3% :small_red_triangle_down:

Note: The list of offending coverage changes extends beyond the presented results and was truncated to prevent reaching the comment size limit.

Checkstyle violations
The code submitted is not complying with one or more of our guidelines. To perform these checks locally, please use this tool.
/home/buildguy/project/plugins/pur/core/src/main/java/org/pentaho/di/ui/repository/pur/repositoryexplorer/abs/controller/AbsController.java

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 132 Column: 72

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 133 Column: 85

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 134 Column: 96

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 135 Column: 114

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 137 Column: 91

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 138 Column: 104

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 157 Column: 108

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 158 Column: 120

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 159 Column: 82

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 160 Column: 94

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 206 Column: 78

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 207 Column: 79

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 208 Column: 108

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 214 Column: 76

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 215 Column: 79

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 217 Column: 118

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 237 Column: 78

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 238 Column: 79

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 239 Column: 108

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 245 Column: 76

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 246 Column: 79

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 248 Column: 118

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 324 Column: 82

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 327 Column: 94

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 333 Column: 108

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 351 Column: 88

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 354 Column: 106

:heavy_exclamation_mark: ';' is not followed by whitespace. at Line: 360 Column: 120


rewrite: Add support for rewrite rule set assignment

So that rewrite rule sets predefined in the app gateway can be assigned
to routing rules by adding an annotation in the corresponding Ingress.
Fixes #1003.
Related to #462.

Checklist

[x] The title of the PR is clear and informative
[x] If applicable, the changes made in the PR have proper test coverage
[x] Issues addressed by the PR are mentioned in the description followed by Fixes.

Description

Fixes

@akshaysngupta is that released with 1.5.0 ? do we have any documentation ?

The docs are here.

https://azure.github.io/application-gateway-kubernetes-ingress/annotations/
This should be updated as well

@bisaloa , It seems that the documentation was updated but the feature still doesn't work. I raised a case with Microsoft support and they have confirmed that the annotation is not useable with 1.5.0 rc1 but might be released in 1.5.0. As usual, no gurantees.

As @m-matharu mentioned, the feature is still not working. Waiting for it...


Documentation update for HtmlEscape and HtmlEscapeMode

Added examples for HtmlEscape and HtmlEscapeMode usage.
Small fixes to texts in file

@googlebot I consent.

review in https://dart-review.googlesource.com/c/sdk/+/218989


Fix assertion in chains test

Description
For this test we expect the TaskRun not to fail as it is running in
non-strict mode. This assertion was erroneously changed from ToBeTrue
to ToBeFalse in #151.
Issue ticket number and link
https://issues.redhat.com/browse/HACBS-949
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Run the test locally against CRC
Checklist:

[x] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have updated labels (if needed)

This is a fix for unblocking pull requests from getting merged in infra-deployments.

Closed in favor of #158


As a content editor, I want to add a formatted abstract to essay content so that I can summarize content for the viewer.

dev notes

[ ] create a new wagtail "abstract" block
[ ] implemented as an <aside>?
[ ] styles: indent and italicize

We're unclear on the specifics of this one and how the abstract differs from the description text displayed on the analysis list page. Will check meeting notes.

closing as we can implement this to our satisfaction now using regular wagtail streamfield formatting.


Public attributes

PROBLEM: Many of the attributes are public.
SOLUTION: Need to make private and replace with public getter/setter methods.
REFERENCE: Bloch - Effective Java - Item 16: In public classes, use accessor methods, not public fields

Now have made public getter/setter methods and private attributes


Feature request: Beam.pro

Hello, there's a new livestreaming service almost like twitch.tv, but it's named beam.pro. They're a new streaming service which already have a lot ready for the future. Many people have already added Beam support and thought it would be useful to have this for livestreamer as well.

Duplicate of #771.


Optimize neg_mod

This change optimizes neg_mod (25% faster here) by performing a bit mask instead of adc.

Thank you!


Fix data ttl keeper timer test case bug

Please answer these questions before submitting pull request

Why submit this pull request?

[x] Bug fix

[ ] New feature provided

[ ] Improve performance

Related issues

Bug fix

Bug description.
when cross month ,the test will fail.so CI will failed for all.
Problem

java.lang.AssertionError:
Expected :20180493000000
Actual   :20180423000000

20180501 - 8 != 20180423

How to fix?
use same logic code to make unit testcase instead of subtract 8.

New feature or improvement

Describe the details and related test reports.

Coverage remained the same at 21.623% when pulling 537cd9117998f0bd9f64d4b7ddd834e38da0c76b on candyleer:Fix_DataTTLKeeperTimerTestCase_bug into c53359a1a0d0823dce233cf4441b6199d7915012 on apache:master.


Fix issue with github/linguist#1932

#1932 introduced an error that prevented download-grammars from working. The script issued an error message saying that vendor/grammars/Elm.tmLanguage is not a file (what is true because it is a directory).
The reason for this is:
Submodules must not end with neither .tmlanguage nor .plist. Otherwise the download-grammars-script will interpret the submodule as a SingleFile instead of a DirectoryPackage, which will lead to an error message.
The relevant line in download-grammars is https://github.com/github/linguist/blob/f2ab426d38dc391a6b0612cecf29cb67efa931b4/script/download-grammars#L153

cc @aroben

Submodules must not end with neither .tmlanguage nor .plist. Otherwise the download-grammars-script will interpret the submodule as a SingleFile instead of a DirectoryPackage, which will lead to an error message.

Thanks for including this explanation. I think a better fix would be to ask the filesystem whether the local path is a file or directory rather than deciding based on the filename extension. A File.directory? check should be sufficient.

Sure, that would be better. My solution was more like a quick and dirty solution to just make it work again. I'll look into it tomorrow and hopefully come up with a better solution.
Thanks for the tip. I'm not very familiar with Ruby, but let's learn by doing ;-).

I've now changed the download-script instead of the name of the Elm-grammar.
But simply changing source.end_with?('.tmLanguage', '.plist') to File.directory?(source) was not sufficient, because e.g. .tar.gz-files produce is_single_file=false, so I simply combined both criteria.

I ran into and fixed this problem over in #1909. Thanks for your work here @floscher; I would have been really confused had you not already diagnosed the problem!


Full of dependency errors

I was trying to set up this package. Tons of dependency errors. Its not clear how to install the dependencies. Relent (based on your 5.0) is not picked up, until i looked at your manifest and used the 2.0 Relent. And then tons of these.
No idea whats happening.

"dependencies": {
"com.boundfoxstudios.fluentassertions": "https://github.com/BoundfoxStudios/fluentassertions-unity.git#upm",
"com.bugsnag.unitynotifier": "https://github.com/bugsnag/bugsnag-unity-upm.git",
"com.cysharp.unitask": "https://github.com/Cysharp/UniTask.git?path=src/UniTask/Assets/Plugins/UniTask",
"com.mochineko.chatgpt-api": "https://github.com/mochi-neko/ChatGPT-API-unity.git?path=/Assets/Mochineko/ChatGPT_API#0.5.0",
"com.mochineko.chatgpt-api.memory": "https://github.com/mochi-neko/ChatGPT-API-unity.git?path=/Assets/Mochineko/ChatGPT_API.Memory#0.4.0",
"com.mochineko.relent": "https://github.com/mochi-neko/Relent.git?path=/Assets/Mochineko/Relent#0.2.0",
"com.mochineko.tiktoken-sharp": "https://github.com/mochi-neko/ChatGPT-API-unity.git?path=/Assets/Mochineko/TiktokenSharp#0.4.0",

@enigmablue
Please remove following dependencies:

"com.mochineko.chatgpt-api.memory": "https://github.com/mochi-neko/ChatGPT-API-unity.git?path=/Assets/Mochineko/ChatGPT_API.Memory#0.4.0",
"com.mochineko.relent": "https://github.com/mochi-neko/Relent.git?path=/Assets/Mochineko/Relent#0.2.0",
"com.mochineko.tiktoken-sharp": "https://github.com/mochi-neko/ChatGPT-API-unity.git?path=/Assets/Mochineko/TiktokenSharp#0.4.0",

I'm sorry that I forgot to update dependencies of sample in README.
"Relent" package is only needed when you use Relent version API of ChatGPT API client: "com.mochineko.chatpgt-api.relent" that can use retry, timeout, circuit breaker and bulkhead to connect API.

I think it can't work because the chatgpt-api has the tests folder and the tests folder has tiktoken.
I have to manually delete the tests folder

Do you install this package by Unity Package Manager?
Tests folder is not included in package.
Minimal introduction is there:
Add following dependencies to mainfest.json on your Unity project.
{
  "dependencies": {
    "com.mochineko.chatgpt-api": "https://github.com/mochi-neko/ChatGPT-API-unity.git?path=/Assets/Mochineko/ChatGPT_API#0.5.0",
    "com.unity.nuget.newtonsoft-json": "3.0.2",
  }
}

If you use sample code in this repository, please add UnTask dependency,
 "com.cysharp.unitask": "https://github.com/Cysharp/UniTask.git?path=src/UniTask/Assets/Plugins/UniTask",
For your information, memory package ("com.mochineko.chatgpt-api.memory") and tiktoken package ("com.mochineko.tiktoken-sharp") are merged to main package ("com.mochineko.chatgpt-api") from ver 0.5.0.


Customize the shortest path algorithm

Hi there! About computing shortest paths, I was wondering if there is a way to customize the algorithm to find it. I need paths that take into account the distance from obstacles, so that a shortest path follower agent can avoid crawling along them. Could you suggest me which classes are responsible for computing the shortest path and how can I modify them? I had a look to the test_greedy_follower.py python script and to the ECCV navigation tutorial notebook but it is not clear to me where the PathFinder and ShortestPath classes are located and what is their role...
Thank you in advance!

Hey @rosanom,
The source code for NavMesh computation and shortest path heuristics are written in C++ and located entirely in the nav module. You are welcome to fork the code and try out your own modifications.
Sounds like you want to add a heuristic that the best path doesn't need to be shortest, but should balance path length with distance to objects. This would require a custom implementation, possibly in C++ if you want to modify existing code.
Another simpler option if you just want a bit more distance from the objects with default sim features is to grow the agent radius (i.e., shrink the navmesh). This has the side effect of possibly closing off tight spaces, however, so it would be a balance.


fixed deprecation error

#4

Thanks for submitting a PR to fix!  I have updated to support new and new-less invocation, and added some rudimentary tests to confirm.


Repository Outdated Compared to Rubygem

The code in this repository (raihan2006i/active_admin_paranoia) is outdated compared to the version on Rubygem. The repository here is up to 1.0.11, while Rubygem has advanced to 1.1.0. The code on Rubygem appears to be from the forked repository DocSpring/active_admin_paranoia.
Could you please update raihan2006i/active_admin_paranoia to the latest version (1.1.0)?
Background
We recently upgraded active_admin_paranoia from 1.0.11 to 1.1.0, encountering a breaking change that introduced destroy and archive actions (https://my.diffend.io/gems/active_admin_paranoia/1.0.11/1.0.12). Initially, I checked GitHub for updates, but found no relevant changes, leading to a time-consuming investigation. It would be helpful if the GitHub repository is kept up-to-date.
I also noticed issue #19, but believe it’s crucial for this repository to at least match version 1.1.0.

@ndbroadbent, Since you are now a collaborator of this repo and Rubygem, could you please sync this repo with your repo?
Also, can you please use this repo as the primary source for any future changes and publish new versions from this repo on Rubygem? While publishing new versions, make sure to tag them as well. Thanks again for your contribution and keep this repo alive 👍


Development

Issue #4447 fixed.

[ ] issue https://github.com/bagisto/bagisto/issues/4455 => fix the icon in ar locale https://prnt.sc/wkxn6x
[ ] issue https://github.com/bagisto/bagisto/issues/4459 => disable wishlist routes also.
[ ] issue https://github.com/bagisto/bagisto/issues/4457 => fixed
[ ] issue https://github.com/bagisto/bagisto/issues/4447 => fixed

[ ] issue https://github.com/bagisto/bagisto/issues/4455 => fix the icon in ar locale https://prnt.sc/wkxn6x
[ ] issue https://github.com/bagisto/bagisto/issues/4459 => disable wishlist routes also.
[ ] issue https://github.com/bagisto/bagisto/issues/4457 => fixed
[ ] issue https://github.com/bagisto/bagisto/issues/4447 => fixed


Mention the concept of providers in NEWS.md and CHANGES.md

Apart from answering the review comments, I also added a bit more text in CHANGES.md

Agree it's urgent

Merged
master:
8e7d941ade3a86e352d9c3d601f61c033dc6788b Mention the concept of providers in NEWS.md and CHANGES.md
3.0:
4c4ab4d7efdf8c9b49c9838742a0fcd7321d88ff Mention the concept of providers in NEWS.md and CHANGES.md


Fan speed : auto

Hello,
Many AC have the option to set the fan speed to « auto ». Tasmota irhvac command supports it too. Maybe this plugin should support ?
I think there could be an option in configuration to enable the « auto fan speed ». That will set this speed when the HomeKit fan speed slider would be set to a low level (or high if you prefers).
An other option could be to force the auto speed, whatever the slider level.
What do you think about it ? If you like the idea, I could give a try to implement it, and submit a PR.

The code in #6 was a very good start, but the PR is just too get around I'm afraid. Please have a look at the review comments - Looking forward to a new PR!


pornhub download error

Checklist

[x] I'm reporting a broken site support issue
[x] I've verified that I'm running youtube-dl version 2020.12.22
[x] I've checked that all provided URLs are alive and playable in a browser
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x] I've searched the bugtracker for similar bug reports including closed ones
[x] I've read bugs section in FAQ

Verbose log

[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', '--proxy', 'socks5://<IP_ADDRESS>:1080/', 'https://cn.pornhub.com/model/sexdeti']
[debug] Encodings: locale cp936, fs mbcs, out cp936, pref cp936
[debug] youtube-dl version 2020.12.22
[debug] Python version 3.4.4 (CPython) - Windows-10-10.0.19041
[debug] exe versions: ffmpeg 4.2.2, ffprobe 4.2.2
[debug] Proxy map: {'http': 'socks5://<IP_ADDRESS>:1080/', 'https': 'socks5://<IP_ADDRESS>:1080/'}
[PornHubPagedVideoList] model/sexdeti/videos: Downloading page 1
[download] Downloading playlist: model/sexdeti/videos
[PornHubPagedVideoList] playlist model/sexdeti/videos: Collected 37 video ids (downloading 37 of them)
[download] Downloading video 1 of 37
[PornHub] ph5fceabef929ce: Downloading pc webpage
[PornHub] ph5fceabef929ce: Downloading tv webpage
ERROR: Unable to extract encoded url; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmprhhzjl7r\build\youtube_dl\YoutubeDL.py", line 803, in wrapper
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmprhhzjl7r\build\youtube_dl\YoutubeDL.py", line 824, in __extract_info
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmprhhzjl7r\build\youtube_dl\extractor\common.py", line 532, in extract
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmprhhzjl7r\build\youtube_dl\extractor\pornhub.py", line 307, in _real_extract
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmprhhzjl7r\build\youtube_dl\extractor\pornhub.py", line 254, in extract_js_vars
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmprhhzjl7r\build\youtube_dl\extractor\common.py", line 1010, in _search_regex
youtube_dl.utils.RegexNotFoundError: Unable to extract encoded url; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Description

WRITE DESCRIPTION HERE

Premium content.


das: DASing of past headers

This PR implements DASing of past headers in a single routine.
Eventually, this will be parallelised.
TODO

[ ] figure out what to do in the instance that DASer runs and samples new headers [100:150] and DASer is stopped, so sample routine stores latest checkpoint to disk as last DASed height (150) but catchUp routine has only sampled from [1:40] so there is a gap missing from (40: 100)?
[x] fix constructor
[x] cleanup
[ ] 2 TODOs
[x] lint
[x] doc.go
[x] open issue for parallelisation of DASer
[x] open issue for DASState

Resolves https://github.com/celestiaorg/celestia-node/issues/181.

I think I will address the first TODO in a separate issue:
figure out what to do in the instance that DASer runs and samples new headers [100:150] and DASer is stopped, so sample routine stores latest checkpoint to disk as last DASed height (150) but catchUp routine has only sampled from [1:40] so there is a gap missing from (40: 100)?

CI won't run with merge conflicts IIRC, so could you fix the conflict as you push?

Tested against devnet 💪🏻

@liamsi the 2 TODOs mentioned initially in the comment of this PR are related to an issue that can only be resolved once https://github.com/celestiaorg/celestia-node/issues/427 is implemented.


comments for K8 describe package

Signed-off-by: Philip-21<EMAIL_ADDRESS>Description
Created comments for k8 describe package
This PR fixes #287
Signed commits

[x] Yes, I signed my commits.

@Aisuko from what you are saying, do you want me to only comment on the role for the describe.go  so it could tally with describe_test.go and should  i also take out some of the comments i wrote in the describe.go ?

@Aisuko from what you are saying, do you want me to only comment on the role for the describe.go so it could tally with describe_test.go and should I also take out some of the comments i wrote for the codes in the describe.go ?

Please keep the code comments in the descrble.go. The mock testing part already include in your previous PR right? This PR is only for code comments. So, we can merge it directly.

Please do not forget to update to the latest version code.

@Aisuko from what you are saying, do you want me to only comment on the role for the describe.go so it could tally with describe_test.go and should I also take out some of the comments i wrote for the codes in the describe.go ?

Please keep the code comments in the descrble.go. The mock testing part already include in your previous PR right? This PR is only for code comments. So, we can merge it directly.

Yes this pr only includes code comments for the describe.go . The other Pr is for the Mock testing

Please do not forget to update to the latest version code.

Please how do you mean by this

ok thanks,  i  have just updated branch to latest version.

We need to only include the describe.go file in this PR. This PR only aims to add code comment to describle.go

ok i have removed the describe_test.go file . The describe.go file is what is in this pr

CI may have some issues, I check the PR manually by using golangci-lint, there is no error. ErrGetDescriberFunc was defined under the same package.

CI may have some issues, I check the PR manually by using golangci-lint, there is no error. ErrGetDescriberFunc was defined under the same package.

does it mean that it shouldn't be there .

CI may have some issues, I check the PR manually by using golangci-lint, there is no error. ErrGetDescriberFunc was defined under the same package.

does it mean that it shouldn't be there .

No worries, this is no related to this PR.


Do not mark unchanged backend var deps as dirty

part of #4487

ci flakiness again, no issue with the changes introduced in this PR


Index Snippet - PHB

Preview vs PHB:

With greater font size and line height, for better readabilty.
completes #1807

I think the text should match the PHB as much as possible, even if the readability suffers.  The goal should always be to match the source, and then let users make desired changes.  This makes it easy to simply say "well this is what matches the book" for any complaints.  Otherwise we will get complaints about why it doesn't match, which will be harder to explain ("we thought ours looked better than the official...").

I think the text should match the PHB as much as possible, even if the readability suffers.

Ok then, will try to measure text size in a physical copy to get the correct size.


It's broken

This doesn't work.  I've followed some of the instructions and it doesn't work.

Ha ha. Try reading some more of the instructions. :-)


Add Ethereum address to FUNDING.yml

I'd like to see an Ethereum address added to the custom property of the FUNDING.yml file for GitHub Sponsors. This would allow a canonical address to send funds to. For example, I'm building a project that allows developers to setup one recurring donation that is split between all of their dependencies with an Ethereum address: https://sustainus.io

are you the respective owner?
On 8/29/19, Jordan Last<EMAIL_ADDRESS>wrote:

I'd like to see an Ethereum address added to the custom property of the
FUNDING.yml file for GitHub Sponsors. This would allow a canonical address
to send funds to. For example, I'm building a project that allows developers
to setup one recurring donation that is split between all of their
dependencies with an Ethereum address: https://sustainus.io
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/pixijs/pixi.js/issues/6055

If you are the respective owner just a head up I am doing all I can to
protect this data.
On 8/29/19, Jordan Last<EMAIL_ADDRESS>wrote:

I'd like to see an Ethereum address added to the custom property of the
FUNDING.yml file for GitHub Sponsors. This would allow a canonical address
to send funds to. For example, I'm building a project that allows developers
to setup one recurring donation that is split between all of their
dependencies with an Ethereum address: https://sustainus.io
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/pixijs/pixi.js/issues/6055

I'm not sure what you mean?

npm-based funding, wow. much crypto.

We are not interest in Ethereum donations at this time. Thanks for the suggestion.


Fix OpenID registration route

Resolves: https://github.com/go-gitea/gitea/issues/2101

LGTM - very welcome. Please merge ASAP :)

LGTM


Failure on GNU screen when TERM=screen

I've noticed that for some reason asciimatics doesn't work when the TERM environment variable is set to screen when using GNU screen. On one of my systems, the GNU screen default is TERM=screen-256color, but on others TERM=screen. manually changing the TERM variable to screen-256color fixes the issue, however I'm confused as to why this TERM value matters so much.
Anyway here's the traceback for when asciimatics fails with TERM=screen. This failure occurs with any code that uses asciimatics, so I used samples/forms.py on the master branch in this traceback:
Traceback (most recent call last):
  File "samples/forms.py", line 147, in <module>
    Screen.wrapper(demo, catch_interrupt=False, arguments=[last_scene])
  File "/root/asciimatics/asciimatics/screen.py", line 1168, in wrapper
    func(screen, *arguments)
  File "samples/forms.py", line 142, in demo
    ], -1)], stop_on_resize=True, start_scene=scene)
  File "/root/asciimatics/asciimatics/screen.py", line 1343, in play
    scenes, unhandled_input=unhandled_input, start_scene=start_scene)
  File "/root/asciimatics/asciimatics/screen.py", line 1412, in set_scenes
    self.clear()
  File "/root/asciimatics/asciimatics/screen.py", line 1232, in clear
    self._change_colours(Screen.COLOUR_WHITE, 0, 0)
  File "/root/asciimatics/asciimatics/screen.py", line 2224, in _change_colours
    self._fg_color, colour).decode("utf-8"))
TypeError: a bytes-like object is required, not 'NoneType'

I tried catching this exception and ignoring it for both fg and bg, however the asciimatics display just fills with a bunch of dollar sign characters instead of any meaningful text

My current workaround for this issue is to programatically change the TERM variable and reset it after asciimatics is done

I'm going to guess that your terminfo DB for screen has no colour support.  In particular, I bet it has no setaf entry.  You should be able to verify that by running infocmp screen.  If so you could try updating the definition.

Ok, it looks like screen provides a load of options on how to tweak which terminfo definitions you use.  See https://www.gnu.org/software/screen/manual/screen.html#Termcap.  I suggest you either tweak the terminfo definition or install a new one to reflect your specific terminal running screen.

For some reason I can no longer reproduce this issue. I'm not sure what changed. setaf is set right now.
I did find a session which had TERM=vt100 where none of the asciimatics samples worked however the windows just froze instead of emitting an error.
Thanks for bearing with me. If I can repro this again I'll try to figure out what awry setting caused the error.


uClock supported by Raspi pico ?

Hi,
i am already using you marvellous library to run a sequencer/arpeggiator on Arduino Mega and it is particularly reliable.
Is the uClock library compatible with the RP2040 used in Raspberry pico boards ? it 's a dual core ARM Cortex M0+ @133MHz
Best regards
JV

Hi @AlpesMachines , great device the matrix_ctrlr! do you have any video or sounds of generated arpeggios?
Are you talking about the Xiao RP2040? I've just wrote a support for the Xiao M0, but unfortunaly i dont have this other one with me to check how can it be ported.
Maybe i can try to get some info over the net about timers usage for RP2040 xiao arduino support and sent to you for tests.

Hi @midilab
thanks for your nice message ! the only video i did has the Matrix Ctrlr in slave mode (external midi sync sent by Roland TR8)
I am not talking about the specific Xiao RP2040 as the board has a very limited number of pins but this one by WeAct which is a clone of the Raspi Pico.
I would be very happy and honoured to test your sketch 👍

this oberheim sounds so good! congrats on the project, the interface is really amazing, how did you made the frontpanel?
So basiclly uClock is wrote for arduino platform only, if they come to support arduino(i didn't see any mention on the forum about it) then it will be easy to port.
Otherwise you can port the library to anyother platform since its basicly c++, but outsite arduino environment you need to figureout the timer usage and interrupt handlers of that platform to port it.

thanks for your approval on my design 😃
the front panel is a face plate in aluminium (but you could use PCB FR4 material) with a sticker on it (polyester V200) exactly like the Matrix6 and some car paint.
I know that uClock is based on arduino, especially TimerOne of AVR 8bits (that's why i am using it, as a replacement of the flexitimer2 lib), but has it is just a timer parameters definition, i would like it to be ported on other platform like STM32 or RP2040. Unfortunately i am not skilled enough within Timer to easily port that myself in just one evening 👅
Hence my question as your development saves me lots of time ❤

Once they have some arduino port that could be viable to do.

Hi @midilab, thanks for this great library.  I recently managed to get it working with my Teensy 4.1 project where it has improved my sequencer's clock accuracy substantially compared to the naïve "track micros-since-last-tick" method.
Since I'm sharing a lot of the code between my Teensy project and my RP2040 projects, and even though the RP2040 project clock is much more accurate even using the naïve approach (I think because I can do all my GUI updates on the second core), I thought it might be good to get uClock working on the RP2040 as well.
I've had a little tinker, and tried to adapt the samd or esp32 platform headers to compile on the RP2040 using the earlephilhower rp2040 core, but not had any luck so far.  The earlephilhower core is built on top of freertos, so I'd hoped that the esp32 platform would be the least bother, but compile fails with eg "'timerBegin' was not declared in this scope".
Would porting uClock to rp2040 be simple at this stage?  Are there any hints you can give me on how to get this up and running?
Thanks!


cunder-12: add gh actions unittest & format

This PR adds github actions for building and running Unittests, and another for formatting C/C++ source/header files.

The windows and linux library is failing because of the hard-coded path, right?

Yes, but it'll still fail we don't load LibTorch dlls since it won't build cunder or unittests.


[CI] Updated RBE Windows Image (MSVC 2022)

Updated the Windows RBE image to use MSVC 2022
This is the last part of upgrading MSVC to 2022. This aligns with the minimum MSVC version required for gRPC, as stated in the Foundational C++ Support Matrix.
An alternative & incremental approach to https://github.com/grpc/grpc/pull/37987
Follow-up of https://github.com/grpc/grpc/pull/38006

Bazel RBE Windows always fail with internal tool errors which are expected. This is a known issue of current RBE/Windows environment.


Error in the process of using

When I activate ipex-llm and use the ollama models for a few seconds, I encounter the following error message during the content output process:
"ollama: Error: Failed to read the llm response due to a connection being forcibly closed by the remote host."
This error does not reappear once I deactivate ipex-llm.

Hi @bwy727 , I am unable to reproduce the issue. Could you please run ollama again with the commands below and provide detailed runtime logs from the ollama server?
export OLLAMA_KEEP_ALIVE=-1
./ollama serve


Update registry binary to version v2.4.0

Update registry binary to version v2.4.0
Add 'serve' to Dockerfile cmd.
Signed-off-by: Richard Scothern<EMAIL_ADDRESS>

LGTM


Add filter event for product price conversion.

1. Why is this change necessary?
convertProductPriceStruct is the only conversion method without a filter event. This prevents a clean extension of this conversion and should be fixed.
2. What does this change do, exactly?
It adds a filter event in a similar manner as in all other conversion methods.
3. Describe each step to reproduce the issue or behaviour.

Try to extend the product price conversion
Fail to do so because there is no filter event

4. Please link to the relevant issues (if any).
There is no issue yet.
5. Which documentation changes (if any) need to be made because of this PR?
Change in UPGRADE-5.5.md is included. I'm not aware of any other necessary changes.
6. Checklist

[ ] I have written tests and verified that they fail without my change
[X] I have squashed any insignificant commits
[X] This change has comments for package types, values, functions, and non-obvious lines of code
[X] I have read the contribution requirements and fulfil them.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-22270
Please use this issue to track the state of your pull request.

Hi @kleinmann, thank you very much for your contribution! 💙


support message delivery status

Hi @eidng8 ,
I havn't forgotten your pull request. I'm just not shure it doesn't break things If someone attaches an actual message. I'll do some more testing and let you know :)

never mine, take your time :smile:
i would've made a unit test, but sorry that i couldn't figure out how to do that it here :disappointed:


Does not inject new code

Hello @AgentME could you please help me out a bit? I having hard times getting this thing to work.
It seems like updates being emitted early, but i don't think so this is the problem because it never inject the code changed in the previous save.
Browser console:
[HMR] Websocket connection successful.
index.js:514 [HMR] Updated modules ["src/javascripts/main.js"]
index.js:514 [HMR] Updated modules ["src/javascripts/main.js"]

This is how my gulpfile looks:
let options = { debug: true };

if (config.isDev) _.extend(options, watchify.args);

let bundler = browserify(paths.src, options).plugin(hmr);

bundler.transform(babelify);
bundler.transform(hbsfy);
bundler.transform(envify);

if (config.isDev) {
  bundler = watchify(bundler);
  bundler.on('update', () => gulp.start('js'));
}

function bundle() {
  return bundler.bundle()
    .on('error', onError)
    .pipe(source(config.js.bundleName))
    .pipe(buffer())
    .pipe(sourcemaps.init({ loadMaps: true }))
    .pipe(sourcemaps.write('.'))
    .pipe(gulp.dest(paths.dest))
    // .pipe(bs.stream({ once: true }));
}

gulp.task('js', preTasks, () => bundle());

Terminal:
[BS] Serving files from: public
GET / 200 10.957 ms - 486
GET /stylesheets/main.css 200 4.258 ms - 560724
GET /javascripts/main.js 200 1.663 ms - 1816775
GET /javascripts/main.js.map 200 3.722 ms - 2103596
19:34:59 GMT+0100 (CET) [HMR] User connected, syncing
[19:35:05] Starting 'js'...
19:35:06 GMT+0100 (CET) [HMR] Emitting updates
[19:35:07] Finished 'js' after 1.67 s
[19:35:12] Starting 'js'...
19:35:13 GMT+0100 (CET) [HMR] Emitting updates
[19:35:13] Finished 'js' after 1.22 s

I also use browsersync for server can that be a problem?
gulp.task('browser-sync', () => {
  bs.init({

    // A, if you don't have a backend api use the built in server
    server: {
      baseDir: 'public'
    },

    // B, if you got a backend api proxy the request to it
    // proxy: 'some-vhost-of-existing-backend.api',

    // custom middleware for mock api
    middleware(req, res, next) {
      require('../../api/api')(req, res, next);
    },

    // default port
    port: config.isProd ? 8080 : 3000,

    // disable notify popup
    notify: false,

    // do not open browser on start
    open: false,

    // disable UI completely
    ui: false
  });

If you're seeing the "Emitting updates" and "Updated modules" messages, then your build process is likely correct. The issue is probably that you don't have any code calling module.hot. See #16.

I'm getting this as well, is there a way to get more verbose logging?

I have also the same problem. As I use websocket, I should not have to add js code, no ?
From the node console :
22:48:11 GMT+0200 (CEST) [HMR] User connected, syncing
updated source
22:48:29 GMT+0200 (CEST) [HMR] Emitting updates
864035 bytes written (0.78 seconds)

From the Dev tool console :

[HMR] Attempting websocket connection to http://localhost:3123
admin.ts:13creating an admin
index.js:425 [HMR] Websocket connection successful.
index.js:514 [HMR] Updated modules ["modules/template.html", "modules/admin.ts", "index.ts"]

Are you using module.hot (or a module that uses it for you, like react-transform-hmr) in your code?

Not at all. Where do we find it ?

Browserify-HMR and Webpack HMR update files by executing them again, but you have to first mark which files can accept updates by using module.hot.accept.
A file can accept updates of itself like this:
console.log("foo");
if (module.hot) {
  module.hot.accept();
}

Each time you edit that file, it will execute (and log something again, unless you've removed that statement). Now that's not terribly useful. Usually you want to update functions or classes in-place that are required by other files. Or maybe you want to update already instantiated instances of a class. This takes more effort to set up. I plan to write a bit about this, but I've been delaying that until I polish up and fix a few bugs in Browserify-HMR (like these misleading log statements, which are a symptom of a deeper issue).
If your project uses React, then go use react-transform-hmr, and all of your files that define React components will be automatically hot-replaceable and you can stop reading here if you want!
If you use the ud library, then it handles using the module.hot APIs to accomplish common tasks for you, and you can make a file with a hot-replaceable function like this:
var ud = require('ud');

function greeting(name) {
  return "Hello, "+name;
}

module.exports = ud.defn(module, greeting);

or you can make a hot-updateable class like this in ES6:
import {defn} from 'ud';

class Greeter {
  constructor(ownName) {
    this._ownName = ownName;
  }
  greet(name) {
    return `Hello ${name}, this is ${this._ownName}`;
  }
}

// defn works on both functions and classes, because they're the same in Javascript anyway
export default defn(module, Greeter);

It's a bit of boilerplate, but the control it gives you is necessary when you have file-scoped state that needs to be persisted between updates (ud's defonce function helps here). I've been brainstorming about automatic code transform tools to make this not necessary, but I haven't yet figured out a technique that would fit all of the needs I've seen in real codebases that ud is able to handle now.

Thanks for your reply. It makes thing much more clear.

Hi @AgentME, did you yet came to write a little more about how to update already instantiated instances? I'm referring to your comment: "Or maybe you want to update already instantiated instances of a class. I plan to write a bit about this, but I've been delaying that until I polish up and fix a few bugs in Browserify-HMR"

Hello @AgentME, I am having this issue too. Also, I am using Browserify+Watchify+BrowserSync. I did use the module.hot.accept() in my custom HMR-like class. I am not using ud or React so I am just adding the following code at the end of my ES6 class.
if(module.hot){
   module.hot.accept();
}

I am also getting the:
[HMR] Updated modules ["./moduleName.js"]

I can see these outputs in the browser console, but I it's as if the JS code isn't being re-inject in the   tag just like WebPack.
Any ideas on what's causing this?


Factor out AsType codec upstream to numcodecs

xref https://github.com/alimanfoo/numcodecs/issues/7

Trying to pursue in PR ( https://github.com/alimanfoo/numcodecs/pull/12 ).


[verification-helper] Show a hint for unit tests

https://github.com/online-judge-tools/verification-helper/issues/233

Duplicate of #17


Reference environment variable or secret when deploying a GrafanaDatasource.

Is your feature request related to a problem? Please describe.
I would like to reference an environment variable or secret when deploying a GrafanaDatasource. I am a bit unsure if this is already a possibility to do, but I can not find any examples on this anywhere, I have tried multiple approaches.

Mounting secret
Referencing the secret key.
Referencing the Env variable. (with different type of brackes)
And I do not understand how I am supposed to pass in the Client Secret of my App Registration without exposing it as cleartext in ArgoCD/Git.

I do not want to patch it in with kustomize or helm as the secret shows in ArgoCD.
And I do not want to directly push my secret to git (obvious reasons).
(If applicable)If your feature request solves a bug please provide a link to the community issue
Describe the solution you'd like
I would like to be able to refer to the Clientsecret from a secret in kubernetes or an environmentvariable in the grafana pod.
Describe alternatives you've considered
List in first question.
Additional context
For context this is what I am trying to achieve.
---
apiVersion: grafana.integreatly.org/v1beta1
kind: GrafanaDatasource
metadata:
  name: azuremonitor-ar
  namespace: grafana
  labels:
    app.kubernetes.io/instance: grafana-operator
    app.kubernetes.io/name: grafana
spec:
  datasource:
    name: azuremonitor-ar
    type: grafana-azure-monitor-datasource
    access: proxy
    jsonData:
      azureAuthType: clientsecret
      cloudName: azuremonitor
      tenantId: <my tenant id>
      clientId: <my client id>
    secureJsonData:
      clientSecret: ${CLIENT_SECRET}           <----- Or reference to a secret in the same namespace.
  instanceSelector:
    matchLabels:
      app.kubernetes.io/instance: grafana-operator
      app.kubernetes.io/name: grafana

Note: The secret is mounted to my grafana pod and also exists in the same namespace.
Existing solutions.
I could not find any solutions on this that use the kind: GrafanaDatasource

Please take a look at our documentation for an example on how to do this:
https://grafana.github.io/grafana-operator/docs/examples/datasource_variables/readme/
If this doesn't cover your use case, feel free to reopen this issue


[FIXED JENKINS-29996] Replace macros in userData

… so the user can refer back to Jenkins easily
JENKINS-29996
@mavlyutov

Reproduced by https://github.com/jenkinsci/acceptance-test-harness/pull/33


SnapToSide misbehaves on screen resize

If screen/viewport is resized the snapping points still remain the same and therefore menu ball moves out or inside viewport.

Fixed in 0.0.3


Level Relative Refs #2 could use more elaboration

First of all, thank you so much for creating this intuitive way to learn and understand Git branching. This is an awesome learning tool.
My issue is that I go through the first 6 lessons and then hit lesson 7 (Relative Refs #2) and hit a brick wall. I get the general idea of how '~' can be used to jump up many levels at once, but using it in the context of the given exercise doesn't make any sense to me. I don't have a clue how to begin.
I'd suggest elaborating on this lesson and making the given examples hew closer to what will be required for completing the exercise...maybe even split this lesson into two lessons which cover the material at greater length (maybe an easier exercise followed by a harder exercise). As it is since I don't have any clue how to use the lesson material to complete the exercise, I can't move past the lesson. And worse, I don't understand the concepts shared.
Thanks again!

didn't know you could force branch to a commit that hasn't been made yet.  how do you do that without knowing the hash??
and why does checking out bugFix at c5 and committing make a c7 and not a c6??  more questions than answers.


plugin: continue on plugin.Open() error

Previously, the daemon could not be started if it encounters an error.
Typically, an error is "plugin.Open: plugin was built with a different version of package github.com/foo/bar/..."
Signed-off-by: Akihiro Suda<EMAIL_ADDRESS>

Codecov Report

Merging #1265 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1265   +/-   ##
=======================================
  Coverage   23.62%   23.62%
=======================================
  Files          40       40
  Lines        4516     4516
=======================================
  Hits         1067     1067
  Misses       3247     3247
  Partials      202      202

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 20fa6ae...e476da8. Read the comment docs.

I think it would be better if we just keep this simple and ignore the error without having to provide an error handler func.  No need to add the extra code until we actually want to make this variable.

Should we not be taking a fail fast approach here? If a plugin was configured to load and failed, it should prevent startup. Just print a log message and continuing to operate will leave the problem unaddressed.

Can we control this behavior via config.toml variable? e.g. skipPluginError
@stevvooe
Builtin plugins does not kill the daemon on failure.
Similary, loading 3rd  party plugin should not kill the daemon, I think

I really don't want a config setting for this.  We need to pick a direction and stick with it.  So far, we have decided that we will fail hard.  Its not killing the daemon, its preventing the daemon from starting until the user fixes the issue.  I don't think this is too much to ask.  There is a problem, you must fix it, then it will start.

ok


Update README to reflect the latest Docker Images.

We are still referring to an older Docker image in the README.

Done.


Relay : Removed the maxLength for entity names

Description
Removed the MaxLength for entity names.
swagger PR Link : https://github.com/Azure/azure-rest-api-specs/pull/1535
This checklist is used to make sure that common guidelines for a pull request are followed.

[X] I have read the contribution guidelines.
[X] The pull request does not introduce breaking changes.

General Guidelines

[X] Title of the pull request is clear and informative.
[X] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[X] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[X] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[X] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
[X] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

@v-Ajnava no tests?


Error on migration for ListBlock - Wagtail 6.2 - IndexError: tuple index out of range

Issue Summary
My StructBlock has a ListBlock declared keyword arg child_block.
class ElementGradientBlock(blocks.StructBlock):
    element = blocks.CharBlock(label=_("Elemento"), required=True, max_lenth=80, icon="view")
    colors = blocks.ListBlock(
        label=_("Cores"), child_block=blocks.CharBlock(label=_("Cor"), required=True, max_lenth=8, icon="radio-empty")
    )

    class Meta:
        icon = "sliders"

When migrating after 6.2, I receive the following error:
IndexError: tuple index out of range
Caused by this method of ListBlock:
def deconstruct_with_lookup(self, lookup):
        path, args, kwargs = super().deconstruct_with_lookup(lookup)
        if getattr(self.__init__, "has_child_block_arg", False) and isinstance(
            args[0], Block
        ):
            block_id = lookup.add_block(args[0])
            args = (block_id, *args[1:])
        return path, args, kwargs

To fix it, I had to remove the child_block keyword argument, and use the child_block as position argument, including on the migrations.
Technical details

Python version: Python 3.9.0
Django version: Version: 4.2.10
Wagtail version: 6.2
Browser version: N/A

Anyone can contribute to this. View our contributing guidelines, add a comment to the issue once you’re ready to start.

Thanks for the report @ducolares! There's an existing issue #12202 for this, which has now been addressed in #12208 and will be part of a 6.2.1 patch release.


Shows nothing on iOS 14 beta

Hi,
It's showing nothing when we run the app on iOS 14
See video for detailed explanation
https://www.dropbox.com/s/paubgb26lf6h3u6/RPReplay_Final1600084354.mp4?dl=0

As far as I know, when you build your code with XCode 12, then window structure is a bit different with what we known with XCode 11 + iOS 13. The application keyWindow is gone! That will cause sub buttons cannot display correctly.


Uncaught (in promise) Error: invalid BigNumber value

https://stackoverflow.com/questions/66193724/bignumber-js9-0-1-which-was-used-for-dapp-over-aws-s3-causes-an-invalid-big

My local is normal, but the production environment is not working

I don't think you are using this library. There is no bignumber.ts file here or any error message which states "invalid BigNumber value".
From your link:

I assumed that it might happen if the bignumber.js version is deprecated to 5.0.14.

There isn't a bignumber.js version 5.0.14. Again, I don't think this library is being used.

I was normal in the test environment, but an error was reported in the production environment. I think it may be that babel did not use commonJS to transfer bignumber.

I don't think you are using this library. There is no bignumber.ts file here or any error message which states "invalid BigNumber value".
From your link:

I assumed that it might happen if the bignumber.js version is deprecated to 5.0.14.

There isn't a bignumber.js version 5.0.14. Again, I don't think this library is being used.

This error message is occurred from the web3.js.

This error message is occurred from the web3.js.

And? What is your point?
Why have you created an issue here? web3.js doesn't even use this library.
Stop spamming closed issues.


Disable text underline on hovering items in Nav Menu

Describe the bug
On hovering over the menu items in Navbar, it has underline as well as border bottom.
Solution
Only border bottom should be present.
To Reproduce
Steps to reproduce the behaviour:

Go to cv-frontend-vue
hover on the items in Navbar
compare the difference with current simulator

I'm reaching out to request that you could assign me this particular issue, I'm interested in working on. Specifically, I'm interested in tackling issue #80. I believe this issue aligns with my skills and experience, and I'm excited to contribute to the project in this way.
I would appreciate it if you could assign me this issue and provide any guidance or suggestions for getting started.
Thank you for your time and consideration.

I want to work on this issue! Can you assign this to me?

hey @Prerna-0202 and @vedant-jain03  Is these issue open to contribute ?
i would like to contribute on these issue.

This issue is already closed as completed


feat: could you add css variable --background-activated for ion-tab-button.

Hi,
could you add css variable --background-activated for ion-tab-button?
ion-tab-button{
--background-activated:rgb(73, 177, 187,0.2);
}

Please see my comment on your other issue, thanks!


Claude integration

Claude have been there for a while and now is free through Slack (https://www.anthropic.com/index/claude-now-in-slack). Is it good time to integrate it into Langchain? BTW, it is a little bit surprise no one had a proposal for this before.

This is done now (commenting since my google search led me here)
https://github.com/hwchase17/langchain/blob/master/langchain/llms/anthropic.py
https://python.langchain.com/en/latest/modules/models/chat/integrations/anthropic.html

same, should this be closed?
updated link https://github.com/langchain-ai/langchain/blob/master/libs/langchain/langchain/llms/anthropic.py
cc @hwchase17


PyProj: pyproj unable to set database path. _pyproj_global_context_initialize()

Installation method/steps
I freshley installed PyProj according to the docs
conda config --prepend channels conda-forge
conda config --set channel_priority strict
conda create -n pyproj_env pyproj
conda activate pyproj_env

When I try
from pyproj import CRS

I get

PyProj: pyproj unable to set database path. _pyproj_global_context_initialize()

Whats going on there?
Environment Information

pyproj version you are attempting to install
PROJ version: Rel. 8.2.1, January 1st, 2022
Python version: Python 3.9.7
Operation System Information: Windows-10-10.0.19042-SP0

What is the value of the PROJ_LIB environment variable?

@snowman2 Its: C:\Program Files\PostgreSQL\13\share\contrib\postgis-3.1\proj

@snowman2 Thanks for the link. It seems like this is the problem. However, I am not sure how to fix it.
To get data directory being used: pyproj.datadir.get_data_dir()
import pyproj
pyproj.datadir.get_data_dir()

'C:\Program Files\PostgreSQL\13\share\contrib\postgis-3.1\proj'

The order for searching for the data directory can be found in the docstrings of pyproj.datadir.get_data_dir()
pyproj.datadir.get_data_dir()

'C:\Program Files\PostgreSQL\13\share\contrib\postgis-3.1\proj'

How to know in which folder pyproj should look instead for the database? If I know the path to the folder, I set it via
[pyproj.datadir.set_data_dir()](https://pyproj4.github.io/pyproj/stable/api/datadir.html#pyproj.datadir.set_data_dir), right?

This is how I found the PATH to PROJ
I looked into this file ...Miniconda3\envs<ENV>\conda-meta\proj--h1cfcee-.json and searched for \pkgs\proj. Once found, I checked the versins of PROJ installed in this folder C:...\Miniconda3\pkgs. There are folder named something like proj--h1cfcee-. Make sure the folder name is the exact same name you found this file links to: ...Miniconda3\envs<ENV>\conda-meta\proj--h1cfcee-.json. Finally I set my environment variable to the version needed ...Miniconda3\pkgs\proj--h1cfcee-<VERSION\Library\share\proj.

https://github.com/pyproj4/pyproj/blob/8f0e1f7ddc5ba5a1992f939f91bb9ea023316219/pyproj/datadir.py#L75
It might not be a bad idea to better support for the Windows prefix search path. Maybe something like:
conda_windows_prefix_datadir = Path(sys.prefix, "Library", "share", "proj")

@Stophface are you able to share the value of sys.prefix after activating your conda environment?

Looks like adding the windows Library prefix search would be useful here: https://github.com/conda-forge/proj.4-feedstock/blob/9bf81fff5781b937f601a9f1b372f5a819f5bb38/recipe/scripts/activate.sh#L14

@snowman2 Sure, I am not sure how to get it thoug. Any hints?

Thanks @Stophface, that was helpful. This is something that I think should be added to the logic in pyproj to find the data directory on Windows conda environments.


Fixed cannot use some commands problem

#11

Hey @cakecatz! Thanks for this PR. Could you update it to be mergeable with current repo state?

Yes, OK!

@jerone Now you mention it, that's right!
I'll fix it.
Thanks :smile:


Add maxWheelZoomSpeed option (#9377)

This pull request replaces the wheelDebounceTime option with the more useful maxWheelZoomSpeed option. It also improves support for zooming via trackpad pinch gestures. It fixes issue #9377.
Further testing on a variety of devices, browsers, and operating systems would be appreciated.

I think for the trackpad it is a much better solution but not for the mouse. So we could implement it only for the trackpad but how to detect? The ctrlKey could be also true, when the user presses the key on the keyboard. Would this be a problem?
Tested on Windows 10, Firefox

How did you find the experience using a mouse wheel?


[FIX] - Documentation readme import lib

Before this release the files were renamed fromReactNativeConfig.ReactNativeConfigPackage to RNCConfig.RNCConfigPackage.
Generating the error:
Note: Recompile with -Xlint:deprecation for details.
/Users/marcelxsilva/Documents/projects/<NAME PROJECT>/android/app/src/main/java/com/<NAME PROJECT>/app/MainApplication.java:10: error: package com.lugg.ReactNativeConfig does not exist
import com.lugg.ReactNativeConfig.ReactNativeConfigPackage;

Basically update the readme to the correct import, after change builded with success.

+1


[FEATURE] show group name on the user event create/edit pages.

with the given a list of group information ( e.g., group id, group name), write a function to get the group name for this event (given event id) and add a new GUI field to show this group name on the event create/edit pages. Display only those groups that the user is an admin of. When a user selects this group, its group ID needs to be added to the createdByGroupId field in the event. isGroupPrivate can be set to false for now.
#638

Example list of groups:
[
{
        "id": "3a931ffb-d928-11eb-9c02-0286d10e0848",
        "title": "Generic Soft Car",
        "privacy": "private",
        "membership_status": "admin"
    },
    {
        "id": "45069a52-d928-11eb-9c02-0286d10e0848",
        "title": "Fantastic Soft Chair",
        "privacy": "public",
        "membership_status": "admin"
    }
]


Update to CIRCT 1.15.0

This PR updates the version of CIRCT.
The command line options for firtool command have been updated.
CIRCT release notes here: https://github.com/llvm/circt/releases/tag/sifive%2F1%2F15%2F0
Contributor Checklist

[x] Did you add Scaladoc to every public function/method?
[ ] Did you add at least one test demonstrating the PR?
[x] Did you delete any extraneous printlns/debugging code?
[x] Did you specify the type of improvement?
[x] Did you add appropriate documentation in docs/src?
[x] Did you state the API impact?
[ ] Did you specify the code generation impact?
[x] Did you request a desired merge strategy?
[x] Did you add text to be included in the Release Notes for this change?

Type of Improvement

bug fix
performance improvement
backend code generation

API Impact

Backend Code Generation Impact

Desired Merge Strategy

Squash

Release Notes

Reviewer Checklist (only modified by reviewer)

[ ] Did you add the appropriate labels?
[ ] Did you mark the proper milestone (Bug fix: 3.4.x, [small] API extension: 3.5.x, API modification or big change: 3.6.0)?
[ ] Did you review?
[ ] Did you check whether all relevant Contributor checkboxes have been checked?
[ ] Did you do one of the following when ready to merge:

[ ] Squash: You/ the contributor Enable auto-merge (squash), clean up the commit message, and label with Please Merge.
[ ] Merge: Ensure that contributor has cleaned up their commit history, then merge with Create a merge commit.

 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.

Changes like this cause havoc on the current branch protection rules (because it changes the name of the matrix tests). I have https://github.com/chipsalliance/chisel3/pull/2743 which should fix that to where we can change branch protection to only point to all-tests-passed again.


Update Makefile2.bat

Before my PR refer on the: OpenWaterAnalytics:win_build_script_fix
So I create new for the dev branch. Thanks
#509
#508

Any windows users object to this merge? @eladsal - I just have to admit being clueless here!


add auto-sd-krita to repos

auto-sd-krita is a Krita plugin built on top of AUTOMATIC1111's fork with support for most basic features. The best part is the optimized focus inpainting workflow for using multiple models to create advanced compositions. Also, I made a decent Youtube tutorial on how to use it to make ai art: https://www.youtube.com/watch?v=nP8MuRwcDN8

Awesome


cmd/link: panic with cgo export and //go:linkname when main.main not declared

What version of Go are you using (go version)?

$ go version
go version go1.16.3 darwin/amd64

Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/zhuah/Library/Caches/go-build"
GOENV="/Users/zhuah/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/zhuah/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/zhuah/go"
GOPRIVATE=""
GOPROXY="https://goproxy.io,direct"
GOROOT="/usr/local/Cellar/gotip/stable"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/gotip/stable/pkg/tool/darwin_amd64"
GOVCS=""
GOVERSION="go1.16.3"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/dev/null"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/8n/mb3y_4bj1xv4q9sdmgjqdx_c0000gn/T/go-build4125710039=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?
the sample code is there:
package main

import (
	"C"
	_ "unsafe"
)

//go:linkname mainMain main.main
func mainMain()

//export runGoMain
func runGoMain() {
	mainMain()
}

and i forgot to declare a main function, then build it with go build -buildmode=c-archive
What did you expect to see?
What did you see instead?
go linker panic:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x2 pc=0x121778b]

goroutine 177 [running]:
cmd/link/internal/amd64.machoreloc1(0x14814e0, 0xc00014cd90, 0xc0004fe000, 0x8776, 0x985c, 0x0, 0xc000080001, 0x166d0, 0x0)
        /usr/local/Cellar/gotip/stable/src/cmd/link/internal/amd64/asm.go:460 +0x4ab
cmd/link/internal/ld.machorelocsect(0xc00014e000, 0xc00014cd90, 0xc00014c4d0, 0xc001078538, 0x92e, 0x11d5)
        /usr/local/Cellar/gotip/stable/src/cmd/link/internal/ld/macho.go:1196 +0x3f4
cmd/link/internal/ld.relocSectFn.func1.1(0x12f18e0, 0xc00014e000, 0xc00014cd90, 0xc00014c4d0, 0xc001074000, 0x11d5, 0x11d5, 0xc001067210, 0xc00013a1c0)
        /usr/local/Cellar/gotip/stable/src/cmd/link/internal/ld/asmb.go:202 +0x66
created by cmd/link/internal/ld.relocSectFn.func1
        /usr/local/Cellar/gotip/stable/src/cmd/link/internal/ld/asmb.go:201 +0x1bd

it's also reproducible in arm64:
➜  ~ CGO_ENABLED=1 GOARCH=arm64 go build a.go
# command-line-arguments
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x2 pc=0x122146b]

goroutine 149 [running]:
cmd/link/internal/arm64.machoreloc1(0x1481620, 0xc00010ed20, 0xc00012a000, 0x80df, 0x90bf, 0x0, 0xc000080001, 0x168d0, 0x0)
        /usr/local/Cellar/gotip/stable/src/cmd/link/internal/arm64/asm.go:500 +0x7eb
cmd/link/internal/ld.machorelocsect(0xc000110000, 0xc00010ed20, 0xc00010e460, 0xc001162548, 0x961, 0x120a)
        /usr/local/Cellar/gotip/stable/src/cmd/link/internal/ld/macho.go:1196 +0x3f4
cmd/link/internal/ld.relocSectFn.func1.1(0x12f18e0, 0xc000110000, 0xc00010ed20, 0xc00010e460, 0xc00115e000, 0x120a, 0x120a, 0xc001204f70, 0xc00006c0e0)
        /usr/local/Cellar/gotip/stable/src/cmd/link/internal/ld/asmb.go:202 +0x66
created by cmd/link/internal/ld.relocSectFn.func1
        /usr/local/Cellar/gotip/stable/src/cmd/link/internal/ld/asmb.go:201 +0x1bd

it's also reproducible in arm64

Thanks. I will update the patch.

This kind of use of linkname is not supported.
Is there a way of reproduce without using linkname? Thanks.

yes, i know this is not a valid go program, maybe go could give a better error message instead of panic itself.
unfortunately i couldn't reproduce it without linkname.

by the way, i'm trying to compile a go program as a android/ios library, and call the runGoMain function from java/objective-c, just like golang/mobile repo.