Use /orgs instead of /org to match GitHub v3 API

As per https://developer.github.com/v3/repos/#create

Codecov Report

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

@@           Coverage Diff           @@
##           master    #2639   +/-   ##
=======================================
  Coverage   27.11%   27.11%
=======================================
  Files          86       86
  Lines       17064    17064
=======================================
  Hits         4627     4627
  Misses      11759    11759
  Partials      678      678

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 a8717e5...45f9c23. Read the comment docs.

The cherry on the cake would be to keep the old url available and mark it as depraceted in swagger.

Keeping the old m.Post("/org/:orgname/repos", reqToken(), bind(api.CreateRepoOption{}), repo.CreateOrgRepo)
Add an other (duplicate) swagger comment with deprected tag inside CreateOrgRepo.

But you're doing this under the /v1/ group, shouldn't it go to /v3/ group instead ?
Those versions are there for a reason...

I agree with @strk that v1 route should be left as it is and note added in swagger docs that it is deprecated and new one should be created under v3 that would be with GitHub compatible route

@lafriks @strk Agreed, but I don't see a v3 in routers/api. Am I missing something?

@raphink no currently there is no such route. But you can add it ;)

@JonasFranzDEV that's why I think this should be done as new /v3 route and current marked as deprecated not to break existing API

Didn't we say that a new endpoint should have been added (/v3/) instead of changing any of the existing ones ?

Since we're not compatible with GitHub v3 we shouldn't put things under /v3/ until we are.

Currently, my issue is to be able to use the Terraform github provider with gitea, which is currently not possible when creating repositories (due to that difference in paths).

@BKC why coulnd't we just put partial support /v3/ while it's being
implemented ? As long as the /v2 still works ?

Put the routers to /api/v3 and keep old router?

I guess implementing v3 isn't done in a single PR. So if nobody starts with it, we will never implemented it.

Or keep both routers for compatibility since there are no conflicts between them.

Wasn't against that suggestion. We should keep both and after v3 is finished we should fix an end date of v1 support

The current API uses v1, adding a v3-router is out or scope for this PR. (But please feel free to create a new one)


How do you support unicorn source files?

Suppose have a cxx_library() with 5 files.  Generally speaking, they all have the same command line options but you have one source file that needs a "unicorn" option.  -ffast-math is a good example of this, you might be building a math library where one file needs to be compiled with -ffast-math.
Splitting it into a separate library is not going to be an option for us, because the cpp files have mutually interdependent headers.  For example, A.cpp includes B.h and B.cpp includes A.h.
Is there presently a way to accomplish something like this?

Splitting it into a separate library is not going to be an option for us, because the cpp files have mutually interdependent headers. For example, A.cpp includes B.h and B.cpp includes A.h.

That shouldn't stop you from being able to split them as you could split them into three parts: a headers target, a B.cpp target and an A.cpp target, both of them depending on the headers, pick one to represent the whole thing and have it export the headers and depend on the other.
Anyway though, there's no need for that. you can do:
cxx_library(
  name = "x",
  srcs = [
    "a.cpp",
    "b.cpp",
    ("c.cpp", ["--flag-for-c-1", "--flag-for-c-2"]),
     "d.cpp",
  ],
  ...
)

It's documented here: https://buck2.build/docs/api/rules/#cxx_library:~:text=2.3 on Linux.-,srcs%3A,-The set of

Oh, that's interesting!  I didn't realize that srcs could be a list of tuples


backend(chore): add session dependency on tools router

Thank you for contributing to the Cohere Toolkit!

[ ] PR title: "area: description"

Where "area" is whichever of interface, frontend, model, tools, backend, etc. is being modified. Use "docs: ..."  for CI changes.
Example: "deployment: add Azure model option"

[ ] PR message: Delete this entire checklist and replace with

Description: a description of the change
Issue: the issue # it fixes, if applicable
Dependencies: any dependencies required for this change

[ ] Add tests and docs: Please include testing and documentation for your changes

[ ] Lint and test: Run make lint and make run-tests

AI Description

This pull request makes changes to the src/backend/config/routers.py file.
Summary
The RouterName.TOOL dictionary in the RouterName class now includes a "default" list with a Depends(get_session) dependency.
Changes

Added a "default" list to the RouterName.TOOL dictionary.
Included the Depends(get_session) dependency in the "default" list.

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

Project coverage is 86.06%. Comparing base (9125660) to head (b656437).
Report is 9 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #374      +/-   ##
==========================================
- Coverage   86.46%   86.06%   -0.41%
==========================================
  Files         178      178
  Lines        6873     7012     +139
==========================================
+ Hits         5943     6035      +92
- Misses        930      977      +47

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


PT-1695 | fix(toast): automatically close toast error messages after 10s

Description :sparkles:
fix(toast): automatically close toast error messages after 10s
default autoclose for toast error messages is 5s, this doubles that to
give users more time to read the message
refs PT-1695
Issues :bug:
Closes :no_good_woman:
PT-1695
Related :handshake:
Testing :alembic:
Automated tests :gear:
Manual testing :construction_worker_man:
Screenshots :camera_flash:
Additional notes :spiral_notepad:

kultus-ui branch is deployed to platta: https://kultus-ui-pr294.dev.hel.ninja :rocket::rocket::rocket:


Rails server does not start when date_time_select_extension is enabled in Rails 5

Rails server does not start when date_time_select_extension is enabled in Rails 5
Details:
Ruby 2.4.0
Rails 5.2.0.beta2
Error Trace:
/home/AquisTech/projects/validates_timeliness/lib/validates_timeliness/extensions/date_time_select.rb:12:in `block in <module:DateTimeSelect>': undefined method `alias_method_chain' for ActionView::Helpers::Tags::DateSelect:Class (NoMethodError)
Did you mean?  alias_method
  from /home/AquisTech/.rvm/gems/ruby-2.4.0/bundler/gems/rails-f7e3c686685f/activesupport/lib/active_support/concern.rb:122:in `class_eval'
  from /home/AquisTech/.rvm/gems/ruby-2.4.0/bundler/gems/rails-f7e3c686685f/activesupport/lib/active_support/concern.rb:122:in `append_features'
  from /home/AquisTech/projects/validates_timeliness/lib/validates_timeliness/extensions.rb:7:in `include'
  from /home/AquisTech/projects/validates_timeliness/lib/validates_timeliness/extensions.rb:7:in `enable_date_time_select_extension!'
  from /home/AquisTech/projects/expense_tracker/config/initializers/validates_timeliness.rb:15:in `block in <top (required)>'
  from /home/AquisTech/projects/validates_timeliness/lib/validates_timeliness.rb:54:in `setup'
  from /home/AquisTech/projects/expense_tracker/config/initializers/validates_timeliness.rb:1:in `<top (required)>'
  from /home/AquisTech/.rvm/gems/ruby-2.4.0/bundler/gems/rails-f7e3c686685f/activesupport/lib/active_support/dependencies.rb:277:in `load'
  from /home/AquisTech/.rvm/gems/ruby-2.4.0/bundler/gems/rails-f7e3c686685f/activesupport/lib/active_support/dependencies.rb:277:in `block in load'
  from /home/AquisTech/.rvm/gems/ruby-2.4.0/bundler/gems/rails-f7e3c686685f/activesupport/lib/active_support/dependencies.rb:249:in `load_dependency'
  from /home/AquisTech/.rvm/gems/ruby-2.4.0/bundler/gems/rails-f7e3c686685f/activesupport/lib/active_support/dependencies.rb:277:in `load'
  from /home/AquisTech/.rvm/gems/ruby-2.4.0/bundler/gems/rails-f7e3c686685f/railties/lib/rails/engine.rb:657:in `block in load_config_initializer'
  from /home/AquisTech/.rvm/gems/ruby-2.4.0/bundler/gems/rails-f7e3c686685f/activesupport/lib/active_support/notifications.rb:170:in `instrument'
  from /home/AquisTech/.rvm/gems/ruby-2.4.0/bundler/gems/rails-f7e3c686685f/railties/lib/rails/engine.rb:656:in `load_config_initializer'
  from /home/AquisTech/.rvm/gems/ruby-2.4.0/bundler/gems/rails-f7e3c686685f/railties/lib/rails/engine.rb:614:in `block (2 levels) in <class:Engine>'
  from /home/AquisTech/.rvm/gems/ruby-2.4.0/bundler/gems/rails-f7e3c686685f/railties/lib/rails/engine.rb:613:in `each'
  from /home/AquisTech/.rvm/gems/ruby-2.4.0/bundler/gems/rails-f7e3c686685f/railties/lib/rails/engine.rb:613:in `block in <class:Engine>'
  from /home/AquisTech/.rvm/gems/ruby-2.4.0/bundler/gems/rails-f7e3c686685f/railties/lib/rails/initializable.rb:32:in `instance_exec'
  from /home/AquisTech/.rvm/gems/ruby-2.4.0/bundler/gems/rails-f7e3c686685f/railties/lib/rails/initializable.rb:32:in `run'
  from /home/AquisTech/.rvm/gems/ruby-2.4.0/bundler/gems/rails-f7e3c686685f/railties/lib/rails/initializable.rb:61:in `block in run_initializers'
  from /home/AquisTech/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/tsort.rb:228:in `block in tsort_each'
  from /home/AquisTech/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/tsort.rb:350:in `block (2 levels) in each_strongly_connected_component'
  from /home/AquisTech/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/tsort.rb:422:in `block (2 levels) in each_strongly_connected_component_from'
  from /home/AquisTech/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/tsort.rb:431:in `each_strongly_connected_component_from'
  from /home/AquisTech/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/tsort.rb:421:in `block in each_strongly_connected_component_from'
  from /home/AquisTech/.rvm/gems/ruby-2.4.0/bundler/gems/rails-f7e3c686685f/railties/lib/rails/initializable.rb:50:in `each'
  from /home/AquisTech/.rvm/gems/ruby-2.4.0/bundler/gems/rails-f7e3c686685f/railties/lib/rails/initializable.rb:50:in `tsort_each_child'
  from /home/AquisTech/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/tsort.rb:415:in `call'
  from /home/AquisTech/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/tsort.rb:415:in `each_strongly_connected_component_from'
  from /home/AquisTech/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/tsort.rb:349:in `block in each_strongly_connected_component'
  from /home/AquisTech/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/tsort.rb:347:in `each'
  from /home/AquisTech/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/tsort.rb:347:in `call'
  from /home/AquisTech/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/tsort.rb:347:in `each_strongly_connected_component'
  from /home/AquisTech/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/tsort.rb:226:in `tsort_each'
  from /home/AquisTech/.rvm/rubies/ruby-2.4.0/lib/ruby/2.4.0/tsort.rb:205:in `tsort_each'
  from /home/AquisTech/.rvm/gems/ruby-2.4.0/bundler/gems/rails-f7e3c686685f/railties/lib/rails/initializable.rb:60:in `run_initializers'
  from /home/AquisTech/.rvm/gems/ruby-2.4.0/bundler/gems/rails-f7e3c686685f/railties/lib/rails/application.rb:360:in `initialize!'
  from /home/AquisTech/projects/expense_tracker/config/environment.rb:5:in `<top (required)>'
  from config.ru:3:in `require_relative'
  from config.ru:3:in `block in <main>'
  from /home/AquisTech/.rvm/gems/ruby-2.4.0/gems/rack-2.0.4/lib/rack/builder.rb:55:in `instance_eval'
  from /home/AquisTech/.rvm/gems/ruby-2.4.0/gems/rack-2.0.4/lib/rack/builder.rb:55:in `initialize'
  from config.ru:in `new'
  from config.ru:in `<main>'
  from /home/AquisTech/.rvm/gems/ruby-2.4.0/gems/rack-2.0.4/lib/rack/builder.rb:49:in `eval'
  from /home/AquisTech/.rvm/gems/ruby-2.4.0/gems/rack-2.0.4/lib/rack/builder.rb:49:in `new_from_string'
  from /home/AquisTech/.rvm/gems/ruby-2.4.0/gems/rack-2.0.4/lib/rack/builder.rb:40:in `parse_file'
  from /home/AquisTech/.rvm/gems/ruby-2.4.0/gems/rack-2.0.4/lib/rack/server.rb:319:in `build_app_and_options_from_config'
  from /home/AquisTech/.rvm/gems/ruby-2.4.0/gems/rack-2.0.4/lib/rack/server.rb:219:in `app'
  from /home/AquisTech/.rvm/gems/ruby-2.4.0/bundler/gems/rails-f7e3c686685f/railties/lib/rails/commands/server/server_command.rb:27:in `app'
  from /home/AquisTech/.rvm/gems/ruby-2.4.0/gems/rack-2.0.4/lib/rack/server.rb:354:in `wrapped_app'
  from /home/AquisTech/.rvm/gems/ruby-2.4.0/bundler/gems/rails-f7e3c686685f/railties/lib/rails/commands/server/server_command.rb:89:in `log_to_stdout'
  from /home/AquisTech/.rvm/gems/ruby-2.4.0/bundler/gems/rails-f7e3c686685f/railties/lib/rails/commands/server/server_command.rb:51:in `start'
  from /home/AquisTech/.rvm/gems/ruby-2.4.0/bundler/gems/rails-f7e3c686685f/railties/lib/rails/commands/server/server_command.rb:147:in `block in perform'
  from /home/AquisTech/.rvm/gems/ruby-2.4.0/bundler/gems/rails-f7e3c686685f/railties/lib/rails/commands/server/server_command.rb:142:in `tap'
  from /home/AquisTech/.rvm/gems/ruby-2.4.0/bundler/gems/rails-f7e3c686685f/railties/lib/rails/commands/server/server_command.rb:142:in `perform'
  from /home/AquisTech/.rvm/gems/ruby-2.4.0/gems/thor-0.20.0/lib/thor/command.rb:27:in `run'
  from /home/AquisTech/.rvm/gems/ruby-2.4.0/gems/thor-0.20.0/lib/thor/invocation.rb:126:in `invoke_command'
  from /home/AquisTech/.rvm/gems/ruby-2.4.0/gems/thor-0.20.0/lib/thor.rb:387:in `dispatch'
  from /home/AquisTech/.rvm/gems/ruby-2.4.0/bundler/gems/rails-f7e3c686685f/railties/lib/rails/command/base.rb:65:in `perform'
  from /home/AquisTech/.rvm/gems/ruby-2.4.0/bundler/gems/rails-f7e3c686685f/railties/lib/rails/command.rb:46:in `invoke'
  from /home/AquisTech/.rvm/gems/ruby-2.4.0/bundler/gems/rails-f7e3c686685f/railties/lib/rails/commands.rb:18:in `<top (required)>'
  from bin/rails:4:in `require'
  from bin/rails:4:in `<main>'

