Latest Xtensa Rust (1.75) does not work under Ubuntu 20.04, GLIBC version error

Bug description
After using espup install under Ubuntu 20.04 (aarch64, NVidia Jetson AGX Xavier), running the cargo binary produces a linker error.
$ ~/.rustup/toolchains/esp/bin/cargo
/home/me/.rustup/toolchains/esp/bin/cargo: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /home/me/.rustup/toolchains/esp/bin/cargo)
/home/me/.rustup/toolchains/esp/bin/cargo: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /home/me/.rustup/toolchains/esp/bin/cargo)
/home/me/.rustup/toolchains/esp/bin/cargo: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /home/me/.rustup/toolchains/esp/bin/cargo)

Would you like to work on a fix? [y/n]

n
To Reproduce
Steps to reproduce the behavior:

run espup install on Ubuntu 20.04 aarch64
try to run cargo

Expected behavior
Cargo works and compiles my project
Environment
$ cat /etc/issue
Ubuntu 20.04.6 LTS \n \l

$ uname -a
Linux aql57 5.10.104-tegra esp-rs/espup#1 SMP PREEMPT Wed Aug 10 20:17:07 PDT 2022 aarch64 aarch64 aarch64 GNU/Linux

$ espup --version
espup 0.10.0

Additional context
This looks similar to this issue in espflash from last year.
I tried to provide the cargo version as well, but /home/me/.rustup/toolchains/esp/bin/cargo --version does of course fail with the same linker error.

Hi, thank you for the quick response! As a quick fix, is it possible to intentionally install an older rust release that's compatible with 20.04 using espup?

Hi, thank you for the quick response! As a quick fix, is it possible to intentionally install an older rust release that's compatible with 20.04 using espup?

Yes, using espup install -v <IP_ADDRESS> should work

Marked as Third Party limitation, since Ubuntu 20 does not support build of latest toolchains.
@SergioGasquez : Would it be possible to add warning to espup, that distribution is not supported?
If somebody finds a solution how to handle such build, we might consider adding it. Otherwise, please upgrade to newer Ubuntu or use container.

If you do espup install -v <IP_ADDRESS> then the default esp-idf template doesn't compile.... Is there no way around this?

If you do espup install -v <IP_ADDRESS> then the default esp-idf template doesn't compile.... Is there no way around this?

how is this related to this issue? Please don't hijack issues if you have a new issue and if so please give a full error report!

If you do espup install -v <IP_ADDRESS> then the default esp-idf template doesn't compile.... Is there no way around this?

how is this related to this issue? Please don't hijack issues if you have a new issue and if so please give a full error report!

Sorry for breaking some fancy hijacking etiquette here... I was just trying to help beginners like me who has pent 3 days now trying to get this to work with some additional info.

I assume MSRV of the esp-idf-template is greater than <IP_ADDRESS>, which is the latest version using the GLIBC that Ubuntu 20.04 support.
Is there any reason not to update to a recent Ubuntu version?

I assume MSRV of the esp-idf-template is greater than <IP_ADDRESS>, which is the latest version using the GLIBC that Ubuntu 20.04 support.
Is there any reason not to update to a recent Ubuntu version?

Thanks for answering and I apologize in advance if I provide non-relevant info now and ask stupid questions but I'm a bit new to this.
I installed WSL Ubuntu in Windows today and it says it is version 20.04 "Focal" which I now understand is an old version. I will try to upgrade it and see what happens.

You don't need to apologize, or be defensive about our comments. Both, @Vollbrecht and I were trying to help you, also for questions I would recommend using our matrix channel https://matrix.to/#/#esp-rs:matrix.org

i am not using windows that much these days though you can get ubuntu 22 directly for wsl i think if you follow for exmaple this

You don't need to apologize, or be defensive about our comments. Both, @Vollbrecht and I were trying to help you, also for questions I would recommend using our matrix channel https://matrix.to/#/#esp-rs:matrix.org

I appreciate that, I really do :)
I did what you recommended and installed WSL Ubuntu 24.04 and it sort of worked. Still have some issues that I don't understand but I will reach out in the matrix.org chat if I need.


[jaeger-v2] Change remote storage API to be the same as query service API

Requirement
As Jaeger-V2 is currently being developed, it would be nicer if the remote storage API had the same API with query service so it could be reused between components.
Problem
As discussed in https://github.com/jaegertracing/jaeger/pull/5322#discussion_r1553914088, by changing the remote storage API to be the same as the query storage API, we can reuse this API for Jaeger-V2 e2e testing purposes.
Proposal
No response
Open questions

Remote storage APIs have read & write span, read & write archive span, get capabilities, and read dependencies while query storage APIs only have read span data. So, the scope of this feature is to change the read span, archive span, and dependencies. Is this correct?

I have looked into query service API and there are v2 and v3, in which v3 uses OTLP model while v2 uses Jaeger model. V3 handles most v2's API except ArchiveTrace and GetDependencies. Do we need to use partially v3 APIs and v2 for the rest or fully v2 APIs?

I think we need to do a bit of analysis before we decide, including the v2/v3 question. The plan for Storage V2 API was to base it on OTLP data model, not the old Jaeger model as query/api_v2 today. Maybe we should start a doc where we can do side by side comparison of both existing v2 and v3 (in terms of capabilities) and the existing storage API, so see if we can arrive to a single unified API. There's also another consideration for the write API to be compatible with OTLP receivers. If we can satisfy all these requirements it would be awesome.

I have compared and analyzed the existing storage API and query service v2 and v3 API here https://docs.google.com/document/d/1IvUcDsdRxMPK-xTUE32w3NSAGTkUcmnDQttN6ijUnWs/edit?usp=sharing.
Please have a look 🙇

Created a copy of the doc in case it gets lost: https://docs.google.com/document/d/1sutIXjVJ_zP13cT9uLWfRH8KCOitPOXEHtgYPUUW06g/edit?tab=t.0#


Modify request_rate_limiter.lua

Update last refresh timestamp only if one request be allowed.
For example. If i set replenishRate=1 and set capacity=1, and i send requests in every 600ms.
Unfortunately, i just got success response in the 1st request, and all failed in others.
If set refresh timestamp with the last allowed request time, i can get one success, one failed, one success, one failed ... ... as i expected.

@Yoruichi Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@Yoruichi Thank you for signing the Contributor License Agreement!

Codecov Report

Merging #591 into master will decrease coverage by 8.53%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #591      +/-   ##
============================================
- Coverage     70.97%   62.43%   -8.54%
+ Complexity      936       75     -861
============================================
  Files           129        8     -121
  Lines          3676      410    -3266
  Branches        262       34     -228
============================================
- Hits           2609      256    -2353
+ Misses          929      130     -799
+ Partials        138       24     -114

Impacted Files
Coverage Δ
Complexity Δ

...handler/predicate/MethodRoutePredicateFactory.java

.../gateway/support/AbstractStatefulConfigurable.java

...loud/gateway/filter/headers/HttpHeadersFilter.java

...mework/cloud/gateway/config/GatewayProperties.java

.../gateway/handler/RoutePredicateHandlerMapping.java

...teway/config/PropertiesRouteDefinitionLocator.java

...ter/factory/SecureHeadersGatewayFilterFactory.java

.../handler/predicate/AfterRoutePredicateFactory.java

...ork/cloud/gateway/config/HttpClientProperties.java

...k/cloud/gateway/support/DefaultClientResponse.java

... and 111 more

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 ebba02e...1cbe4f6. Read the comment docs.


Added a bot for contributers

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Checklist:

[x] This pull request follow our contribution guidelines
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation (postman and swagger)
[ ] I have written tests for the code
[ ] I have updated .env.example file for new .env variables

What is current behavior?

Closes #(issue_number)
What is new behavior?

Breaking Changes?

Additional information

@shivamvishwakarm please follow contribution guidelines and follow conventional commits for writing commit messages
and also update the pull request description to actually what you did instead of of just submitting our pre defined template
I have created pull request template so that you can take refrence from it

nice

Thank's for your support aayush. you instruct very nicely

@all-contributors please add @shivamvishwakarm for doc


Feature: cascading deletion of resources

This PR adds two flags to delete commands for Applications and Functions objects:

recursive (r):  Will retrieve all sub-objects and attempt to delete them from the bottom up before deleting the primary resource (user is prompted to continue after all of the associated resources are listed)
force (f): Will silence the prompt from a cascading delete and just deletes all resources without further user input (this only has an effect when used in combination with the cascading flag)

Example usage:
example cascading
command:
fn delete fn <app-name> <fn-name> -r

will result in this prompt:
You are about to delete the following resources:
   Functions:    1
   Triggers:     <number of associated triggers>
This operation cannot be undone
Do you wish to proceed? y/n:

if the user replies 'y' then:
Trigger  <trigger-name>  deleted
Function  <fn-name>  deleted

if the user replies 'n' then nothing is deleted:
Cancelling delete

example cascading & forced
command:
fn delete app -f -r <app-name>

results in:
Trigger  <trigger-name>  deleted
Function  <fn-name>  deleted
App <app-nam> deleted

Would prefer -r over -c as it’s consistent with  (e.g rm)

LGTM but could you write a couple of e2e tests (e.g. in cli_crud_test.go) ?  thanks

LGTM but could you write a couple of e2e tests (e.g. in cli_crud_test.go) ? thanks

Added this in now, though it would seem that the tests on master are broken already, but the test I have written passes. 👍


Add USAFOrionMod-TD-subedition from Kerbal Stuff

This pull request was automatically generated by Kerbal Stuff on behalf of TiktaalikDreaming, to add USAFOrionMod-TD-subedition to CKAN.
Please direct questions about this pull request to TiktaalikDreaming.

Depends on http://forum.kerbalspaceprogram.com/threads/28428-Orion-aka-Ol-Boom-boom which doesn't seem to have a binary for 0.90.

Extended my search and it seems the original mod has some semi-fixed .dlls spread through inofficial channels. I'm closing this since I see very little hope for this PR unless someone re-releases Orion and in that case a new PR is sure to be created.


Incorrect highlighting for C++ special identifiers

Describe the bug
C++ identifiers with special meaning (final, override, import and module). are incorrectly highlighted out-of-context. These keywords should be considered as regular identifiers when used out of their special meaning context (c.f. C++20 standard, section 5.10, paragraph 2).
To Reproduce

