unexpected end of data while downloading the pdparam for EDVRPredictor

I am in Australia and would like to use Paddle as well. It seems that the downloading of the pdparam file always too slow and ends up without downloading the full file which is indicated by the progress bar: 81920/82300, which leads to the unexpected end of data.
Are we thinking of adding some CDN for overseas users to speed up the downloading?
I have enrolled in 2 classes and hopefully I could use it in my project.
How to reproduce:
import paddle
paddle.set_device('gpu')

from ppgan.apps import EDVRPredictor
sr = EDVRPredictor()

frame_path, video_path = sr.run("video/result/TheProfessor.mp4")

[04/23 00:44:22] ppgan INFO: Downloading edvr_infer_model.tar from https://paddlegan.bj.bcebos.com/applications/edvr_infer_model.tar to /home/winstonfan/.cache/ppgan/edvr_infer_model.tar
100%|█████████▉| 81920/82300 [28:12<00:07, 48.39it/s]
[04/23 01:12:37] ppgan INFO: Decompressing /home/winstonfan/.cache/ppgan/edvr_infer_model.tar...
---------------------------------------------------------------------------
ReadError                                 Traceback (most recent call last)
<ipython-input-6-42021b04bd7a> in <module>
----> 1 sr = EDVRPredictor()
      2
      3 frame_path, video_path = sr.run("video/result/TheProfessor.mp4")

~/anaconda3/envs/paddle/lib/python3.8/site-packages/ppgan/apps/edvr_predictor.py in __init__(self, output, weight_path)
    139
    140         if weight_path is None:
--> 141             weight_path = get_path_from_url(EDVR_WEIGHT_URL)
    142
    143         self.weight_path = weight_path

~/anaconda3/envs/paddle/lib/python3.8/site-packages/ppgan/utils/download.py in get_path_from_url(url, md5sum, check_exist)
     84     if ParallelEnv().local_rank == 0:
     85         if tarfile.is_tarfile(fullpath) or zipfile.is_zipfile(fullpath):
---> 86             fullpath = _decompress(fullpath)
     87
     88     return fullpath

~/anaconda3/envs/paddle/lib/python3.8/site-packages/ppgan/utils/download.py in _decompress(fname)
    170
    171     if tarfile.is_tarfile(fname):
--> 172         uncompressed_path = _uncompress_file_tar(fname)
    173     elif zipfile.is_zipfile(fname):
    174         uncompressed_path = _uncompress_file_zip(fname)

~/anaconda3/envs/paddle/lib/python3.8/site-packages/ppgan/utils/download.py in _uncompress_file_tar(filepath, mode)
    215 def _uncompress_file_tar(filepath, mode="r:*"):
    216     files = tarfile.open(filepath, mode)
--> 217     file_list = files.getnames()
    218
    219     file_dir = os.path.dirname(filepath)

~/anaconda3/envs/paddle/lib/python3.8/tarfile.py in getnames(self)
   1797            the same order as the list returned by getmembers().
   1798         """
-> 1799         return [tarinfo.name for tarinfo in self.getmembers()]
   1800
   1801     def gettarinfo(self, name=None, arcname=None, fileobj=None):

~/anaconda3/envs/paddle/lib/python3.8/tarfile.py in getmembers(self)
   1789         self._check()
   1790         if not self._loaded:    # if we want to obtain a list of
-> 1791             self._load()        # all members, we first have to
   1792                                 # scan the whole archive.
   1793         return self.members

~/anaconda3/envs/paddle/lib/python3.8/tarfile.py in _load(self)
   2377         """
   2378         while True:
-> 2379             tarinfo = self.next()
   2380             if tarinfo is None:
   2381                 break

~/anaconda3/envs/paddle/lib/python3.8/tarfile.py in next(self)
   2310             self.fileobj.seek(self.offset - 1)
   2311             if not self.fileobj.read(1):
-> 2312                 raise ReadError("unexpected end of data")
   2313
   2314         # Read the next block.

ReadError: unexpected end of data

问题过于久远，如果有图像和视频生成的需求，可以使用新的跨模态工具: https://github.com/PaddlePaddle/PaddleMIX/tree/develop


Fix typo in PR template (missing 'for')

Fix a minor typo in the pull request template.

coverage: 81.929%. remained the same
when pulling ecc5ace746179eda6d973593c38d38fdcced19c9 on cowuake:devel
into ceb596030ec2ce551e20c772c139bad24e389c36 on jcubic:devel.

Thanks.


Enh/improve test coverage

tests look good, but the python26 tests are failing on circle due to long timeouts
it looks like there's a no_output_timeout parameter in the circle config, though: https://circleci.com/docs/2.0/configuration-reference/

@neuromusic the circleci tests are very slow compared to appveyor and travis tests, can we ditch the circleci tests or address this speed related problem in a separate pr? changes to circleci seem out of the scope of this pr

Codecov Report

Merging #94 into master will increase coverage by 23.31%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master      #94       +/-   ##
===========================================
+ Coverage   67.09%   90.41%   +23.31%
===========================================
  Files          14       14
  Lines         699      699
===========================================
+ Hits          469      632      +163
+ Misses        230       67      -163

Impacted Files
Coverage Δ

neuroglia/datasets/synthetic_calcium.py
97.91% <0%> (+41.66%)
:arrow_up:

neuroglia/calcium/oasis/functions.py
88.88% <0%> (+45.39%)
:arrow_up:

Continue to review full report at Codecov.

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


Add icons for homeassistant default conditions

Hey, can you add an iconset for the default HA conditions? I really love your card, but right now I can't use it with my weather provider.
I tried to compile the project by myself, but I am missing something so it's not working. Can you please include it? Here is the mapping for the values:
export const cwcDefaultHassDayIcons: { [key: string]: string } = {
  cloudy: "cloudy-day-3",
  exceptional: "severe-thunderstorm",
  fog: "fog",
  hail: "snow-and-sleet-mix",
  lightning: "severe-thunderstorm",
  "lightning-rainy": "scattered-thunderstorms",
  partlycloudy: "cloudy-day-3",
  pouring: "rainy-6",
  rainy: "rainy-5",
  snowy: "snowy-6",
  "snowy-rainy": "snow-and-sleet-mix",
  sunny: "clear-day",
  windy: "wind",
  "windy-variant": "wind",
}

export const cwcDefaultHassNightIcons: { [key: string]: string } = {
  ...cwcDefaultHassDayIcons,
  "clear-night": "clear-night",
}

And one suggestion: in ha-card-weather-conditions.ts you are overwriting the icon setting always with climacell. The correct implementation has to be:
if ((!!config.weather) && (!!config.weather.icons_model))
  switch (config.weather.icons_model.toLowerCase()) {
    case 'darksky':
      this._iconsConfig.iconsDay = cwcDarkskyDayIcons;
      this._iconsConfig.iconsNight = cwcDarkskyNightIcons;
      this._iconsConfig.icons_model = "darksky";
      break;
    case 'openweathermap':
      this._iconsConfig.iconsDay = cwcOpenWeatherMapDayIcons;
      this._iconsConfig.iconsNight = cwcOpenWeatherMapNightIcons;
      this._iconsConfig.icons_model = "openweathermap";
      break;
    case 'defaulthass':
      this._iconsConfig.iconsDay = cwcDefaultHassDayIcons;
      this._iconsConfig.iconsNight = cwcDefaultHassNightIcons;
      this._iconsConfig.icons_model = "defaulthass";
      break;
    default:
      this._iconsConfig.iconsDay = cwcClimacellDayIcons;
      this._iconsConfig.iconsNight = cwcClimacellNightIcons;
      this._iconsConfig.icons_model = "climacell";
  }

Done. The enhancement is in the newly released version.
Thanks, bye.
Renato