alias_method_chain is completely removed now in Rails 5.2.0 so need to make code compatible using Module.prepend

Changes done for fixing this issue.
PR #167 is raised for the fix.
@adzap Please review changes.
I am already using changes in my Rails 5.2.0 project.


Add check for X-Forwarded-Proto to detect HTTPS

Related to #1080

[test]

[test]

[test]

[test] ugh..


pep8 style analysis

Coverage remained the same at 87.719% when pulling 46ae3746c1738e67d32b83a93a3978c040f750f3 on develop into adffb0a781291b01d203ecaad9abc2cbb2a8eff0 on master.


Conflicts between globomap-driver-acs and requests

Hi, users are unable to run globomap-driver-acs due to dependency conflict with requests package. As shown in the following full dependency graph of globomap-driver-acs, globomap-loader-api-client requires requests ==2.18.4，while globomap-driver-acs requires requests ==2.10.0.
According to pip’s “first found wins” installation strategy, requests 2.10.0 is the actually installed version. However, requests 2.10.0 does not satisfy ==2.18.4.
Dependency tree-----------
globomap-driver-acs - 0.0.46
| +- globomap-loader-api-client(install version:0.0.7 version range:==0.0.7)
| | +- requests(install version:2.18.4 version range:==2.18.4)
| | | +- certifi(install version:2019.11.28 version range:>=2017.4.17)
| | | +- chardet(install version:3.0.4 version range:<3.1.0,>=3.0.2)
| | | +- idna(install version:2.6 version range:<2.7,>=2.5)
| | | +- urllib3(install version:1.22 version range:<1.23,>=1.21.1)
| +- pika(install version:0.10.0 version range:==0.10.0)
| +- python-dateutil(install version:2.4.2 version range:==2.4.2)
| | +- six(install version:1.13.0 version range:*)
| | +- six(install version:1.13.0 version range:>=1.5)
| +- requests(install version:2.10.0 version range:==2.10.0)

Thanks for your help.
Best,
Neolith

Suggested Solution

Fix your direct dependency to be requests>=2.10.0. I have checked this revision will not affect your downstream projects now.
Remove your direct dependency requests, and use requests transitively introduced by globomap-loader-api-client.

@victor-mendes-eduardo Which solution do you prefer, 1 or 2?
Please let me know your choice. I can submit a PR to solve this issue.


"Exception thrown, see JavaScript console" instead of game window without compatibility mode

Hi,
There's a problem which I have to report. I tried to launch my game on Python localhost without compatibility mode due to unavoidable bug with disappearing music in less than a second. Though the game runs almost perfectly on compatibility mode (besides this mess with music), it fails on "normal" mode giving tons of errors linked below. I don't understand what's going on.

Notice that this issue occurs whether you export your game in the "normal" mode, not "compatibility". Tested on Chrome, Firefox and Edge, all of them give the same effect: "Exception thrown, see JavaScript console.". Does somebody know what's wrong with it?

Online demos work as expected. All of them. I didn't modify the default HTML structure at all. Of course I've put my game into ".love" file before running.

Online demos work as expected. All of them. I didn't modify the default HTML structure at all. Of course I've put my game into ".love" file before running.

I still can't solve the problem. Any ideas?

I still can't solve the problem. Any ideas?

OK, I've found in the "love.js" the "text/plain" string, but even when I changed this to suggested entries taken from the same link, it doesn't solve the problem. I still have the same errors. Is there any other "text/plain" string I need to change?

OK, I've found in the "love.js" the "text/plain" string, but even when I changed this to suggested entries taken from the same link, it doesn't solve the problem. I still have the same errors. Is there any other "text/plain" string I need to change?

Sorry, I don't have the time to look into this right now. I'll ping a few people that I think ran into similar issues, maybe they will be able to help you. @thomasgoldstein @Sheepolution

OK, thanks for reply.

Sorry, I don't have the time to look into this right now. I'll ping a few people that I think ran into similar issues, maybe they will be able to help you. @thomasgoldstein @Sheepolution

OK, thanks for reply.

@Davidobot
Wait, I've got something! I think you may be right, because I've just launched the same template on my other PC and it worked! The same command: "python -m http.server". Tested on Chrome and Python 3.8.1 (32-bit). I made the second test on the same PC, but this time on "XAMPP" and it also launched (there were some errors linked below, but it became accessible)!
Here's the output on "XAMPP" localhost (Google Chrome, Python 3.91 (64-bit)):

Any clues what it means?

OK, thanks, anyway. The most important is it finally works and I don't have to use any workarounds for "buggy" music in compatibility mode. I'm going to use "XAMPP" if I can't figure how to fix this "worker.js" problem on Python localhost.
After all, good job! It's a good tool.


Remove duplicate environment creation

Fixes #649
Our environments were getting loaded twice, once in firstUpdate, and again in update. I think generation only happened once because of three's caching, but reading in the HDR file and running PMREM were both definitely happening twice, and are both quite expensive. I can't see anything going wrong from removing the firstUpdate function, but I'm also not sure why it was there, so please let me know if I've missed some side effect.

👍 How can we catch regressions?

I'm not sure; I'm hoping our current tests and fidelity tests will tell us. Can you think of new cases we should add?

Our current test suite is not comprehensive, and we rely on folks layering on regression tests and feature tests as changes are made.
Off the top of my head, I see tests here for checking the background color when nothing is configured, but not the environment lighting:
https://github.com/GoogleWebComponents/model-viewer/blob/42553986abe851fbe966b838bad5c5eafc9704c6/src/test/features/environment-spec.ts#L148-L160
Since the comment that you removed claims that firstUpdated was needed in the case that no environment is configured, it sounds like this is an important test case to cover.

Good idea, I've added the unconfigured tests. As for checking how many times the environment is generated, I would spend significantly more time making that test than on the whole PR and I still wouldn't be convinced it would reliably catch those perf bugs. I think this is a relatively unlikely regression, so I would skip this particular test, but you're welcome to overrule me if this is more important than our other work.

I would spend significantly more time making that test than on the whole PR

This is the reason why easy / small PRs are dangerous :)

I think for the near term let's just add a test that waits for a reasonable window of time (call it one second) after the model loads and asserts that the environment did not re-generate in that window of time.
In some failure scenarios, this test will fail flakily. But, I think flakey failure in this case is better than no test at all.


adding test cases for WSAS-1913 - Test cases for CARBON-15038

Closing this PR as the conflict in this is solved in https://github.com/wso2/product-as/pull/406


Build mode url handling

In the docs we mention the build_mode property on the toolbar, but it is never used to determine in which mode we actually initialize it. This PR attempts to fix that.
New behaviour is - always respect GET param (which helps with sharing urls) and if the browser is fresh enough to support history api (http://caniuse.com/#feat=history support is good) the url will always be updated whenever you change mode.
I'm pretty sure that the behaviour of python code is incorrect, so please advise /cc @yakky @mkoistinen

FE LGTM


[rtl] Move memory ECC checks and generation into core

Previously integrity checks for incoming memory reads and integrity
generation for outgoing memory writes were handled within ibex_lockstep
and weren't duplicated.
This moves the integrity checks and generation into the core so they are
replicated and checked as part of the lockstep mechanism.
Additionally it generates a bus error on any memory integrity check
failure. This will result in Ibex taking an exception if any data read
or instruction fetch has bad integrity.

However, I wonder whether it would be a good idea to tweak things slightly and pass around "data + integrity" as a single signal. The width could then be controlled by a parameter (MemECC, here) and this would avoid adding more ports to the modules and feeding through zeros when it's not enabled. I think that should be an easy tweak?

Done, though the top-level remains as it is. This is because in an effort to avoid explosion of parameter space we have no MemECC at top-level, it's just on/off depending on SecureIbex. However in order to allow those that wish to to alter the definition of SecureIbex I'd rather not have changing port sizes depending upon SecureIbex so I've left the _intg signals in there.
Everything below ibex_top uses unified signals.


Perk Hash check failed@ 1.4.1

Lots of perk's hash check failed @ 1.4.1 , how to get new hash?
feats:
KhuzaitCavalryAgilityPatch
AseraiCheapCaravansEffectBonusPatch
MenuWhenEncounteringAnArmyPatch
steward:
ProsperousReignPatch
BannerlordPatch
NourishSettlementPatch
SupremeAuthorityPatch
WarmongerPatch
politice:
LandGrantsForVeteransPatch
leadership:
DisciplinarianPatch
UltimateLeaderPatch
riding:
ConroiPatch
NomadicTraditionsPatch
SquiresPatch
TramplerPatch
Athletics:
PeakFormPatch
Roguery:
ScavengerPatch
EyeForLoot
RaidingPartyPatch
SlaveTraderPatch
engineering:
BallisticsPatch
BuilderPatch2
GoodMaterialsPatch
HeavierSiegeEnginesPatch
WallBreakerPatch
cunning:tactics
AmbushSpecialistPatch
BaitPatch
CompanionCavalryPatch
ElusivePatch
HammerAndAnvilPatch
PhalanxPatch
TacticalSuperiorityPatch
scouting:
HealthyScoutPatch

There was no official release for e1.4.1 when you posted this, all of the download locations say e1.4.0 and below.
https://www.nexusmods.com/mountandblade2bannerlord/mods/186?tab=files

Says "For e1.4.0 and below."
On GH releases page;

At the time of posting, there is now this re-uploaded e1.4.1 build;

https://github.com/Tyler-IN/MnB2-Bannerlord-CommunityPatch/releases/tag/v0.1.0-rc6
For the hash failures; you don't get new hashes.
It means we need to update those patches to work with that version of the game.
The patches are skipped when the code changed enough that the patch shouldn't apply (possibly because it's no longer required).