Run vim --clean
Edit a.cc
Type 'int final, override, import, module;'
Incorrect highlighting for these variables name

Expected behavior
Highlighting for these variables names should be the same as the one for int x;
Environment (please complete the following information):
Vim version 8.2.3323

That is a CPP syntax issue. So I'll leave that for https://github.com/vim-jp/vim-cpp

This is probably difficult to do properly as C++ syntax is complex and Vim does not use a C++ parser, but uses heuristics based on regexp for syntax highlighting.  We can maybe improve heuristics, but we can't expect to get syntax highlighting it 100% right with heuristics. In practice, it's already doing a fairly good job for C++. Calling variables override,final or module seems quite a rare and is asking for trouble. I understand that C++ allowed that for to avoid breaking existing software. Backward compatibility is important for C++. For Vim, the cost / benefit of fixing this ticket seems low IMO.
The only way to syntax highlight C++ correctly (and other languages) 100% correctly, is to have a real C++ parser using e.g. Tree-sitter.  Maybe something for Vim-10? :-)

yes, related: #8658
Note, Vim cannot do semantic highlighting (yet), just regex based highlighting.

This is probably difficult to do properly as C++ syntax is complex and
Vim does not use a C++ parser, but uses heuristics based on regexp for
syntax highlighting.  We can maybe improve heuristics, but we can't
expect to get syntax highlighting it 100% right with heuristics. In
practice, it's already doing a fairly good job for C++. Calling
variables override,final or module seems quite a rare and is
asking for trouble. I understand that C++ allowed that for to avoid
breaking existing software. Backward compatibility is important for
C++. For Vim, the cost / benefit of fixing this ticket seems low IMO.
The only way to syntax highlight C++ correctly (and other languages)
100% correctly, is to have a real C++ parser using e.g. Tree-sitter.
Maybe something for Vim-10? :-)

I know someone was working on Tree-sitter, and it was not easy.  Is it
working now?  Evaluating the advantages and disadvantages would be a
good idea.  I would expect it to behave very different from the
pattern-based syntax highlighting.  E.g., how well does it handle syntax
errors?  What happens while typing?  Is there a noticeable delay when
opening a large file?  Does it solve the slowness of long lines (e.g.
with XML)?
--
Hacker: Someone skilled in computer programming (good guy).
Cracker: A hacker that uses his skills to crack software (bad guy).
/// Bram Moolenaar -- @.*** -- http://www.Moolenaar.net   \
///                                                                      \
\\        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

apparently it works quite nicely for Neovim (for languages that have treesitter parsers).


Show complete path and line number?

Nice project, thanks, it's true that pytest default output makes it hard to find location of failing tests.
In the summary table, would it make sense to print the complete file path and the line number (separated with :) to benefit from terminals and IDE capabilities (ctrl-click to go to that file and line)? It would make it even easier to go to the test that failed IMO.

Ah, the path:lineno is displayed in the real-time error summary though, so feel free to dismiss my request 🙂

no, that would be a useful option.
Happy to accept a PR to add it via a flag. I wouldn't use it myself since that doesn't work with my setup, but I can completely see the case for it.

Note you can probably use a [link] to be able to open the file directly even if the full path isn't shown..


Security:  Modify Dockerfiles to create and run as a non-default User

As per the Security Architecture
In the Dockerfile, create a user and run as that non-default user:
...
RUN adduser \
  --disabled-password \
  --home /app \
  --gecos '' app \
  && chown -R app /app
USER app
...

Acceptance Criteria

[ ] Do this for CentOps
[ ] Do this for .NET DMR
[ ] Do this for MockBot
[ ] Do this for MockClassifier

Releasing the ticket in case anyone else gets to it before I do


treewide: Simplify negated uses of versionAtLeast, versionOlder

Description of changes
Simplify !lib.versionAtLeast v1 v2 to lib.versionOlder v1 v2, and !lib.versionOlder v1 v2 to lib.versionAtLeast v1 v2.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

In general this seems like a good change, improving readability and setting a precedent for future changes.


gen-convert-rev1.1

The renaming of various things looks good to me, and I like the code de-duplication with calculateDeltaBFromReserves, merging this in.


Getx wrongly detect "the improper use of a GetX"

I having this code:
// my view
Obx(() => MyCustomWidget(
                controller.listData,
              )),

// my CustomWidget
class MyCustomWidget extends StatelessWidget {
  MyCustomWidget(this.listData)

  final dynamic listData;

  @override
  Widget build(BuildContext context) {

    return ListView(
      scrollDirection: Axis.horizontal,
      physics: ClampingScrollPhysics(),
      children: listData.map<Widget>((e) => MyDisplayWidget(e)),
    );
  }
}

I got the bug
[Get] the improper use of a GetX has been detected.
You should only use GetX or Obx for the specific widget that will be updated.
If you are seeing this error, you probably did not insert any observable variables into GetX/Obx
or insert them outside the scope that GetX considers suitable for an update
(example: GetX => HeavyWidget => variableObservable).
If you need to update a parent widget and a child widget, wrap each one in an Obx/GetX.
However, without MyCustomWidget, it works fine.
// my view
Obx(() => ListView(
      scrollDirection: Axis.horizontal,
      physics: ClampingScrollPhysics(),
      children: controller.listData.map((e) => MyDisplayWidget(e)),
    )),

The MyCustomWidget is necessary because it help me save reuse this widget in different part of the app. I use the obs variable exactly the same way but one is allow and other is forbidden?
Ways I had try but still not working: use Getview insteald of StatelessWidget for MyCustomWidget; change dynamic listData to RxList listData;

Initially, this is not a bug, it is an alert that forces you to code in the least expensive and most performant way possible. If in the future you insert 300 built-in widgets into your class, you will rebuild 300 widgets instead of just 1.
You're not componentizing anything, ListView.builder does exactly what this code does, and it's a ready-made Flutter component, with the advantage of only rebuilding the visible part.
But if you want to continue this, you can "bypass" GetX by using:
controller.listData.toList()
This is not a recommendation, but if you want to do it, go ahead.

Add .toList() works. Closing the ticket
Thank you for the support!

@jonataslaw
I really like GetX syntax and all, but I do often have a hard time with RxLists in Obx. For instance, I'm currently working on an app which has a set of filters which pops up as a bottom sheet when the user clicks on a button:
// this is
void showFilter(BuildContext context) async {
    // below is just an extension method which calls showModalBottomSheet
    await context.showCustomModalBottomSheet(
      child: Obx(
        () => CustomSimulatorFilterSheet(
          // the 4 lists below are declared as final filters = <Filter>[].obs; in the controller
          brands: controller.brandsFilters,
          establishments: controller.establishmentsFilters,
          selectedBrandIds: controller.selectedBrandIds,
          selectedEstablishmentIds:
              controller.selectedEstablishmentIds,
          onToggleEstablishment: controller.onToggleEstablishment,
          onToggleBrand: controller.onToggleBrand,
          onClearSelectedBrands: controller.onClearSelectedBrands,
          onClearSelectedEstablishments:
              controller.onClearSelectedEstablishments,
          onApply: controller.onFiltersChanged,
        ),
      ),
    );
  }

This throws an "improper use" exception, but I don't want to be forced to use Obx inside my bottom sheet component, because this way it might be reusable in some other project which does not use GetX. In this case, I do think that Obx => Heavy bottom sheet => { FilterA, Filter B } would make more sense that Heavy bottom sheet => { Obx => FilterA, Obx => Filter B }.
Maybe you could add the "toList()" workaround information to the message in the exception, it'd be very helpful when the developer does not want to push the Obx widgets further down in the widget tree.


Add Conv2DBNActiv

Reopend https://github.com/chainer/chainercv/pull/379

@yuyu2172 Perhaps, it is better to set nobias=True by default because nobias=True is common when batchnorm is used.

I agree. That sounds better.


Uncaught TypeError: Cannot read property 'setActive' of undefined

[Enter steps to reproduce below:]

...
...

Atom Version: 0.186.0
System: linux 3.13.0-74-generic
Thrown From: php-debug package, v0.2.1
Stack Trace
Uncaught TypeError: Cannot read property 'setActive' of undefined
At /home/javier/.atom/packages/php-debug/lib/php-debug.coffee:257

TypeError: Cannot read property 'setActive' of undefined
  at Object.module.exports.PhpDebug.toggleDebugging (/home/javier/.atom/packages/php-debug/lib/php-debug.coffee:257:18)
  at atom-workspace.subscriptions.add.atom.commands.add.php-debug:toggleDebugging (/home/javier/.atom/packages/php-debug/lib/php-debug.coffee:102:93)
  at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/usr/share/atom/resources/app/src/command-registry.js:243:29)
  at /usr/share/atom/resources/app/src/command-registry.js:3:61
  at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/usr/share/atom/resources/app/node_modules/atom-keymap/lib/keymap-manager.js:558:16)
  at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/usr/share/atom/resources/app/node_modules/atom-keymap/lib/keymap-manager.js:396:22)
  at HTMLDocument.module.exports.WindowEventHandler.onKeydown (/usr/share/atom/resources/app/src/window-event-handler.js:182:20)

Commands
     -0:00.9 php-debug:toggleDebugging (atom-text-editor.editor.is-focused)

Config
{
  "core": {},
  "php-debug": {
    "ServerPort": 15000
  }
}

Installed Packages
# User
atom-alignment, v0.12.1
atom-chai-snippets, v0.3.0
coffee-navigator, v0.0.16
color-picker, v1.7.0
cucumber, v0.5.0
docblockr, v0.6.3
editorconfig, v1.2.0
highlight-line, v0.10.2
language-vue, v0.8.0
linter, v0.12.2
linter-coffeelint, v0.2.3
linter-cpplint, v1.0.0
linter-js-yaml, v1.0.0
linter-jshint, v0.1.4
minimap, v4.8.0
php-debug, v0.2.1

# Dev
No dev packages

Hopefully fixed in v0.2.2 - Released Today


"Organizations" settings page fixes and tweaks

Remove right transition on hover on settings cards.
Move disconnect button to extreme right using flex.
Text-overflow for server urls using ellipsis.

Partly fixes #456 .

Merged. Thanks, @abhigyank. I'm not closing the issue since we still need to work on the responsive part.


MODE CSI statistics produces spurious results

Describe the Problem
There is an issue with the way the MODE CSI statistics are being calculated (inconsistent with what is documented, and results are not consistent). This was discovered and reported in the METplus Github Discussion:

https://github.com/dtcenter/METplus/discussions/2496

This is calculated in the R script code.  A similar issue exists in METcalcpy:

https://github.com/dtcenter/METcalcpy/issues/360

Expected Behavior
Provide a clear and concise description of what you expected to happen here.
Environment
Describe your runtime environment:
1. Machine: (e.g. HPC name, Linux Workstation, Mac Laptop)
2. OS: (e.g. RedHat Linux, MacOS)
3. Software version number(s)
To Reproduce
Describe the steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
Post relevant sample data following these instructions:
https://dtcenter.org/community-code/model-evaluation-tools-met/met-help-desk#ftp
Relevant Deadlines
List relevant project deadlines here or state NONE.
Funding Source
Define the source of funding and account keys here or state NONE.
Define the Metadata
Assignee

[ ] Select engineer(s) or no engineer required
[ ] Select scientist(s) or no scientist required

Labels

[ ] Select component(s)
[ ] Select priority
[ ] Select requestor(s)

Projects and Milestone

[ ] Select Organization level Project for support of the current coordinated release
[ ] Select Repository level Project for development toward the next official release or add alert: NEED CYCLE ASSIGNMENT label
[ ] Select Milestone as the next bugfix version

Define Related Issue(s)
Consider the impact to the other METplus components.

[ ] METplus, MET, METdataio, METviewer, METexpress, METcalcpy, METplotpy

Bugfix Checklist
See the METplus Workflow for details.

[ ] Complete the issue definition above, including the Time Estimate and Funding Source.
[ ] Fork this repository or create a branch of main_<Version>.
Branch name: bugfix_<Issue Number>_main_<Version>_<Description>
[ ] Fix the bug and test your changes.
[ ] Add/update log messages for easier debugging.
[ ] Add/update unit tests.
[ ] Add/update documentation.
[ ] Push local changes to GitHub.
[ ] Submit a pull request to merge into main_<Version>.
Pull request: bugfix <Issue Number> main_<Version> <Description>
[ ] Define the pull request metadata, as permissions allow.
Select: Reviewer(s) and Development issues
Select: Organization level software support Project for the current coordinated release
Select: Milestone as the next bugfix version
[ ] Iterate until the reviewer(s) accept and merge your changes.
[ ] Delete your fork or branch.
[ ] Complete the steps above to fix the bug on the develop branch.
Branch name:  bugfix_<Issue Number>_develop_<Description>
Pull request: bugfix <Issue Number> develop <Description>
Select: Reviewer(s) and Development issues
Select: Repository level development cycle Project for the next official release
Select: Milestone as the next official version
[ ] Close this issue.

The fix apparently does not work. @CPKalb tested on 'dakota' and the issue persists.

Fix is working for @CPKalb , closing again.

The python version is also affected by the same issue and likely needs to be updated as well

There is already an issue for the Python version:
https://github.com/dtcenter/METcalcpy/issues/360
Minna Win
Pronouns: she/her
National Center for Atmospheric Research
DTC/Research Applications Lab
Phone:<PHONE_NUMBER>
My work hours may not be your work hours. Please do not feel obliged to
reply to this email outside of your normal working hours.
On Fri, Feb 16, 2024 at 11:29 AM Christina Kalb @.***>
wrote:

The python version is also affected by the same issue and likely needs to
be updated as well
—
Reply to this email directly, view it on GitHub
https://github.com/dtcenter/METviewer/issues/516#issuecomment-1949071243,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA4UJHUGFFAY7BCN4IFNEWDYT6QRFAVCNFSM6AAAAABDJFPB6WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNBZGA3TCMRUGM
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

Ah, great.  Let me know if you want me to test the python issue.  I have xmls saved that make it easy to test


Removed chart.height and chart.cols functions

Because there are always 12 months in a year, there isn't really a need for chart.cols(). In addition, chart.height() isn't really used. However, I believe chart.width() should stay because some users of the library may wish to make a version of the site with a bigger or smaller version of the squares, and in order to do so, chart.width would need to be supported. For our use case, keeping it at 200 is good, but for extensibility allowing it to be changed is even better.
For example, this may be used to create a zoom function in someone else's site.

Can you show some examples of other widths, so we can get a feel for how they look with this being left as a parameter? Are there upper/lower bounds we should enforce?

Here's 150, 250, and 400. I think these could look fairly nice if we added scaling of the text and scale.
Currently, around 700, the text becomes very small.

Yes, if we let height be a parameter, we would need to be scaling the text to fit. Everything other than 200 looks off to me.

If we scale the text as we change the height, then doesn't this become moot? The image already scales as an SVG.

Is there another way to scale the spacing between squares?
In the smaller examples, there is more spacing between the squares, but in the larger examples, there is more spacing between squares.

I think the square spacing has to do with the stroke on line 141. But like I was saying before, I think the SVG is a responsive image, and scales, from the code in 73 and 74. If we scale all the text and other spacing as they change height, are we really changing anything?
In any case, we should probably make this stroke match the background color of #fafafa instead of white.


Kirill Anokhin add

Congratulations, you have write access to the repository now! It allows you to assign yourself to one of the issues. Please revise our contribution rules before submitting a pull request.

@KirillAnokhin You have to add your Phystech.edu e-mail pukhov.vyu to GitHub so your commits are attributed to your account. Go to that page and proceeding instructions: https://github.com/settings/emails


Make sure the "Open Settings" in menu switches to our settings if Settings are already opened

This requires fixing an upstream bug in JupyterLab: https://github.com/jupyterlab/jupyterlab/issues/16479

I opened jupyterlab#17121 that address this


Objective-c Project ~ PermissionScope Error CBPeripheralManagerDelegate