Thank you, for what I can see now (Next 4 days) the correct icon is showing.
Just can't seem to get the icon showing in the top for current weather (next to where normally moon phase is showing).
Using this code:
  - type: custom:ha-card-weather-conditions
    language: en
    animation: true
    camera: camera.buienradar
    weather:
      icons_model: "buienradar"
      current:
        sun: sun.sun
        # moon_phase: sensor.cc_climacell_moon_phase
        current_conditons: sensor.br_detailed_condition
        humidity: sensor.br_humidity
        pressure: sensor.br_pressure
        temperature: sensor.br_temperature
        feels_like: sensor.br_feel_temperature
        visibility: sensor.br_visibility
        wind_bearing: sensor.br_wind_direction_azimuth
        wind_speed: sensor.br_wind_speed
        precipitation: sensor.br_precipitation```

The sensor.br_detailed_condition is currently showing: 'clear'

Hi, check your browser console for icon errors.

Done. The enhancement is in the newly released version.
Thanks, bye.
Renato

Thanks for the quick integration!

Hi, check your browser console for icon errors.

It is throwing me this error:
ha-card-weather-conditions.js:270 Icons issue. States: icons_model=buienradar - isDay=true - condition: na.


Various build fixes

Here are few recent commits that fix various issues in Bazel-related files (BUILD, WORKSPACE, *.bzl), mostly as a result of changes in recent version of Bazel.
Tested with "bazel test -c opt ..." on Ubuntu 18.04, Ubuntu 20.04, macOS 10.14.6, and macOS 11.1 with Bazel 3.7.2 and Bazel 4.0.

Thanks, Martin!

Thanks, Martin!


fix: allow additional params in the schema

This update removes "additionalProperties": false from the schema, allowing extra params to be included
without causing schema validation errors.
As discussed here: Link

The default is they are allowed, right?

Yes, the default is all keys are allowed

/test all

/retest


[Review]: Chip review

The review for code readability and design spec diff for the Chip variants.
See Chip on digital.sbb.ch

Code readability (emoji): 🎉
Diff to specs (large / medium / small / none): none

No work needed - closing this.


About bound and  marching_cubes_bound

Hi，
Thank you for your excellent work。For the bound and marching in the configuration file_ Cubes_ I have some questions about bound and I need your help. May I ask what is the reason for setting it here? I think this is a hyperparameter. If I want to use my own dataset to run ESLAM, how should I configure bound and marching_ Cubes_bound。
Thanks in advance.

Hi,
Yes, that is a hyper parameters and you should set it in a way that it at least cover your whole room/apartment. You could provide the number in actual meter scale, or normalize them arbitrary. Just note that you should also set the camera pose of the first frame, and it should match the bounds that you give to the model. I mean, all other predicted camera poses are relative to the first camera pose, and the reconstructed mesh should fit in the bounds you define at the beginning.
Kind regards,


RC Spot-Check Test: GA Maintenance Release

RC Spot-Check Test
Mentions: @KatieWoe @jonathanolson
https://phet-dev.colorado.edu/html/friction/1.5.18-rc.1/phet/friction_en_phet.html
https://phet-dev.colorado.edu/html/friction/1.5.18-rc.1/phet/friction_en_phet.html?ga=UA-5033201-2&ga4=G-NT4RB93Q46
https://jonathanolson.net/phet/ga30-test.html?ga=UA-5033201-2&ga4=G-NT4RB93Q46
Making sure this is working as intended (loads on supported platforms)
Make sure stats are sent to GA across browsers - see 2 collect calls:
tid: G-4EVJVBSTB9
tid: UA-5033201-1
Simulation links
General Test:
Tester = KW, Platform = Windows 11 (Chrome, Firefox, Edge), Time =
Tester = ON, Platform = , Time =

I'm seeing some possible indications that our new GA4 property is firing twice.
https://phet-dev.colorado.edu/html/friction/1.5.18-rc.1/phet/friction_en_phet.html?ga=UA-5033201-2&ga4=G-NT4RB93Q46&SafariDuplicateTest
https://phet-dev.colorado.edu/html/friction/1.5.18-rc.1/phet/friction_en_phet.html?ga=UA-5033201-2&ga4=G-NT4RB93Q46&SafariDuplicateTest2
https://phet-dev.colorado.edu/html/friction/1.5.18-rc.1/phet/friction_en_phet.html?ga=UA-5033201-2&ga4=G-NT4RB93Q46&FirefoxDuplicateTest
https://phet-dev.colorado.edu/html/friction/1.5.18-rc.1/phet/friction_en_phet.html?ga=UA-5033201-2&ga4=G-NT4RB93Q46&FirefoxDuplicateTest2

Also going to test these since our 3rd party UA is still "Connected" to our 3rd party GA4 - to see if that is the potential cause.
https://jonathanolson.net/phet/ga30-test.html?ga=UA-5033201-2&ga4=G-NT4RB93Q46&FirefoxDuplicateExternal
https://jonathanolson.net/phet/ga30-test.html?ga=UA-5033201-2&ga4=G-NT4RB93Q46&FirefoxDuplicateExternal2

Ok - looks like a false alarm. All of the tests above showed 1 View in our new GA4 analytics

Also, both of the query parameter properties received 1 view for each test page.

The external test links (from jonathanolson.net) also registered 2 views in the PhET Third Party GA4 account, as expected:

The only inconsistency are the views recorded to our new GA4 analytics property: 5 pages registered a single view (after filtering for any page that contains "Duplicate"). SafariDuplicateTest is missing. It was recorded on every other property (UA, both external query parameter properties). It may have just been a peculiar case, not sure.
@jonathanolson I think we're safe to deploy - hits are recording properly (mostly) and there aren't any duplicate hits.

Ok thanks, will plan to move forward with the deployment! Got some other patches fixed up.

Closing, thanks!


Export options

The Monero CLI supports several history export options:

Type: [in|out|all|pending|failed|pool|coinbase]
Subaddress index: [index=<N1>[,<N2>,...]]
Min/max block height: [<min_height> [<max_height>]]
Output path: [output=<filepath>]
With keys: [option=<with_keys>]

It would be nice if Feather Wallet supported export options. Most notably, the ability to export with_keys is important to me.

+1, but also I'd like to add the ability for a user to specify a date range.
For example, many users will want to export all transactions between January 1st and December 31st (inclusive) for generating a file to send to their accountant at year-end.


How can I parse ISO 8601 / RFC 3339 datetime string and format in browser's timezone?

How can I parse a ISO 8601 / RFC 3339 datetime string and format it in the browser's timezone? (or a given timezone)
Thanks :)

We're mostly deferring to purescript-datetime for dealing with locales.
Here's the output of a quick pulp repl session that defines and uses a few locales.
import Prelude
> import Data.DateTime.Locale
> import Data.Maybe
> import Data.PreciseDateTime.Locale (toRFC3339String)
> import Data.PreciseDateTime (fromRFC3339String)
> import Data.RFC3339String
> import Data.Time.Duration as Duration

> pst = Locale (Just $ LocaleName "PST") (Duration.Minutes $ -8.0 * 60.0)
> pdt = Locale (Just $ LocaleName "PDT") (Duration.Minutes $ -7.0 * 60.0)
> utc = (Just $ LocaleName "UTC") (Duration.Minutes 0.0)
> precDateTime = fromRFC3339String $ RFC3339String "2018-03-07T18:21:10.123456789Z"

> LocalValue pst <$> precDateTime
(Just (LocalValue (Locale (Just (LocaleName "PST")) (Minutes -480.0)) PreciseDateTime ((DateTime (Date (Year 2018) March (Day 7)) (Time (Hour 18) (Minute 21) (Second 10) (Millisecond 123)))) (Nanosecond 123456789)))
> toRFC3339String <<< LocalValue pst <$> precDateTime
(Just (RFC3339String "2018-03-07T18:21:10.123456789-08:00"))

> LocalValue pdt <$> precDateTime
(Just (LocalValue (Locale (Just (LocaleName "PDT")) (Minutes -420.0)) PreciseDateTime ((DateTime (Date (Year 2018) March (Day 7)) (Time (Hour 18) (Minute 21) (Second 10) (Millisecond 123)))) (Nanosecond 123456789)))
> toRFC3339String <<< LocalValue pdt <$> precDateTime
(Just (RFC3339String "2018-03-07T18:21:10.123456789-07:00"))

> LocalValue utc <$> precDateTime
(Just (LocalValue (Locale (Just (LocaleName "UTC")) (Minutes 0.0)) PreciseDateTime ((DateTime (Date (Year 2018) March (Day 7)) (Time (Hour 18) (Minute 21) (Second 10) (Millisecond 123)))) (Nanosecond 123456789)))
> toRFC3339String <<< LocalValue utc <$> precDateTime
(Just (RFC3339String "2018-03-07T18:21:10.123456789Z"))

I'm not sure about how to get the browsers' locale but maybe purescript-js-date can help with that.

If you call javascript's Date.toString() it will format the date in your browser's timezone. I think this function is exported somewhere in purescript-datetime.

@paulyoung But how does that work with CET which sometimes has a daylight savings time? Do I have to manually compute if DST is active now and then apply the offset conditionally? Or is there support for this already?

@Boscop we're leveraging much of what purescript-datetime offers, and since it provides no built-in support for such things 1, we also defer to other libraries for this sort of thing.
I think you would need to know if DST is active and do something like this:
cet = Locale (Just $ LocaleName "CET") (Duration.Minutes $ 1.0 * 60.0)
cetDst = Locale (Just $ LocaleName "CET DST") (Duration.Minutes $ 2.0 * 60.0)

@themattchan Thanks, but I want to convert the timezone before doing custom (german) formatting. This is my current function which is wrong because it doesn't convert the timezone from utc to browser local / german:
fmt_rfc3339 = parseFormatString "YYYY-MM-DDTHH:mm:ss+00:00"
fmt_german = parseFormatString "DD.MM.YYYY, HH:mm"

humanTime s = either id id do
  decode <- fmt_rfc3339
  encode <- fmt_german
  datetime <- unformat decode s
  pure $ format encode datetime

And it also fails when the datetime string is valid rfc3339 but not matching the format string I'm using (e.g. if it has microseconds or a different timezone)..
@paulyoung

Thanks. I have a question: In your first reply, why did you use Locale for pdt but not utc?

> pdt = Locale (Just $ LocaleName "PDT") (Duration.Minutes $ -7.0 * 60.0)
> utc = (Just $ LocaleName "UTC") (Duration.Minutes 0.0)

Looking at this it should be possible to use that in PS, right?
In my browser (CET) it returns -60.
So can I use that in PS like this?:

now = ? -- PureScript equivalent of `new Date()`
utcOffset = getTimezoneOffset now
browserLocale = Locale (Just $ LocaleName "browser") (Duration.Minutes utcOffset)
precDateTime = fromRFC3339String $ RFC3339String "2018-03-07T18:21:10.123456789Z"
timeAslocal = LocalValue browserLocale <$> precDateTime
-- now format `timeAslocal` as "DD.MM.YYYY, HH:mm"

But what's the PureScript equivalent of new Date()?
And how can I then format timeAslocal as "DD.MM.YYYY, HH:mm"?


refactor(insights): improve inconsistency of codes.

Overview

What is it?

[ ] Feature / enhancement
[ ] Bug
[ ] Docs / tests / types / typos

Description
Nothing related to features or bugs. It is just a coding enhancement. making sure Single Source of Truth.

I'm thinking about this change, did you find any problem in the previous code?

I'm thinking about this change, did you find any problem in the previous code?

No problem in the previous code, it is just best practice to follow the Single Source of Truth.

This will work smoothly, As I've already deployed insights in our environment for staging & production sites without any problem. And working perfectly.


[0319/173114.430:ERROR:crash_report_database_win.cc(469)] failed to stat repor

[ x] I have checked issues with bug label and found no duplicates

Expected Behavior
To generate the docs normally.
Actual Behavior
It generates the pages index and globals, but with no content about my code and after open the page, the file "debug.log" is generated inside the docs folder with the bellow content:
[0319/173114.428:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0319/173114.429:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0319/173114.429:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0319/173114.429:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0319/173114.430:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0319/173114.430:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0319/173114.430:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0319/173114.430:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0319/173114.430:ERROR:crash_report_database_win.cc(469)] failed to stat report
[0319/173114.430:ERROR:crash_report_database_win.cc(469)] failed to stat report
Steps to reproduce the bug
I'm using Next.js with React Native for Web and just converted my project from JS to TS. The file is generated when i open the web page. (Actually i don't know if this file means something or if i'm missing some config)
Environment

Typedoc version: 0.17.1
TypeScript: 3.8.3
Node.js version: v10.16.3
OS: Windows 10 Pro 1809

The file is generated when i open the web page.

This doesn't make sense to me. TypeDoc does all of its work before any files are created.. so if files are created the issue is likely outside of TypeDoc. Do you get errors when running TypeDoc in the console?


Updated CloudFront details.

👍 lgtm, thank you for your contribution, @dreamiurg!
@jlevy would you mind checking this out for final review/merge?

👍 Thanks @dreamiurg !


migrating from django 3.2.x to django 4.1.x : AttributeError: 'Query' object has no attribute 'explain_query'

Just opened a new issue since it looks like the same previous issue was kept open for quite some time.
https://github.com/ESSolutions/django-mssql-backend/issues/125

I'm not sure about the etiquette of mentioning other repos to solve an issue on github (please do let me know if this is not a good practice or so), but from my own experience I had to migrate from django-mssql-backend to mssql-django (https://github.com/microsoft/mssql-django) as it supports Django 3.0+. This repo is a fork from django-mssql-backend, so I didn't have to make much changes on it.


Fixing the Code Coverage build

After my last change the optimization was enabled for code coverage builds which affected the total blocks count. This change fixes it.

@curtisman Can you please take a look?

@dotnet-bot test Ubuntu static_ubuntu_linux_test please

@dotnet-bot test Ubuntu static_ubuntu_linux_test please


Use a shell script for generating OTLP modules

This PR proposes to:

Use a (POSIX) shell script for generating the Haskell OTLP modules.
Remove the custom setup (https://github.com/iand675/hs-opentelemetry/issues/158).
Generate all the Haskell OTLP modules by running ./otlp/scripts/generate-modules.sh v1.0.0.

The script takes, as argument, the git tag of opentelemetry-proto project. It clones the repository, it copies all the protobuf files, and run protoc.
Let's say, for example, that we want to generate the modules for the OTLP v1.3.2, we'll just have to run ./otlp/scripts/generate-modules.sh v1.3.2.

Great, thanks for doing this! I was just about to look at it :joy:

I reused/refactored something I wrote for another OpenTelemetry Haskell library [1] 😄
[1] https://github.com/Siprj/otel-haskell-sdk

Great, I'm happy, I'm going to leave it a few days in case there is any dissent, and then merge.

Beautiful! :shipit:


Add Rector for 'depends'

This adds support for converting the @depends PHPUnit doc tag to Pest's ->depends() chainable method.
Closes https://github.com/pestphp/drift/issues/14

The failures in the test suite appear to be unrelated to the code I've added. 🤔 Any thoughts @olivernybroe?

@owenvoke So the test which fails is because we simply haven't implemented it yet :)
This way we don't forget that this the issue is there.
The warning in the tests is because we simply haven't added any tests for checking if the removal of the php unit class is done correctly

Thanks! From looking at Drift, Rector is so neat. 😀

@owenvoke Yeah, it's really awesome to work with! :)
And the creator is active and willing to answer support questions and even help with the code.


Issue building OIIO with OCIO 1.0.9 support

I tried compiling OIIO with my own build of OCIO 1.0.9 (current master branch) and I'm getting this error. Maybe someone can help.
'''
...
Linking CXX shared library libOpenImageIO.so
[ 81%] Built target OpenImageIO
[ 82%] Building CXX object src/libOpenImageIO/CMakeFiles/imagebuf_test.dir/imagebuf_test.cpp.o
Linking CXX executable imagebuf_test
libOpenImageIO.so.1.4.5: undefined reference to YAML::Node::begin() const' libOpenImageIO.so.1.4.5: undefined reference toYAML::Node::~Node()'
libOpenImageIO.so.1.4.5: undefined reference to TiXmlNode::TiXmlNode(TiXmlNode::NodeType)' libOpenImageIO.so.1.4.5: undefined reference toTiXmlNode::FirstChildElement() const'
libOpenImageIO.so.1.4.5: undefined reference to vtable for TiXmlPrinter' libOpenImageIO.so.1.4.5: undefined reference toYAML::Emitter::PostWriteStreamable(std::basic_stringstream<char, std::char_traits, std::allocator > const&)'
libOpenImageIO.so.1.4.5: undefined reference to YAML::Node::FindAtIndex(unsigned long) const' libOpenImageIO.so.1.4.5: undefined reference toYAML::Iterator::second() const'
libOpenImageIO.so.1.4.5: undefined reference to YAML::Node::Node()' libOpenImageIO.so.1.4.5: undefined reference toTiXmlElement::SetAttribute(char const_, char const_)'
libOpenImageIO.so.1.4.5: undefined reference to YAML::Iterator::operator++()' libOpenImageIO.so.1.4.5: undefined reference toYAML::Parser::~Parser()'
libOpenImageIO.so.1.4.5: undefined reference to vtable for TiXmlDocument' libOpenImageIO.so.1.4.5: undefined reference toTiXmlNode::FirstChild(char const_) const'
libOpenImageIO.so.1.4.5: undefined reference to YAML::Emitter::PreWriteIntegralType(std::basic_stringstream<char, std::char_traits<char>, std::allocator<char> >&)' libOpenImageIO.so.1.4.5: undefined reference toTiXmlDocument::TiXmlDocument()'
libOpenImageIO.so.1.4.5: undefined reference to TiXmlNode::~TiXmlNode()' libOpenImageIO.so.1.4.5: undefined reference toYAML::Iterator::first() const'
libOpenImageIO.so.1.4.5: undefined reference to TiXmlNode::InsertBeforeChild(TiXmlNode_, TiXmlNode const&)' libOpenImageIO.so.1.4.5: undefined reference to YAML::Emitter::Write(YAML::Tag const&)'
libOpenImageIO.so.1.4.5: undefined reference toYAML::Emitter::~Emitter()' libOpenImageIO.so.1.4.5: undefined reference to TiXmlElement::Attribute(char const*) const'
libOpenImageIO.so.1.4.5: undefined reference toYAML::Parser::Parser(std::basic_istream<char, std::char_traits<char> >&)' libOpenImageIO.so.1.4.5: undefined reference to YAML::Parser::GetNextDocument(YAML::Node&)'
libOpenImageIO.so.1.4.5: undefined reference toYAML::Emitter::good() const' libOpenImageIO.so.1.4.5: undefined reference to YAML::operator!=(YAML::Iterator const&, YAML::Iterator const&)'
libOpenImageIO.so.1.4.5: undefined reference toTiXmlDocument::Parse(char const_, TiXmlParsingData_, TiXmlEncoding)' libOpenImageIO.so.1.4.5: undefined reference to YAML::Emitter::PostWriteIntegralType(std::basic_stringstream<char, std::char_traits, std::allocator > const&)'
libOpenImageIO.so.1.4.5: undefined reference toYAML::Emitter::GetFloatPrecision() const' libOpenImageIO.so.1.4.5: undefined reference to YAML::Iterator::~Iterator()'
libOpenImageIO.so.1.4.5: undefined reference toYAML::Emitter::Write(bool)' libOpenImageIO.so.1.4.5: undefined reference to YAML::Emitter::PreWriteStreamable(std::basic_stringstream<char, std::char_traits, std::allocator >&)'
libOpenImageIO.so.1.4.5: undefined reference toYAML::Convert(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, bool&)' libOpenImageIO.so.1.4.5: undefined reference to YAML::Node::GetScalar(std::basic_string<char, std::char_traits, std::allocator >&) const'
libOpenImageIO.so.1.4.5: undefined reference toYAML::Emitter::Write(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)' libOpenImageIO.so.1.4.5: undefined reference to YAML::Node::end() const'
libOpenImageIO.so.1.4.5: undefined reference toTiXmlElement::TiXmlElement(char const_)' libOpenImageIO.so.1.4.5: undefined reference to YAML::Emitter::c_str() const'
libOpenImageIO.so.1.4.5: undefined reference toTiXmlNode::NextSibling(char const_) const' libOpenImageIO.so.1.4.5: undefined reference to YAML::Node::size() const'
libOpenImageIO.so.1.4.5: undefined reference toTiXmlNode::LinkEndChild(TiXmlNode_)' libOpenImageIO.so.1.4.5: undefined reference to TiXmlHandle::FirstChild(char const) const'
libOpenImageIO.so.1.4.5: undefined reference to TiXmlDocument::Accept(TiXmlVisitor*) const' libOpenImageIO.so.1.4.5: undefined reference toYAML::Emitter::Emitter()'
libOpenImageIO.so.1.4.5: undefined reference to YAML::Iterator::Iterator(YAML::Iterator const&)' libOpenImageIO.so.1.4.5: undefined reference tovtable for TiXmlText'
libOpenImageIO.so.1.4.5: undefined reference to TiXmlElement::GetText() const' libOpenImageIO.so.1.4.5: undefined reference toYAML::Emitter::SetLocalValue(YAML::EMITTER_MANIP)'
collect2: ld returned 1 exit status
make[2]: *** [src/libOpenImageIO/imagebuf_test] Error 1
make[1]: *** [src/libOpenImageIO/CMakeFiles/imagebuf_test.dir/all] Error 2
make: *** [all] Error 2
'''
EDIT: Sorry, I pasted the wrong error log at first, now it's the right one
Thanks in advance

I just ran into this, and traced it back to what looks like an issue with the OCIO static library build process.
Basically, if you build a static OCIO library, it doesn't properly include the compiled YAML and TinyXML objects in the archive, so all of their related symbols are missing. As a test, I manually dumped all of the objects from libOpenColorIO.a, libtinyxml.a, and libyaml-cpp.a, and reassembled them into a new libOpenColorIO.a. Linking that new library, the OIIO build completed without errors.
It looks like OIIO may be trying to work around this by explicitly trying to link tinyxml, yaml-cpp, and lcms2 if LINKSTATIC is enabled (see here), but because those libraries are always built and linked statically by OCIO, they aren't actually installed in any way that will let OIIO find them at build time.
I'm adding an issue on the OCIO side related to building a complete static library, and I think I may take a crack at a PR in the near future. It's somewhat awkward, since building objects as targets isn't directly supported by CMake prior to 2.8.8, and the only other option that I'm aware of is using a custom target for the static library that either locates all the necessary object files, or unpacks and re-packs the archives the way I did.

Must be a bug as I spent a lot of time getting the static build to be
correct back in the day.
We you do look at it I would first look at what happens when yamlcpp and
tinyxml are found on the system. As I always build with the bundled
versions.
On 30 Sep 2016 8:38 am, "Nathan Rusch"<EMAIL_ADDRESS>wrote:

I just ran into this, and traced it back to what looks like an issue with
the OCIO static library build process.
Basically, if you build a static OCIO library, it doesn't properly include
the compiled YAML and TinyXML objects in the archive, so all of their
related symbols are missing. As a test, I manually dumped all of the
objects from libOpenColorIO.a, libtinyxml.a, and libyaml-cpp.a, and
reassembled them into a new libOpenColorIO.a. Linking that new library,
the OIIO build completed without errors.
It looks like OIIO may be trying to work around this by explicitly trying
to link tinyxml, yaml-cpp, and lcms2 if LINKSTATIC is enabled (see here
https://github.com/OpenImageIO/oiio/blob/master/src/cmake/externalpackages.cmake#L245),
but because those libraries are always built and linked statically by OCIO,
they aren't actually installed in any way that will let OIIO find them at
build time.
I'm adding an issue on the OCIO side related to building a complete static
library, and I think I may take a crack at a PR in the near future. It's
somewhat awkward, since building objects as targets isn't directly
supported by CMake prior to 2.8.8, and the only other option that I'm aware
of is using a custom target for the static library that either locates all
the necessary object files, or unpacks and re-packs the archives the way I
did.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/OpenImageIO/oiio/issues/839#issuecomment-250680161,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAL7h_Y5wPJxuExn-R6oT4pRwyp6S-BXks5qvLyLgaJpZM4BzxKq
.

Well, libOpenImageIO will link libOpenColorIO.a without complaining, but as soon as something actually tries to use it (in this case, the OIIO tests), things fall apart. From what I've found, it doesn't seem like CMake knows (or can be explicitly told) that linking one static library into another requires the objects to be extracted from the dependency and included in the assembled target. However, in this case, I suspect that the OBJECT library type would be the "right" way to deal with the issue, since the dependencies are being compiled at the same time.

Sorry, I forgot to mention that I've always built OCIO with the bundled dependencies as well.

Closing. This is very old, both OIIO and OCIO have changed quite a lot in the mean time. Somebody will re-open or file a new issue of the modern versions fail to build against each other.


Process AAC-LC Specific Config according to the spec

I noticed two issues with AAC-LC specific config where it does not comply to the referenced ISO+IEC-14496-1:2010.
Issue A: Use the "expandable" fields for DecoderConfigDescriptor and DecooderSpecificInfo.
Unfortunately when investigating the difference between ISO+IEC-14496-1:2010 and ISO+IEC-14496-1-1998
(https://github.com/AOMediaCodec/iamf/issues/338) no one noticed the "expandable" keyword and associated
syntax. This keyword applies to DecoderConfigDescriptor and DecoderSpecificInfo through their inheritance of BaseDescriptor.
§  8.3.3 defines the use of the "expandable"  keyword. It encodes a size in the bitstream using a scheme that appears to be like a big-endian version of leb128.
As of b60e7195a this field does not seem to be handled by the decoder and it is missing in the test vectors.

Update the decoder to handle this field in both locations.
Update the test vectors to use this field.

Issue B: Set DecoderConfigDescriptor reserved field to 1.
This is more trivial because it does not shift any bits around. See #338 which notes DecoderConfigDescriptor has a reserved field fixed at 1.
As of b60e7195a the test set has this set incorrectly to 0.

Check the decoder is OK when this field is 1.
Update the test set to have this field be set to 1.

For both issues, we will regenerate the test vectors for both v1.0.0-errata and v1.1.0 to match the spec. For issue A we will also update the decoders to match.
We will also double check other implementations (e.g. the ffmpeg implementation) to make sure they match the spec and not the old reference implementation.

It can be closed as PR #118 have adressed this

It has also been addressed in ffmpeg.


add Dockerfile to build image for OTC

@novoelgy asked for docker image to host the nginx

Please delete the stale branch add/Dockerfile!


html title

adds html_title to Report class so that we can customize the html title of a report
renames nb_name to html_title in the ReportGenerator, as it was only being used for setting the html title anyway

@hyukim17 I think these errors have nothing to do with your changes. I'm going to fix them, add Python 3.12 support, add a new testing bundle with the latest versions of libraries, and then I'll do a release.

What's the process for deploying a new wheel?

I just released v0.5.0: https://github.com/ansatzcapital/leda/releases/tag/v0.5.0. It's now available via pypi: https://pypi.org/project/leda/0.5.0/.
The process is simply to create a new GitHub release here: https://github.com/ansatzcapital/leda/releases. (GitHub has a button to auto-generate release notes, which I use.) Then the CI will do the rest:  https://github.com/ansatzcapital/leda/actions/runs/8039217496.
Note that in this case, we just crossed the 100MB limit for the sdist--but not the whl--file, so only the wheel was uploaded. I'll look into fixing this.
Note also that I added a scheduled daily run here so that external changes don't silently break the CI tests in between PRs, as they did in this one.


Add Documentation

The project is currently severely needing documentation. This is something that needs to be worked on before it gets too big to understand.

Document should be up-to-date.


FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory

Running angular 2 tests, all been working fine until this morning when I upgraded some packages. One of them is typescript - from 1.7.5 to 1.8.2
Using with typescript 1.8.2, node 5.7.0,
"karma": "^0.13.21",
"karma-chrome-launcher": "^0.2.2",
"karma-coverage": "^0.5.3",
"karma-jasmine": "^0.3.7",
"karma-mocha-reporter": "^1.2.3",
"karma-phantomjs-launcher": "^1.0.0",
"karma-sourcemap-loader": "^0.3.7",
"karma-webpack": "1.7.0",

Here's an output:
ts-loader: Using<EMAIL_ADDRESS>and d:\Documents\Visual Studio 2015\Projects\MyPrj\tsconfig.json
<--- Last few GCs --->
80496 ms: Mark-sweep 1380.1 (1457.2) -> 1379.9 (1457.2) MB, 1205.6 / 0 ms [allocation failure] [GC in old space requested].
81726 ms: Mark-sweep 1379.9 (1457.2) -> 1379.9 (1457.2) MB, 1229.6 / 0 ms [allocation failure] [GC in old space requested].
82944 ms: Mark-sweep 1379.9 (1457.2) -> 1377.5 (1457.2) MB, 1217.7 / 0 ms [last resort gc].
84158 ms: Mark-sweep 1377.5 (1457.2) -> 1379.9 (1457.2) MB, 1213.9 / 0 ms [last resort gc].
<--- JS stacktrace --->
==== JS stack trace =========================================
Security context:<PHONE_NUMBER>DE3AD1
2: objectTypeRelatedTo(aka objectTypeRelatedTo) [d:\Documents\Visual Studio 2015\Projects\MyPrj\node_modules\typescript\lib\typescript.js:19809] [pc=000003AA2E94DD3E] (this=0000017062D04189 ,source=00000182C9217CC1 <a TypeObject with map 000003805A847911>,originalSource=00000182C9217CC1 <a TypeObject with map 000003805A847911>,target=0000037567B6A851 <a TypeObject with...
FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "run" "test" "--" "--auto-watch" "--no-single-run"
npm ERR! node v5.7.0
npm ERR! npm  v3.6.0
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>test: karma start "--auto-watch" "--no-single-run"
npm ERR! Exit status 3
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>test script 'karma start "--auto-watch" "--no-single-run"'.
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 angular2-webpack-starter package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     karma start "--auto-watch" "--no-single-run"
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs angular2-webpack-starter
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls angular2-webpack-starter
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     d:\Documents\Visual Studio 2015\Projects\MyPrj\npm-debug.log
npm ERR! Windows_NT 10.0.10586
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "run" "watch:test"
npm ERR! node v5.7.0
npm ERR! npm  v3.6.0
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>watch:test: npm run test -- --auto-watch --no-single-run
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>watch:test script 'npm run test -- --auto-watch --no-single-run'.
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 angular2-webpack-starter package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     npm run test -- --auto-watch --no-single-run
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs angular2-webpack-starter
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls angular2-webpack-starter
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     d:\Documents\Visual Studio 2015\Projects\MyPrj\npm-debug.log
karma.config.js:
// @AngularClass

module.exports = function(config) {
  var testWebpackConfig = require('./webpack.test.config.js');

  config.set({

    // base path that will be used to resolve all patterns (e.g. files, exclude)
    basePath: '',

    // frameworks to use
    // available frameworks: https://npmjs.org/browse/keyword/karma-adapter
    frameworks: ['jasmine'],

    // list of files to exclude
    exclude: [ ],

    // list of files / patterns to load in the browser
    // we are building the test environment in ./spec-bundle.js
    files: [ { pattern: 'spec-bundle.js', watched: false } ],

    // preprocess matching files before serving them to the browser
    // available preprocessors: https://npmjs.org/browse/keyword/karma-preprocessor
    preprocessors: { 'spec-bundle.js': ['coverage', 'webpack', 'sourcemap'] },

    // Webpack Config at ./webpack.test.config.js
    webpack: testWebpackConfig,

    coverageReporter: {
      dir : 'coverage/',
      reporters: [
        { type: 'text-summary' },
        { type: 'json' },
        { type: 'html' }
      ]
    },

    // Webpack please don't spam the console when running in karma!
    webpackServer: { noInfo: true },

    // test results reporter to use
    // possible values: 'dots', 'progress'
    // available reporters: https://npmjs.org/browse/keyword/karma-reporter
    reporters: [ 'mocha', 'coverage' ],

    // web server port
    port: 9876,

    // enable / disable colors in the output (reporters and logs)
    colors: true,

    // level of logging
    // possible values: config.LOG_DISABLE || config.LOG_ERROR || config.LOG_WARN || config.LOG_INFO || config.LOG_DEBUG
    logLevel: config.LOG_INFO,

    // enable / disable watching file and executing tests whenever any file changes
    autoWatch: false,

    // start these browsers
    // available browser launchers: https://npmjs.org/browse/keyword/karma-launcher
    browsers: [
      'Chrome',
      //'PhantomJS'
    ],

    // Continuous Integration mode
    // if true, Karma captures browsers, runs the tests and exits
    singleRun: true
  });

};

tried typescript 1.7.5 - no go. so it's not because of typescript.

Closing as the referenced error seems to be solved and this is not an issue with Karma


Missing required request header. Must specify one of: origin,x-requested-with

how fix this error
Missing required request header. Must specify one of: origin,x-requested-with
very ty great work. cheers

This issue has been raised many times before. The error message clearly states the problem. If you don't know how to resolve it, search on this issue tracker for that message.


feat: add folding builder

Add folding builder for:

Enum
Senum
Struct
Union
Exception
Service
XsdAttrs
ConstList
ConstMap
BlockComment

@arhont375
Please check this PR when you are free. 👍
No contribution process found in repo. If there is anything else that needs to be done, please let me know.

According to the comments, I has changed the code😁.
By the way, what do you think about adding a formatter like https://github.com/thrift-labs/thrift-fmt?

By the way, what do you think about adding a formatter like https://github.com/thrift-labs/thrift-fmt?

I don't mind having PR for this :slightly_smiling_face:
Seems there is support for defining external formatters by plugins: https://plugins.jetbrains.com/docs/intellij/code-formatting.html#external-code-formatter


Make link button variants match other buttons.

Preview on the site:

Looks great, thanks @LegNeato!


NO-ISSUE: Add JIRA bug trend generator

Which issue(s) this PR addresses:

Closes #

Doesn't Jira have built-in tools for producing these sorts of graphs?

Doesn't Jira have built-in tools for producing these sorts of graphs?

Yes, but we have an issue with that. JIRA produces these charts using the resolution field, which in our case does not transition to Done until errata takes over and includes the bug in an advisory. In other words, charts lag until automation kicks in.
This happens quite late, so JIRA charts don't show the current situation for the team. What this tool does instead is take the transition of the status to verified as another measure for classifying the issue as resolved. Once an issue is in that status, the team does not need any further involvement.

Doesn't Jira have built-in tools for producing these sorts of graphs?

Yes, but we have an issue with that. JIRA produces these charts using the resolution field, which in our case does not transition to Done until errata takes over and includes the bug in an advisory. In other words, charts lag until automation kicks in. This happens quite late, so JIRA charts don't show the current situation for the team. What this tool does instead is take the transition of the status to verified as another measure for classifying the issue as resolved. Once an issue is in that status, the team does not need any further involvement.

We can edit those filters in Jira.

Close for now. If we need something not supported in JIRA we can bring it up again.


Migrate documentation tests to new design

Codecov Report
Base: 97.08% // Head: 97.08% // No change to project coverage :thumbsup:

Coverage data is based on head (fbff10c) compared to base (fefa9f6).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #715   +/-   ##
=======================================
  Coverage   97.08%   97.08%
=======================================
  Files          24       24
  Lines        3057     3057
=======================================
  Hits         2968     2968
  Misses         89       89

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


[Renderers/NanoVG] Add GLFW3 + NanoVG example and renderer

Just cloned this and had a look, it's looking fantastic already! I didn't know about nanoVG, love the super simple API!


WebGPU: manage context loss and restoration (part 2)

Follow up to #14655

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/14674/merge
Test environment:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14674/merge/index.html
To test a playground add it to the URL, for example:
https://babylonsnapshots.z22.web.core.windows.net/refs/pull/14674/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/14674/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/14674/merge
https://gui.babylonjs.com/?snapshot=refs/pull/14674/merge
https://nme.babylonjs.com/?snapshot=refs/pull/14674/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/14674/merge#BCU1XR#0


Is it compatible with KubeJS

https://user-images.githubusercontent.com/50533513/183263155-3893400a-15f7-4db1-a3b3-8e5d0b8cc3d9.mp4

https://user-images.githubusercontent.com/50533513/183263155-3893400a-15f7-4db1-a3b3-8e5d0b8cc3d9.mp4

I tried, but need to know under the hood

There is nothing to know, look at the mixins. It works if KubeJS uses vanilla tag code its fine.


Fix rubocop issues

Trying to make the CI happy

Coverage increased (+0.02%) to 95.865% when pulling e75f1160dcbf3dc5db607889531a99ab5241f309 on anakinj:minor_rubocop_fixes into 53b250299855dd8be5db4c14b31a9c5d663b42ef on ruby-grape:master.

Coverage increased (+0.02%) to 95.865% when pulling e75f1160dcbf3dc5db607889531a99ab5241f309 on anakinj:minor_rubocop_fixes into 53b250299855dd8be5db4c14b31a9c5d663b42ef on ruby-grape:master.

thanks @anakinj


Is this project still active?

Seems like a while since the last release

Hi Nathan! Wisp is not under active development.

If WISP is not active, do you have any suggested alternative?  I think it's awesome to have a lightweight option like this right in the console rather than going full on with an environment like zeppelin.


merge from template-arlac77-github

.github/workflows/ci.yml

chore(deps): add 22.6.0 remove 22.5.1 (jobs.test-node.strategy.matrix.node-version)
chore: add 22.6.0 (jobs.release.steps.with.node-version)
chore: (jobs.release.steps)

.github/workflows/codeql_analysis.yml

chore: add 22.6.0 (jobs.analyze.steps.with.node-version)

.github/workflows/update_package_lock.yml

chore(deps): add 22.6.0 remove 22.5.1 (jobs.update_package_lock.strategy.matrix.node-version)

.github/workflows/update_readme_api.yml

chore: add 22.6.0 (jobs.update_readme_api.steps.with.node-version)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>0
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 95.161%

Totals

Change from base Build<PHONE_NUMBER>6:
0.0%

Covered Lines:
54

Relevant Lines:
56

💛  - Coveralls


Crashes with selenium-4.0.0

TypeError: __init__() got an unexpected keyword argument 'firefox_options'
in
File ".../scrapy_selenium/middlewares.py", line 51, in init.
I looked at the code in "selenium/webdriver/firefox/webdriver.py". There is no more 'firefox_options', but there is 'options' (if i get it right).

This Issue still appeared for me using Selenium 4.43 and scrapy_selenium 0.0.7.

And the following settings:
# # Scrapy Selenium
DOWNLOADER_MIDDLEWARES = {"scrapy_selenium.SeleniumMiddleware": 800}

SELENIUM_DRIVER_NAME = "firefox"
SELENIUM_DRIVER_EXECUTABLE_PATH = which("geckodriver")
SELENIUM_DRIVER_ARGUMENTS = [
    "-headless",
    # "--no-sandbox",
    # "--disable-dev-shm-usage",
]

Error is the same.


Workflow dirt check Supplement

Add: Ignore Dirty operations caused by order position changes due to click actions.
Add: Ignore Dirty operations caused by position corrections due to click actions.

could you add some comments to explain it? thank you!

could you add some comments to explain it? thank you!

delete obj["order"]; the purpose of this is to ignore the change in order. order changes because clicking on it changes the value, which I missed last time. Extract the pos and compare it separately, ignoring the deviation. pos is compared with deviation because I found that when the node is dragged, the pos exists with a precision of less than 1px, but when the click occurs, LiteGraph corrects it 120.829898>121, so the 5px displacement is ignored here.
All that is intended is to address the fact that when the workflow is open, the DIRT behavior occurs when clicked but not moved during the normal viewing behavior. This behavior triggers a subsequent save reminder action, which bothers me if I switch workflows frequently

ok～就是不知道这个对performance会不会有有影响？感觉多了很多check。我先merge了，后续麻烦你观察一下，有没有掉帧 帧率下降的问题，尤其是nodes比较多的workflow～
感谢contribute！


Uploading SRPM file to Copr times out

This is the issue we often face on Tuesdays.
https://sentry.io/organizations/red-hat-it/issues/3230234228/?project=1767823&query=is%3Aunresolved
The problem is the SRPM upload process gets stuck, in Copr's httpd eating all CPU while also blocking our long-running workers.
Copr issue: https://pagure.io/copr/copr/issue/2232

Update from Pavel: Copr may already have a solution in place in the main branch. We just need to wait 1-2 weeks to get it rolled out to production.

This Tuesday it did not happen - our workers were not stuck and we did not need to  recreate them. That's good!

2nd Tue in a row this is no longer happening, closing
\o/


Should I prefer this extension over direct using Codeception?

Or is this outdated/no more maintained?

I guess it is outdated as of the refactoring in advanced app that will come with 2.0.10 release. Am I correct, @samdark @DavertMik?

Yes.

We need to deprecate it after 2.0.10 release.


fix: NPE when no headers in the request

Issue
https://gravitee.atlassian.net/browse/APIM-6659
Description
when setting JWKS_URL in the JWT policy otel throws NPE because no headers are set link
Additional context

Gravitee.io Automatic Deployment
🚀 A prerelease version of this package has been published on Gravitee's private artifactory, you can:

use it directly by updating your project with version: 1.0.1-APIM-6443-fix-npe-SNAPSHOT
download it from Artifactory here

:tada: This PR is included in version 1.0.1 :tada:
The release is available on:

1.0.1
GitHub release

Your semantic-release bot :package::rocket:


Background location doesn't work in Android >= 10 (API level 29)

Describe the bug
Background location updates are blocked on Android >=10 (API level 29) due to missing permissions.
Expected behavior
The plugin should include the permissions necessary to enable background location tracking on Android >=10 (API level 29).
According to the docs, the plugin must include the ACCESS_BACKGROUND_LOCATION permission.

I'm not sure there's an actual issue here. My users have android 10 and 11 and are using this plugging successfully.
Assuming you use foreground mode.
If be happy to help if something is not working for you...

Hmmm... This is a bit confusing!
I've read through the comments on that issue you linked in the PR, and there's really quite a few people seeing issues with this.
I experienced it with one of my users who upgraded to a new phone, which I assume is running Android 10 or 11. The option to allow the app to track location in the background just isn't there any more - the permissions in the Settings do not list "Always" as an option.
Now, if I understand what you're saying correctly: this doesn't matter, as the background/foreground service still runs and reports location data as it's really still in the foreground. Is that right?

Yes.
Foreground service = a service that run, has a notification icon but still works when the screen is locked, the app is minimized or the app is in the front.
Background service = the same as above without letting the user know - i.e. without the notification icon.
Background service requires the permission you added but also requires a store approval by google.
This is what the approval dialog with the "always" option is there for - allow the user know the app can collect location data all the time, not just when the app is "running".
Since I want the user to know the app is running, foreground is the right approach I believe for my case, I guess it's also the case in most apps.
Supporting both modes (foreground and background) is possible but I think it's not easy to implement as you need to do some work in the post install script in the Cordova side (or at least this is how it was done in the plugin that you can pay for - i.e. transistorsoft).
I think we should add support only for foreground and allow the community to support this if someone needs it by submitting a pull request later on.

I've been doing some testing with my app and the plugin on Android, and it's all over the place. I'm still looking at it, and have still to fully understand it, but I did find this in the Android docs here:

Caution: If your app starts a foreground service while running in the background on a device that runs Android 11 (API level 30) or higher, your app cannot access location information unless the user has granted the ACCESS_BACKGROUND_LOCATION permission to your app. For more information, view the guidance about the while-in-use restrictions that are associated with foreground services.

From what I can understand, unless startForeground is true, the plugin does indeed start a foreground service when the app is in the background. Am I correct in thinking that?

If I understood your question then yes. You have to set stratForground to true so that the app will start a service in foreground mode to be able to collect location while the app in not in the front. When clicking a button to start this service you make sure that the service is created when the app is in the foreground and avoid the above pitfall.

Hello all,
I have an app with this installed plugin (from mauron85 repo) and I have following configuration:
const config: BackgroundGeolocationConfig = {
desiredAccuracy: 20,
stationaryRadius: 10,
distanceFilter: 20,
startForeground: true,
interval: 5000,
fastestInterval: 2000,
activitiesInterval: 5000,
// startForeground: true,
notificationsEnabled: true,
notificationTitle: "Tracciamento posizione",
notificationText: "ATTIVA",
debug: true,
url: 'http://localhost:3000/api/v1/trips/test',
httpHeaders: {
// 'X-FOO': 'bar'
},
// customize post properties
postTemplate: {
latitude: '@latitude',
longitude: '@longitude'
},
stopOnTerminate: false // enable this to clear background location settings when the app terminates
};
this.backgroundGeolocation.configure(config).then(() => {
  this.backgroundGeolocation
    .on(BackgroundGeolocationEvents.background)
    .subscribe((data: BackgroundGeolocationResponse) => {

      this.bgWork(data);
    });

  this.backgroundGeolocation
    .on(BackgroundGeolocationEvents.foreground)
    .subscribe((data: BackgroundGeolocationResponse) => {

      this.bgWork(data);
    });

  this.backgroundGeolocation
    .on(BackgroundGeolocationEvents.location)
    .subscribe((data: BackgroundGeolocationResponse) => {

      this.bgWork(data);

    });

});

bgWork function is where I send data to server.
The app must send location data to a server backend even if is in background but it seems doesn't work for me. I see notification for foreground service but how can I send data when app is in background?
Can you help me?

This won't work in general as explained in this thread.
You need to use the plugin's http native calls to send data, this is the only thing that will work in the background as you want.
The other option, which is what I'm doing is waiting for the app to get to the front and send all that data that was missed when the app was in the background.
This is a Cordova limitation as I have explained in this thread.

This won't work in general as explained in this thread.
You need to use the plugin's http native calls to send data, this is the only thing that will work in the background as you want.
The other option, which is what I'm doing is waiting for the app to get to the front and send all that data that was missed when the app was in the background.
This is a Cordova limitation as I have explained in this thread.

Is the following configuration correct to send data through plugin's http native calls?
const config: BackgroundGeolocationConfig = {
desiredAccuracy: 20,
stationaryRadius: 10,
distanceFilter: 20,
startForeground: true,
interval: 5000,
fastestInterval: 2000,
activitiesInterval: 5000,
// startForeground: true,
notificationsEnabled: true,
notificationTitle: "Tracciamento posizione",
notificationText: "ATTIVA",
debug: true,
url: 'http://<IP_ADDRESS>:3000/api/v1/trips/test',
httpHeaders: {
// 'X-FOO': 'bar'
},
// customize post properties
postTemplate: {
latitude: '@latitude',
longitude: '@longitude'
},
stopOnTerminate: false // enable this to clear background location settings when the app terminates
};
Do I have to add something else or is this correct?

@HarelM I have tried but when app is active it calls the url http://<IP_ADDRESS>:3000/api/v1/trips/test but when in background it does nothing. If BACKGROUND_GEOLOCATION permission isn't added how can the app locate you position and so send it to backend?

Is your plugin defined as foregroundService?

@HarelM another question: I'm using original plugin from mauron85/cordova-plugin-background-geolocation. Should I use this HaylLtd/cordova-background-geolocation-plugin and, if so, how can I point to this?

Is your plugin defined as foregroundService?

How can I check this?

On the configuring of the plugin you can specify to use foreground service (configure method).
In order to migrate to this plugin you simply need to uninstall the existing one and install this one using cordova (see our readme).
You need this plugin I order to work with Android 10, this might explain the problem you face...

@HarelM I have installed your plugin and it seems to work :D
I just noticed that geolocation icon, after some minutes of inactivity, will turn off in foreground service. Is it normal?

You need to make sure the app doesn't get killed by the OS.
The best way to do it is in the app configuring.
I use a popup in my app to tell users they need to do it when they start recording a route.
As far as I know this can't be done programmatically...

@HarelM Sorry for the delay! Yep, I'll close this as won't fix. I'll endeavour to update the docs ASAP to make it absolutely clear why we don't need this permission, and make it clearer how to post updates in the background on Android.

Is your plugin defined as foregroundService?

still not sure where that goes!

https://haylltd.github.io/cordova-background-geolocation-plugin/api.html
Look for startForeground

startForeground

My app seems to be working fine in the background without the startForeground though!!
am I missing here?

It will probably stop after a while if you won't assign it to start as a foreground service...
Please try and read more of the documentation...

This won't work in general as explained in this thread. You need to use the plugin's http native calls to send data, this is the only thing that will work in the background as you want. The other option, which is what I'm doing is waiting for the app to get to the front and send all that data that was missed when the app was in the background. This is a Cordova limitation as I have explained in this thread.

Hi @HarelM ,
I'm trying something similar and the app works perfectly fine when in foreground and when device is unlocked. However, I see that I lose the data when the app moves to background / device is locked although I have used the foreground mode. Could you please post a snippet of your code sample of sending all the data that was missed when the app was in the background for reference.

The following is the code I use in my app:
https://github.com/IsraelHikingMap/Site/blob/main/IsraelHiking.Web/src/application/services/geo-location.service.ts


Grammar and redundancy cleanup

Various grammar and typo fixes. Also removed the bit about arrays from the context that had mentioned both arrays and IEnumerable, since all arrays already implement IEnumerable.

Thanks for these!


navX-Micro Android FTC Library - I2C Read Timeouts do not cause IsConnected() == FALSE

After the AHRS class successfully communicates w/the navX-Micro, it sets connected = true.  And it sets it false if it ever gets a response from the CDIM that has invalid data (this behavior occurs if navX-Micro gets reset or power-cycled).  However, once connected, if there's a I2C read timeout (which occurs in case of the conflict you've found), the connected flag is not being set false.  So that's an outright bug that needs fixing.  It should be set to false, which will trigger the navx_ftc IO thread to re-initialize communication with the navX-Micro.

Resolved w/commit 09abe90221cb9d0ae104776af037d0b8a7f2d72 (2/10/2017).


Apply formatting to just children?

If I change the prefix in the nestable.php file it applies it to all options in the list.  Is it possible to have it only apply the prefix to just children?
'dropdown' => [
    'prefix' => ' - ',
    'label' => 'name',
    'value' => 'id'
]

Hi @gracedigital
Not possible. Applies to all options.


New package: zarunbal.LogExpert version 1.6.13

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[x] Is there a linked Issue?

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

#172587

Automatic Validation ended with:

Executable C:\Users\validator\AppData\Local\Microsoft\WinGet\Links\logexpert.exe returned exit code: -532462766

Automated error analysis suggests -532462766 may mean EXCEPTION_COMPLUS (Unhandled Exception)
(Automated response - build 895.)

Edit: Sorry for the "noisy" approval process. Feel free to suggest improvements.


_checkValue method on rule.js assumes value is required.

We are trying to validate the maxLength on a text field that is optional. Sometimes it can be null or empty. However, we get an error message thrown from the this._checkValue that states Validator.value not set.
This messes with our unit tests because an error is thrown.
Rule.prototype._checkValue = function() {   if (this._value === undefined) {     throw new Error('Validator.value not set'); // this is the message   }   return this._value; };
We would prefer if the validation didn't make the assumption that a field is required. So, the following rule for maxLength would make sense:
Rule.prototype.maxLength = function (length, message) {   var value = this._checkValue(); // change this to this._value - especially since the next line is checking for null or undefined or empty any way.   if (!utils.isEmpty(value)) {     var string = String(value);     if (string.length > length) {       this._messages.push(message || utils.format(this.templates.maxLength, length));     }   }   return this; };

The incentive of the _checkValue method is to ensure that Validator.value() method is always called. If _checkValue is removed and you forgot to call Validator.value() in your code, all optional rules will be skipped, and it's hard to know what went wrong.
You said that the value can be null or empty, but this is totally fine, as _checkValue is only checking for undefined. Is it possible that your test code failed to call Validator.value() in the first place?

Thanks for responding. I ended up converting to a customer validator instead.


Some basicaly styling tweaks

Basicaly do styling fixes. Also open inkscape and allow set again new inkscape

A few things that I have noticed:

The animations don't work for me, not sure why
There is some repeated functionality that I already did on dev branch, but haven't integrated in master, like change inkscape path
I have modified probably all 17 files in my dev, so is going to mean merge conflicts evereywhere

My bad for not merging master with dev before, but we could communicate better next time so we coordinate efforts better.
I don't think it is going to be possible to merge this PR, but I like many of the style tweaks, and I'm going to try to pick them and integrate them. Thanks!


Add Custom foreground and background colors

This PR addresses #1 .
After working on this a bit I figured it would just be best to customize the foreground and background colors.
The only outstanding item is to hide the Custom color fields unless the user chooses "Custom" in the dropdown.
I will try to work on this and update this PR to not be draft status.
Eager for any feedback or suggestions.
Thanks,

Vince

This looks pretty sweet! I came looking through the tracker exactly for this feature. I love the tool but not so much the red color >_<

Closing to clean up my open PRs since it doesn't seem there is any interest.


Failed to update git submodule of dependency

Problem
Cargo can't clone/update a git submodule of dependency, for example redbpf crate, which contains submodule libbpf.
Steps

cargo new cargo_issue_git_submodule
cd cargo_issue_git_submodule
echo 'redbpf = { git = "https://github.com/foniod/redbpf" }' >> Cargo.toml
cargo check

And we will get an error:
error: failed to get `redbpf` as a dependency of package `cargo_issue_git_submodule v0.1.0 (/home/user/cargo_issue_git_submodule)`

Caused by:
  failed to load source for dependency `redbpf`

Caused by:
  Unable to update https://github.com/foniod/redbpf

Caused by:
  failed to update submodule `bpf-sys/libbpf`

Caused by:
  object not found - no match for id (5a10cd2060c19959e2c55ee33421baa358c09c0b); class=Odb (9); code=NotFound (-3)

Possible Solution(s)
Update submodule manually in ~/.cargo/git/checkouts/redbpf-HASH/b81f069/bpf-sys/libbpf.
Notes
cargo version: cargo 1.55.0
commit of cargo: 4c27c96645e235d81f6c8dfff03ff9ebaf0ef71d

It looks like the commit 5a10cd2060c19959e2c55ee33421baa358c09c0b does not exist on any branch or tag in the repository https://github.com/redsift/libbpf.git.  The way cargo fetches submodules needs to assume that it exists on some branch or tag.
Unfortunately I can't find any APIs in libgit2 that provide a way to fetch a specific commit, so I don't see a direct way this can be supported.  One option is to restructure the net.git-fetch-with-cli option so that it uses git submodule update --init instead of git fetch (or pass the direct revision to git fetch which is supported as of git 2.5).

This is something i'm currently running into that i'd really like to see resolved. At the current moment this is making it so that a submodule of one of my dependencies must be on the main/master branch, and that's not exactly doable


Analysis of effect of cookie banner design changes

What is the problem to solve?
We need to change the appearance of the cookie banner so that more users choose to close the cookie banner (which we are interpreting as consent to cookies) so that we can collect more data from consenting users.
What stage of research is it? (discovery/general usability testing/post release)
general usability testing
What are the objectives?
collect data for before and after design change to see if % of users who close the banner increases
What are the assumptions?
users' decisions are influenced by the placement, size, wording and colouring of banner.
Acceptance criteria
At least 2 week's worth of data both before and after design changes.

Cookie banner currently looks like this

:

GA event set up 15/11/21
Event category: CookieNotice
Event action: click close cookie notice button
Event label: url displayed when banner clicked

Tacey, I'm closing this one because we won't need the data as we're doing a full redesign anyway.


Add subi pseudo-instruction

I recently came across a flavour of RISC-V that had subi as a pseudo-instruction and it wasn't recognised by this plugin, so This PR adds it to the list of recognised instructions.

Thanks for this addition! Sorry for the delay in merging. In the future, I'll have to think a bit on whether there's a better way to handle non-standard pseudoinstructions (since some/many people may assume there is a subi and then be surprised that vim highlighted it but their assembler rejects it). But for now I think erring on the side of including more pseudo-instructions that exist out there may be useful for people.


react-transform-webpack-hmr is deprecated and new config

react-transform-webpack-hmr is deprecated to react-transform-hmr .
new .babelrc
{
  "stage": 0,
  "env": {
    "development": {
      "plugins": [
        "react-transform"
      ],
      "extra": {
        "react-transform": {
          "transforms": [{
            "transform": "react-transform-hmr",
            "imports": ["react"],
            "locals": ["module"]
          }, {
            "transform": "react-transform-catch-errors",
            "imports": ["react", "redbox-react"]
          }]
        },
      }
    }
  }
}

Could you make a PR with those changes?

will.. try (never did before :-) )... gimme some time as I am heading out.. thanks..

Closed by #12


Update abp-model-card.md

Updating to fields and presentation of fields for Model Card++ 3.0 Release.
Description

Closes
By Submitting this PR I confirm:

I am familiar with the Contributing Guidelines.
When the PR is ready for review, new or existing tests cover these changes.
When the PR is ready for review, the documentation is up to date with these changes.

Merging without CI to avoid hammering CI for documentation changes.

/merge


Force type to be object if any properties are defined

Force type to be object if any properties are defined
Closes #121

Perhaps a warning should also be printed? Personally I'd still prefer to have an explicit type: object in my specs, a warning would allow to easily find and fix these cases.


CLI: Reorganize bump/restore into three subcommands each

What problem does your feature solve?
Makes it clearer to the user what the options are when using the commands.
What would you like to see?
soroban contract restore/bump (data/contract/code)
Also have contract bumping also bump the code. This would prevent users from needing to do two actions when it's always the case that the contract's code should not expire before the contract.
What alternatives are there?
Keep using the two commands with less clear mutually exclusive flags.

Latest changes in main no longer have bump as a command, so this would apply to the restore command

The bump subcommand was renamed to extend, so I believe this issue still applies to both.


Fix how last tab is defined on Tabs component

The Tabs component was using the wrong prop to define which tab is the last.

https://github.com/VenusProtocol/venus-protocol-interface/pull/361/files#diff-c0e46dd2c5468e987e524ea4f4b0f206be2199aee093c913a895c6f18a7e33d5R57

Ok sounds good, I'll close it then


CommandBarFlyout static initialization creates winrt objects using COM API prohibited during DllMain()

This is an issue that was caught by AppVerifier.
When Microsoft.UI.Xaml.dll is loaded, during DllMain is instantiates winrt objects, which is invalid. This is due to a pair of static arrays defined on CommandBarFlyout that were adding in PR #5347.
The fix is to initialize these arrays to nullptr, and populate them on the first creation of a CommandBarFlyout in its ctor.

/azp run


Disable "missing destination name" error

Is there an option to disable the "missing destination name" error returned when columns exist in the table but not in the model?
This makes it somewhat frustrating during development if you switch branches (and are then forced to roll back migrations) or even worse in production if you keep temporary columns around which could then bring down your application.

Any thoughts on this?

Sorry, I missed this notification.
See  http://godoc.org/github.com/jmoiron/sqlx#DB.Unsafe

please, omit the fields that are not present in the given struct, this would be a huge bonus.


Verify Bailout bytecode register restore

Verify bytecode upward exposed used for bailouts is consistent with what we had before backward pass.
Encapsulate Block::byteCodeUpwardExposedUsed to ensure consistency with Block::trackingByteCodeUpwardExposedUsed.

This change is

I tried profiling box2d.js to see to cost of the additional checks
ch box2d.js -profile
### SCORE: 617
Profiler Report            :   Incl   (%)    Excl   (%)     Max    Mean Count
-------------------------------------------------------------------------------
All                          9572.8   100   278.7     2  9572.8  9572.8     1
 LibInit                       16.8     0    16.5     0    16.8    16.8     1
  RegexCompile                  0.3     0     0.3     0     0.3     0.3     1
 Parse                        101.3     1   101.3     1   101.3   101.3     1
 ByteCode                      97.5     1    97.5     1    97.5    97.5     1
 Run                         9078.6    94  7983.8    83  1946.4   131.6    69
  Parse                       157.9     1   157.9     1     5.3     0.5   339
  ByteCode                    240.7     2   240.7     2     4.1     0.7   339
  Delay                       696.2     7     0.7     0    31.0     1.2   597
   Speculation                  0.2     0     0.2     0     0.2     0.2     1
   GatherCodeGenData          695.2     7   695.2     7    31.0     1.2   596
-------------------------------------------------------------------------------
Profiler Report            :   Incl   (%)    Excl   (%)     Max    Mean Count
-------------------------------------------------------------------------------
All                          9606.2   100  9606.2   100  9606.2  9606.2     1
-------------------------------------------------------------------------------
Profiler Report            :   Incl   (%)    Excl   (%)     Max    Mean Count
-------------------------------------------------------------------------------
All                          9144.0   100  1460.4    15  9144.0  9144.0     1
 BackEnd                    15307.4   167  1707.6    18   459.0    46.8   327
  IRBuilder                   313.1     3   313.1     3     7.2     1.0   327
  Inline                      476.8     5   166.0     1    18.7     1.5   327
   IRBuilder                  310.8     3   310.8     3    17.2     0.2  1391
  FGBuild                     105.1     1    91.7     1     2.7     0.3   327
   FGPeeps                     13.4     0    13.4     0     0.4     0.0   327
  GlobOpt                    6383.5    69   160.3     1   286.1    19.5   327
   CaptureByteCodeRegUse      141.5     1   141.5     1     4.6     0.4   327
   Backward                   699.8     7   699.8     7    38.4     2.1   327
   Forward                   4168.7    45  4168.7    45   191.8    12.7   327
   DeadStore                 1213.3    13  1213.3    13    43.2     3.7   327
  Lowerer                    1742.4    19  1742.4    19    37.9     5.3   327
  EncodeConstants              28.5     0    28.5     0     0.8     0.1   326
  RegAlloc                   3146.5    34  2604.2    28    73.9     9.7   326
   Liveness                   542.3     5   542.3     5    16.8     1.7   326
  Peeps                       187.7     2   187.7     2     5.2     0.6   326
  Layout                       74.1     0    74.1     0     2.8     0.2   326
  FinalLower                   15.8     0    15.8     0     0.4     0.0   326
  PrologEpilog                 35.0     0    35.0     0     0.3     0.1   326
  InsertNOPs                   26.5     0    26.5     0     1.4     0.1   326
  Encoder                    1064.8    11   947.5    10    24.4     3.3   326
   Emitter                    117.3     1   117.3     1     2.1     0.4   326
-------------------------------------------------------------------------------

From what I can see it seems to be about 1% of Jit time where most of the cost is in the extra loop through the instrs. I think we could leave this on by default.

Turns out, the optimization of bytecode register tracking I added is too aggressive and we're loosing a lot of info causing way too many false positive.
I have to rework this change, so I will close it for now and make a new one once it's ready.
Thanks @Penguinwizzard for the comments


The image preview thumbnail is squashed

The image preview in the compose screen is squished. This is possibly because it uses fill rather than aspectFill, or something similar.

Fixed in 1.0 (build 73).


Removal of Default Resource Values in Helm Chart

Proposal
This feature is about removing the default resources values in the helm chart. The solution would just commenting the default values and allow certain users to implement them if need be.
Use-Case
Unfortunately there has been a long standing bug helm/helm#9027 that prevents default values used in dependencies to be removed (which is a common use case for argocd).
I understand that this is not the chart behalf, but an alternative is to at least remove the cpu limit since more often then not cpu limits are considered more detrimental than anything nowadays.
Anything else?
No response

Hi @JuanPabloSGU ,
I transfer this issue to chart repository because it's more appropriate here.
I get your point and it's true what you said about CPU limit, but if the CPU limit is your issue, why don't you just define the values with a huge limit? I mean, you could define the values like:
resources:
  operator:
    limits:
      cpu: 10
      memory: 1000Mi
    requests:
      cpu: 100m
      memory: 100Mi
  metricServer:
    limits:
      cpu: 10
      memory: 1000Mi
    requests:
      cpu: 100m
      memory: 100Mi

And this is practically removing the limit.
WDYT?

I agree, the majority of end-users are not using dependencies which means we'd put a lot of burden on them having to understand how to configure KEDA which decreases usability and increases support

Since these are default values that will be used by any users not defining their own, I believe it would make sense to have the best and most general values possible.
As such, I do think that removing CPU limit does make for a better default, whereas currently the chart is artificially limiting the bursting capabilities of the application  (not taking advantage of any CPU that might be available) and potentially introducing throttling for users that, as you said, might not know how to properly configure it.

Experienced users can overwrite those values as they are explained in the docs and not experienced users have a default behavior, e.g:  you can define other limits if you prefer other values, but I don't imagine an inexperienced (k8s) user managing more than 300-400 ScaledObjects, so 1 CPU as maximum is a good value.
As I said, that value is not hardcoded, it's just a default value. I understand that due to helm limitation, you cannot ignore them, but definitively you can override them, setting other values better for you, in this case, you can override limit.cpu with 1000 cpus, which is virtually imposible to reach.

Sure and that is totally fine.
I guess my point was mostly that the Kubernetes community in general seems to be moving to no CPU limit as the default, although there is some contention for very specific use cases. If you think the current values will serve the general users better, that is fine.

TBH, I totally understand you, and we (in my work) don't use limits in a lot of cases, but without knowing it, you could have bad neighbours in the cluster, each scenario is different, and we try to cover the safest cases (it's the same with users and privileges).
The feedback is more than welcome and it's sane having discussions about the things, so, thanks :)


Can't read shapefiles zipped up on mac.

Hello,
When trying to open the attached shapefile, or any that was zipped up on a Mac, I get an error:
Archive.zip
"Offset is outside the bounds of the DataView" (chrome)
It appears to be coming from code reading a dbf row header, but the error went away if i unzip/rezip on Windows, and has happened for multiple shape files.

weird, I'm on a mac too

Were you able to reproduce it? It originally came up with an end-user of our product having the issue, and I was able to reproduce with my personal mac. I took a perfectly good shape file, unzipped it and re-zipped it on the mac, and ran into the error.

probably won't get around to digging in until tommorow
On Wed, Mar 1, 2017 at 4:03 PM chriserickson<EMAIL_ADDRESS>wrote:

Were you able to reproduce it? It originally came up with an end-user of
our product having the issue, and I was able to reproduce with my personal
mac. I took a perfectly good shape file, unzipped it and re-zipped it on
the mac, and ran into the error.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/calvinmetcalf/shapefile-js/issues/73#issuecomment-283469128,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABE4n-tSKOXRMGFNcJjiaacneH5dONnEks5rhd0MgaJpZM4MP7Qf
.

how are you trying to open it, it works on http://leaflet.calvinmetcalf.com/#10/37.7061/-104.7670

I'm getting a lot of 401 errors for the mapbox api on that page, and the drag and drop is doing nothing....

Yeah switch the layer picker in the top right and then zoom into your layer
which is there
On Mon, Mar 6, 2017, 8:57 PM chriserickson<EMAIL_ADDRESS>wrote:

I'm getting a lot of 401 errors for the mapbox api on that page, and the
drag and drop is doing nothing....
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/calvinmetcalf/shapefile-js/issues/73#issuecomment-284495185,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABE4n2H0ljh7zpreXB8LdSQ7h_0YugIxks5rjFcOgaJpZM4MP7Qf
.

The problem went away when I updated to the newest version of shp.js...


Extensibility issues: Page 9233 G/L Balance by Dim. Matrix

We need new event to handle the behavior of the Drilldown method.
Something like:
    [IntegrationEvent(false, false)]     local procedure OnBeforeDrillDown(SetColFilter: Boolean; var GLAcc: Record "G/L Account"; AnalysisByDimParameters: Record "Analysis by Dim. Parameters"; var Handled: Boolean)
The DrillDown procedure changed as following:
    local procedure DrillDown(SetColFilter: Boolean)
    var
        GLEntry: Record "G/L Entry";
        GLBudgetEntry: Record "G/L Budget Entry";
        Handled : Boolean; //Added Variable
    begin
        SetCommonFilters(GLAcc);
        SetDimFilters(GLAcc, 0);
        if SetColFilter then
            SetDimFilters(GLAcc, 1);

        //Start Added
        OnBeforeDrillDown(SetColFilter, GLAcc, AnalysisByDimParameters, Handled);
        if Handled then
            exit;
        //Stop Added

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


RFC: Where do the values of substitution variables come from?

Context
cargo-generate's main job is to copy file and replace some of their contents. It does so by looking for placeholders and replacing them with known values for known placeholder names.
Questions
Where do the values for these placeholders come from?
If they come from multiple sources, in which order are these accessed (with either first/last one wins)?
Possibles solutions
Suggestion:

(optional) global config files
env vars
CLI arguments (exact naming and syntax t.b.d.)
prompting the user

Last one wins.

I do like this proposal, but I do have second thoughts on the order.
if

CLI arguments (exact naming and syntax t.b.d.)
is the --template-values-file argument, then I agree (and we should add that argument to the favorite definition)

Otherwise I'd like to suggest this order:

CLI variable definitions (is -d already used, makes sense to use it as 'define' as used in other CLI's)
Env vars (prepended with CARGO_GENERATE_?)
Vars from the global config file
--template-values-file CLI argument
Prompting the user

I guess this issue can be closed with #389 ?


Turkish translations added

Hello,
First of all, thanks for making this package available for the community. This made implementation of AdminLTE with Laravel quite effortlessly.
You can find the Turkish translation of the resources at this pull request.
Thanks again,

@Ardakilic Thank you for your request!


Ensure translation of LevelTiers is working as expected

Because LevelTier text is being stored as English in the database, ensuring that the values get translated into non-English will require some extra effort.  This is true for any place that saved LevelTiers are displayed.

[ ] IPTT web and export
[ ] Program Page (Sanjuro)
[x] Indicator modal
[x] Logframe view and export
[x] Results framework builder (Sanjuro)

On the Program Page, I think "Outcome" in the Group indicators pulldown is untranslated:

2 places needed on Indicator modal

I think the program page Outcome non-translation will be fixed once we copy the template translations over to the djangojs.po file.  I think it's marked for translation.

@jennyhavah I'm wondering if you want the old style levels to be translated as well?  They would also need to be treated somewhat differently since they're database values too, just like the RF levels.

Tier name translations look good on logframe web view, and should now be working in XLS export as well.

@camgnostic @sanjuroj  Examples of untranslated areas, just added to the ticket under the IPTT header -- not intended to be a comprehensive list of everything in the IPTT.

@sanjuroj I see a change to the translation in the IPTT level menu, but it's not quite there. Here's what I see:

It appears to be a mishmash of languages, and grammatically incorrect. For example, in French I would expect something like "chaîne de résultats" if RF tier 2 is called "Résultat", "chaîne d’objectifs" if tier 2 is "Objectif", etc.

Got the iptt ones handled.  I used a previous translation for "and sub-levels".  I also used the existing (for the program page) translation for "by result chain".

@sanjuroj @camgnostic Almost there in the filter menu! Just need to translate tiers in the Level menu.

@jennyhavah I'm wondering if you want the old style levels to be translated as well? They would also need to be treated somewhat differently since they're database values too, just like the RF levels.

@sanjuroj Sorry, just now seeing this. If it will not add a significant amount of delay, it would be great to translate old levels. But I don't see it as a must have / release blocker.

What I'm seeing now:

Based on what's in the "Group by" menu, I think it should be "CHAÎNE RÉSULTAT" instead of RÉSULTAT CHAINS"

Looks good! This is what I see for the level menu:

Here's the Indicators menu:

@sanjuroj Regarding translation of old levels, if you decide to go ahead and make that change, please create a new ticket for it. (To be clear, I do not consider it high priority.)

I actually think we shouldn't translate the old level values.  They appear in a lot of places so it would take a relatively high level of effort, but we're phasing them out so it would be for something that is relatively short-lived.  I think we've given them a much better translated option in the RF levels.

I agree, @sanjuroj ! Thanks for checking in, though.


User should be able to add item with photo on goodmarket when on mobile

Add test case to check that it works on ios 13 + android

Checked on eWallet ver 0.10.3
Using devices:
iPhone XS // iOS 13.1
Xiaomi Redmi 7 // Android 9.0


Add Swift

I'd rather not commit 20 times to find what causes "Bad substitution", please fix it for me @asottile

Testing with swiftlint because that uses SourceKit which requires libsourcekitdInProc.so at /usr/lib/libsourcekitdInProc.so or LINUX_SOURCEKIT_LIB_PATH env var set to it's location. See: https://github.com/Cyberbeni/install-swift-tool/issues/68

I'd rather not commit 20 times to find what causes "Bad substitution", please fix it for me @asottile

in dockerfiles the shell is sh which doesn't understand ${OS/.//} -- probably a better way to do this would be to . /etc/lsb-release &&  and then use the variables from that (here's what they look like):
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=20.04
DISTRIB_CODENAME=focal
DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS"

There is still a spot where the dot is omitted from DISTRIB_RELEASE

Now the only question is how to run a tool that doesn't have a hooks.yaml? 🤔 The test should use https://github.com/realm/SwiftLint with swiftlint lint --strict file

seems like the pre-commit implementation of swift doesn't yet support additional_dependencies -- that would probably be the way
pre-commit currently tests the swift implementation by setting up a "remote repository" (on disk)

(If you decide to split it to a different image, here is a list of required packages that I found after I got the libedit.so.2 missing error, as some of them were already included here: https://github.com/apple/swift-docker/blob/c0daa8c7a96e310e20c4b02bbfaf600f2d92eda9/5.3/ubuntu/20.04/Dockerfile )
I have a similarly good GitHub Action but that only uses the default GH Action caching, so rebuilding the tool happens more often (If activity in the repository is infrequent then this is a bit annoying), so I'm not in a hurry to get this merged.

Swift on Linux is not ABI stable yet, so if the swift version changes on the runner image, the tool has to be rebuilt, IDK if that is properly handled.

Swift on Linux is not ABI stable yet, so if the swift version changes on the runner image, the tool has to be rebuilt, IDK if that is properly handled.

yes, pre-commit.ci assumes all languages are abi unstable and rebuilds on any image change

a lot of these are redundant and/or install the world -- please don't add these packages unless there's actual demonstrable things that they break (and please include a test for that)

just making sure you didn't miss this

Ah, I overlooked that. I copied them from the official swift focal docker tag but since swiftformat currently is the only supported tool, I guess I'll test them 1-by-1 if they are required for it.

The focal-slim docker tag doesn't specify libedit2 and libz3-dev but the test fails without them. The tests work correctly without libcurl4 and tzdata buit they are included in focal-slim, is it okay to keep those 2 even though they doesn't seem to be required? (libcurl is probably used for networking and swiftformat doesn't use networking but there are other tools, like https://github.com/mono0926/LicensePlist that could be nice to integrate into pre-commit.ci but use networking)

this looks good, but I'm going to hold off on merging this for a bit -- I need to rethink how language support works for pre-commit.ci so that this image doesn't grow indefinitely (while still making it accessible for outsiders to run the image like CI does).

this looks good, but I'm going to hold off on merging this for a bit -- I need to rethink how language support works for pre-commit.ci so that this image doesn't grow indefinitely (while still making it accessible for outsiders to run the image like CI does).

I've merged this via #69 -- it's not available yet (I need to adjust the backend to work with the new image format)


Support Stack Deletions

Good to have a feature which enables you to delete the stacks as well. The trigger can be a ENV variable

@mridhul please assign it to me, I would like to work on it as part of Hactoberfest

Done @codemii . Please let me know your approach before you start implementing


Debug log on terminal

Hi,
when using Halo with boto3, I have a strange behaviour, all the debug log from boto are displayed

MacOS/Python3.6
halo (0.0.5)
boto3 (1.4.4)
Thanks

Hi,
I have the same behaviour when using halo and openstacksdk on python 2.7.
Regards.

@ManrajGrover I can work on this one. I think the solution here is to just create a logger specific for halo rather than removing logging altogether as was done in #18

It looks like solved in #12. @ManrajGrover right?

@JungWinter Yes, I'm waiting for final changes before merging. :)


fix KeyError in delete_alias in the KmsBackend.

If there're several aliases in the backend, previously we will bump into an unexpected KeyError here.
I haven't created a unit test for this little change. If the devs are inclined to add one, I'd be happy to do it.

Coverage decreased (-0.3%) to 91.953% when pulling 823cc483684a36ce6195900ea40233ded2ff4d76 on xiaket:master into e227a30aa9269585ef854d0a9a27552014829266 on spulec:master.

Coverage increased (+0.0003%) to 92.231% when pulling 9a4bd506257bcbb35ba8075ffce9ebd4a44bf1b2 on xiaket:master into e227a30aa9269585ef854d0a9a27552014829266 on spulec:master.

Yeah a test would be nice if thats alright

Coverage decreased (-0.06%) to 92.173% when pulling 9388b3fb1efcb3808fad2021e0a27f438c994e69 on xiaket:master into e227a30aa9269585ef854d0a9a27552014829266 on spulec:master.

Nice :smile:


Detect/allow override for the drush aliases docroot

Currently hardcoded as /app/public

Related to #268 (but a different problem)

Improved in v2.7.0


Mesh optimization

There is a problem during decimation, if the mesh has vertices that are duplicated (same position). This is due to the nature of the simplification used (the point references is being moved, but when two points with the exact same properties are referenced in the indices, not all indices will move correctly).
The optimize function will optimize the indices of a mesh. It will not(!) remove unused vertices to avoid problems with submeshes (since they are referencing the vertices start and count), it will only reorder the indices correctly.

Just a note - I think creating an optimized exporter (from obj, blender, 3ds etc') will render this useless. It is not needed if the mesh was exported correctly.


icd/CMakeLists.txt should not use copy command when targeting WIN32

In icd/CMakeLists.txt, there are statements like:
if (WIN32)
  add_custom_target(json COMMAND copy src_json dst_json)
endif()

In CMake code, the CMAKE_SYSTEM_XXX variables always describe the target platform. The same is true for the short WIN32, UNIX, APPLE variables. (https://cmake.org/cmake/help/book/mastering-cmake/chapter/Cross Compiling With CMake.html)
WIN32 do not mean host platform is Windows rather than means target platform is Windows.
And copy command is a windows command. It should only be used on Windows platform. It should be used like:
if (CMAKE_HOST_WIN32)
  add_custom_target(json COMMAND copy src_json dst_json)
endif()

I think origin statements could be changed to:
if (WIN32)
  configure_file(src_json dst_json COPYONLY)
  add_custom_target(json DEPENDS dst_json)
endif()

I'm updating the JSON logic to be similar to the logic in the validation layers since it's essentially the same thing.


Add position to AdvancedWindow

Required to transform coordinates from a touch device to the screen.

Perhaps this should be a new trait DesktopWindow.

Could be added to AdvancedWindow and return Result<(), String> if the window can not be moved.
There can be many reasons why a window can not be moved, and we can not guarantee distinction between the reasons:

window backend runs in fullscreen
window backend does not support positions
window is pinned to an environment where the size is decided by the user
window runs on a mobile device where the size can not change


stop / stop_regex - did they work?

When generation is terminated by a stop-word, can I check it in some logs or print it out easily?
In the below example I think generation was terminated by stop_regex, but how can I check it?:

More logging is a todo. But for your use case you can just use the gen argument save_stop_text="var_name" and then you can check what is inside lm["var_name"]