Problem: No greater than and less than opcodes

Solution: implement them

@sjmackenzie I don't have write access to this repository....

ah darn!

okay fixed


preliminary ECDH support

make sure that we can import ECDH private keys
make some test cases
write out some test data
start on actual ECDH decryption, but the crux is unimplemented

@oconnor663 can you take a look?
This allows us to import and pass through ECDH keys, but I didn't implement decryption with ECDH keys.

With this fix, we're now able to run keybase pgp select on keys that have ECDH subkeys (over Nist or Brainpool curves). Whereas before we weren't

Looks fine to me, with the one question above.


Spec profile: present slow examples duration in human friendly

Hello,
Before I send a pull request on this subject, I wanted to check if the current behavior was desired or not.
Right now (as master), when run crystal spec --profile, will present slow examples duration in seconds, which can be a problem for fast-running examples, like Radix:
$ ccr --version
Using compiled compiler at .build/crystal
Crystal 0.18.7+355 [5b3c9dc] (2016-08-19)

$ ccr spec --profile
Using compiled compiler at .build/crystal
..............................................

Top 10 slowest examples (0.0004548 seconds, 44.74% of total time):
  0.3.1 matches version defined in shard.yml
    0.0002726 seconds ./spec/radix/version_spec.cr:6
  Radix::Tree(T) #add dealing with duplicates does not allow same path be defined twice
    4.68e-05 seconds ./spec/radix/tree_spec.cr:176
  Radix::Tree(T) #add dealing with catch all and named parameters prioritizes nodes correctly
    2.06e-05 seconds ./spec/radix/tree_spec.cr:190
  Radix::Tree(T) #add shared root inserts multiple nodes with mixed parents
    2.0e-05 seconds ./spec/radix/tree_spec.cr:112
...
Finished in 1.02 milliseconds
46 examples, 0 failures, 0 errors, 0 pending

Want to confirm if will be better the examples duration leverage on Spec.to_human (like other places).
Perhaps is a presentation issue and requesting n number of decimals will correct it instead.
Please let me know and will send the appropriate pull request.
Thank you.
:heart: :heart: :heart:

IMO a presentation issue, as I argued in #2875 I think choosing the same scale for all examples depending on the slowest one makes comparing them a whole lot easier.

Indeed just a presentation issue (is not that things are broken), but having a more human friendly version presented to the end user have value too.
Just checking, will be something I can spend a bit of time improving and would love to.
Thank you for your quick response. If nobody objects until the end of the day, will get that sorted out tomorrow.
Cheers.

Wow, I just realize --profile is an available flag, is this documented somewhere?
crystal spec --help shows me this:
➜  ~ crystal spec --help
Usage: crystal spec [options] [files]

Options:
    -d, --debug                      Add full symbolic debug info
    --no-debug                       Skip any symbolic debug info
    -D FLAG, --define FLAG           Define a compile-time flag
    --error-trace                    Show full error trace
    --release                        Compile in release mode
    -s, --stats                      Enable statistics output
    -p, --progress                   Enable progress output
    -t, --time                       Enable execution time output
    -h, --help                       Show this message
    --no-color                       Disable colored output
➜  ~ crystal -v
Crystal 0.24.2 (2018-03-19)

LLVM: 6.0.0
Default target: x86_64-pc-linux-gnu

@faustinoaq crystal spec -- --help

@RX14 Yeah, that's very commonly misunderstood. For starters, adding a note about checking the runtime help to the compiler help output would be an improvement.


ProjectDirs path problem under Windows