I'm unable to build my project, I'm receiving an error in PermissionScope (interface) code:
"CBPeripheralManagerDelegate protocol not found".
I'm using an Objective-c based project.
I added the library through Cocoapods: "pod PermissionScope". (version 1.1.1)
Just in case, also add the CoreBluetooth framework to my project (although I'm not using, just to check). Try cleaning and building, but still the issue persist.
Thanks in advance

The issue was a category that I created for PermissionScope (to some extra utilities). Just need to import CoreBluetooth in the Category header.


RELEASE-0.2.4

 You should sign our Contributor License Agreement in order to get your pull request merged.


Login Hook doesnt work

Describe the bug
When I use  the Login Method from the Doku it gets executed 2 times. For example<EMAIL_ADDRESS>results in aaddmmiinn@@eexxaammppllee..ccoomm'. Same goes for Password
// unlighthouse.config.ts
export default {
  puppeteerOptions: {
    // slow down slightly so input is not missed
    slowMo: 50,
  },
  lighthouseOptions: {
    // allow storage to persist between pages
    disableStorageReset: true,
  },
  hooks: {
    'puppeteer:before-goto': async (page) => {
        // login to the page
      await page.goto('https://example.com/login')
      const emailInput = await page.$('input[type="email"]');
      await emailInput.type('admin@example.com');
      const passwordInput = await page.$('input[type="password"]');
      await passwordInput.type('password');
      await Promise.all([
        page.$eval('.login-form', form => form.submit()),
        page.waitForNavigation(),
      ]);
    },
  },
}

Reproduction
No response
System / Nuxt Info
System:
    OS: macOS 13.3.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 4.61 GB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 16.20.0 - /opt/homebrew/bin/node
    npm: 9.6.5 - /opt/homebrew/bin/npm

Iam using the default chromium thats get installed along  unlighthouse.

I have the same issue

Hey @paul1995tu, thanks for the issue.
I'll be looking at this issue next time I'm on unlighthouse, hopefully within a few days.

I'm also having trouble using the Login Hook. Where when I have submitted the form there is no response at all until I get an error Exception thrown when visiting route: Error: Navigation failed because the browser has disconnected!. I've tried using the login function using puppeter directly, it can run normally. I even set the timeout in unlighthouse.config as below, it's still the same.
page.setDefaultTimeout(300*1000) page.setDefaultNavigationTimeout(300*1000)

Hi, in v0.10.0 I've introduced the authenticate hook that should solve this.
It works pretty much the same, except it will collect any localStorage or cookies after the authentication and share that with subequent browser sessions.
See here: https://unlighthouse.dev/guide/guides/authentication#programmatic-usage

@harlan does this hook also collect IndexedDB? our firestore key is placed here after login
I am finding that if using 1 worker its is ok (but extremely slow), 3 workers and the state is unauthenticated.


remove unrequired comparisions

The other 3 cases are all already covered by these two if clauses

@aceakash is there anything that stops this from being merged?

@aceakash is there anything that stops this from being merged?

Thank you @maxbachmann , merged and published

Thank you @maxbachmann , merged and published


Resize image file size

This image is used with a 500 pixel wide resolution so it is total overkill and wast of library space to store the source file as a 3.5 MB high-res image.

Since there has not been much development going on in the repo since the initial upload, you might consider doing a fresh upload without the high-res image also lingering in the git archive itself. Now is still a chance.


darktable: Add openmp when cc.isClang to fix macos

Motivation for this change
darktable currently fails to build on macos
Things done
This fix is based on similar code here.

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

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

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

Notify maintainers
cc @

@GrahamcOfBorg build darktable


Lil refactoring. ;D

Useing Wrappers instead of primitives!
Using modern for instead of typical for!
Title/Heading < Edit this part>
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. < Edit this part>
Fixes # (issue)
Type of change
Please delete options that are not relevant.

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

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generates no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

@mohammadmasoomi2 Thanks for making this PR. Your changes will be reviewed soon. Until then please fill the PR template properly !


Summer Vacation Notice - Extended Response Time

Dear KEDA Community,
We hope this message finds you well and that you're enjoying the ongoing advancements in the KEDA project. As the proud maintainers of the KEDA project, we wanted to inform you about an upcoming change in our availability during the summer months.
During the months of July and August, the KEDA team will be taking some well-deserved summer vacations. As a result, we anticipate that our response time to GitHub issues and requests may be longer than usual. We believe that taking this time off will help us recharge and return with renewed energy and enthusiasm to continue improving the KEDA project.
We want to emphasize that we remain committed to supporting and maintaining the project, and we will make every effort to minimize any disruptions during this period. However, please understand that there might be delays in addressing your GitHub issues, pull requests, and other inquiries.
We kindly request your understanding and patience during this time. We value your contributions and feedback, and we assure you that we will address all outstanding matters as soon as we return from our vacations. We highly encourage you to continue engaging with the KEDA community, as there are many experienced and knowledgeable members who may be able to provide assistance in our absence.
In the meantime, we encourage you to refer to our comprehensive documentation, which covers various aspects of KEDA and may help address any immediate concerns or questions you may have.
We will be posting an official notice in our GitHub repository to remind the community about our upcoming vacation period and extended response time. Additionally, we will update our GitHub templates and provide an estimated timeline for responses to manage expectations effectively.
We sincerely apologize for any inconvenience this may cause and appreciate your understanding. Your continued support and patience mean a lot to us, and we are confident that we will return with even greater enthusiasm to further enhance the KEDA project.
Thank you for being a valued member of the KEDA community!
Warm regards

We will hold our last standup on Tuesday, July 18th before starting summer vacation for the rest of summer.
Standup will re-instate on September 12th, right in time for KEDA 2.12! If you are subscribing to our Google calendar than you should already received notifications.


Upgrade to pgx v5

Version 5 of pgx introduced several breaking changes that affected our code base. You can read more about them here:
https://github.com/jackc/pgx/blob/29ad306e47c491a0ecc52d502241539aedd636bd/CHANGELOG.md#codec-and-value-split
In summary:

NULL Representation

Previously, types had a Status field that could be Undefined, Null, or
Present. This has been changed to a Valid bool field to harmonize with
how database/sql represents NULL and to make the zero value useable.

Codec and Value Split

Previously, the type system combined decoding and encoding values with
the value types...
This concepts have been separated. A Codec only has responsibility for
encoding and decoding values. Value types are generally defined by
implementing an interface that a particular Codec understands (e.g.
PointScanner and PointValuer for the PostgreSQL point type).

Array Types

All array types are now handled by ArrayCodec instead of using code
generation for each new array type...

Other Changes

JSON and JSONB types removed. Use []byte or string directly.

There are some changes that don't seem to appear in the CHANGELOG:

An error is returned when scanning NULL into a variable that can't handle nil values. For example, scanning NULL into an int64.

Custom types must be register into the connection's typeMap *pgtype.Map, otherwise, an error will be returned when the encoding/decoding plan is not found for the custom type OID.

Requires go 1.18 since it uses generics for some features, like arrays.

To deal with the custom types, we added the register logic in the afterConnect method of the pool. Every time a connection is created a new pgtype.Map is generated with all the default PostgreSQL, meaning that whenever a connection is created, we need to register our custom types with it.
Description

Merge requirements
Please take into account the following non-code changes that you may need to make with your PR:

[ ] CHANGELOG entry for user-facing changes
[ ] Updated the relevant documentation

I'm going to take a day off this PR and then re-review everything with a clear mind.

It would be interesting to compare memory profiles while running https://github.com/timescale/promscale-benchmark/ . Like you noted before we expect this upgrade to use less memory due to improvements in PGX.


TypeError: $setup.error is a null

Environment
pnpm dev
Operating System: Linux
Node Version: v18.14.0
Nuxt Version: 3.2.2
Nitro Version: 2.2.2
Package Manager<EMAIL_ADDRESS>Builder: vite
User Config: typescript and javascript
Runtime Modules: -
Build Modules: -

Reproduction

Describe the bug

error when click back goes to home from error.vue
Additional context
No response
Logs
No response

the code is on my github
https://github.com/bobbyrahmanda13/carshop


ENH: Add an axis parameter to DataFrame.diff

+1 on this. I think the axis should be flipped though, right? axis=0 is a difference along the index, i.e. df.iloc[1] - df.iloc[0]. Similar to how cumsum operates along the index.
See also np.diff.

@TomAugspurger: You're right about np.diff having a different convention. All of the internal diff machinery (in core.internals.Block, core.common, and C implementations in algos) has this opposite convention as well, but maybe I'll just invert the axis in this public facing DataFrame.diff method.

@evanpw you need to pass the axis as self._get_block_manager_axis(axis) which handles this. frames (only) are represented with inverted axes.

Ahh, that explains it.

@evanpw thanks!


Nested ternary operations

My VSCode User preferences:
{
    "prettier.printWidth": 120,
    "prettier.singleQuote": true
}

Original code:
const retVal = diff < -365 ? 'sameElse' :
  diff < -6 ? 'lastYear' :
  diff < -1 ? 'lastWeek' :
  diff < 0 ? 'lastDay' :
  diff < 1 ? 'sameDay' :
  diff < 2 ? 'nextDay' :
  diff < 7 ? 'nextWeek' :
  diff < 365 ? 'nextYear' : 'sameElse';

Expected:
const retVal = diff < -365 ?
      'sameElse' :
      diff < -6 ?
        'lastYear' :
        diff < -1 ?
          'lastWeek' :
          diff < 0 ?
            'lastDay' :
            diff < 1 ?
              'sameDay' :
              diff < 2 ?
                'nextDay' :
                diff < 7 ?
                'nextWeek' :
                  diff < 365 ?
                  'nextYear' :
                    'sameElse';

Result:
const retVal = diff < -365
      ? 'sameElse'
      : diff < -6
          ? 'lastYear'
          : diff < -1
              ? 'lastWeek'
              : diff < 0
                  ? 'lastDay'
                  : diff < 1
                      ? 'sameDay'
                      : diff < 2 ? 'nextDay' : diff < 7 ? 'nextWeek' : diff < 365 ? 'nextYear' : 'sameElse';

2 issues here:

The indents are set to 4 even though my user preferences specify a tab size of 2.
The formatting sort of gives up breaking lines for ternary (see last line). I am guessing this is because it decides that the rest of the operation can fit in one line knowing that the ruler is set to 120. I would still like to give the annotation consistency. Keeping this "ladder" all the way to the end would make it more readable.

I am pretty sure my second point should be more of an issue for the prettier project itself but I thought there was some conversations I can get from here first.

It seems to me both of your issues are for prettier. Your output is prettier's one as of prettier 0.22.0:
const retVal = diff < -365
 ? 'sameElse'
 : diff < -6
     ? 'lastYear'
     : diff < -1
         ? 'lastWeek'
         : diff < 0
             ? 'lastDay'
             : diff < 1
                 ? 'sameDay'
                 : diff < 2 ? 'nextDay' : diff < 7 ? 'nextWeek' : diff < 365 ? 'nextYear' : 'sameElse';

see prettier/prettier#924
I've no knowledge of such an issue in prettier.

Quite new there is prettier/prettier#1171 which seems to be your 2nd point.

Closing this as this is a prettier issue :-) let me know if you think otherwise @CiGit @yannickguillemot


move io to new module jsprit-io

to make the core really lightweight and to get rid of two dependencies in core.
after this jsprit-core just has two dependencies slf4j and commons.math3.
todo:

[x] new module jsprit-io
[x] move algorithm.io
[x] move problem.io
[x] refine Schrimpf, GreedySchrimpfFactory as well as ThresholdGenerators
[x] adapt tests to read instances without xml reader

working branch: https://github.com/graphhopper/jsprit/tree/jsprit-io

closed via https://github.com/graphhopper/jsprit/commit/9e6ff24cab3fbb0c9b10eb08f117e4bcea43e124

jsprit-core has now only two dependencies
    <dependencies>

        <dependency>
            <groupId>org.apache.commons</groupId>
            <artifactId>commons-math3</artifactId>
            <version>3.4</version>
        </dependency>

        <dependency>
            <groupId>org.slf4j</groupId>
            <artifactId>slf4j-api</artifactId>
            <version>${logger.version}</version>
        </dependency>

</dependencies>

Vers nice!!

nice! BTW: why math3?

DBSCANClusterer as well as some descriptive statistics


[WIP][Discussion] Standalone preprocessor design

SV Standalone Preprocessor Design
Introduction
The goal of this thread is to discuss the design of a standalone System-Verilog preprocessor.
The preprocessor should fully support the directives described in 2018 SV-LRM, and provide APIs that can be used to build a standalone tool (token in / token out basis).
This proposal is a continuation on the already built pseudo-preprocessing.
Also, refer to #1318 to track the current progress.
Functions (APIs)
ScanStream (DONE)
Parameters

Input: constant reference to a token stream (full SV source code).
Return: VerilogPreprocessData

Algorithm

Calls MakeConstIteratorStreamer, to create an iterator generator.
Generates iterators using generator, calls HandleTokenIterator for each token iterator.
Return a move from the VerilogPreprocessData.

HandleTokenIterator (DONE)
Parameters

Input: constant iterator to a token stream view.
Input: steam iterator generator (is needed for cases when more than one token is consumed).

Algorithm

This function is a mainly a case switch, that calls the needed function for each directive.
Calls HandleDefine, HandleIf, HandleMacroIdentifier, and so on when needed.
Forwards the token to the preprocessed token stream view.
Returns status.

HandleMacroIdentifier (DONE)
Parameters

Input: Token iterator (pointing to a macro call e.g. `MACRO).
Output: is appended to preprocessor memory

Algorithm

Find the macro definition that matches the macro being called.
Calls ConsumeAndParseMacroCall.
Calls ExpandMacro.
Add the last vector of tokens in the preprocessor memory to the preprocessor output stream.
Return status.

ExpandMacro (IN PROGRESS)
Parameters

Input: MacroCall (populated by ConsumeAndParseMacroCall)
Input: MacroDefinition
Output: is appended to preprocessor memory

Algorithm

Begin to re-lex the macro definition body
Forward lexed tokens to the output sequence
A lexed token should is directly forwarded to the output sequence, unless the lexed token is:

A formal parameter in the MacroDefinition then substitute with ExpandText [^1], then forward the last vector of tokens in the preprocessor memory to output sequence.
Another macro identifier, then call HandleMacroIdentifier, then forward the last vector of tokens in the preprocessor memory to output sequence.
A preprocessor directive, HandleTokenIterator should be called, then forward the last vector of tokens in the preprocessor memory to output sequence.

Append the output sequence to the preprocessor backup memory (which is a vector of token sequences).

Return status.
ConsumeAndParseMacroCall (DONE)
Parameters

Input: stream iterator generator by ref (if we need to consume more than one token).
Input: TokenStreamView iterator (pointing to the macro name).
Input: a MacroDefinition reference.
Output: a MacroCall.

Algorithm

Extract macro name (directly pointed to by iterator)
Determine if the macro definition is callable or not
Populates MacroCall, which should contain:

MacroName
Flag if it has parameters.
Parameters as a vector of tokens.

Return status

[^1]: ExpandText should work exactly as ExpandMacro, but only accepts plain text, kind of like ScanStream?

Question: I am thinking instead of adding a handling method for each directive inside ExpandMacro, It would be a better idea to just use ScanStream? Because that would be the end result anyway.
For example, right now only these tokens are correctly interpreted inside ExpandMacro:

Actual parameters being replaced.
Other macro calls (with or without parameters).
Other tokens that are not preprocessor directives.

So, If we find some way to use ScanStream on the macro body itself, that would solve all the limitations we have right now.

CC @hzeller @mglb

Also cc @fangism


nan with betainc for a=0, b=3 and x=0.5

scipy.special.betainc(a, b, x)  returns nan when a=0, b=3, and x=0.5.
Reproducing code example:
# Script ported from Matlab documentation:
# https://www.mathworks.com/help/matlab/ref/betainc.html

import numpy as np
from scipy.special import betainc

X = 0.5
Z = np.array(range(0,11))
W = 3

print(betainc(Z,W,X))

Output:
[       nan 0.875      0.6875     0.5        0.34375    0.2265625
 0.14453125 0.08984375 0.0546875  0.03271484 0.01928711]

Scipy/Numpy/Python version information:
1.0.0 1.14.0 sys.version_info(major=3, minor=5, micro=4, releaselevel='final', serial=0)

EDIT: edited for clarity

You set x = 0.5 in that example? And it gave nan for a = 0, which is sensible because the incomplete beta integral doesn't converge then.

@person142 it seems that the limit of the integral for a -> 0+ is 1. For what it's worth, Matlab returns 1 for a = 0.

Ah, I was forgetting about the regularization. Looks like the limit can be fairly simply demonstrated to be 1 by using the relation to the Gauss hypergeometric function
https://dlmf.nist.gov/8.17#E7,
so should be a straightforward fix.

@person142 I would like to work on this issue

Sure. The code is here:
https://github.com/scipy/scipy/blob/master/scipy/special/cephes/incbet.c#L81.

Currently, the implementation, which has not been significantly changed since this issue was opened, treats non-positive a, non-positive b, x<0 or x>1 as being an error (and possibly other criteria in subroutines).
I'm afraid this isn't an area of expertise for me, but I think the first two at-least could be fixed by:

If a is non-positive, apply this identity to shift it positive.
If b is non-positive, apply this identity to flip the arguments. Then apply the first identity again.

Of-course, the underlying reason why non-positive arguments aren't accepted could also be fixed. But I don't know about that.


slackchannel? What is it job?

Been lookin in to slack. And must be doing something wrong or something but I don't see point in script variable slackchannel.
slackchannel=""                                    # Slack Channel #example
It dosn't seam to do anything. It could be null value, it could have a Slack channel under my account, could be set anything like total random nonsence. Make no diffrance.
You could remove code on line 87 and 97 and still works.
"channel": "'$slackchannel'",
So what is job? Because I would nice if webhooks I have that would be able to post another channel, but it will only post to channel that defiened when creating that webhook.

Hey @northportio, if its possible do take a look at this.

Thanks for queuing me in @K0p1-Git.
I haven't looked into this in-depth yet but I'll explore this more.
My initial answer:
To the best of my knowledge, I may be incorrect here but you basically create the app in slack, copy the webhook to the script and then add the app to the channel (that gives authorization to post in said channel). If you had the app added to multiple channels, I believe that's where the channel name designation matters.
I will look into this more on my spare time but that's my initial answer. Hope that somewhat answers your question.

@northportio Yep! You're correct however...(Hey! Just my two cents opinion down here)
Afaik, because of security scopes, Webhooks are usually tied to a specific channel. Each webhooks uri is unique, no matter the app, destination channel etc. (You can try create a duplicate webhook, and see that the request uri is different even thought they post to the same channel, from the same app etc)
To implement channel name designation, i think the following steps must be done.
An user needs to go to here. Create an app, and go to OAuth & Permissions, then setup the necessary OAuth permission scopes like channels:read for reading available channels, and chat:write for sending messages.
Then copy the bot user oauth token, it usually starts with xoxb-<...>.
Then post request code shall be like:
#!/bin/bash
slack_api_url="https://slack.com/api/chat.postMessage"
slack_app_token="your-bot-user-oauth-token-here"
slack_channel="general"

slack=$(curl -s -X POST $slack_api_url \
    -H "Authorization: Bearer $slack_app_token" \
    -H "Content-type: application/json; charset=UTF-8" \
    --data "{\"channel\":\"$slack_channel\",\"text\": \"Hello world! I'm sending message to $slack_channel channel.\"}")


Document error on v6

If I use this in basic v6 template:
// static.config.js
export default {
Document: ({ Html, Head, Body, children, siteData, renderMeta }) => (

{children}

),
}
I get the error that react is not defined.

You must import react wherever you use jsx
On Fri, Dec 21, 2018 at 7:39 AM Thomas Schöller<EMAIL_ADDRESS>wrote:

If I use this in basic v6 template:
// static.config.js
export default {
Document: ({ Html, Head, Body, children, siteData, renderMeta }) => (
{children}
),
}
I get the error that react is not defined.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/nozzle/react-static/issues/911, or mute the thread
https://github.com/notifications/unsubscribe-auth/AFUmCbG01RZNdAvEv1za8GYDIsa2_xHtks5u7PKqgaJpZM4ZeFN1
.

yes but in 6.0.2 it failed with another error after importing react. In 6.0.11 it seems to work now 👍
one short question: how could I get the routeData there for title and some meta tags?
Thanks


Norwegian Snippet Set (Nynorsk nn-NO) uses translations for nb-NO (Bokmål)

Used Shopware Version: <IP_ADDRESS>
The Norwegian snippet set nn-NO (language: Nynorsk) uses translations for the language Bokmål. However, the latter language is the commonly used language of Norway.
Therefore, the ISO code would have to be adapted accordingly to nb-NO (as this affects not only the indexing by google) and, if necessary, a dedicated snippet set for nn-NO with the translation used for it would have to be created.

[public] Shopware automated response: This issue is linked to the internal issue: LAN-143
[created from LAN-143, comment 514141]


Fix the judgment of update flag

// Describe your PR here; eg. Fixes #issueNo
Fix the judgment of update flag

pls check ci pass

Hi， can you fix ci error @wavesZh

Codecov Report

Merging #1374 (8263450) into master (d9668dc) will decrease coverage by 0.71%.
The diff coverage is 85.71%.

:exclamation: Current head 8263450 differs from pull request most recent head 851b2e8. Consider uploading reports for the commit 851b2e8 to get more accurate results

@@             Coverage Diff              @@
##             master    #1374      +/-   ##
============================================
- Coverage     64.12%   63.40%   -0.72%
+ Complexity     2043     2037       -6
============================================
  Files           407      407
  Lines          8797     8799       +2
  Branches        880      881       +1
============================================
- Hits           5641     5579      -62
- Misses         2739     2801      +62
- Partials        417      419       +2

Impacted Files
Coverage Δ
Complexity Δ

...che/shenyu/sync/data/http/HttpSyncDataService.java
63.10% <66.66%> (-19.25%)
12.00 <0.00> (ø)

...nyu/sync/data/http/refresh/DataRefreshFactory.java
100.00% <100.00%> (ø)
5.00 <2.00> (ø)

...enyu/client/tars/TarsServiceBeanPostProcessor.java
31.70% <0.00%> (-51.22%)
8.00% <0.00%> (-6.00%)

...henyu/plugin/httpclient/NettyHttpClientPlugin.java
57.14% <0.00%> (-2.05%)
10.00% <0.00%> (ø%)

...elimiter/handler/RateLimiterPluginDataHandler.java
69.23% <0.00%> (-1.54%)
14.00% <0.00%> (ø%)

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 d9668dc...851b2e8. Read the comment docs.


Chapter 3 broken links

Chapter 3:
Links 3.2, 3.3, 3.4 do not lead to setup instructions, but instead advance you to the quiz.

could not reproduce


commitizen の WARNING 調査

=======================================================
[LOG] START: git-cz installation
=======================================================
[LOG] START (Step 1): $ npm install -g commitizen
npm warn deprecated<EMAIL_ADDRESS>This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated<EMAIL_ADDRESS>Glob versions prior to v9 are no longer supported

changed 168 packages in 7s

27 packages are looking for funding
  run `npm fund` for details
[LOG] END (Step 1): $ npm install -g commitizen
------------------------------------------------------
[LOG] START (Step 2): $ npm install -g --force git-cz

up to date in 265ms
npm warn using --force Recommended protections disabled.

added 1 package in 3s
[LOG] END (Step 2): $ npm install -g --force git-cz
=======================================================
[LOG] END: git-cz installation
=======================================================

自分ではどうにもならなそう。クローズ。


chore(package): update @kronos-integration/service to version 6.1.17

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Support chaining

It would be cool and is already some habit for some devs.
const mitt = require('mitt')
const emitter = mitt()
emitter.on('foo', console.log).on('bar', console.log).emit('foo', 123)

Interesting! Would be curious to see the filesize hit.

I think the easiest fix is to make to exports. The default to be the "instance" (like invoking mitt()) and the another to export the current function
export default mitt()
export const mitt

function mitt(all) {

// code ...

Something like that? So if users want to add initial events through mitt({}) they will use
import { mitt } from 'mit'

Oookey, okey, let me think a bit, i'll try. Coding at github issue isn't feels good haha

Hmm - that'd be a singleton, which is generally not going to be a good thing (npm dupe issues, etc).  I've used that pattern before with a similar EventEmitter, and that was actually one of the reasons I wrote this one - you can do this:
import mitt from 'mitt';
const { on, off, emit } = mitt();
export { on, off, emit };

That's probably the better option if you're looking to then import the singleton methods later on.  You get to use an instantiable library (mitt) but then work with your own created singleton in your codebase.
Just my 2 cents :)

Actually, I did it :) But is 212 ;/ All of my above snippets was wrong. Idea is different.
We need to not just return an object with the methods but assign that object to const ret, return that const and use that const in each method.
export default function mitt(all) {
	// Arrays of event handlers, keyed by type
	all = all || {};

	// Get or create a named handler list
	function list(type) {
		let t = type.toLowerCase();
		return all[t] || (all[t] = []);
	}

	const ret = {

		/** Register an event handler for the given type.
		 *	@param {String} type		Type of event to listen for, or `"*"` for all events
		 *	@param {Function} handler	Function to call in response to the given event
		 *	@memberof mitt
		 */
		on(type, handler) {
			list(type).push(handler);
      return ret;
		},

		/** Remove an event handler for the given type.
		 *	@param {String} type		Type of event to unregister `handler` from, or `"*"`
		 *	@param {Function} handler	Handler function to remove
		 *	@memberof mitt
		 */
		off(type, handler) {
			let e = list(type),
				i = e.indexOf(handler);
			if (~i) e.splice(i, 1);
      return ret;
		},

		/** Invoke all handlers for the given type.
		 *	If present, `"*"` handlers are invoked prior to type-matched handlers.
		 *	@param {String} type	The event type to invoke
		 *	@param {Any} [event]	An event object, passed to each handler
		 *	@memberof mitt
		 */
		emit(type, event) {
			list('*').concat(list(type)).forEach( f => { f(event); });
      return ret;
		}
	};

  return ret;
}

It will fit if we use #8

Gotta get that size down somehow 😉  208 is pretty good though, basically just paying for one return ret thanks to gzip.

Seems like this issue and #1 are incompatible.

Oooh - good point. I totally did not think of that.

Yea, absolutely. But I believe this lib is meant to be with kind of compat with most common and to be small. Or at least it is promoted as that. I not mean that #1 will be with bigger size, but it is other thing and can be done in separate more smaller lib.

Instead of returning unsuscribe method (#1) we can add the getUnsuscribe on the fluent API. So you can get it when you whenever to.

@sospedra I'm not sure how viable a new method would be as the 200 B gzipped limit is quite a challenge to work around. @tunnckoCore has been doing some heroic with in #19.

adding getUnsubscribe() would require that a fluent API return new instances of the interface for every call. I don't think that is possible given the size limitations here, and the performance would be quite poor.

Using Closure Compiler, you end up with 197 bytes after including the return in each function by it converting all let or const to var. If using let & const aren't a requirement, that's an easy way to get that gzip size down.
function mitt(b){function c(a){a=a.toLowerCase();return b[a]||(b[a]=[])}b=b||{};var d={on:function(a,e){c(a).push(e);return d},off:function(a,e){var b=c(a),f=b.indexOf(e);~f&&b.splice(f,1);return d},emit:function(a,b){c("*").concat(c(a)).forEach(function(a){a(b)});return d}};return d};

The source gets transpiled by Buble so those let declarations actually are var - good to know we could save a few bytes going with closure though.


Release: hwc-buildpack (Jan)

Release reminder for hwc-buildpack

See diff from latest version and validate if a release is required.
Make sure the latest commit on  has passed tests on the CI
Refer release instructions. (private link)

Nothing to release.


Making faster ingest pipeline

multiprocessing, multithreading, asyncio.
First load documents and store to DB => embed documents from DB

Langchian supports concurrency loader + multi_processing


Update fastpages-styles.scss

remove clipping on table cells, as discussed here:
https://forums.fast.ai/t/solved-markdown-tables-truncating-colums/76504/2

/preview

I’m not sure this is a desirable change.  For dataframes with very long values like long strings of texts, this will cause the table to exhibit undesirable behavior and overflow or become too wide.
Any thoughts?  We need to add an example with lots of text and long values.  And perhaps we need to add instructions so people know how to change it.

/preview

Thanks @joedockrill looks good!


https://github.com/standardhealth/shr-cli/wiki/CIMPL-Documentation#includes-code -- not clear

Perhaps density of the reader, but I don't follow this:
The second example above expands the allowable codes in ProblemCategory to include #adverse_reaction. Unlike the first example, the value set does not precede the code, because it has defined on ProblemCategory's parent using a from statement.

Overcome by events. Not longer finding such statements in the current doc.


Add SuperDuper!

NOTE: Each discrete (stand-alone) request should be in its own issue.
Put "Add ____" as Title
[x ] Done
Provide a link to the proposed addition.
https://shirt-pocket.com/SuperDuper/SuperDuperDescription.html
Explain why it should be added
Painless fully bootable disk backups.
Issue Checklist
Put an x in the boxes once you've completed each step. You can also fill these out after creating the issue. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before responding to the issue.

[x ] I have checked for other similar issues
[x ] I have explained why this change is important
[x ] I have added necessary documentation (if appropriate)

@margoussian You can open a PR and I will merge it.

Thanks. Created PR: https://github.com/jaywcjlove/awesome-mac/pull/594


Weird behavior vue-router 2.0.1

I'm not sure if this is a bug or if i'm doing something wrong.
I looked out on the open issues and didn't see anything like this.
I'm trying to secure my web app using jwt, and i'm having trouble after my app redirect to login when i try to access a path that requires auth and the token is not valid.
The router does the redirection to login and after the authentication the redirection to the secured page also works fine, but then the router dies, no other route works, no errors or anything on the console either, the weird thing is that after a browser refresh everything works normal again.
It only happens after a redirect like this one: { path: '/', redirect: '/app' }, but /app requires authorization, so next('/login'); is executed (check my code below), then if the login is successful i execute self.$router.push('/app'); and that's that, i have to refresh in order to continue.
In firefox over windows64 it happens when i enter the app the first time if there is no token (when it has to do the redirection to login), if i delete the token and close/open the browser it happens again.
In chrome over windows64 happens sometimes, also after a redirect, if go directly to the login page it works normally.
Im using this:
router.beforeEach(function(to, from, next) {
    if(to.matched.some(function(record) {
        return record.meta.authorization || false;
    })) {
        var token = jwt.getToken();
        if(token && token.valid) {
            next();
        } else {
            next('/login');
        }
    } else {
        next();
    }
});

my routes look like:
[
    { path: '/login', component: loader('login') },
    {
        path: '/app',
        component: loader('main'),
        children: [
            { path: '', component: loader('dashboard') },
            { path: 'areas', component: loader('administration/areas') },
            { path: 'macro-processes', component: loader('administration/macro-processes') },
            { path: 'processes', component: loader('administration/processes') },
            { path: 'products', component: loader('administration/products') },
            { path: 'documents', component: loader('documentation/documents') },
            //Lot of routes
        ],
        meta: {
            authorization: true
        }
    },
    { path: '/', redirect: '/app' },
    { path: '*', redirect: '/app' }
]

loader is a function that concatenates the full path of te component an returns a function to use resolve
function loader(component) {
    return function(resolve) {
        require(['js/components/' + component + '-component'], resolve);
    }
}

and in my app.js i have this:
Vue.http.interceptors.push(function(request, next) {
    var token = jwt.getToken();
    if(token) {
        if(token.valid) {
            request.headers.set('Authorization', 'Bearer ' + jwt.getRawToken());
        }
    }
    next();
});

Thanks.

I have the same problem now.I have found that adding query query: { redirect: 'test' } can fix it temporarily.

Hi, thanks for filling this issue. Please follow the Issue Reporting Guidelines and provide a live reproduction on jsfiddle, codepen etc. Thanks!

It seems that te problem happens only when i using <a href="#/...."> in the template or $router.push('/...'); on the component. the links made with<router-link> works fine and after i click any <router-link>, $router.push('/...') works again.
I started the app with vue 1.0 using another router, so i'm just starting to change the <a> to <router-link>.
As @Yiiu said using $router.push({path: '/app', query: {redirect: 'test'}}); also works.
I'll try to create a jsfiddle asap to reproduce the problem.

I am able to produce the steps, please see below.
Vue.js version
2.1.0
Vue-Router version
2.0.3 - using hash mode
Reproduction Link
https://jsfiddle.net/starkhorn/pz56e342/4/
Steps to reproduce / What is happening
The issue happens when the current browser hash is different from the one being redirected to (using a navigation guard). After the redirect, vue-router will not work when the browser hash changes.
I tried stepping through the code, it seems that, for some reason, the callback function that should add an event listener to window's hashchange event is skipped -- the transitionTo() gets called though.
history.transitionTo(getHash(), function () {
  window.addEventListener('hashchange', function () {
    history.onHashChange()
  })
})

In the JSFiddle provided, if you change the initial hash to '#/login', vue-router will correctly listen to window's hashchange event.
Note: navigation using router-link still works though.

Seems to be a bug.


Move the pending CCTX iteration logic into the observer module

PendingNonce and PendingCCTX is part of the observer module scope. Detecting which CCTXs are stale because of TSS signing should be part of the observer module, while the logic to increase the gas price used in a CCTX should stay in the crosschain module.
We should:

Move the IterateAndUpdateCctxGasPrice method and BeginBlocker logic for cctx price increase in the observer module

Will be simpler to keep it as is


Add create_timestamp to metastore split

It would be nice to have  create_timestamp  added to split in the metastore. This will help in debugging and monitoring.
As a bonus, one could use the Diesel ORM trigger feature for keeping both create_timestamp and update_timestamp in sync automatically

Had to reverse the PR as it broke backward compatibility.
@evanxg852000 can you fix and resend a merge request?


Updating links for flux-viewport and related docs

This adds the requested documentation as links in the book.

Fine by me if it's fine with Karl! :)


Replace Joda Time to Java 8 Date Time

Are there any plans to replace Joda Time with Java 8 Date Time?

You know, I was thinking about that... but it would be quite a bit of refactoring.

Would be nice as I think mostly everybody is now using Java 8 Date Time. But I understand that this will be quite a bit of work. Thanks anyway and great job you are doing with ta4j. We have used ta-lib in the past but unfortunately it does not allow continuous calculations of technical indicators which your library does

ta4j currently uses Java 6. See this discussion for context
https://github.com/mdeverdelhan/ta4j/issues/93

@andyflury Yep, that's why I switched to this library too... though, it has been a bit less stable than ta-lib admittedly. I'd move only if you were confident enough to solve your own problems or make your own improvements with it. While there are contributors other than the original author, progress is at a slower pace than most individuals or teams develop at.  Hopefully that improves as the library matures.

Thank you @dan-lind. It may evolve.
I did not know that Date/Time API was such improved in Java 8. We could remove the old Joda dependency. Feel free to make a PR if you get enough time. Furthermore I don't know anyone which is still using Java 6 now.

Note:
Joda-time Period includes years to milliseconds, java.time Period only includes year/month/day (we have to use Duration for other durations/periods). It involves to refactor TimeSeries#split(...) and TimeSeries#subseries(...) method if we want to manage daylight savings, etc.
See also: http://blog.joda.org/2014/11/converting-from-joda-time-to-javatime.html

Yeah I implemented Periods and Durations for the slices in my PR. Long story short after a series of unfortunate events my forked repository got corrupted and thus I deleted it. I still have the Java 8 code in my own version of ta4j but extracting just those changes (again) is going to be a tedious process.

I think that you can manage it following thoses steps:

Fork and clone again
Make a raw copy of your local version in the new clone
Check the diff according to what I suggested
Commit, push and submit a new PR

Fixed by #158.


Added focusRing + showFocusRing boolean

The focus ring shows up on a single tap gesture. Gives the user visual feedback on what they are focusing on. Can be turned off via the showFocusRing boolean.

Thanks for the request, I will review this when I get home.
I will have think about whether or not this framework includes any UI of its own. The purpose was to support the functionality of a camera application, without dictating the style.
This is why the delegate includes
func swiftyCam(_ swiftyCam: SwiftyCamViewController, didFocusAtPoint point: CGPoint)

This way, the user of the framework can supply their own focus rings like the sample application. Can I ask why you think bundling one is a better option?
Thanks
Andrew


Missing ./Step/defaultRun.dhall file?

I stumbled across this repository and tried to interpret example.dhall but ran into this issue:
$ dhall <<< 'https://raw.githubusercontent.com/ababkin/dho/master/example.dhall'

↳ https://raw.githubusercontent.com/ababkin/dho/master/example.dhall
  ↳ https://raw.githubusercontent.com/ababkin/dho/master/Step/defaultRun.dhall

Error: Remote file not found

@ababkin same problem as @Gabriel439


lago-530 uniswap routing explained in tests

What's the purpose of your PR?

[ ] Fixing a bug
[ ] A new Feature
[ ] Techdebt
[x] General Task

What your PR is all about?
Any special instructions for the reviewer?

@tkeidar I think your approval is needed for this to be merged


No 3D audio in SoundCollision Framework

I see you have setup spatial bend to 3D in the CollisionSoundPrefab but the resulting sound in my earphones is 2D. Can't see what's wrong though, but I think 3D audio is really essential for VR.

Think I fixed this in 0.9.


chore(test): e2e tests in firefox

Ad for now Firefox e2e tests is blocked by
https://github.com/angular/protractor/issues/2784

root issue: https://github.com/angular/zone.js/issues/234


Simplify Scheduler and ClusterState Logic

Remove unnecessary/messy logic/clean up variables

Had a few minor comments, but otherwise looks good enough to merge. Merging. :+1:


Add no_std support using alloc if std feature is disabled

Tried to minimize code impact by not adding pure no_std. no_std with alloc should still be very useful.

Codecov Report

Merging #103 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master     #103   +/-   ##
=======================================
  Coverage   96.14%   96.14%
=======================================
  Files          12       12
  Lines        1479     1479
=======================================
  Hits         1422     1422
  Misses         57       57

Impacted Files
Coverage Δ

src/lib.rs
92.3% <ø> (ø)
:arrow_up:

src/chunked_encoder.rs
98.78% <ø> (ø)
:arrow_up:

src/write/encoder_tests.rs
95.66% <ø> (ø)
:arrow_up:

src/tests.rs
100% <ø> (ø)
:arrow_up:

src/display.rs
100% <ø> (ø)
:arrow_up:

src/encode.rs
98.03% <100%> (ø)
:arrow_up:

src/decode.rs
94.4% <100%> (ø)
: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 7e90f80...9f736dd. Read the comment docs.

Thanks, I'll take a look soon.


Use test registry in npmrc for alpha packages

Currently, the Autorest Regen Preview pipeline for autorest.csharp publishes alpha versions of the c# emitter package to an alternate package feed. This is breaking the validation builds of azure-sdk-for-net because the alpha version specified doesn't exist in the default public repository.
To fix this, if we detect an alpha package version number in emitter-package.json, we create an npmrc file prior to running the code generation check.

To verify, I ran in azure-sdk-for-net using these pipelines:
Should pass because doesn't use alpha package:
https://dev.azure.com/azure-sdk/public/_build/results?buildId=2799062&view=results
Should fail because uses alpha package and didn't regenerate code in branch:
https://dev.azure.com/azure-sdk/public/_build/results?buildId=2799252&view=results
Should pass because uses alpha package and did regenerate code in branch:
https://dev.azure.com/azure-sdk/public/_build/results?buildId=2801691&view=results

The following pipelines have been queued for testing:java - templatejava - template - testsjs - templatenet - templatenet - template - testspython - templatepython - template - tests You can sign off on the approval gate to test the release stage of each pipeline. See eng/common workflow


[SUPPORT] Maybe should cache baseDir in nonHoodiePathCache in HoodieROTablePathFilter?

For a non hoodie table, with table path: hdfs://test/warehouse/db/table, 3 partition columns(p1, p2, p3), for a specific partition, like(p1=A, p2=B, p3=C), the path should be hdfs://test/warehouse/db/table/p1=A/p2=B/p3=C, HoodieROTablePathFilter will check baseDir(hdfs://test/warehouse/db/table) is a valid HoodieTable path or not, othervise, cache hdfs://test/warehouse/db/table/p1=A/p2=B/p3=C in nonHoodiePathCache.
I'm wondering why don't we cache baseDir in nonHoodiePathCache, if we cache baseDir, for other partitions(like p1=A1, p2=B1, p3=C1), we only check if baseDir in nonHoodiePathCache or not.
Pls correct me if I'm wrong.

yeah. I also could not think of a reason. @bvaradar @n3nash : any thoughts here. If not, we will go ahead and work on a fix.
@boneanxs : Do you think you can put up a fix on this end. We can probably get it into upcoming release.

Yes, I'm willing to put up a fix for it, will do it these days.


Dynamically updated stylesheets may not have pseudo states applied

The addon currently processes every stylesheet in the document only once. It marks the stylesheet as "rewritten" and will never touch it again. However, sometimes a stylesheet might get updated dynamically, e.g. as a result of switching a theme global. In such cases any newly injected CSS rules will not get rewritten for pseudo states, because their parent stylesheet has been rewritten before.
Likely the solution would be to mark individual CSS rules as having been rewritten, rather than the stylesheet as a whole.

Hopefully it's not rude to ask, but is there a timeline or estimation for when this would be done?

Working on it today. Ran into a snag though, so this might need a little more work.

Shipped in v2.1.2


Change UID and GID variables to ENV instead of ARG ?

Prerequisites

[X ] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem.
Checked that your issue isn't already filed.
Filled the form.
Included logs and system information.

Description
Is it possible to change the
ARG CONTAINER_UID=1000
ARG CONTAINER_GID=1000
to be environment variables so that we can use the parent image from dockerhub and pass the UID and GID as environment variables instead of using the Dockerfile in github directly ?
I can make a fork/copy and try but didnt want to maintain seperate versions
Thanks

I do not think the ARGs actually work because it's already overwritten in line 65 of the Dockerfile.
The whole issue is doable but just rather challenging as the ARG user is already used inside the Dockerfile. I do not know if you can adjust the jira user after the Jira installation. Also, you would have to reown stuff each time the container is started, which is rather dirty.
You can make a fork/copy and afterwards do a pull request. After a proper review you do not have to maintain separate versions.
For example I would like a proper implementation expect to behave in an idempotent manner, means:

Files should not be reowned each time but there should be a proper routine that expertly decides a reown is required.

Downwards Compatibility for people already using the image:

Must be activated, default behavior must be the current entrypoint behavior with default user.

Ok, let me think about it. Right now Iam trying to migrate our existing applications to docker from a server env and using host path volumes to use the existing home directories but the 1000 uid maps to a random user in our system making all the permissions off. Trying to find a solution for that.
Thanks


Document the internals

Write documentation about:

[ ] Overall code structure.
[ ] Clarifying picture.
Code paths.
[x] Class definition.
[x] Constructor definition.
[ ] Method definition.
[ ] C++ class construction through JavaScript new.
[ ] C++ function call.
[ ] JavaScript callback function call.
[ ] Object passing by value from JavaScript to C++.
[ ] Object passing by value from C++ to JavaScript.
Data structures.
[ ] Storage of class definitions.
[ ] How different argument and return types are passed between the languages.

See Documentation so far.

Let's track this in a project instead.


some group permissions not updating

Currently on the latest version of GAM at the time of writing this 4.94.  Trying to update whoCanAdd and whoCanInvite setting to allow managers to update groups.  I run the commands to ALL_MANAGERS_CAN_ADD and ALL_MANAGERS_CAN_INVITE.  Commands run fine with no errors but when you run gam info group, the values haven't changed.

Those settings are deprecated, see
https://drive.google.com/file/d/1-ux3z6-hcjsPbhAj_EIwS7cd_emkE-NC/view
You want whoCanModerateMembers OWNERS_ONLY | OWNERS_AND_MANAGERS |
ALL_MEMBERS | NONE
Ross
On Wed, Sep 11, 2019 at 10:17 AM sgymchan<EMAIL_ADDRESS>wrote:

Currently on the latest version of GAM at the time of writing this 4.94.
Trying to update whoCanAdd and whoCanInvite setting to allow managers to
update groups. I run the commands to ALL_MANAGERS_CAN_ADD and
ALL_MANAGERS_CAN_INVITE. Commands run fine with no errors but when you run
gam info group, the values haven't changed.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jay0lee/GAM/issues/1010?email_source=notifications&email_token=ACCTYLZLPDZZFN5YDR3FFSDQJERZ5A5CNFSM4IVWVCGKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HKY4EVQ,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACCTYLZCAWYJ23OYEPRFRTTQJERZ5ANCNFSM4IVWVCGA
.

--
Ross Scroggs
<EMAIL_ADDRESS>


UI-Mask remains $dirty when used inside of ng-repeat and form.$setPristine is called.

I created a Plunker. Change the field and hit 'Reset'. You will see the form and field stay dirty. Clicking a second time sets everything to $pristine properly. Interestingly enough, you don't actually have to change the field - just click Reset and the field and form will be marked dirty without even doing anything!
ng-repeat seems to have some weird behavior where it creates a new element temporarily when $setPristine is called. This causes ui-mask's initializeElement() to be called, which tries to avoid dirtying the form by setting $viewValue directly rather than using $setViewValue, but the form still seems to be dirty afterwards.
          function initializeElement(){
            ...
            iElement.val(viewValue);
            controller.$viewValue = viewValue;  // THIS LINE SEEMS TO DIRTY THE FORM
            // Not using $setViewValue so we don't clobber the model value and dirty the form
            // without any kind of user interaction.
          }

Commenting out the line marked in the code snippet above seems to fix the part of the problem with ng-repeat (the first click doesn't dirty the form anymore),  but it doesn't seem like a good fix. And, there is the problem of the form still being dirty after the first call to $setPristine() anyways. Even using the field outside of an ng-repeat seems to have a similar problem with $dirty being set after changing the field and then calling $setPristine(). It does not have the problem when not changing the field, however.
Note: This uses the 0.2.1 version of ui-mask modified slightly with the fix in #350 as we want clearOnBlur working properly.
FYI, for some reason I couldn't get the plunker to behave exactly the same as the code in my app... in my app, commenting out the above line seems to fix the problem entirely (still probably not a correct fix though).

UI.Utils modules was split in individuals repositories. If still valid, please consider re-submitting on its dedicated repository: https://github.com/angular-ui/ui-mask
See the README for details.


[BUG] thrown egg entity shows vanilla egg texture

Steps to reproduce:
throw any colored egg
What happens:
the entity renders the texture of the vanilla chicken egg

Chickens: 5.0.0
Minecraft: 1.11.2
Forge: <IP_ADDRESS>5

im thinking this was a "lazy" way of doing it maybe ? xD

probably, yeah, but changing the color is as easy as adding a single call to GLStateManager.color() to the Renderer class...

Its been meaning to get fixed, but hasn't been high on the list of things to get changed.

Getting fixed next update.. 1.12, I look into backporting later.

https://github.com/setycz/ChickensMod/commit/ba5e0ae9204c3fda6b202858ac7e8fbdd66232dd


Collaboration performance on slow upload connections

We've been using Excalidraw collaborative sessions and encountered issues where the updates being sent take an exceptionally long time to make it to other participants. The updates seem to get queued up and slowly propagated to the receiving participant at a rate slower than the updates are being sent, leading to one participant's view potentially being minutes behind another's.
How can we go about diagnosing this? Could it be upload latency to the server? We're all in Australia if that helps.

I've been seeing very bad lag and voicing similar concerns over the last few weeks myself. I'm in Europe, but with a 100Mbit uplink, so I'm thinking latency. But the upload bottleneck is indeed a consideration as well as we're sending upwards of tens of updates per second, where each individual update could in theory climb up to hundreds of kbs.

we designed the protocol so we can drop any queued updates and only send the latest. @idlewinn can socket.io tell us when a message was successfully delivered?

I think switching mouse movements to be volatile will help with this - I landed support for this on the socket server but never went back to fix this on the client - at the time there were some changes being worked on that I didn’t want to conflict with. Since we’re seeing perf issues that would be a good start since it’s likely by far the most common type of update.

Following up, I think more aggressively using volatile messages is the best solution for this. Queued updates on a slow connection are part of socket.io's design assuming that these updates are all critical, and volatile updates are thrown away if they're not ready to be received (which I think makes sense for mouse movements - we don't care that the animation of the mouse is perfect, we just want it to be as up to date as possible). Let's start with that and debug further if it continues to be a problem.

Is there a way to mark “Last one wins”, so if there are many in the queue you can drop everything but the last one?

Hmmm, haven't really found a good solution for that yet. you'd think there would be....

I encounter the issues mentioned above on excalidraw.com: when I'm drawing, collaborators receive the drawing and my mouse location with a delay that is increasing as I keep drawing more and more. Indeed some form of queueing seems to be the problem. Interesetingly enough sometimes the throughput is instant, but then for no apparent reason it changes to the slow behavior. My collaborators and I are all in Europe (actually on the same connection) with 600MBit/s symmetric internet speed.
Can I be of help with diagnostics?

We'll need to fine tune our collab server, consider optimizations such as backpressure, but also probably just add more servers because you guys are collaborating a lot lately that even our upgraded server is starting to sweat 😊


Elastic Beanstalk stack creation failed

Hi,
On branch xray-gettingstarted using 2-deploy.sh fails to create stack properly. My user has admin access.
Below are few things I did to make it work. Please see if we can fix this or if I am doing something wrong.
Hopefully this is helpful for anyone else facing same issues. I am not sure if these are ideal fixes but I was able to being up the stack.

Minor: stack complains its using unsupported platform version. I changed arn:aws:elasticbeanstalk:::platform/Java 8 running on 64bit Amazon Linux to arn:aws:elasticbeanstalk:::platform/Corretto 8 running on 64bit Amazon Linux 2/3.2.5.
stack creation failed due to error Attribute: EndpointURL was not found for resource: BETA. Rollback requested by user. Underlying errors that caused this:
2.2. AWSEBLoadBalancer failed to create with reason Issue found with the default subnets: VPC vpc-189b1e73 has no internet gateway (Service: AmazonElasticLoadBalancing; Status Code: 409; Error Code: InvalidConfigurationRequest; Request ID: 7b5d4f96-8148-40d5-ba7f-896dc2c74d5c; Proxy: null)
Solution: I created InternetGateway and assigned to VPC manually
2.3. Elastic BeanStalk environment stack fails with error WaitCondition timed out. Received 0 conditions when expecting 1. My guess is, EC2 instance that gets spun up doesn't make HTTPS call to satisfy wait condition.
Solution: Not sure if this is a definite fix, but I spun up a EC2 instance with my key pair within same VPC, Security group and added NAT gateway route to routing table and logged in to instance, and executed that https request.
Minor: template.yml has email parameter, if it's mandatory for updating that email, 2-deploy.sh script should probably ask for this variable and pass it on.

Hi Gautam, thanks for your feedback
1 - Platform is updated to Corretto 8 in https://github.com/aws-samples/eb-java-scorekeep/pull/18
2 - vpc-189b1e73 has no internet gateway indicates that your default VPC's internet gateway has been deleted. This is not common but it will prevent you from creating Elastic Beanstalk environments in your default VPC.  Try using the VPC console to recreate your default VPC
3 - This is intentional, to show an error in the service map and how to find the exception. See the readme or tutorial for instructions.

The v2 release for the xray-gettingstarted branch is published: https://github.com/aws-samples/eb-java-scorekeep/releases/tag/xray-gs-v2


Add LoadIrepFile()

Propose a solution for #61

I do not know the reason why the CI will get an error.

golint's gopath changed a while back, and it hasn't been updated here is my guess.
@mitchellh do you mind if I fix this, and at the same time bump travis to be testing against 1.9, 1.10 and 1.11 instead of the versions we're supporting?

try rebasing and force pushing now.


netrw :Rexplore overwrites the 'plus' register

I have 'unnamedplus' in my 'clipboard' setting.
I find that :Rexplore changes the value of the 'plus' register.
While :Explore has code to save/restore some registers, I did not see (may have missed it) any code in :Rexplore to do the same

Not exactly sure what is the purpose of netrw_starkeep, it seems to be used for saving/restoring the star register, similar to keepregstar.
I don't know whether it is related to this problem, but shouldn't the same be done with the plus register?

Yes -- please try v162d of netrw (http://www.drchip.org/astronaut/vim/index.html#NETRW

Fixed in v162d


Updated swagger and internal client since the removal of eboks

Updated swagger and internal client since the removal of eboks provider

version change is required

Added


New sample script: list all tenant-wide extensions

Related to https://github.com/pnp/office365-cli/discussions/1377
Make sample script showing how to list all tenant-wide extensions, their IDs and status. Configuration is stored in a hidden list in the tenant app catalog site. This script would show how to get all entries from this list with the relevant fields.

Hi Waldek, May I take this up.

Please do! Appreciate your help 👏


Add colab version to all tutorials

All tutorials need to be available on colab.
Not a hard task, just need to install the dependencies at the beginning of the notebook and add the colab badge.

[ ] fasterrcnn_voc
[x] hub_detr_finetune_pennfundan
[ ] hub_detr_finetune_wheat
[ ] mantisshrimp-fasterrcnn
[ ] parser
[ ] wheat

Wheat and mantisshrimp-fasterrcnn is done, working on others. Will submit a PR for all at once. Please add pets too, its colab version is also ready.

Nice!! You just need to work on the ones that show on the documentation, the others are probably going to be refactored or removed.
I'll update the list in the OP

Yes that is what I was thinking, thanks for clarifying. 😃

The tutorials described here are outdated, we can open a new issue for this if necessary


LiveShare module not found on running any DataScience command

Install this:
https://pvsc.blob.core.windows.net/extension-builds/ms-python-release.vsix
Run a cell
Crash in finding vsls/package.json

Seems that removing and reinstalling the live share extension fixed the problem.

Actually I can still repro this on the same machine. Just have to reload the vscode window

Ah this only repros if the live share feature flag is on. So we have to fix this before we ship live share support, but not yet.


Chore/601 Refactor random song selection

Summary

Refactor random song selection
Update logging information

It was originally selecting a random song by creating an array of index up to the song count then keeping swapping between them over and over again
I deleted all of that and just opted for selecting a random index instead

Hello, thank you for your contribution!
song.stackランダム演奏番号 being no longer used, can you remove all its references as well?

I have removed all references of stackランダム演奏番号. Ready for review

Looks good to me! Merging it, thank you!


Run through training on Windows ARM64

Migrated from GitLab: https://gitlab.com/meltano/academy/-/issues/18
Originally created by @afolson on 2021-07-19 16:31:53

Background: While looking through WSL issues that folks had during training, I found several references to issues on Windows ARM64 builds that may impact how folks install wsl/dev tools. It would be good to run through the process on a clean install just to see what issues pop up.

View 2 previous comments from the original issue on GitLab


Add automatic chain initialization of chain directories to trinity.

What was wrong?

Added detection for whether these things are initialized and code to do intelligent initialization.  Note that this is just a start, as it won't handle cases where it's a custom chain with custom genesis data, etc.
This PR currently special cases a number of things that will need to be polished out (such as only supporting the ropsten chain and light sync mode.
Cute Animal Picture

@carver looking for review on this.  So much of this is really rough so think of this as a high level review.  Guessing much of this will still morph and change as I figure things out.