Under Windows, there is a split between the local appdata folder and the roaming appdata folder. With regards to what goes where, they're almost interchangeable except that the roaming folder is for user app data that should be synchronized across machines while the local folder is for user app data that is machine-specific and need not/should not be synchronized to other machines.
(The only time any of this comes into play is when people are connected to a domain and using roaming profiles which brings their environment with them each time they log onto a machine, even if it's not "their" machine.)
I'm not sure the decision to use the roaming folder for ProjectDirs is correct given that the description says it's for caching, etc. and caches should generally not be synchronized.
e.g. Chrome stores its caches and more under %localappdata% and not %appdata%, Microsoft stores a user's own crash dumps under %localappdata% while they store things like the dictionaries that a user has installed to %appdata%.
But configuration (aka $HOME/.config) definitely belongs in %roamingappdata%.

I'm closing this issue, feel free to re-open it with additional information.


Feat/use azapi for subnets

Description

NOTE: This pull request is a clone of https://github.com/Azure/terraform-azurerm-avm-res-network-virtualnetwork/pull/74 submitted by @kewalaka. We just had to migrate to an un forked branch on this occasion for ease of testing, etc.

This ports the approach used in the sub vending LZ module

functionally, this allows a second team to create subnets within a vnet, without terraform overwriting the subnets

This also ports the example from @haflidif where subnets are also created using azapi, to allow an immediate association with an NSG & route table, along with aligning it to the AVM way.  As noted, this fixes deployments when faced with typical Azure Policy restrictions.

This includes the logic to be able to deploy subnets into an existing vnet (fixes #43)

On the examples;

The 'complete' example is now much more complete.  It deploys all the various resources such as routes, NSGs, DDOS (but disabled, for cost saving), etc.
The 'default' example just deploys the minimal vnet
There is an additional example to test (3)

This fixes a number of variables that do not follow AVM spec, noting;

vnet_location is now location
virtual_network_dns_servers is dns_servers
virtual_network_ddos_protection_plan is ddos_protection_plan
virtual_network_address_space is address_space
vnet_peering_config is peerings (?)

... and the outputs have been updated to align more closely with AVM too.

Change works with recent changes in azapi 1.13

The code passes lint, docs & grept apply checks.
Fixes  #43, #65, #71, #73
Supersedes #62
-->
Type of Change

[ ] Non-module change (e.g. CI/CD, documentation, etc.)
[X] Azure Verified Module updates:

[ ] Bugfix containing backwards compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in locals.version.tf.json:

[ ] Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
[ ] The bug was found by the module author, and no one has opened an issue to report it yet.

[ ] Feature update backwards compatible feature updates, and I have bumped the MINOR version in locals.version.tf.json.
[X] Breaking changes and I have bumped the MAJOR version in locals.version.tf.json. edit: bumped the minor version as we are still < v1.0
[X] Update to documentation

Checklist

[X] I'm sure there are no other open Pull Requests for the same update/change (except those noted that this supersedes)
[X] My corresponding pipelines / checks run clean and green without any errors or warnings
[X] I did run all  pre-commit checks

@matt-FFFFFF How important is it that we provide an automated migration path here? There is a lot of change happening here. Adding the removed and import blocks to the examples is certainly feasible, but given we are pre-v1.0 I'm wondering how much time we should spend on it. I appreciate that users have probably already adopted the module, but in order to fully automate this we would need to do it in an external script. We'd need to find the resource ids from their state and then create remove and import blocks or commands. Interested in your thoughts as to how far we should go with this.

@matt-FFFFFF Refactored this a bit more following our discussion yesterday. Not specifically supporting the sub module being used independently, but it is there if we want to take that approach. Keen to get your thoughts. Also moved away from supplying the resource_id for existing VNETs and instead re-using the existing variables to reduce clunkiness. Final change is to make it so that subnet role assignments actually work. I will consider splitting out peerings into a sub module too, but can wait until later.
I did add support for reverse peerings too, so that the module supports an end to end solution. Otherwise there was a circular dependency and you could only ever do half a peering.

thanks for helping finish this off @jaredfholgate - LGTM - what do we need to do before pressing the Big Green Button & making a release?

I think we probably need it to be Monday 😂
Been a long week but glad to get there. I'm sure we will get this released soon.

just doing some quick usage testing, spotted shouldn't these be nullable = false :
private_link_service_network_policies_enabled &
private_endpoint_network_policies
in https://github.com/kewalaka/terraform-azurerm-avm-res-network-virtualnetwork/blob/feat/use-azapi-for-subnets/modules/subnet/variables.tf

@kewalaka, @haflidif  and @matt-FFFFFF.  I'll get this release out today.


Verify services deleted when cluster scales down

This addresses bug https://jira.oraclecorp.com/jira/browse/OWLS-71460, which reports that service services were not being removed on scale down. The unit tests now show that they are, which may mean that the service work over the past month has addressed the issue.
This change now addresses a number of code issues, including demonstrating the ability to unit test cluster scaling and file I/O (without actually accessing the file system). It also does some code cleanup, needed to get the unit tests to work, including:

Moved certificate reading from the REST service to the Certificates class, so we no longer need to bring up a server to read them,
Moved the JobWatcher cache into the JobWatcher class, so we don't need to pass parameters through a long chain of steps, most of which don't do anything with them, and
Used a delegate to break the dependency of DomainProcessorImpl on Main, allowing it to be unit-tested.

At least one person has thought that adding a label:
weblogic.createdByOperator: “false”

should be enough to tell the operator to leave a resource alone. It seems a reasonable assumption, so I have updated the code to behave accordingly.


New App Submission

App Logo (Required)

App Details (Required)
Type: Dapp
Name: Delta.theta
Description: Delta.theta Terminal
Homepage Url: https://deltatheta.tech
Chains supported: Ethereum, Binance Smart Chain
Versions supported: 1
App Url (Required - at least one)
Browser Url: https://app.deltatheta.tech
iOS Url:
Android Url:
Mac Url:
Windows Url:
Linux Url:
Mobile Linking (Optional)
Deep Link:
Universal Link:
Desktop Linking (Optional)
Deep Link:
Universal Link:
Metadata (Optional)
Short Name:
Primary Color:
Secondary Color:

Added to cloud registry


fix: rewrite error message

The error message which can appear when trying to load entity list views has become outdated (makes references to entity settings declarations we don't use anymore), this PR fixes this + rewords the message for clarity.

thanks!


ipcache: Add probe to check for dump capability to support delete

Besides the ability to delete, the ipcache garbage collector also requires the
ability to dump the table. Add this to the existing probe which feeds
SupportsDelete().
level=debug msg="Detected IPCache delete operation support: true" subsys=map-ipcache
level=debug msg="Detected IPCache dump operation support: true" subsys=map-ipcache

Fixes: #10080

This change is

test-me-please

Coverage increased (+0.01%) to 44.615% when pulling 8cf084acdc7c158ce9c4311dfd198beb6bac1474 on pr/tgraf/ipcache-dump-probe into c58d749816d943c4f9426f67738013f4e8778463 on master.

For the release note particularly for older releases, I think we should make it more clear that kernel 4.15 will change its ipcache GC implementation and why.

For the release note particularly for older releases, I think we should make it more clear that kernel 4.15 will change its ipcache GC implementation and why.

Isn't this just a bugfix? We did not do any GC at all for 4.15.

test-me-please

Isn't this just a bugfix? We did not do any GC at all for 4.15.

What I mean is "ipcache: Add probe to check for dump capability to support delete" doesn't sound like a bugfix as an item in the release note, and it doesn't mention 4.15. Even if the release-note is "Fix ipcache garbage collection on Linux 4.15" then this would be clear for the next 1.6 release. Users running that kernel would know that this change may affect them.

Added release note based on suggestion by @joestringer


Update vendoring in src/server

Currently, make docker-build fails when a container is created using generated code from the new go protobuf compiler, because the names used in some of the imports have changed. This PR updates the affected files so that we can build again. Specifically, this updates vendoring in src/server with the following:

(removed) github.com/gengo/grpc-gateway/runtime
(removed) github.com/gengo/grpc-gateway/utilities
(updated) github.com/golang/protobuf/jsonpb
(added) github.com/grpc-ecosystem/grpc-gateway/runtime/internal
(added) github.com/grpc-ecosystem/grpc-gateway/runtime
(added) github.com/grpc-ecosystem/grpc-gateway/utilities
(updated) go.pedge.io/proto/version
(updated) go.pedge.io/proto/server

Dank, this meme is

Lol


suggestion: Update return type annotation to match new implementation

          **suggestion:** Update return type annotation to match new implementation

The method no longer returns a string. Consider changing the return type to -> bool and return whether new categories were found, which could be useful for callers.
    def check_new_categories(self) -> bool:
        """Check for new categories and compare them with dictionary of existing categories."""
        new_categories: dict = self.parse_category_urls()
        return bool(set(new_categories.keys()) - set(self.existing_categories.keys()))

Originally posted by @sourcery-ai[bot] in https://github.com/bartczak-pa/WebScraper/pull/58#discussion_r1749343399

Not applicable


HowManyOccurrences should be able to manage null and empty input

HowManyOccurrences should be able to manage null and empty input

Hs been solved with Commit fe0ed7ce10b8cfb0742ea0b6b23ee7be160ac2a3


App crashes

Hi, so when I try to insert the URL (https://quizizz.com/join?gc=1234567) and click get answers it hangs for a bit then crashes. Maybe its because this is a 7-digit code instead of a 6-digit code. Let me know!

Should be fixed in the last update. check it out and let me know if the issue still persists.

I'm sorry to tell you that but the update isn't, unfortunately, resolving this issue. Now it says "Please wait..." and crashes. I've tested it on the .exe and the .rar

Can you send me the link to this specific quiz that is not working?

Yes, of course! https://quizizz.com/join?gc=7987523

Ok, thanks for the input the issue has been fixed and the program should not crash in case of error like this.


phonegap gestures not working

Phonegap gestures (http://docs.phonegap.com/references/developer-app/gestures/) are not working for me in a project with MULTIPLE HTML pages.  In this case:

the gestures work fine from index.html
they work fine from other .html pages at the same level as index.html
they do not work from .htm pages within my project (even when I include cordova.js in those pages)
they do not work from .html pages that are within subfolders of my project (even when I include cordova.js in those pages)

I am using PhoneGap Build 0.4.5 with cli-c.5.0 on iOS 9.3.5.
Any ideas? I can of course force-quit the app and reload but that gets tedious very quickly.
FWIW:  Navigation between pages is working fine.  The only part broken is the gestures.

Hi @gms384,
Not sure what could be causing this as the scripts that we inject for gestures should work from any HTML page. Usually when we find issues with the gestures it is the result of the some broken JS that is causing errors on the page. Maybe it could be an issue with the specific pages you are noticing this on.
Another thing to check, we attach the gestures to using event listeners. So if you have something on your site that effects those that could cause the issue as well.

Thanks for the quick response.  I do not think that is the issue though.  To test, I did this:

created blank Phonegap project

edited index.html to add this:
 index
 good
 bad

saved resulting file as index.html, then as good.html, then as bad.htm.
when you navigate to index.html- gestures work.
when you navigate to good.html- 3-finger tap does "back" to index.html then 3-finger does back to reload- all good.
when you navigate to bad.htm - 3 finger tap does not work at all.
code in all 3 pages is the same (ie default index.html page with these 3 links)
You can achieve similar result by putting index.html page within a subfolder (and adjusting the path to cordova to be correct:  )
Greg

Well the quick fix would be to rename bad.htm -> bad.html. In connect-phonegap, where we inject all these scripts, we are specifically looking for html files.

True- but I am dealing with a project with 50-100 html files, and would even consider renaming them from .htm to .html, but they exist in a folder structure which I cannot feasibly flatten.  Is there hope that at some point you can inject your scripts into all the htm/html files within the project?

One other quick fix that might help would be a simpler way to quit the application rather than force-quit. I've tried both navigator.app.exitApp() and setting exit-on-suspend as listed in http://docs.phonegap.com/phonegap-build/configuring/preferences/#exit-on-suspend but neither worked.
Is there a way to simpler call to quit the app?  I realize that you don't want to do that for production, but it sure would be helpful during development.

Because we are loading your project resources into the developer app there isn't really a good catchall that would quit the app back to the home screen. This is why we need to inject these scripts into your served application so that we can provide this functionality. But all the 3 finger tap is doing is calling window.history.back(window.history.length);. So for now on the broken pages you are seeing you can add this as a way to go back a page.

Hi @gms384
I made a quick fix to the server side component connect-phonegap to allow the scripts to be injected into .htm files. We're currently adding some more things to the phonegap-cli so the update should be ready in a few days time.

Thanks- that's awesome!  Will it also handle .htm files in subfolders?  That is the bigger problem.

I have just release<EMAIL_ADDRESS>that has the changes needed to fix your issue @gms384. Thanks for bringing this to our attention!

That's great...thanks!    Is there a way to update the cli to your new release, or would I have to abandon the desktop version and use the command line version until the next PhoneGap Desktop release?
Or do you mean that http://docs.phonegap.com/getting-started/1-install-phonegap/desktop/#win is updated as well?
Thanks again,
Greg

The PhoneGap Desktop app has not been updated yet, for this fix you will need to use the phonegap-cli. Once you have the CLI installed you just need to run phonegap serve and it will do the same thing as the desktop app.

Sorry for more questions- I am new to this.  I assume to install it is just:
npm install -g<EMAIL_ADDRESS>If I do that, will it affect in any way my version of PhoneGap build, or will I still be able to use either PhoneGap build (as it currently is) or the newer fixed CLI version?
If there is some interaction, does it make any sense to install it with:
npm install<EMAIL_ADDRESS>and would that change anything?
thanks,
Greg

Yes, that is the correct way to install the CLI.
I think you have the names a little confused but either way installing the CLI will not affect anything else you have installed. The desktop app comes bundled with its own version of the CLI and currently it does not have the fix for your issue. PhoneGap build is different, that is a website where you can upload your project assets to create a build.

Thanks for clarifying names- and yes I meant the desktop app.  I went to install the CLI with:
npm install -g<EMAIL_ADDRESS>and it says:
'phonegap-cli' is not in the npm registr
You should bug the author to publish it
Am I doing something wrong?

Sorry, I didn't notice you had added the "-cli" at the end. It should just be, npm install -g phonegap.


TS016677155 -- we are trying to create a qmgr with LogFilePages=65535 and getting INI error as below(same reported in the PMR)

error :
│ 2024-07-08T18:46:23.628Z AMQ5778E: Automatic configuration of INI files attempted to update a restricted value. [CommentInsert1(Log), CommentInsert2(LogType), CommentInsert3(Replicated)]                                          │
│ 2024-07-08T18:46:23.628Z AMQ5776E: Auto configuration INI definitions contain invalid syntax or illegal attributes. [CommentInsert1(INI)]
we are using same approach as this repository to create QMGR on AWS EKS.
Please suggest us on how to create qmgr with below ini.
Log:
LogPrimaryFiles=12
LogSecondaryFiles=2
LogFilePages=65535
LogType=REPLICATED
LogBufferPages=0
LogWriteIntegrity=TripleWrite
LogManagement=Automatic
NOTE: we were able to update primary and secondary files  value once the qmgr is up and running(editing the configmap) and i  know we cannot touch the "LogFilePages" once QMGR is created.

In the error message, it points out the problematic value: "Replicated".  You can't set the LogType in this way — Native HA is configured using different Native HA INI settings, and those are in turn configured automatically by environment variables passed to the container.  The Helm chart sets those environment variables, so you can't set the LogType directly yourself.

how can we change environment variables?
do you have any example ?

i was able to change it by adding below :
      - name: MQ_QMGR_LOG_FILE_PAGES
        value: "65535"


Why PasswordHasher is generic class?

Hi
Could you please explain me, why PasswordHasher is generic? How I saw the source  code, we do not using it in code.
For example method HashPassword we pass parameter user, but we don using this user in code.

Its to enable extensibility for password hashers that want to hash based on data in TUser itself, like a salt


Podman Desktop does not able to update or create new podman vm

Bug description
Fresh install of Podman Desktop 1.8.0 on Windows 10 22H2, install was smooth. In my case have I have prior wsl vm for podman with version 4.1.1 which podman found. Had issues attempting to upgrade existing wsl vm. Steps taken:

Podman desktop found prior VM but the status of the vm differed between the dashboard and resources pages.

I followed the dashboard wizard to upgrade and it reports that it was upgraded to version 4.9.3.

Dashboard shows notification to "set up" podman and the podman widget that shows initialize and start.

Running the notification setup wizard has an error that "podman-machine-default" already exists modifying the name of the VM in the wizard allows it to complete. (I choose "podman-machine" as name) After running setup wizard notification to set up podman does not clear. Can confirm that new wsl vm was created, but podman doesn't appear to have picked it up:

PS> wsl --list
Windows Subsystem for Linux Distributions:
Ubuntu (Default)
podman-machine
podman-machine-default

No podman vm resources are shown on resources setting page.

Selecting "initialize" or "initialize and start" on the dashboard podman widget returns:

Initialization failed. Please check the error below and try again
Error: Command execution failed with exit code 125
Command execution failed with exit code 125
sh: line 1: /etc/containers/registries.conf.d/999-podman-machine.conf: No such file or directory
Error: system connection "podman-machine-default" already exists. consider a different machine name or remove the connection with `podman system connection rm`

As far as I can tell there does not appear to be a way to resolve this from Podman Desktop nor does Podman desktop seem to be able to register a VM with a separate name.
Operating system
Windows 10 22H2
Installation Method
Installer from website/GitHub releases
Version
1.8.0
Steps to reproduce
No response
Relevant log output
No response
Additional context
No response

If you hit this issue. Use wsl and remove the old installation:
wsl --unregister podman-machine-default
Then click the initialize and install button in desktop again.
It worked easily for me!


Anchors in the documentation do not work

I am using firefox and for some reason clicking anchors here does not work (eg. clicking on Configuring Amplitude.js doesn't scroll anywhere.

Thanks for the report on this. We have a few UX improvements to make. Looks like the anchors work in the body (but jump too far down), but the sidebar does not work at all.
The link changes at the top, but nothing happens (see this video).

@danpastori Can we get this addressed in 3.1?

This should be fixed now. Thanks for reporting it @Darker!


Use NodeJS-bin instead of the user's node install

Description
Our test suite currently relies on the user manually installing NodeJS in order for npm commands to be run.
This is an error prone process with way to control what npm version the end-user has. This method also can also fail due to missing PATH variables.
This PR uses premade binaries for npm instead of the user's local npm installation.
Checklist:
Please update this checklist as you complete each item:

[ ] Tests have been developed for bug fixes or new functionality.
[ ] The changelog has been updated, if necessary.
[ ] Documentation has been updated, if necessary.
[ ] GitHub Issues closed by this PR have been linked.

By submitting this pull request you agree that all contributions comply with this project's open source license(s).

FYI @rmorshea
NodeJS-Bin seems pretty nice to me. It's a bit unfortunate the author stopped posting version updates beyond 18.x, but for our purposes 18.x works.


764 add time field to distribution

Resolves #764
Description

Designed a new time format
Added an hours and minutes field for issued_at, with minutes snapped to the quarter hour
Added logic for old issued_at datetimes that did not include a time to display without the time.
New entries that include a time will display the time along with the date"

Type of change

New feature (non-breaking change which adds functionality)

How Has This Been Tested?

I ran rspec tests on the method, the model, and the entire application. All passed.

Build is failing because of Rubocop:
Run rubocop -a, then fix anything that isn't autocorrected, commit and re-push -- should clear it up.

Offenses:
spec/models/distribution_spec.rb:81:39: C: Rails/TimeZone: Do not use Time.parse without zone. Use one of Time.zone.parse, Time.current, Time.parse.in_time_zone, Time.parse.utc, Time.parse.getlocal, Time.parse.xmlschema, Time.parse.iso8601, Time.parse.jisx0301, Time.parse.rfc3339, Time.parse.httpdate, Time.parse.to_i, Time.parse.to_f instead.
        distribution.issued_at = Time.parse("2014-03-01 14:30:00 UTC")
                                      ^^^^^
app/models/distribution.rb:54:20: C: Style/RedundantSelf: Redundant self detected.
    if is_midnight(self.issued_at)
                   ^^^^^^^^^^^^^^
app/models/distribution.rb:55:7: C: Style/RedundantSelf: Redundant self detected.
      self.issued_at.strftime("%B %-d %Y")
      ^^^^^^^^^^^^^^
app/models/distribution.rb:57:7: C: Style/RedundantSelf: Redundant self detected.
      self.issued_at.to_s(:distribution_date_time)
      ^^^^^^^^^^^^^^```

This update doesn't honor changes in #774
Please, make sure these changes are compatible with email trigger which is for date change only right now

This update doesn't honor changes in #774
Please, make sure these changes are compatible with email trigger which is for date change only right now

Huh?


Uncaught SyntaxError: Unexpected end of JSON input

The requests that this library make assume that the entire JSON response is returned in the first data callback here:

https://github.com/rat9615/passport-notion/blob/c5011ec115081e04d395743366dfdcef87eb6ef8/lib/passport-notion/strategy.js#L113-L114

(getUserProfile) https://github.com/rat9615/passport-notion/blob/c5011ec115081e04d395743366dfdcef87eb6ef8/lib/passport-notion/strategy.js#L143-L145

The solution is to wait for the done event on the response to parse the JSON. Example:
    return new Promise((resolve, reject) => {
      const accessTokenRequest = https.request(requestOptions, (res) => {
        let data = ""
        res.on("data", (d) => {
          data += d
        })

        res.on("end", () => {
          try {
            resolve(JSON.parse(data))
          } catch (error) {
            reject(error)
          }
        })
      })

      accessTokenRequest.on("error", reject)
      accessTokenRequest.write(JSON.stringify(accessTokenBody))
      accessTokenRequest.end()
    })
  }

If you're willing to raise a PR. I'll be glad to review and accept it.


Add a navigation link in the resource type field in VSCode

Please add a navigation link in the type field of a resource in VSCode.
Background
I'm often looking at resource parameters to see what's appropriate for my given resource and often search for the resource by highlighting the type and cutting and pasting it into my browser search window.
It would be extremely helpful if the VSCode extension could generate a link and allowing a CTRL-Click to launch your browser to the appropriate resource.
Navigation Types
Navigation could be supported for the following:

Resource - URL to the MS Docs for the resource
Module relative path - open the module in VS code.
Module via Bicep Registry - open the module registry page (when complete)
Module via git URL - open the git/github URL.

Sample Images
Link in variable with "Follow Link" tool tip:

Proposed Resource Link:

@anthony-c-martin - how realistic would this be to do as part of #668? Do you want to track it separately?

@anthony-c-martin - how realistic would this be to do as part of #668? Do you want to track it separately?

Definitely makes sense to track this separately. The big question from me is "what should the resource type link to?". The Bicep type docs generated here are the only real source of truth for this data, but they are really designed for internal use, and are not currently very user-friendly.

Linking to #658 for clickable links on module paths.

The big question from me is "what should the resource type link to?"

Good question. My vote would be to send them to the public REST API doc that is generated off of swagger that @tfitzmac maintains.
For this bicep resource:
resource rg 'Microsoft.Resources/resourceGroups@2020-10-01' = {
  name: 'foo'
  location: 'eastus'
}

Should take me here:
https://docs.microsoft.com/rest/api/resources/resourcegroups/createorupdate
Though, I'm just now realizing that the above doc doesn't have an apiVersion selector, so maybe it makes more sense to go to the equivalent page in the ARM Template/Bicep reference:
https://docs.microsoft.com/azure/templates/microsoft.resources/resourcegroups?tabs=bicep

@alex-frankel and @anthony-c-martin - I am reworking the process to generate the template reference docs. Should I use https://github.com/Azure/bicep-types-az/tree/main/generated as the source for types and properties? I could repackage it in a more presentable format.

I'd certainly like it to go to the Docs pages more than anything else.  If nothing else, a generic browser search will most likely bring you the docs page.
It looks like the generic URL is
https://docs.microsoft.com/en-us/azure/templates/<namespace>/<APIVersion>/<Type>?tabs=bicep

Which should be simple to parse from the resource type.

Thanks for the link! The template docs are generated using the template schema generator which generally will be very closely aligned with Bicep types, but may contain subtle differences. I definitely agree in general with linking to type docs, but will need to discuss with @tfitzmac as per his above suggestion to ensure they're fully accurate.

Was going to suggest this as an issue, but I see this was discussed some time ago. This feature would be very useful for the authoring experience in VS Code with a link to the ARM template/Bicep reference docs (i.e. https://docs.microsoft.com/en-us/azure/templates/<namespace>/<APIVersion>/<Type>?tabs=bicep) from the Bicep resources.
Are there blockers regarding bicep types or schema generation as of now? @anthony-c-martin @tfitzmac

I'll let @tfitzmac & @alex-frankel answer - if they don't have any objections, then as long as the VSCode infrastructure supports linking to external documents from code, I think we should be able to get this done.

That should work with the docs.

I'll let @tfitzmac & @alex-frankel answer - if they don't have any objections, then as long as the VSCode infrastructure supports linking to external documents from code, I think we should be able to get this done.

Did some digging - I don't think returning a web URI is permitted with the LocationLink response to the goto def command in LSP. We might have to get creative with a solution.

Trying to bring this back into view...

I've re-added the triage label so that we discuss this one during the next triage

Removing triage as it looks like Anthony got a quick PR in :)


The OGC API process is fast or slow?

Actually, I'm not sure that accelerating the process of creating standards is a good idea.
In OGC API Common we believe that going too fast in OGC API Features ignoring the possibility to create a common backend where all the other APIS could grow, is creating all sorts of small problems that could be solved by a slowing down for a moment and thing about the big picture.

Yet, at the same time, there are things that have been submitted a long time ago for consideration, and are still not integrated by the unifying OGC API Common, slowing down the development of all standards depending on it, and causing a lot of redundant discussions across SWGs.
For example, the x-ogc- properties:

https://github.com/opengeospatial/ogcapi-common/issues/334
https://github.com/opengeospatial/ogcapi-features/issues/945
https://github.com/opengeospatial/ogcapi-features/issues/954
https://github.com/opengeospatial/ogcapi-coverages/issues/173
https://github.com/opengeospatial/ogcapi-processes/issues/395
etc.

I find that, by acting quickly and not waiting too much after Common to "officially" publish definitions, OGC API Features was able to actually propose many parameters that created a common ground for discussion and consideration by other standards. Although definitions do not align "perfectly", they have somewhat of a similar naming, representation and intention, which greatly limits discrepancies between SWG due to many people not talking to each other and coming up with their own custom properties each time.

@fmigneault
I've created a Wiki page on the OGC API - Common repo to keep track of the x-ogc-* extension keywords until the Naming Authority sets up a register for them:
https://github.com/opengeospatial/ogcapi-common/wiki/Table-of-extensions-to-the-JSON-Schema-vocabulary

@ghobona @rob-metalinkage See https://github.com/opengeospatial/NamingAuthority/issues/315 .


Clarification: httpVueLoader(...)() kinda works most of the time.

Mostly a clarification/question:
I had an issue here where suddenly in my project I was not able to use custom components registered in the "outer" Vue environment any more, and the same with $plugins: they were not available (undefined) on this.$* but was available through this.$root.$* (in the http-vue-loader components' contexts).
I eventually tracked it down to having used       httpVueLoader(url)()   instead of just  httpVueLoader(url) when loading the components.  I'm not sure why the first variant event works, but apparently it did.
The first variant DOES seems to work a random'th portion of the time, but then just suddenly starts misbehaving again, then works again, then stops working. Is there any logic behind this? :) A promise / caching / load time race condition combo of sorts?

Are you able to provide a minimalist testcase ?


there are memory leak with current_trace_spans.

Environment details (Operating System, PostgreSQL version, pg_tracing version, etc)

PostgreSQL version: 16.2
pg_tracing version:latest
Operating System:centos 7

Steps to reproduce the issue

1.when the trace complete with a sql command, max_nested_level will be  -1 again.
2.when max_nested_level is -1, current_trace_spans will malloc again.
3.but current_trace_spans only malloc, not free.
Describe the results you received
memory leak in every trace.
Describe the results you expected
memory leak in every trace.
Additional information you deem important (e.g. issue happens only occasionally)

current_trace_spans is allocated using palloc which relies on PostgreSQL's allocator.
Allocations are done within pg_tracing_mem_ctx memory context. This context is reset during cleanup_tracing, freeing all allocations done for the trace.
So unless I missed something, I haven't been able to reproduce a memory leak. Checking with MemoryContextStats(pg_tracing_mem_ctx);, the amount of memory used by the context is stable on a backend process generating traces with every query.
pg_tracing memory context: 25856 total in 3 blocks; 8680 free (5 chunks); 17176 used
Grand total: 25856 bytes in 3 blocks; 8680 free (5 chunks); 17176 used
...
pg_tracing memory context: 25856 total in 3 blocks; 8680 free (5 chunks); 17176 used
Grand total: 25856 bytes in 3 blocks; 8680 free (5 chunks); 17176 used

It turns out there was one leak, though it's not on current_trace_spans.
The query file is loaded in a malloced buffer that was never freed. I've fixed the issue in https://github.com/DataDog/pg_tracing/commit/eca9c9c8be3778e224e3eb10c5780f43a21d96ed


🐛 New install of manjaro sway is not including dex

branch
stable
Architecture
x86_64
Description
Hi, I noticed that dex is used in /etc/sway/definitions:
# autostarts set $autostart_dex '[ -x "$(command -v dex)" ] && gdbus wait --session org.kde.StatusNotifierWatcher && dex --autostart'
However, on my new Manjaro Sway installation I had to explicitly install the dex package as it was not present from the start.
Because dex is not installed, nm-applet is not starting. At the moment I am not sure if this affects any other functionalities.
Reproduction steps
- Fresh manjaro sway install
- dex package is not installed

Screenshots
No response
Logs
No response

@all-contributors please add @hyperion-ak for fixing and reporting bugs


能在coco数据集训练mobilenetv2吗？

Hi @zeckireck，
No, COCO is a single-frame dataset, and SmoothNet needs videos or several frames to train it.


FederatedStore Skipping making graph from cache on exception.

Skipping making graph from cache on exception.
If a proxy graph fails then federated store doesn't initialise.

Merged into develop


Add itertools module

Resolves #1368
Add itertools to modules documentation, with an example. The Python docs are much more thorough, so clearly linking to those is really our best bet: https://docs.python.org/3/library/itertools.html
Prerelease docs
If this change is related to functionality in a prerelease version of dbt (delete if not applicable):

[x] I've added versioning components, as described in "Versioning Docs"
[x] I've added a note to the prerelease version's Migration Guide

Closing in favor of omnibus PR: https://github.com/dbt-labs/docs.getdbt.com/pull/1698


[KYUUBI #6623] Support bearer token authentication on swagger UI

:mag: Description
Issue References 🔗

This pull request fixes #6623
Describe Your Solution 🔧
This is a subtask of #6590
Followup of #6591
Types of changes :bookmark:

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Test Plan 🧪
Behavior Without This Pull Request :coffin:
Behavior With This Pull Request :tada:
Related Unit Tests

Checklist 📝

[x] This patch was not authored or co-authored using Generative Tooling

Be nice. Be informative.

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

Project coverage is 0.00%. Comparing base (a4390a7) to head (7c38c63).

Files
Patch %
Lines

...e/kyuubi/server/api/v1/KyuubiOpenApiResource.scala
0.00%
9 Missing :warning:

Additional details and impacted files
@@          Coverage Diff           @@
##           master   #6625   +/-   ##
======================================
  Coverage    0.00%   0.00%
======================================
  Files         680     680
  Lines       42000   42007    +7
  Branches     5729    5729
======================================
- Misses      42000   42007    +7

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

thanks, merged to 1.10.0


MGMT: Build failure w/ Unexpected value 'MdTabsModule'

From: https://travis-ci.org/apereo/cas/jobs/284148540
Date: 2017-10-06T11:41:51.353Z
Hash: e7d69d9bebec3c792528
Time: 8707ms
chunk {0} styles.f4d1bf31c4f7cff048ee.bundle.css (styles) 44.5 kB {3} [initial] [rendered]
chunk {1} polyfills.3bc34265385d52184eab.bundle.js (polyfills) 86 bytes {3} [initial] [rendered]
chunk {2} main.e402deade8b026b7d50e.bundle.js (main) 84 bytes [initial] [rendered]
chunk {3} inline.8c3d4d4604a3d1fec8f8.bundle.js (inline) 1.45 kB [entry] [rendered]
ERROR in Error: Unexpected value 'MdTabsModule in<EMAIL_ADDRESS>imported by the module 'SharedModule in /home/travis/build/apereo/cas/webapp-mgmt/cas-management-webapp/src/app/shared/shared.module.ts'. Please add a @NgModule annotation.
    at syntaxError (/home/travis/build/apereo/cas/webapp-mgmt/cas-management-webapp/node_modules/@angular/compiler/bundles/compiler.umd.js:1729:34)
    at /home/travis/build/apereo/cas/webapp-mgmt/cas-management-webapp/node_modules/@angular/compiler/bundles/compiler.umd.js:15582:44
    at Array.forEach (native)
    at CompileMetadataResolver.getNgModuleMetadata (/home/travis/build/apereo/cas/webapp-mgmt/cas-management-webapp/node_modules/@angular/compiler/bundles/compiler.umd.js:15565:49)
    at addNgModule (/home/travis/build/apereo/cas/webapp-mgmt/cas-management-webapp/node_modules/@angular/compiler/bundles/compiler.umd.js:24408:58)
    at /home/travis/build/apereo/cas/webapp-mgmt/cas-management-webapp/node_modules/@angular/compiler/bundles/compiler.umd.js:24419:14
    at Array.forEach (native)
    at _createNgModules (/home/travis/build/apereo/cas/webapp-mgmt/cas-management-webapp/node_modules/@angular/compiler/bundles/compiler.umd.js:24418:26)
    at analyzeNgModules (/home/travis/build/apereo/cas/webapp-mgmt/cas-management-webapp/node_modules/@angular/compiler/bundles/compiler.umd.js:24293:14)
    at analyzeAndValidateNgModules (/home/travis/build/apereo/cas/webapp-mgmt/cas-management-webapp/node_modules/@angular/compiler/bundles/compiler.umd.js:24303:35)
    at AotCompiler.analyzeModulesAsync (/home/travis/build/apereo/cas/webapp-mgmt/cas-management-webapp/node_modules/@angular/compiler/bundles/compiler.umd.js:23937:46)
    at CodeGenerator.codegen (/home/travis/build/apereo/cas/webapp-mgmt/cas-management-webapp/node_modules/@angular/compiler-cli/src/codegen.js:32:14)
    at Function.NgTools_InternalApi_NG_2.codeGen (/home/travis/build/apereo/cas/webapp-mgmt/cas-management-webapp/node_modules/@angular/compiler-cli/src/ngtools_api.js:73:30)
    at _donePromise.Promise.resolve.then (/home/travis/build/apereo/cas/webapp-mgmt/cas-management-webapp/node_modules/@ngtools/webpack/src/plugin.js:386:44)
npm ERR! Linux 4.4.0-93-generic
npm ERR! argv "/home/travis/build/apereo/cas/webapp-mgmt/cas-management-webapp/.gradle/nodejs/node-v7.10.0-linux-x64/bin/node" "/home/travis/build/apereo/cas/webapp-mgmt/cas-management-webapp/.gradle/nodejs/node-v7.10.0-linux-x64/bin/npm" "run" "build"
npm ERR! node v7.10.0
npm ERR! npm  v4.2.0
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build: `ng build --prod`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script 'ng build --prod'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the cas-management-angular-webapp package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     ng build --prod
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs cas-management-angular-webapp
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls cas-management-angular-webapp
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /home/travis/.npm/_logs/2017-10-06T11_41_51_412Z-debug.log
:webapp-mgmt:cas-management-webapp:buildClient FAILED
:autoLintGradle

Ok, looks like latest material update change the module names to MatMODULE_NAME instead of MdMODULE_NAME.  I will get a PR to merge soon.

From: Misagh Moayyed<EMAIL_ADDRESS>Sent: Friday, October 6, 2017 5:15:40 AM
To: Unicon/cas
Cc: Subscribed
Subject: [Unicon/cas] MGMT: Build failure w/ Unexpected value 'MdTabsModule' (#50)
Date: 2017-10-06T11:41:51.353Z Hash: e7d69d9bebec3c792528 Time: 8707ms chunk {0} styles.f4d1bf31c4f7cff048ee.bundle.css (styles) 44.5 kB {3} [initial] [rendered] chunk {1} polyfills.3bc34265385d52184eab.bundle.js (polyfills) 86 bytes {3} [initial]
[rendered] chunk {2} main.e402deade8b026b7d50e.bundle.js (main) 84 bytes [initial] [rendered] chunk {3} inline.8c3d4d4604a3d1fec8f8.bundle.js (inline) 1.45 kB [entry] [rendered] ERROR in Error: Unexpected value 'MdTabsModule in<EMAIL_ADDRESS>imported by the module 'SharedModule in /home/travis/build/apereo/cas/webapp-mgmt/cas-management-webapp/src/app/shared/shared.module.ts'. Please add a @NgModule annotation. at syntaxError (/home/travis/build/apereo/cas/webapp-mgmt/cas-management-webapp/node_modules/@angular/compiler/bundles/compiler.umd.js:1729:34)
at /home/travis/build/apereo/cas/webapp-mgmt/cas-management-webapp/node_modules/@angular/compiler/bundles/compiler.umd.js:15582:44 at Array.forEach (native) at CompileMetadataResolver.getNgModuleMetadata (/home/travis/build/apereo/cas/webapp-mgmt/cas-management-webapp/node_modules/@angular/compiler/bundles/compiler.umd.js:15565:49)
at addNgModule (/home/travis/build/apereo/cas/webapp-mgmt/cas-management-webapp/node_modules/@angular/compiler/bundles/compiler.umd.js:24408:58) at /home/travis/build/apereo/cas/webapp-mgmt/cas-management-webapp/node_modules/@angular/compiler/bundles/compiler.umd.js:24419:14
at Array.forEach (native) at _createNgModules (/home/travis/build/apereo/cas/webapp-mgmt/cas-management-webapp/node_modules/@angular/compiler/bundles/compiler.umd.js:24418:26) at analyzeNgModules (/home/travis/build/apereo/cas/webapp-mgmt/cas-management-webapp/node_modules/@angular/compiler/bundles/compiler.umd.js:24293:14)
at analyzeAndValidateNgModules (/home/travis/build/apereo/cas/webapp-mgmt/cas-management-webapp/node_modules/@angular/compiler/bundles/compiler.umd.js:24303:35) at AotCompiler.analyzeModulesAsync (/home/travis/build/apereo/cas/webapp-mgmt/cas-management-webapp/node_modules/@angular/compiler/bundles/compiler.umd.js:23937:46)
at CodeGenerator.codegen (/home/travis/build/apereo/cas/webapp-mgmt/cas-management-webapp/node_modules/@angular/compiler-cli/src/codegen.js:32:14) at Function.NgTools_InternalApi_NG_2.codeGen (/home/travis/build/apereo/cas/webapp-mgmt/cas-management-webapp/node_modules/@angular/compiler-cli/src/ngtools_api.js:73:30)
at _donePromise.Promise.resolve.then (/home/travis/build/apereo/cas/webapp-mgmt/cas-management-webapp/node_modules/@ngtools/webpack/src/plugin.js:386:44) npm ERR! Linux 4.4.0-93-generic npm ERR! argv "/home/travis/build/apereo/cas/webapp-mgmt/cas-management-webapp/.gradle/nodejs/node-v7.10.0-linux-x64/bin/node"
"/home/travis/build/apereo/cas/webapp-mgmt/cas-management-webapp/.gradle/nodejs/node-v7.10.0-linux-x64/bin/npm" "run" "build" npm ERR! node v7.10.0 npm ERR! npm v4.2.0 npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR<EMAIL_ADDRESS>build:
ng build --prod npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the<EMAIL_ADDRESS>build script 'ng build --prod'. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely
a problem with the cas-management-angular-webapp package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! ng build --prod npm ERR! You can get information on how to open an issue for this project with: npm ERR!
npm bugs cas-management-angular-webapp npm ERR! Or if that isn't available, you can get their info via: npm ERR! npm owner ls cas-management-angular-webapp npm ERR! There is likely additional logging output above. npm ERR! Please include the following file
with any support request: npm ERR! /home/travis/.npm/_logs/2017-10-06T11_41_51_412Z-debug.log :webapp-mgmt:cas-management-webapp:buildClient FAILED :autoLintGradle
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/Unicon/cas/issues/50, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AS0kve53-WoKYf6C6uecz9EBMi8apME1ks5sphnrgaJpZM4PwZYG.

Fix has been pushed to mgmt-material-refactor.

Passing build. Merged. Deleted branch. Thank you!

Do I need to merge this into the tooltip PR before it can be merged?

From: Misagh Moayyed<EMAIL_ADDRESS>Sent: Friday, October 6, 2017 10:13:50 AM
To: Unicon/cas
Cc: Travis S Schmidt; Comment
Subject: Re: [Unicon/cas] MGMT: Build failure w/ Unexpected value 'MdTabsModule' (#50)
Passing build. Merged. Deleted branch. Thank you!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/Unicon/cas/issues/50#issuecomment-334815848, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AS0kvZH_q4IAKXQ4tUa-Sw2SNzSaX8Mtks5spl_OgaJpZM4PwZYG.

No, but if you would be better to merge apereo/cas:master into this branch so the PR can rebuild itself and pass green.

will do

From: Misagh Moayyed<EMAIL_ADDRESS>Sent: Friday, October 6, 2017 11:00:32 AM
To: Unicon/cas
Cc: Travis S Schmidt; Comment
Subject: Re: [Unicon/cas] MGMT: Build failure w/ Unexpected value 'MdTabsModule' (#50)
No, but if you would be better to merge apereo/cas:master into this branch so the PR can rebuild itself and pass green.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/Unicon/cas/issues/50#issuecomment-334827890, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AS0kveehkGEawqXFgHQcBDRwJIWoVsWsks5spmq_gaJpZM4PwZYG.


[Bug]: Jest needs additional config for supporting modules that use subpath imports

Version
27.5.1
Steps to reproduce
Repo with reproducable case: https://github.com/ottokruse/jest-subpath-import

Clone my repo: git clone https://github.com/ottokruse/jest-subpath-import.git
Install dependencies: npm install
Run jest: npx jest

Expected behavior
Jest works fine, doesn't throw errors. Under the hood, jest thus understand subpath imports natively, as NodeJS does too. Subpath imports (link) were added to NodeJS in: v14.6.0, v12.19.0
Actual behavior
Jest errors with this message:
 FAIL  ./index.test.js
  ● Test suite failed to run

    Cannot find module '#node-web-compat' from 'node_modules/aws-jwt-verify/dist/cjs/https.js'

    Require stack:
      node_modules/aws-jwt-verify/dist/cjs/https.js
      node_modules/aws-jwt-verify/dist/cjs/jwk.js
      node_modules/aws-jwt-verify/dist/cjs/jwt-rsa.js
      node_modules/aws-jwt-verify/dist/cjs/index.js
      index.test.js

      at Resolver.resolveModule (node_modules/jest-resolve/build/resolver.js:324:11)

Test Suites: 1 failed, 1 total
Tests:       0 total
Snapshots:   0 total
Time:        0.283 s
Ran all test suites.

Additional context
Subpath imports (link) were added to NodeJS in: v14.6.0, v12.19.0
However Jest does not support modules using subpath imports, unless jest users do additional config (e.g. specify a moduleNameMapper in their config).
This is not obvious and requires users to waste time googling around looking for a fix.
The "fix", to add a moduleNameMapper in their config, is not a real fix, because it requires the developer to get to know, and use, the implementation details of the module with the subpath imports --> the user needs to copy paste the subpath import definition from the module's package.json into their jest config. This is of course also brittle:
module.exports = {
  // To know what to put here I have to look inside the package.json of the module that has the
  // subpath import, and put the declaration here:
  moduleNameMapper: {
    "#subpath-import-name": "mapping-to-actual-js-file-or-external-module",
  },
};

Environment
System:
    OS: macOS 11.6.5
    CPU: (8) x64 Intel(R) Core(TM) i7-1068NG7 CPU @ 2.30GHz
  Binaries:
    Node: 16.8.0 - ~/.nvm/versions/node/v16.8.0/bin/node
    Yarn: 1.22.17 - ~/.nvm/versions/node/v16.8.0/bin/yarn
    npm: 8.3.0 - ~/.nvm/versions/node/v16.8.0/bin/npm
  npmPackages:
    jest: ^27.5.1 => 27.5.1

I hit this snag today

Duplicate of #12270


Keys should not be stored in azd environments or outputted in bicep

This repo outputs the openAI key here:
https://github.com/Azure-Samples/azure-search-openai-demo/blob/main/infra/main.bicep#L392
That will add the secret to the Azure deployment and it will add the secret to the azd environment in clear text.

Consider using a secure input for the key #920 and then save that to KV and read that value from KV instead of putting in azd env.

Ah good call out. We have an upcoming PR (from a private fork) that adds KeyVault for a different key so it will be easier to use KV to store the OpenAI key after that is in.

@jongio To confirm, were you imagining the flow would be:

azd env set OPENAI_KEY keyhere
azd up
main.bicep stores openAiKey in keyvault
app code checks keyvault for key

OR:

azd up
main.bicep creates a keyvault
user manually adds key to keyvault
app code checks keyvault for key

The first flow has drawback that the secret will be stored in plaintext in .azure/ENVNAME/.env, but is easier for user.
And I specifically didn't suggest possibility of using App Service environment variables with KeyVault references since we want access to this secret locally as well.

@jongio To confirm, were you imagining the flow would be:

azd env set OPENAI_KEY keyhere
azd up
main.bicep stores openAiKey in keyvault
app code checks keyvault for key

OR:

azd up
main.bicep creates a keyvault
user manually adds key to keyvault
app code checks keyvault for key

The first flow has drawback that the secret will be stored in plaintext in .azure/ENVNAME/.env, but is easier for user.
And I specifically didn't suggest possibility of using App Service environment variables with KeyVault references since we want access to this secret locally as well.

Right now, we can't recommend putting a secret in the azd env because the .env file could be inadvertently committed to GH.com.
I think, the best we can do is ask them to set the env var for the key in the current shell and then use it in bicep.  You can have secure inputs, just not secure outputs (yet).

If you do azd env set, doesn't that immediately update the env file? (I just tried, and it did). I'm trying to figure out how they'd set something for use in the Bicep file without using azd env set.

Yes, but we don't want to encourage people to store keys in azd env b/c clear text and only thing preventing it from getting committed is a .gitignore.
I believe the only thing we can do is tell them to set an environment variable manually with export or set

There's a bit of a catch-22 here right now
#1052
There are some secrets that only exist in the .env file, but we need to move them to keyvault as part of resolving this issue
We can use "secretOrRandomPassword" (https://github.com/Azure/azure-dev/discussions/940) to generate a new secret, but we can't specify an optional "default" value in case the user has previously run azd up and has the secrets initialized already.
I'll have to think about this one for a bit - please let me know if you have any thoughts on how to move secrets from the .env file to key vault if they already exist

I wonder if we can use the same method that we use here with the default of USE_APIM

https://github.com/Azure-Samples/todo-csharp-sql/blob/main/infra/main.parameters.json


Update CSE Insight Enrichment Server doc

The checksum file for the FedRAMP version of the Insight Enrichment Server shows up to version 1.0.3 - https://script-collection.s3.amazonaws.com/caravel/checksum.txt
• However, the download link in the documentation links directly to 1.0.1 - https://help.sumologic.com/docs/cse/integrations/insight-enrichment-server/
I was able to download 1.0.3 just fine by changing the download URL
• also on that page - JAVA_PATH should be JAVA_HOME
• also C:\Windows\SumoLogic\EnrichmentServer should be C:\Windows\SumoLogic\EnrichmentService
• and another Enrichment Server documentation issue - https://help.sumologic.com/docs/cse/integrations/insight-enrichment-server/
per the docs, when I set my proxy_url variable to http://x.x.x.x:xxxx (using an IP address, so x.x.x.x in my example), the only error I was seeing in enricher.log was: [ERROR InsightManager:236] http://x.x.x.x
no traffic was getting sent from the Enrichment Server to the proxy via the Insight Enrichment Server service. the issue? the http://
Slack Message

Fixed in https://github.com/SumoLogic/sumologic-documentation/pull/1095

FIxed in https://github.com/SumoLogic/sumologic-documentation/pull/1095.

The download still points to 1.0.1 for the FedRAMP version, despite 1.0.3 being listed in the checksums file at https://script-collection.s3.amazonaws.com/caravel/checksum.txt . now I'm wondering if 1.0.3 IS the latest FedRAMP version, or if there's a newer version with bug fixes that simply hasn't been linked to

The download still points to 1.0.1 for the FedRAMP version, despite 1.0.3 being listed in the checksums file at https://script-collection.s3.amazonaws.com/caravel/checksum.txt .

@ramneetm20 , thank you for letting us know. @ptobia @pkazmir-sumo , I'll reopen this ticket.


insert jquery-mobile

Maybe integrate the jquery-mobile lib from beginning.
For example: I often use it to trigger tap events, because old Android Phones (version <= 4.2) don't know how to trigger on('click') events.

Since this is no common component rather a whole framework I would like to install it via bower command and not as an option for kickstart


Menu Bar Disappears

My environment:
Windows 10 build 1703 64bit
Poedit 2.0.1, Chinese locale

If you prefer to use the bug tracker instead of standard support channels, please use it as intended and check existing issues and post-release commits before filing issues, to prevent outdated or duplicate issues (or as is the case here, both).


Adds the possibility to set on full screen preferred orientations

Currently developers are restricted to use landscape right or left when in full screen while using an Android device, whereas in iOS it will adapt automatically. This will result in an odd behavior when playing portrait (aspect ratio 9:16 for example) videos.
This will add the deviceOrientationsOnFullScreen property that accepts a List<Orientation> for full screen playback that will be used for both platforms. If not provided, it will use de default landscape right/left for Android, as it is.

@brianegan regarding the comment in #225 about the Hero widget, as a suggestion, it would be great if the Hero could be optionally enabled instead of removing at all.

@miguelpruivo applied your wishes in this PR: https://github.com/brianegan/chewie/pull/289 like @brianegan wanted to be in that PR. Please follow that PR for onEnterFullScreen :)

That's great news @Ahmadre, thank you!

Is there any information when this PR will be merged?

@miguelpruivo @alexxlagutin Since version 0.10.x it's possible :) a big pr and many other changes came in 🥳


libmsgpack: 2.1.5 -> 3.0.1

Motivation for this change
The major version change is only due to this bug fix, which affects the reported offset in a malformed msgpack message after trying to parse it (and the previously reported offset was useless). This is not likely to have an effect on any existing software.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

Success on aarch64-linux (full log)
Attempted: libmsgpack
Partial log (click to expand)
-- Installing: /nix/store/0ml48048vsjvcpn6jpyhs913g1zas7kv-libmsgpack-3.0.1/lib/cmake/msgpack/msgpack-targets-release.cmake
-- Installing: /nix/store/0ml48048vsjvcpn6jpyhs913g1zas7kv-libmsgpack-3.0.1/lib/cmake/msgpack/msgpack-config.cmake
-- Installing: /nix/store/0ml48048vsjvcpn6jpyhs913g1zas7kv-libmsgpack-3.0.1/lib/cmake/msgpack/msgpack-config-version.cmake
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/0ml48048vsjvcpn6jpyhs913g1zas7kv-libmsgpack-3.0.1
shrinking /nix/store/0ml48048vsjvcpn6jpyhs913g1zas7kv-libmsgpack-3.0.1/lib/libmsgpackc.so.2.0.0
strip is /nix/store/4md2i310zklkkl5j41yw70gcwgn4kav5-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/0ml48048vsjvcpn6jpyhs913g1zas7kv-libmsgpack-3.0.1/lib
patching script interpreter paths in /nix/store/0ml48048vsjvcpn6jpyhs913g1zas7kv-libmsgpack-3.0.1
checking for references to /build in /nix/store/0ml48048vsjvcpn6jpyhs913g1zas7kv-libmsgpack-3.0.1...

Success on x86_64-linux (full log)
Attempted: libmsgpack
Partial log (click to expand)
-- Installing: /nix/store/v723wf6lw7778qx5fk99l0pjh8vq1wb8-libmsgpack-3.0.1/lib/cmake/msgpack/msgpack-targets-release.cmake
-- Installing: /nix/store/v723wf6lw7778qx5fk99l0pjh8vq1wb8-libmsgpack-3.0.1/lib/cmake/msgpack/msgpack-config.cmake
-- Installing: /nix/store/v723wf6lw7778qx5fk99l0pjh8vq1wb8-libmsgpack-3.0.1/lib/cmake/msgpack/msgpack-config-version.cmake
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/v723wf6lw7778qx5fk99l0pjh8vq1wb8-libmsgpack-3.0.1
shrinking /nix/store/v723wf6lw7778qx5fk99l0pjh8vq1wb8-libmsgpack-3.0.1/lib/libmsgpackc.so.2.0.0
strip is /nix/store/553rihc190vsyy8b22iqcq25a6489h8y-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/v723wf6lw7778qx5fk99l0pjh8vq1wb8-libmsgpack-3.0.1/lib
patching script interpreter paths in /nix/store/v723wf6lw7778qx5fk99l0pjh8vq1wb8-libmsgpack-3.0.1
checking for references to /build in /nix/store/v723wf6lw7778qx5fk99l0pjh8vq1wb8-libmsgpack-3.0.1...

Success on x86_64-darwin (full log)
Attempted: libmsgpack
Partial log (click to expand)
-- Installing: /nix/store/l9w154rkrlkmi8r943k11xvn3r4xs271-libmsgpack-3.0.1/include/msgpack/zone_decl.hpp
-- Installing: /nix/store/l9w154rkrlkmi8r943k11xvn3r4xs271-libmsgpack-3.0.1/lib/pkgconfig/msgpack.pc
-- Installing: /nix/store/l9w154rkrlkmi8r943k11xvn3r4xs271-libmsgpack-3.0.1/lib/cmake/msgpack/msgpack-targets.cmake
-- Installing: /nix/store/l9w154rkrlkmi8r943k11xvn3r4xs271-libmsgpack-3.0.1/lib/cmake/msgpack/msgpack-targets-release.cmake
-- Installing: /nix/store/l9w154rkrlkmi8r943k11xvn3r4xs271-libmsgpack-3.0.1/lib/cmake/msgpack/msgpack-config.cmake
-- Installing: /nix/store/l9w154rkrlkmi8r943k11xvn3r4xs271-libmsgpack-3.0.1/lib/cmake/msgpack/msgpack-config-version.cmake
post-installation fixup
strip is /nix/store/bg39mxc401qqxgjasxfgardi6xl2ikmc-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/l9w154rkrlkmi8r943k11xvn3r4xs271-libmsgpack-3.0.1/lib
patching script interpreter paths in /nix/store/l9w154rkrlkmi8r943k11xvn3r4xs271-libmsgpack-3.0.1


z_vcpkg_download_distfile_via_aria() uses malformed arguments to aria2 download command

Describe the bug
In the implementation of z_vcpkg_download_distfile_via_aria(), the following call (from here) is made to use aria2 to download a file:
        vcpkg_execute_in_download_mode(
            COMMAND ${ARIA2} ${URL}
            -o temp/${arg_FILENAME}
            -l download-${arg_FILENAME}-detailed.log
            ${headers_param}
            OUTPUT_FILE download-${arg_FILENAME}-out.log
            ERROR_FILE download-${arg_FILENAME}-err.log
            RESULT_VARIABLE error_code
            WORKING_DIRECTORY "${DOWNLOADS}"
        )

The -o temp/${arg_FILENAME} argument is malformed. That must not contain any path, it must only be a file name. The -d <dir> option must be used to specify the path instead.
When a path is included in the -o option, it breaks downloads where a redirection is involved. The original URL is first downloaded to the file name specified with the -o option, which is in the temp subdirectory. aria2 checks the HTTP response code and contents of that file and determines that it is a redirect and it needs to try the location specified in the returned content. When it does this retry, the download-${arg_FILENAME}-detailed.log file shows that the temp part of the output file name has been dropped, and now it is downloading the retry to the working directory instead. This succeeds and the aria2 command returns success. However, z_vcpkg_download_distfile_via_aria() then ends up calling z_vcpkg_download_distfile_test_hash() a bit further below and it tests the file in the temp subdirectory, not the final downloaded file in the working directory:
        z_vcpkg_download_distfile_test_hash(
            "${DOWNLOADS}/temp/${arg_FILENAME}"
            "downloaded file"
            "The file may have been corrupted in transit."
            "${arg_SHA512}"
            ${arg_SKIP_SHA512}
        )

This test fails because that file contains content about the redirection, not the final downloaded file. This results in a fatal error, but importantly it also leaves behind the requested downloaded file in the working directory. If you then re-run exactly the same command a second time, it will succeed because the download gets skipped now that the file is there and has the expected hash.
As an example where this bites users, the openssl port for versions before 3.0.7-1 require the jom tool on Windows (#27150 added a fallback to using nmake if using jom results in an error). It calls vcpkg_find_acquire_program(JOM), which eventually finds its way to calling vcpkg_download_distfile(), which then calls z_vcpkg_download_distfile_via_aria(). In vcpkg_find_acquire_program(), the first URL it provides for JOM is https://download.qt.io/official_releases/jom/jom_1_1_3.zip which returns a redirection, triggering the bug.
Environment

Windows 64-bit
Compiler: MSVC, but I doubt it matters

To Reproduce

Checkout the 2021.08.31 tag of vcpkg. This is just to make the steps easy, the latest master still has the bug. Latest master will also show the bug if you start with a clean vcpkg repo (more critically, you don't have a jom executable in downloads/tools/jom/jom-1.1.3).
Make sure downloads/jom_1_1_3.zip does not exist. Delete it if you have that file from some earlier runs. This is critical!
./vcpkg install openssl:x64-windows

The above will try to install openssl 1.1.1m (or a later version if you're using vcpkg master), but will fail. The error claims that the downloaded jom_1_1_3.zip file has a different hash to what was expected.
If you now re-run exactly the same command, it will succeed on this second attempt.
Expected behavior
The jom tool should be downloaded successfully on the first try.
Failure logs
Sorry, can't attach logs for privacy reasons in this case.

Thanks for reporting this issue to vcpkg!
Unfortunately, I can't reproduce this issue in my side, I have tested the following two scenarios:

Git clone a new vcpkg and then checkout to the 2021.08.31 tag, the jom_1_1_3.zip could be downloaded successfully.
Git clone a new vcpkg and use manifest mode to install openssl 1.1.1m#2, the jom_1_1_3.zip could be downloaded successfully.

I have checked the vcpkg_download_distfile.cmake file and I found that when installing the openssl, because _VCPKG_DOWNLOAD_TOOL has no value, z_vcpkg_download_distfile_via_aria() is not executed. This should be the reason why I can't reproduce the issue, so I want to confirm with you whether there are any operations on aria2 to reproduce this issue?

Apologies for the delay in replying. Make sure you don't already have anything in your source tree from earlier work. It is critical that you don't have anything downloaded from earlier steps or else it will mask the underlying problem.
Make sure you follow the exact steps I outlined. The sequence is very specific. Unfortunately, it is also what a typical CI job is going to do if it is using aria for its downloads. I don't know why it is using aria in my case (both locally and in CI), I don't appear to have any thing set to force that.
I suggest trying to do this from different shells. I think if you use Powershell, you get burnt by a dodgey pseudo curl command (lost days chasing that a year ago when exploring curl v aria2 for downloads). Try a standard Dos/Command prompt instead. That would more closely match what I have been doing locally too.
Even if you can't reproduce it though, note that the issue description details how the aria code path is doing the wrong thing. I assume you've got some testing somewhere that exercises that code path. You just need to point it at something that comes back with a redirect to replicate the problem.

Thanks for your reply. I will try again.

You could also potentially try setting the VCPKG_INSTALL_OPTIONS CMake variable to --x-use-aria2. I see that is being done in our own CI jobs, but I didn't have to do that when testing locally.

Stay active

@Cheney-W  I just repro'd a very similar error building opencv4 with  --x-use-aria2
And after fixing the debug_message on line 70 of vcpkg_download_distfile.cmake:
ie: filename should be arg_FILENAME
debug_message("Download Command: ${ARIA2} ${URL} -o temp/${filename} -l download-${filename}-detailed.log ${headers_param}")

This is the error I get. Notice the output filename has subdirectories which fails to download
           -- Using source at C:/vcpkg/buildtrees/opencv4/src/4.8.0-f4e8005717.clean
           -- Downloading opencv-cache/tiny_dnn/adb1c512e09ca2c7a6faef36f9c53e59-v1.0.0a3.tar.gz...
           -- [DEBUG] Download Command: C:/vcpkg/downloads/tools/aria2-1.37.0-windows/aria2-1.37.0-win-64bit-build1/aria2c.exe https://github.com/tiny-dnn/tiny-dnn/archive/v1.0.0a3.tar.gz -o temp/opencv-
         cache/tiny_dnn/adb1c512e09ca2c7a6faef36f9c53e59-v1.0.0a3.tar.gz -l download-opencv-cache/tiny_dnn/adb1c512e09ca2c7a6faef36f9c53e59-v1.0.0a3.tar.gz-detailed.log
           -- Downloading opencv-cache/tiny_dnn/adb1c512e09ca2c7a6faef36f9c53e59-v1.0.0a3.tar.gz... Failed.
               Exit Code: 1
               See logs for more information:
                   C:/vcpkg/downloads/download-opencv-cache/tiny_dnn/adb1c512e09ca2c7a6faef36f9c53e59-v1.0.0a3.tar.gz-out.log
                   C:/vcpkg/downloads/download-opencv-cache/tiny_dnn/adb1c512e09ca2c7a6faef36f9c53e59-v1.0.0a3.tar.gz-err.log
                   C:/vcpkg/downloads/download-opencv-cache/tiny_dnn/adb1c512e09ca2c7a6faef36f9c53e59-v1.0.0a3.tar.gz-detailed.log

This is OVER a year old! It should be fixed by now.


migrate to using uboot

@imrehg this needs a description. I do not understand what this is for

@floion this is a PR made as per @agherzan's request late night on Friday, he'll add more.

@floion added.

u-boot is now used in the bootchain, closing this issue


migrate to vite

Migrate RDD over to vote for typescript and general qol

tested and binaries do extract and function as intended could have re made this but decided to keep as much of base code as possible

Thanks for the PR!
Sorry, we're not planning to add any extra build steps or web frameworks to RDD, as to keep the project as minimal as possible... It is necessary for index.html to be able to run directly off of the filesystem with no build/serve steps. However, I do still plan on a slight redesign and complete refactor of rdd.js to use fetch instead of XMLHttpRequest eventually.

?? this is serverless once it is built and you can use gh actions to build or cf pages

?? this is serverless once it is built and you can use gh actions to build or cf pages

I am aware,

we're not planning to add any extra build steps or web frameworks to RDD, as to keep the project as minimal as possible

It is necessary for index.html to be able to run directly off of the filesystem with no build/serve steps

?? this is serverless once it is built and you can use gh actions to build or cf pages

I am aware,

we're not planning to add any extra build steps or web frameworks to RDD, as to keep the project as minimal as possible

It is necessary for index.html to be able to run directly off of the filesystem with no build/serve steps

ok


Create the SimpleListItemStyle variant with padding

Relates to https://github.com/JetBrains/jewel/pull/651#pullrequestreview-2381649661

Close #658