info_density: Blockers on the road to testing for the 9.0 release.

This is a list of all blocking issues that need to be addressed in order to begin wider testing of 16/140 information density (as there will certainly be other issues caught in that phase; these are just the most obvious ones).
Non-blocking issues are being tracked in #30476
Bugs

[x] Database-stored line-heights not getting picked up when toggling dense mode

Navbar

[x] Correct size of text in Search box, including placeholder (search results list looks great at 16/140, but probably needs more checking)

Left sidebar

[x] Correct for too-tight spacing between DM unread and usernames (E.g., in the DM area, “Prospero from The Tempest” hugs way tight to 1 when there’s an unread DM from him.)

Views
Inbox

[x] Remove font-size: 15px on .inbox-container

Recent conversations view

[x] DM-related icons (envelope; status circle; group) are anemically small and need to be adjustable
[x] The unread sort icon becomes misaligned with unreads: CZO discussion; this is an issue at legacy sizes, too.

Message rows

[x] Allow timestamps to size larger >> convert existing value to ems
[x] Don't resize EDITED/MOVED markers for now; no space

Compose box

[x] Collapsed compose box has a larger New direct message button than reply button container
[x] Both the dropdown at the topic marker container have height values set to var(--compose-recipient-box-min-height), which is a precise pixel value that may be unnecessary
[x] Banners have their own font-size and line height (15px, 18px) hard-coded in; and there are some layout things tied to those (e.g., the max-height: 36px on .main-view-banner-action-button comes from two 18px line-heights)

Organization settings

[x] Lock links move to second line on 16/140; need a flex rewrite in there
[x] Under Organization profile, the “Preview organization” button looks screwy (might look screwy at legacy sizes, too; check i18n)

Help modal

[x] Revisit widths of the help modal under 16/140 (and also legacy) > stop-gap max-width value set in #30437

Pills

[x] Pills have a bunch of pixel-specific values set on them. Those at the very least need to be expressed as ems at 14px (coordinate with @evykassirer)
[x] Pills are a problem under the Create channel portion of the Channel settings modal

Blockers here have all been addressed. Remaining work leading to 9.0 is being tracked in #30476


Update KOLIBRI_WHL_URL for v0.16.0-alpha8

https://phabricator.endlessm.com/T34559

This requires some kolibri-explore-plugin fixes before we can merge it.

This has been replaced by #116.


fix(standalone): ensure meta service started before starting other services

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Alternative to #16341. Follow the idea of https://github.com/risingwavelabs/risingwave/pull/16341#issuecomment-2063438847. Make @xxchan happy happy.
Checklist

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[x] All checks passed in ./risedev check (or alias, ./risedev c)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

#16410  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @BugenZhao and the rest of your teammates on  Graphite


[googleapis_auth] Add support for non-Google OAuth providers

This change allows consumers of this package to provide their own authorization and token endpoints for use with non-Google OAuth providers.
This is accomplished through the introduction of an AuthEndpoints class, which has properties for these two URIs. There is a single concrete subclass of AuthEndpoints in this package for the Google values (GoogleAuthEndpoints). Consumers wishing to support other providers should subclass AuthEndpoints and provide the appropriate URIs for the provider they wish to support.
Most of the exported APIs now accept an AuthEndpoints parameter whose default value is GoogleAuthEndpoints.
This change should be non-breaking and transparent to existing users.
Fixes https://github.com/google/googleapis.dart/issues/596
Note: there are some added tests in auth_code_test.dart that aren't directly relevant to this PR. They were added in Shorebird's fork to satisfy our coverage checks. Happy to remove them to make this PR cleaner/more focused.

How 'bout a changelog entry?

Done. Wasn't sure about versioning, but a minor bump seemed appropriate.

published!

Awesome! Thanks for the help and quick attention


Used in https://github.com/kubernetes/kubernetes/pull/16232


Add feature to parse "none" as "all" when toggling is activated.

Rather useful functionality that has been requested via several support threads:
https://mixitup.kunkalabs.com/support/topic/issue-when-no-filters-are-selected/
Should probably be added as a configuration option within the controls object, perhaps as follows:
controls: {
   toggleDefault: 'none' // or 'all'
}

controls.toggleDefault
https://github.com/patrickkunka/mixitup/releases/tag/v3.0.0


No scene rendered in android Modal

Current behaviour
No scene render in android Modal view.

Expected behaviour

Code sample

Screenshots (if applicable)

What have you tried
When I try Toggle inspector -> Touchables, then close inspector, all are good, seems its an issue with PagerAndroid, when I switch to PagerScroll, works fine.

Your Environment

software
version

ios or android
android

react-native
0.52.0

react-native-tab-view
1.0.2

node
v8.11.2

npm or yarn
6.1.0

It's an issue with ViewPagerAndroid, upgrade react-native to 0.55+ resolve the issue


Add Dockerfile

Hello,
I thought it would be nice to add a base Dockerfile to poetry. I initially made https://hub.docker.com/r/etiennenapoleone/docker-python-poetry/ but it might be better to include it in the project directly. Let me know if you would do it another way.
Thanks for this great tool!

Seems like it's not needed. Also still use deprecated ON BUILD. Discarding this PR


[stable/weave-scope] add apiVersion

Adding the apiVersion for chart.yaml
to fix the issue: https://github.com/helm/charts/issues/13763
Checklist

[x] DCO signed
[x] Chart Version bumped
[x] title of the PR contains starts with chart name e.g. [stable/chart]

/assign @mattfarina

/lgtm


styling added, but not done

was some conflicts in your PR. @VictorManzanilla remember before any pull request, first fetch latest updates git pull


Markdown cannot contain not latin-1 characters

Markdown cannot be rendered if markdown file has not latin-1 chacters(Japanese characters, emoji etc).
For example, README.md is here
⌘

% grip --version
Grip 3.1.0
% grip README.md

And I accessed http://localhost:5000 then I got following error(and stack trace)
builtins.UnicodeEncodeError

UnicodeEncodeError: 'latin-1' codec can't encode character '\u2318' in position 0: ordinal not in range(256)

How can I avoid this ? (Or is this bug ?)
Thanks for awesome tool.

Ah, yeah, this is indeed a bug.
I was able to take a look tonight. Seems grip wasn't actually encoding the Unicode text it read from the README before sending it off to GitHub, leaving requests to use the default encoding of ISO 8859-1 (latin-1). Just deployed a fix that encodes to UTF-8 and sets the appropriate charset.
Run a pip install --upgrade grip and let me know if this works for you.
Thanks for opening the issue, @syohex!

Thanks for quick fix.
I confirmed that this issue is fixed. :smile:


[Source Request]

Hello Admin, I think it's time to add an extension for the indondesian viewers
So either gomunime or anoboy would be great
Source website

Name: anoboy
Link: https://anoboy.media/
Language(s): subtitle Indonesia

Other details

New url: https://anoboy.monster/

https://anoboy.lol/
https://anoboy.live/home/
Putting these here to close other duplicates

https://anoboy.monster/


 It may be due to no-replacement sampling past the size of arr.
xt::xarray<int8> arr {-1, 1};
auto bin_arr = xt::random::choice(arr, 5);
std::cout << bin_arr;
{ -1,   1, -12,   7,   0}

I will take ownership of this bug and fix it soon :)

We should also implement reservoir sampling (the upcoming std::sample for the method with replacement=false).
Here is the libc++ implementation for C++17 that we can backport:
https://github.com/llvm-mirror/libcxx/blob/0d0b9729271b3ef6c4ac9dfcee3c8c9f4aa79ec9/include/algorithm#L3125-L3144
And the wiki link to the pseudo code for this method:
https://en.wikipedia.org/wiki/Reservoir_sampling#Algorithm_R
that would be really cool...


feat: Add host and port options.

Closes #3

@diasdavid no idea why travis is failing, seems it can't run npm install properly :(


Development php8.1 compatibility (#8)

PHP8.1 Dependency https://github.com/kaskus/mongo-php-adapter/pull/8
Improve testing (#293)
Run workflows every Sunday
Remove failing seed list test
Add instrumentation when connecting
Use Ubuntu 20.04 for tests (#302)
Use internal class instead of now-removed internal function (#301)
PHP 8.2 compatibility - deprecation notice fix (#306)
Avoid using private API to fix regression (#307)
PHP8.2 Dependency
revert old changes overriden by new commit

Conflict resolved by using latest code from alceus

Previous code : https://github.com/kaskus/mongo-php-adapter/commit/7d488cc5b3ba6802d9237a71e5ed8d72391f15e7#diff-9575d640e99515ef6bc2d851fa1fe613da192e8f5b64b57980fd555f6d66fec2R1048
Changes: https://github.com/kaskus/mongo-php-adapter/commit/561496fca4989dc728ed3dda50331aacae62ee9c


Installation requires MPI

Currently, running setup.py instantiates the MPI-aware unit test runner.  This effectively means that in order to install the package (python3 setup.py install), it must be possible to initialize MPI.  However, on some systems (NERSC), MPI cannot be initialized on the login nodes.  This is inconvenient, but when installing from a compute node, the global/common filesystem is mounted read-only.  So we effectively cannot install pytoast to global/common.  We should be able to optionally enable MPI somehow to bypass this.

fixed by 8ff8ce81c65d1c892566423c2ed4d1aa5fc3ceae


[TE8][TC_WNCV_3_1, TC_WNCV_3_2, TC_WNCV_3_4,  TC_WNCV_3_5, TC_WNCV_4_3] CurrentPositionLiftPercentage is optional

Problem
Chip-Tool tries to read CurrentPositionLiftPercentage although it is marked as optional according to the spec. Our device does not have this attribute.
Proposed Solution
Check should not fail if it is not present.

although it is marked as optional according to the spec

Those reads are gated on PICS bits, as far as I can tell.  Was that PICS set correctly for the test?

Indeed if you can use PICS info the file to filter out those

Well, the Test Harness has no selection for PICS? Or did I miss that?

file  /tmp/PICS.txt contains let say:
A_CONFIGSTATUS=0
./out/debug/standalone/chip-tool tests Test_TC_WNCV_2_2 0x12345 --PICS /tmp/PICS.txt
the if = 0 it will skip the test
sadly YAML  cannot simply read the feature map to apply a test (yet hopefully)
then you got
[1643286226417] [32173:84101267] CHIP: [TOO]  ***** Test Step 2 : Reads ConfigStatus attribute from DUT
[1643286226417] [32173:84101267] CHIP: [TOO]  **** Skipping: A_CONFIGSTATUS == false


Check if Sentence is Pangram (Leetcode) in Java Under LGMSOC'21

Aim

Want to add solution for Check if the Sentence is Pangram in Java Under LGMSOC'21.

Details

Problem link - https://leetcode.com/problems/check-if-the-sentence-is-pangram/

Language Used - Java.
@Ayush7614 @ravikr126 please assign me this.
Programming language

[ ] C
[ ] C++
[x] Java
[ ] Python

@Ayush7614 Can I work on this issue, Language - Cpp.

Im preparing for my coding interviews and it would really help me if you assign this question to me
Kindly assign me this
I have immense interest  in codin

##Check if Sentence is Pangram (Leetcode)
class Solution {
public boolean checkIfPangram(String sentence) {
HashSet set = new HashSet<>();
for(char ch : sentence.toCharArray()){
set.add(ch);
}
return set.size()==26;
}
}


pythonPackages: move __attrsFailEvaluation to allow deeper inspection

Description of changes

#324619

The test (nix-build pkgs/test/release/default.nix) continues to pass.
These lines were added in https://github.com/NixOS/nixpkgs/pull/269356.
New derivations reported: https://gist.github.com/philiptaron/918e9ec33ec9e9eddf6c23639643dbb9
Things done

[x] Tested, as applicable:

[x] nix-build pkgs/test/release/default.nix

[x] Fits CONTRIBUTING.md.

I accidentally removed recurseIntoAttrs for Python 3.11 and 3.12. @mweinelt fixed it in #330205.


cmd: add log get and delete subcommands

Added log get and log delete commands (#183 and https://talk.agola.io/t/cli-run-logs-management/59/2)

Updated as requested with the  add of --taskid option

@camandel LGTM! merging. Thanks a lot!


DataCite output schema

i all,
We (https://www.eiscat.se)  plan to provide metadata to B2Find, http://b2find.eudat.eu, so we are looking to set up an OAI-PMH server and I found pycsw.
It would be good to be able to serve both DublinCore and DataCIte, and I found an email thread from 2018 about adding DataCite to the output schemas.
Was there any progress on this? If not I would be willing to contribute, thankful for directions where to start.
Best regards Carl-Fredrik

There is a plugin that produces a bare minimum of DataCite records at
I plan to extend on it and create a proper fork and pull request when I have tested it.

Thanks for the initial work @cfenell, we're interested in this development also.
Some extra resources are:

datacite profile in openaire
a python library to create datacite metadata

Hi, thanks a lot for taking up this project!
I am afraid I have not done anything here recently, but had planned to return to it before EISCAT 3D starts producing data during next year.
I'll be happy to look at your work and test it, and not least to have a good Python library for writing DataCite metadata.
What we have done so far about DataCite is:
Data from our old systems can be browsed through the Schedule:

select Archived Data
click Query
click ranges of blue "A":s
You will then be redirected to a system called Madrigal, where data are archived in files called MADxxx.hdf5
There are also  attached supplemental  files EISCAT_yyyy-mm-dd....hdf5, which are the original data in our own format with an added dataset  /metadata/schemes/DataCite.
Our legacy system however uses Matlab to produce these files and I am looking for an open source replacement for the future. The data and metadata formats to be used in EISCAT 3D are still very much TBD, but the possibility to write DataCite metadata from Jupyter notebooks will almost certainly be required and we still consider to provide OAI-PMH harvesting.

@cfenell, this is now ready to be reviewed, welcoming your thoughts (for example about the use of contentUrl)

Looks good, thanks for the contribution!


[Bug report] The 2nd Y-axis on the right side in the Mixed Time-Series does not allow Label to be vertically aligned on the side!

Screenshot

Description
Currently, the 2nd Y-axis on the right side in the Mixed Time-Series does not allow Label to be vertically oriented on the side. Can this be fixed?
Design input
Naturally, the label should behave the same as the left Y-Axis (which is oriented vertically).

Duplicate of #129472

@rumbin Thanks for pointing that out, should I close this?

I think it makes sense to close this one.


Opinionated Bookkeeper Defaults Decrease Throughput Performance on Large Cluster

The configuration for dbStorage_writeCacheMaxSizeMb and dbStorage_readAheadCacheMaxSizeMb each default to 32.
https://github.com/sky-big/pulsar-operator/blob/2e5d026abdcd4781c41e03f03d7253ccba9eb46c/pkg/pulsar/components/bookie/constant.go#L6-L8
This configuration is very opinionated considering pulsar (and bookkeeper) defaults these values to 25% of the available memory.
https://github.com/apache/bookkeeper/blob/3a8f4b4d3e762ac24a0563eeaffd068efaab2b81/conf/bk_server.conf#L660-L663
I recently discovered that my pulsar cluster was under-performing on throughput because these caches were undersized. Given that there seem to be appropriate defaults in pulsar itself, I think it would be valuable to remove these restrictive defaults. Obviously, I can just override the default and move on, but it took me a while to figure out why my pulsar cluster was under-performing, so I thought I'd share here.
Thanks!

Do you need to be flexible with CRD configuration?

I'm not sure I understand your question. My point is that I don't see any value added by overriding the default behavior provided by pulsar, which is to allocate 25% of direct memory to each of these caches, as shown here. The dynamic defaults make for appropriate sized caches regardless of the size of ones deployment.
To be fair, I was looking at how the pulsar helm chart sets these values, and it appears that the helm chart uses 32 for each config, just like this project.

I'm not sure I understand your question. My point is that I don't see any value added by overriding the default behavior provided by pulsar, which is to allocate 25% of direct memory to each of these caches, as shown here. The dynamic defaults make for appropriate sized caches regardless of the size of ones deployment.
To be fair, I was looking at how the pulsar helm chart sets these values, and it appears that the helm chart uses 32 for each config, just like this project.

yes, it is.

apiVersion: pulsar.apache.org/v1alpha1
kind: PulsarCluster
metadata:
  name: example-pulsarcluster
spec:
  bookie:
    size: 1
    writeCacheMaxSizeMb: 32
    readAheadCacheMaxSizeMb: 32
    image:
      repository: apachepulsar/pulsar-all
      tag: 2.5.0
      pullPolicy: Always

These two parameters can be configurable by adding parameters to the CR configuration file，It just hasn't been implemented yet.

@sky-big - I opened https://github.com/sky-big/pulsar-operator/pull/19 to show you what I'm requesting.


feat: red and pink color palettes and swatches

@rultor good to merge.

@rultor good to merge.

@rafamizes OK, I'll try to merge now. You can check the progress of the merge here

@rultor good to merge.

@rafamizes Done! FYI, the full log is here (took me 3min)

Merged by Rultor.
Closes #57


[Review & Discuss] Preliminar version of bash and bash_

Hey Greg,
this is a first naive attempt to create bash and bash_. A couple of comments:

They internally uses escaping False as it's required for the && and such

We should probably add a note in the function documentation.

I suspect bash_ to be memory inefficient as it does not discard line by line the stdout, can we make it such without boilerplate? (i.e. piggybacking on some internal functions?)
Tests are there but are quite barebone. I didn't go overboard in testing those.

Immediate thoughts?

The sanitizing is brittle but will probably work fine in practice. Just make bash_ use run_

I have amended the PR. I had to essentially duplicate the 2 functions in order for bash_ to use run_ but I think they are small enough for it to not be a biggie. If you can think of a way to keep this DRY then let me know and I will amend accordingly.

it could be DRYed, but it is only 2 spots. My rule is always DRY when there are 3.

thanks! released as 1.6.3

Thanks for reviewing and merging!


feat: handle partial state objects

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Fix/Feature

What is the current behavior? (You can also link to an open issue here)

The input states are expected to be 'complete' objects, according to the AtemState definition. If some expected keys are missing, that can result in TypeErrors being thrown.

What is the new behavior (if this is a feature change)?

The library should be able to handle partial objects. When any keys are missing, the 'default' values should be used instead

Other information:

This has not yet been tested, and could do with some work to test edge cases. It should be possible to automate this by taking complete state objects, deleting random keys and making sure a resolve doesnt error.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@74d5682). Click here to learn what that means.
The diff coverage is 89.86%.

@@            Coverage Diff            @@
##             master      #18   +/-   ##
=========================================
  Coverage          ?   95.06%
=========================================
  Files             ?       18
  Lines             ?      446
  Branches          ?      140
=========================================
  Hits              ?      424
  Misses            ?        7
  Partials          ?       15

Impacted Files
Coverage Δ

src/atemState.ts
91.66% <ø> (ø)

src/resolvers/mixEffect.ts
88.54% <77.08%> (ø)

src/resolvers/upstreamKeyers/index.ts
92.68% <84.61%> (ø)

src/resolvers/supersource.ts
95.31% <92.00%> (ø)

src/defaults/video.ts
96.00% <100.00%> (ø)

src/resolvers/audio.ts
100.00% <100.00%> (ø)

src/resolvers/downstreamKeyer.ts
100.00% <100.00%> (ø)

src/resolvers/index.ts
100.00% <100.00%> (ø)

src/resolvers/macro.ts
100.00% <100.00%> (ø)

src/resolvers/media.ts
94.11% <100.00%> (ø)

... and 5 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 74d5682...68bb82d. Read the comment docs.

Some tests have been written as part of #20 (they are dependent on further changes added there).


How to use it with Nuxt ?

I have the answer, simply add a ~/plugins/tilt.js file with the imports :
import Vue from "vue";
import VueTilt from 'vue-tilt.js'
Vue.use(VueTilt)

then add to your html template the v-tilt attribute

@MattixNow Nice 👍
Good to see, that you've found a solution.


Add missing 2021 RAV4 TSS2 esp FW

From dongle b97486b552c1f5e3

For reference, this user's car responded only to the [TESTER_PRESENT_REQUEST, DEFAULT_DIAGNOSTIC_REQUEST, EXTENDED_DIAGNOSTIC_REQUEST, UDS_VERSION_REQUEST] request.


[e2e]: nodejs release main default slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/6129317797
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.release.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.release.main.default.slsa3.yml
Trigger: schedule
Branch: main
Date: Sat Sep  9 06:09:02 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/v40.0.84
Run: https://github.com/slsa-framework/example-package/actions/runs/6135476862
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.nodejs.release.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.nodejs.release.main.default.slsa3.yml
Trigger: release
Branch: v40.0.84
Date: Sun Sep 10 06:15:25 UTC 2023
Tests are passing now. Closing this issue.


rubocop linting

Let's add it! You can see first steps here - https://github.com/postmodern/command_kit.rb/compare/main...gurgeous:rubocop?expand=1
I used rubocop --auto-gen-config to create a starter config. The config disables rules that conflict with the current code. In other words, running rubocop autocorrect will produce zero changes. I created a preview gist that shows how enabling each rule would affect the source. It's not exactly meant for reading, but you can search in there to see how each rule works.
We can use editorial discretion to turn on some rules. It's totally up to you, but I'd suggest enabling some. Let rubocop do work for us. For example, see DuplicateMethods, MutableConstant, or UselessAssignment. Could be real bugs in there. I'd also suggest turning on rules to enforce our preferred style if possible. For example, consider Style/StringLiterals: { EnforcedStyle: double_quotes }.
What do you think? Would you like me to recommend specific rules?

Awesome!
I reviewed the list of 1 or 2 violations, and fixed the following:

DuplicatedAssignment
ElseAlignment
EndAlignment
IndentationWidth
DuplicateMethods
UselessAssignment
Encoding
RedundantBegin
RedundantInterpolation
TrailingCommaInArrayLiteral

The following rules might just need exclusions:

RescueException (exclude lib/command_kit/exception_handler.rb:42)
UnreachableLoop (exclude lib/command_kit/interactive.rb:129)
QuotedSymbols (exclude spec/inflector_spec.rb:26)
RedundantException (exclude spec/exception_handler_spec.rb:76)

I will need to refactor Inflector.camel_case to get rid of UnusedBlockArgument (also not happy with using Regexp.last_match).
RedundantRegexpEscape referring to lib/command_kit/commands/subcommand.rb:59 looks invalid (the regexp is supposed to match all non-. characters starting at the beginning of the first line).
I couldn't easily fix MissingSuper in lib/command_kit/commands/auto_load.rb:76, as adding super() caused two specs to fail with:
     TypeError:
       no implicit conversion of nil into String
     # ./lib/command_kit/commands/auto_load.rb:141:in `join'
     # ./lib/command_kit/commands/auto_load.rb:141:in `join'
     # ./lib/command_kit/commands/auto_load.rb:124:in `command'
     # ./spec/commands/auto_load_spec.rb:34:in `block (5 levels) in <top (required)>'
     # ./lib/command_kit/commands/auto_load.rb:77:in `initialize'
     # ./lib/command_kit/commands/auto_load.rb:77:in `initialize'
     # ./spec/commands/auto_load_spec.rb:33:in `new'
     # ./spec/commands/auto_load_spec.rb:33:in `block (4 levels) in <top (required)>'
     # ./spec/commands/auto_load_spec.rb:40:in `block (4 levels) in <top (required)>'

Great start! I merged your fixes into my branch. Few comments -

In case you haven't tried it, rubocop -A will autocorrect the majority of issues. When we decide to adopt a rule, often you can do it without manual changes.
UnreachableLoop - Took a quick peek. Is there any need for the loop? As rubocop said, it seems to only run once. My personal code golf would probably produce answer = ask(...) ; !!(answer =~ /^y/i) or similar 😛
QuotedSymbols - We can tell rubocop to always use double quotes
RedundantException - Can we just raise "error" ?
RedundantRegexpEscape - I think no backslash required for dot inside [xxxx]
MissingSuper - No clue on this one. I like the rule, though. It's saved me from bugs in the past. It's possible to get around stuff like this with rubocop comments if we decide to turn on the rule.

I know rubocop can be a pain, sorry. The nice thing about building a decent .rubocop.yml is that you can reuse it across projects and enforce your desired style everywhere.
How should I proceed? I can tell you are having fun with this and I don't want to step on your toes 😄

UnreachableLoop - Took a quick peek. Is there any need for the loop? As rubocop said, it seems to only run once. My personal code golf would probably produce answer = ask(...) ; !!(answer =~ /^y/i) or similar ￼

The loop is used to re-print the input prompt if the user entered an invalid answer, or if they just hit <enter> and a response is required.

QuotedSymbols - We can tell rubocop to always use double quotes

See the offending spec. I suppose it could be rewritten as "Foo::Bar".to_sym. Also I think :"foo" syntax is useful for when you want to define a symbol that contains spaces or other non-alpha-numeric characters.

RedundantException - Can we just raise "error" ?

Uh sure. Although I kind of like specifying the exception class explicitly, even when it's RuntimeError.

RedundantRegexpEscape - I think no backslash required for dot inside [xxxx]

Ah I think you're right. However, I would argue that you should always escape . within a regexp, even inside a [ ] range, as . is normally interpreted as any-char.
As long as we can disable the pedantic or annoying rubocop rules, I'm fine with rebasing and merging it. It will help automate away some of the code review work.

The loop is used to re-print the input prompt if the user entered an invalid answer, or if they just hit <enter> and a response is required (ex: ask("Must answer", required: true)).

I think I see the confusion. Look at line 129 (not line 199) 😄

QuotedSymbols - We can tell rubocop to always use double quotes

See the offending spec. I suppose it could be rewritten as "Foo::Bar".to_sym. Also I think :"foo" syntax is useful for when you want to define a symbol that contains spaces or other non-alpha-numeric characters.

I believe rubocop wants to change it to :'Foo::Bar' (single quote). We can have it format with double quotes if you want, though.

RedundantException - Can we just raise "error" ?

Uh sure. Although I kind of like specifying the exception class explicitly, even when it's RuntimeError.

There are a lot of fringe rubocop rules like this... We can just turn rules off whenever we have a stylistic preference. Here's an example from one of my other projects.

RedundantRegexpEscape - I think no backslash required for dot inside [xxxx]

Ah I think you're right. However, I would argue that you should always escape . within a regexp, even inside a [ ] range, as . is normally interpreted as any-char.

Regex is a dark art and I have no objection to leaving in the backslashes.

As long as we can disable the pedantic or annoying rubocop rules, I'm fine with rebasing and merging it. It will help automate away some of the code review work.

Sounds good. I'll try to re-enable the rules that you fixed and put up a PR. I usually just use github's squash and merge button in lieu of a rebase... You can make that the default for the repo if you want, I think. Happy to rebase manually if you prefer that. Just LMK
Thanks @postmodern this is great!

Quick question. I'm a little worried about using -A to auto-fix issues. Wouldn't this cause issues if we added bundle exec rake rubocop to the GitHub Actions CI pipeline and a contributor sent a malformed PR? We'd probably want to flag but not auto-correct the PR.

Good question, I'm leery of that too. Linting is nice but it feels wrong to have it break CI IMO. I've used these a couple of different approaches in the past:

Precommit hook (bail if anything chages). This is good for projects where you can enforce a convention.
Run on rake release (bail if anything changes). This is good for gems. As a maintainer I just get in the habit of running rake rubocop occasionally to clean things up.

Happy to help set something up.

We could hook rubocop into the release task as a "pre-flight check". I'm mainly concerned with checking PRs for bad syntax and getting contributors to fix bad syntax before I have to manually review it or it gets merged prematurely.

OK, let's start with the CI. We can run rubocop -A manually (via rake or otherwise), and encourage contributors to do the same. Maybe this?
name: rubocop
on: [ push, pull_request ]
jobs:
  rubocop:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - name: Set up Ruby
        uses: ruby/setup-ruby@v1
        with:
          ruby-version: 2.7
      - name: Install dependencies
        run: bundle install --jobs 4 --retry 3
      - name: Run rubocop
        run: bundle exec rubocop --parallel

@gurgeous looks good to me. What's the standard practice for adding linting to GitHub Actions CI: should it be added to the existing testing workflow, or should a new workflow be created to keep the two separate?

Not totally sure. It could probably be another job in the same workflow since they share the same properties (push/pull_request). Harmless to make it a separate workflow, though.


Allow customization of firmware image headers

Currently every firmware image we create with from_elf has hard coded flash attributes
https://github.com/esp-rs/espflash/blob/eeb0e8f95d184209cc42be9c4fec15c7172729fc/espflash/src/elf.rs#L49-L57
We should add CLI options to configure these, for the cases where the flash size of a chip may be different (see: https://github.com/esp-rs/esp-idf-template/issues/15)

Should hopefully have a PR ready for this tomorrow.


Login feature

I would like to add a feature where user login first then able to access website.
Please assign me this issue under GSSoC'24.

I think login is not necessary atleast upto now. Maybe we can consider it in future.

I think login is not necessary atleast upto now. Maybe we can consider it in future.

@Abidsyed25 Then can you please assign me a issue where i can work on?

Yeah sure, If I found any issue I will assign it to you. Till then if you find any bug in the existing site you can open an issue and work on it.

Yeah sure, If I found any issue I will assign it to you. Till then if you find any bug in the existing site you can open an issue and work on it.

Okay thankyou!!


fix codecov.yaml

What type of PR is this?

What this PR does / why we need it:
Sorry, the threshold is not to reach a number.
Is allow the coverage to drop by %, and posting a success status.
refer to https://docs.codecov.com/docs/commit-status
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

/hold


Incimpatible with swiping

Regression?
No
Hyprlock Info and Version
Hyprlock version 0.5.0
Compositor Info and Version
Infos

Hyprland 0.45.0 built from branch  at commit b1003445953474b967464d4d0878955d37498647  ().
Date: 2024-11-22
Tag: , commits:
built against aquamarine 0.5.0
flags set:
debug
System Information:
System name: Linux
Node name: home
Release: 6.6.62
Version: #1-NixOS SMP PREEMPT_DYNAMIC Sun Nov 17 14:08:59 UTC 2024

Description
I have this in my hyprland config (Nix)
gestures = {
workspace_swipe = true;
workspace_swipe_touch = true;
workspace_swipe_cancel_ratio = 0.1;
};
And when I swipe while hyprlock is enabled, I can swipe worspace
How to reproduce

Buy a touchscreen
Add the config I mentioned earlier to hyprland (convert to hyprlang btw)
hyprlock
Swipe from edges
Unlock
See that you changed workspace

Crash reports, logs, images, videos
No response

that's a hyprland issue


Do not show frame

what should I do   like electron  set frame:false ?

That's not a feature currently, but you could consider submitting a PR.


[CT-1610] [Bug] Private key got changed when changing bigquery timeout in cloud UI

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
I changed the bigquery timeout in the cloud UI which somehow erased the private key. The first change was possible which seemed to have overwritten the existent private key. After this change dbt was unable to query bigquery. Afterwards I was unable to change the timeout value again as the private key field showed up empty.
The bug seemed to be related to the way the settings are stored in the cloud UI where settings and credentials seem to be stored together.
Screenshot where I changed the value:

Expected Behavior

Changing the timeout value in the cloud UI without overwriting the existing private key.
The settings should be changed individually for each environment IMO.

Steps To Reproduce

in the cloud UI
I changed the bigquery timeout in account settings
--> Settings
--> Account Settings
--> Project Settings
--> Connection
--> Edit Timeout
--> Save
run dbt run (or any other dbt command building a model)
see error:
´´´Connection 'list_staffbase-data-dev' was properly closed.
dbt runtime exception
Database Error
Could not deserialize key data. The data may be in an incorrect format or it may be encrypted with an unsupported algorithm.```

Relevant log output
No response
Environment
- OS: macOS v12.4 (Monterey)
- Python:
- dbt: cloud 1.3

Which database adapter are you using with dbt?
bigquery
Additional Context
The problem was solved by uploading a new service account JSON file including a newly created private key.

Hello @kmende94!
If you're a user of dbt Cloud, reaching out to dbt Cloud Support is always a good first bet to get support on bug reports related to the web interface. This issue does in fact look specific to dbt Cloud, so they should be able to send you in the right direction and help to resolve your issue.
There's information on how to reach out to dbt Cloud Support here: https://docs.getdbt.com/guides/legacy/getting-help#dbt-cloud-support

please reach out to us by using the speech bubble (💬) in the dbt Cloud interface or at<EMAIL_ADDRESS>
Hopefully this gets resolved quickly! In the meantime, I'm going to close this issue as not planned, since it's not something we can solve with a change to the dbt-core codebase.


Franklin Dispatcher configurations such as CSP

For Phase 1 we must implement the dispatcher settings on Crosswalk
Content-Security-Policy:
frame-ancestors 'self' https://.danaher.com https://danaher.sharepoint.com https://.decibelinsight.net https://.decibel.com wss://.decibelinsight.net;object-src https://www.bioz.com;base-uri 'self';
and
X-Frame-Options:
SAMEORIGIN

Closing as we have it deployed on stage & prod


xcode 7.3 keyboard above textfield

xcode 7.3
Swift 2.2
Textfield stopped being "attached" to keyboard.
If start entering text - keyboard becomes above textfield, which continue lie on the bottom of view.
yesterday on Xcode 7.2 everything worked fine

Thanks @ADevelopStudio ! :smile:

@jessesquires could you please let me know if it is possible to be fixed soon or not?
basically, I am using your module for one of the projects where due date in 3 days :( and I was shocked when I saw that it stopped working... So, I just wanted to know If it's not so easy to fix - I will need to find something similar. Thanks!

Same problem here. I need to get this fixed 😢

Hey @ADevelopStudio -- can you post a screenshot?

Also, does this happen in the demo project?

Is there any advance with this? I have stuck my project because of this.

This is exactly what is happening:

are you calling super on all view lifecycle methods?

I was missing a super:
override func viewDidAppear(animated: Bool) {
    // missing super here
    self.collectionView?.collectionViewLayout.springinessEnabled = true
}

now is:
override func viewDidAppear(animated: Bool) {
    super.viewDidAppear(animated)
    self.collectionView?.collectionViewLayout.springinessEnabled = true
}

Thanks


Shutdown MockWebServer after response

New SocketPolicy to shutdown MockWebServer after response. More details in #4227

@fred84 if you haven't already, could you complete http://square.github.io/okhttp/#contributing

@yschimke completed


feat: setup instructions, move screenshots

Fixes #24

Move screenshots to /docs/screenshots
Add Project setup details

Please help by following the descriptions in issues. Move the screenshots to /docs/img/

I verified with susi_android repo it was named screenshots but in open-event it was under img, will make it img then.

Please avoid spaces in names.

Hey can you please point me to what you are referring to?

Screen 1.png -> Screen1.png

Ok will fix in a moment.

Please help to resolve merge conflicts.


Avoid toggling welcome message when core/nux is not available

Description
Since the deprecation of the core/nux store, the default WordPress 'welcome guide' modal can only be toggled on or off, not explicitly disabled.
In order to prevent the welcome guide from showing, which can block test execution, we are checking whether it is enabled, then toggling it to disable it.
This appears to cause a situation where the welcome guide is dismissed automatically when Cypress interacts with the page, after which our code (which is intended to dismiss the welcome guide) actually toggles it back on and blocks further test execution.
This is only visible since WordPress 6.2 as this is when the core/nux package was removed, after being deprecated for some time.
By removing the call to toggle the welcome guide, this issue is avoided and it appears that the welcome guide is automatically dismissed without interfering with the test execution.
Change Log

Remove the call to toggle the welcome modal if core/nux is not found

Screenshots/Videos
This has been tested on 6.2 and 6.0 to check backwards compatibility.

Note: I want to test this further especially since the issue doesn't seem to crop up on CI

Types of changes (if applicable):

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

Checklist (if applicable):

[x] Meets provided linting standards.

Closing in favour of #126


Update Gulp scripts to support FTP

FTP support was added in a prior commit. It just hadn't been added to a release yet.


[Refactor] Faster instantiation

woohoo! +112% on creation speed!
@albertbou92 @matteobettini @BY571 @skandermolla
In practice, for torchrl it's a >10% further speedup on data collection speed (but also impacts all other modules)
Can anyone review this?

I see, so defining directly the attributes as class-level attributes is faster at runtime than doing attribute assignment in the new method, is that it?

Yes that and removing slots

Yes that and removing slots

looking forward to see how it affects torchrl speed! :)


Enable ModifierOrderRule

ModifierOrderRule was added to release notes but not enabled, I think this was a mistake? This PR resolved the issue.
If this wasn't a mistake please close this PR.

:man_facepalming: Thank you for noticing @REggar. I'm pretty sure it would take me forever to find it on my own :blush:

@REggar released as part of 0.8.0.


Dynamic compression APIs

Hi,
I maintain a fork of LevelDB (https://github.com/pmmp/leveldb) for reading Minecraft Bedrock worlds.
The only significant difference between mojang/leveldb and google/leveldb is that mojang/leveldb uses more compression types instead of Snappy (primarily zlib).
I currently maintain a fork of google/leveldb to implement support for zlib, and recently realized it might be much better if LevelDB had some dynamic compression APIs, so that custom compressors can be used without making LevelDB depend on every compression library under the sun, and so that other users of LevelDB don't have to fork LevelDB in order to use their own compression algorithms.
This would require the following:

Ability to dynamically map compression IDs to decompressor callbacks (Snappy would remain as 1, everything else would be user-defined)
Ability to provide a custom compressor callback (and compression ID) for output of compressed data.

Is this the kind of change that would be suitable for LevelDB itself, or should I continue to maintain a fork?
Thanks.

The addition of zstd as hardcoded ID 2 now makes upstream compatibility with google/leveldb a pain for anyone who used ID 2 for a different compression type.


feat (admin): Add edit list item route

Resolves #1387
Resolves #1528
Resolves #1520

@LukasStoeckli With the current client code generation framework, each endpoint has to have a single base URL path for all its routes. For the lists endpoint, this is currently admin/lists. In this PR you have some list routes that use admin/lists and others that use admin/nodes. Can you change admin/nodes to admin/lists/nodes, so that all the list routes start with admin/lists?

sure

if you need my help integrating this PR into knora-api-s-lib, please let me know. Ideally, this would be automated, see #1554

if you need my help integrating this PR into knora-api-s-lib, please let me know.

@tobiasschweizer Yes please. The semantics of the list update API have changed, so some of the existing client API functions and test data had to be replaced.

What has changed exactly and how could this affect existing code?

What has changed exactly and how could this affect existing code?

@tobiasschweizer The client function updateListInfo has been removed, and the following client functions have been added:

updateListName
updateListLabels
updateListComments
updateListNodeName
updateListNodeLabels
updateListNodeComments

Each of the new functions has new test data.

So this means that the test for updateListInfo has to be removed and tests for the new methods have to be added using the new test data?
This may also affect @kilchenmann and @flavens since the admin method are already in use.

So this means that the test for updateListInfo has to be removed and tests for the new methods have to be added using the new test data?

That's right.

This may also affect @kilchenmann and @flavens since the admin method are already in use.

Yes. I had understood that the existing functionality wouldn't be changed, but it looks like that wasn't feasible.

Yes. I had understood that the existing functionality wouldn't be changed, but it looks like that wasn't feasible.

What functionality exactly?

@benjamingeer @LukasStoeckli @tobiasschweizer we do not need to edit anything in the ui modules or lib. All the methods come from the knora-api-js-lib. If Tobias does change the name of the methods, it is all good for us on this point!

The issues addressed in this PR are implemented in #1753.


Firestore iOS SDK "Could not reach Cloud Firestore backend " on iOS simulator behind socks5 proxy.

[REQUIRED] Step 1: Describe your environment

Xcode version: 11.4
Firebase SDK version: 6.20.0
Firebase Component: Firestore
Component version: 1.11.2
Installation method: CocoaPods | Carthage | Zip file (select one)
CocoaPods

[REQUIRED] Step 2: Describe the problem
Everything works fine on real device. Cannot connect to firestore backend on iOS simulator.
My mac and iPhone are both using same socks5 proxy service. When i run the app on device, everything works fine, but error showed on iOS simulator.
I did some research, maybe the reason is that gRPC doesn't support socks5 proxy. Is there any way to solve this? I really don't get it why it works on device but not on simulator. Many thanks!
I'm in China, so I have to use proxy to call google service.
Steps to reproduce:
turn socks5 proxy on on your mac (shadowsocks or v2net, eg)
run any firebase project on simulator
What happened? How can we make the problem occur?
This could be a description, log/console output, etc.
[Firebase/Firestore][I-FST000001] Could not reach Cloud Firestore backend. Connection failed 1 times. Most recent error: failed to connect to all addresses  This typically indicates that your device does not have a healthy Internet connection at the moment. The client will operate in offline mode until it is able to successfully connect to the backend.
If you have a downloadable sample project that reproduces the bug you're reporting, you will
likely receive a faster response on your issue.

@jerrypainter, thanks for writing in!
As you suspected, gRPC does not support SOCKS5 proxies. I can't really explain why it would work on a real device but not on a simulator--Firestore and gRPC aren't doing anything to connect to the local SOCKS server.
The latest discussion I can find on this is a mailing list conversation from 2017. gRPC does support traditional HTTP proxies, and you can configure this with environment variables.
Unfortunately, without support for this from gRPC, there isn't anything we can do in the Firestore client to support your use case.


Bypassing Row Level Security Not working

Bug report
Describe the bug
Hi, so stated in the documents I can use the service_role key to bypass row level security (in my server)
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:

Initialise with the service key

const supabase = createClient(SUPABASE_URL, SUPABASE_SERVICE_KEY, {
  localStorage: AsyncStorage as any,
  persistSession: true,
  autoRefreshToken: true
});

Normal supabse call to RLS protected table:

    const { user,error } = await supabase
      .from('profiles')
      .update({
        first_name: 'Testing',
        last_name: 'Bypass'
      })
      .eq('user_id', '0fcd924a-d90b-48a2-af43-f7e7df4ca2a8');

Expected behavior
The users first and last name should be changed by the server even with the policies set as (uid() = user_id)
System information

Version of supabase-js: 1.25.2
Version of Node.js:12

I ran into something that looks similar to this - not sure if you're still having the issue, but for future users or others looking into this, I found the problem occurred when I had two clients with different keys, or was logged in (as a user) whilst trying to use the service key, e.g.
const supabase = createClient(SUPABASE_URL, SUPABASE_ANON_KEY, ...)
const adminClient = createClient(SUPABASE_URL, SUPABASE_SERVICE_KEY, ...)

// try to use adminClient, fail to circumvent RLS
// If you sign out, the same code (with adminClient, not supabase here) works

Not sure if that should be a bug or not, but I managed to get what I wanted to do (seeding the db, mostly) working when I signed out first.

This is working correctly now afaict - for folks having the issue above, you can set the storageKey option so the anon client signing in/out doesn't affect the admin client's creds.

what may i do if im using the supabase-py library, as there's no storage_key option in create_client's ClientOptions?


Auditing with mikro-orm

I'm looking for a way to implement auditing (entity history / change tracking) for my application. The ORM layer might be a fitting place for this. The concept of change sets is already there and the auditing isn't in any way specific to my application. Hibernate, for example, offers Envers for that purpose.
Now I'm not asking for this as a feature, I can see how this is a bit out of scope. My question is, would you advise me to implement this in my application layer, or is there another, smarter way where I could hook into mikro-orm or reuse stuff?  Any suggestions?

Check the onFlush event, it allows to hook into the change set tracking and do pretty much whatever you want, e.g. you can handle soft deletes this way:
https://github.com/mikro-orm/mikro-orm/issues/1492#issuecomment-785394397
https://mikro-orm.io/docs/lifecycle-hooks/#using-onflush-event


[tutorials] rllib tutorial text

The notebook has the following print output, which looks like a spurious error, can we perhaps re-run it? This is the tutorial most likely to be visited, so I'm marking it as high priority.
Remote function stop failed with:

Traceback (most recent call last):
  File "/home/aboudy/Documents/ray/python/ray/worker.py", line 862, in _process_task
    *arguments)
  File "/home/aboudy/Documents/ray/python/ray/actor.py", line 245, in actor_method_executor
    method_returns = method(actor, *args)
  File "/home/aboudy/Documents/ray/python/ray/tune/trainable.py", line 258, in stop
    self._stop()
  File "/home/aboudy/Documents/ray/python/ray/rllib/ppo/ppo.py", line 274, in _stop
    ev.__ray_terminate__.remote(ev._ray_actor_id.id())
  File "/home/aboudy/Documents/ray/python/ray/actor.py", line 432, in remote
    return self._submit(args, kwargs)
  File "/home/aboudy/Documents/ray/python/ray/actor.py", line 443, in _submit
    dependency=self._actor._ray_actor_cursor)
  File "/home/aboudy/Documents/ray/python/ray/actor.py", line 746, in _actor_method_call
    args = signature.extend_args(function_signature, args, kwargs)
  File "/home/aboudy/Documents/ray/python/ray/signature.py", line 214, in extend_args
    .format(function_name))
Exception: Too many arguments were passed to the function '__ray_terminate__'

  You can inspect errors by running

      ray.error_info()

  If this driver is hanging, start a new one with

      ray.init(redis_address="<IP_ADDRESS>:45220")

Looking into this; if someone solves this first, ping me so I stop

I had that error until I removed all the import ipdb; ipdb.set_trace() from my local ray. After which, I'm unable to reproduce that error. This is what I get instead:
== Status ==
Using FIFO scheduling algorithm.
Result logdir: /Users/kathyjang/ray_results/ring_stabilize
PENDING trials:
 - PPO_WaveAttenuationPOEnv-v0_0:	PENDING

Created LogSyncer for /Users/kathyjang/ray_results/ring_stabilize/PPO_WaveAttenuationPOEnv-v0_0_2018-09-06_13-54-04a3bfu7pz ->
== Status ==
Using FIFO scheduling algorithm.
Resources requested: 1/4 CPUs, 0/0 GPUs
Result logdir: /Users/kathyjang/ray_results/ring_stabilize
RUNNING trials:
 - PPO_WaveAttenuationPOEnv-v0_0:	RUNNING

TrainingResult for PPO_WaveAttenuationPOEnv-v0_0:
  date: 2018-09-06_13-54-33
  done: true
  episode_len_mean: 100.0
  episode_reward_mean: -618.7483764247104
  experiment_id: 6e288a62b5154bd29d39e429c252e365
  hostname: Kathys-MacBook-Pro.local
  info:
    kl_coefficient: 0.1
    kl_divergence: 1.4180838661559392e-05
    load_time: 0.08836102485656738
    rollouts_time: 5.992580890655518
    sample_throughput:<PHONE_NUMBER>3213805
    sgd_time: 1.6662120819091797
    shuffle_time: 0.00016307830810546875
  node_ip: <IP_ADDRESS>
  pid: 13922
  time_this_iter_s: 10.317247867584229
  time_total_s: 10.317247867584229
  timestamp:<PHONE_NUMBER>
  timesteps_this_iter: 400
  timesteps_total: 400
  training_iteration: 1

Remote function stop failed with:

Traceback (most recent call last):
  File "/Users/kathyjang/research/ray/python/ray/worker.py", line 864, in _process_task
    *arguments)
  File "/Users/kathyjang/research/ray/python/ray/actor.py", line 245, in actor_method_executor
    method_returns = method(actor, *args)
  File "/Users/kathyjang/research/ray/python/ray/tune/trainable.py", line 257, in stop
    self._stop()
  File "/Users/kathyjang/research/ray/python/ray/rllib/ppo/ppo.py", line 274, in _stop
    ev.__ray_terminate__.remote(ev._ray_actor_id.id())
  File "/Users/kathyjang/research/ray/python/ray/actor.py", line 432, in remote
    return self._submit(args, kwargs)
  File "/Users/kathyjang/research/ray/python/ray/actor.py", line 443, in _submit
    dependency=self._actor._ray_actor_cursor)
  File "/Users/kathyjang/research/ray/python/ray/actor.py", line 749, in _actor_method_call
    args = signature.extend_args(function_signature, args, kwargs)
  File "/Users/kathyjang/research/ray/python/ray/signature.py", line 216, in extend_args
    raise Exception("Too many arguments were passed to the function '{}'"
  File "/Users/kathyjang/research/ray/python/ray/signature.py", line 216, in extend_args
    raise Exception("Too many arguments were passed to the function '{}'"
  File "/Users/kathyjang/anaconda/envs/kathy/lib/python3.5/bdb.py", line 48, in trace_dispatch
    return self.dispatch_line(frame)
  File "/Users/kathyjang/anaconda/envs/kathy/lib/python3.5/bdb.py", line 67, in dispatch_line
    if self.quitting: raise BdbQuit
bdb.BdbQuit

  You can inspect errors by running

      ray.error_info()

  If this driver is hanging, start a new one with

      ray.init(redis_address="<IP_ADDRESS>:27387")

== Status ==
Using FIFO scheduling algorithm.
Resources requested: 0/4 CPUs, 0/0 GPUs
Result logdir: /Users/kathyjang/ray_results/ring_stabilize
TERMINATED trials:
 - PPO_WaveAttenuationPOEnv-v0_0:	TERMINATED [pid=13922], 10 s, 400 ts, -619 rew

== Status ==
Using FIFO scheduling algorithm.
Resources requested: 0/4 CPUs, 0/0 GPUs
Result logdir: /Users/kathyjang/ray_results/ring_stabilize
TERMINATED trials:
 - PPO_WaveAttenuationPOEnv-v0_0:	TERMINATED [pid=13922], 10 s, 400 ts, -619 rew

@cathywu can you post the full trace; the Ray errors are often really high up in the log

Was this solved?


:seedling: Fix gofmt warning: redundant type from array, slice, or map composite literal

Signed-off-by: Zou Yu<EMAIL_ADDRESS>

What this PR does / why we need it:
Fix gofmt warning: redundant type from array, slice, or map composite literal.
I run the following command:
gofmt -s -w -d controllers/metal3labelsync_controller_test.go

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

/retest
/ok-to-test

/ok-to-test

/test-integration
/lgtm

/test-centos-integration
/cc @kashifest


No way to reset

Looking for a way to reset everything. Read through the docs, found nothing. Setting recordedBlob to null and audioSrc to '' does nothing. There ought to be a way to reset these things. If there is, it should be more clearly documented.

I'm seeing a method called "clearCanvas". Is this the intended method? It says it clears the canvas, but makes no mention of recordedBlob or audioSrc and only claims to clear the canvas. Therefore, it is implied that it will not reset audioSrc. However, when I tested it out, it seems to reset audioSrc.
In my opinion, this section of the documentation is misleading.


Address issue #24, also added sorting to job id column

 Review https://github.com/JoshKarpel/condor_watch_q/pull/29

I'm so sorry about that, I made a separate branch for the progress bar and changed to a lambda method.


Made changes in the nav bar

Added FAQ section in the nav bar
closes #734

@himanshu-03 Please review it soon


Is there a way to download this from musecore?

https://musescore.com/pro/landing/official-score?official_score_id=477334&feature=official-from-search-real

See my pull https://github.com/Xmader/musescore-downloader/pull/49... the script works again, but must wait 8 seconds at the least so far for it to work again without tripping Musescore.

The updated version here should be able to download official scores.


Syndie smokes buff

About the PR

Syndie smokes have been pretty bad ever since microdosing got thrown out the window, this probably will make them okay again.

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

:cl: BurninDreamer

tweak: Syndicate smokes now have 3x the healing chemical.

What if someone put syndie cig into material reclaimer?
Wouldn't they be able to extract all those sweet omnizine and use them in pill or syringe?

What if someone put syndie cig into material reclaimer? Wouldn't they be able to extract all those sweet omnizine and use them in pill or syringe?

I mean it's probably possible to do this now, but it just gives you less, either way I'm up for this even if you can farm omnizine like that.

salv and kitchen can get omnizine so even if pros farm it from syndie smokes its not that bad


RDM-13130 Add CategoryId to CaseField and Validation

[###] JIRA link (if applicable) ###
RDM-13130 [Sub-task] CategoryID column in CaseField tab
RDM-13079 [Parent-task] CategoryID column in CaseField and ComplexTypes tab
Change description
Add CategoryId to the CaseFiled Tab and then validate that the caseField is the correct type and has a categoryId that exists in the categories tab
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

These changes (plus accompanying FTA tests) are now all present in this PR
https://github.com/hmcts/ccd-definition-store-api/pull/1171
Closing this PR and deleting branch as no longer required


[BugFix] Add timezone data to the ubuntu docker image

What type of PR is this：

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：
Fixes https://github.com/StarRocks/starrocks/issues/17849
Problem Summary(Required) ：
The docker runtime container needs to set timezone data to make the broker load working correctly.
Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)
[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[X] I have checked the version labels which the pr will be auto backported to target branch

[X] 3.0
[X] 2.5
[ ] 2.4
[ ] 2.3

run starrocks_admit_test

@Mergifyio backport branch-2.5

https://github.com/Mergifyio backport branch-3.0


CNF-15060: Switch to use ownerReference for ProvisioningRequest created CRs

Switch to use ownerReference to simplify the resources cleanup and watchers:

Set the ProvisioningRequest as the owner for its created resources that haven't been set yet
Remove finalizers
Remove watch mappers for NodePool and ClusterInstance

/lgtm

/approve


Minor config bug with ritualDurationMultiplier

When editing occultism-server.toml, if you forget the zero when decreasing ritualDurationMultiplier (i.e. .25 instead of 0.25), it causes NeoForge to regenerate the entire file. I suspect it has something to do with either the way the config is processed or the variable type used, so I'm not sure it's even fixable or even really worth the trouble of fixing. I'd suggest adding to the comment line that says what ritualDurationMultiplier does that you need to have a 0 before the decimal for values below 1.
Side note, discovered this on ATM10 and spent a couple of hours combing through modpack scripts making sure there wasn't one that was defaulting out the config on purpose before I thought to try Occultism on a clean instance. Once I did, I figured out what was going on in like five minutes. I need to learn to apply Occam's razor to troubleshooting Minecraft mod issues.

@KamiN0Baka I suspect that is how Neo's config (Nightconfig) handles floating point numbers, as I am just using their "DoubleValue" config. Indeed whenever it discovers an error it just goes nuclear ... Sadly not a lot of influence I have as a modder here, but the comment idea is great


Can't compile - error in TwoWire function

Hi there,
I'm trying to use your library but I can't compile it... Here is the output :

include/BQ25896.h:255:42: error: no matching function for call to 'TwoWire::TwoWire()'
             BQ25896(TwoWire& w) : wire(&w){};
packages/framework-arduinoespressif32/libraries/Wire/src/Wire.h:73:5: note: candidate: 'TwoWire::TwoWire(uint8_t)'
     TwoWire(uint8_t bus_num);
     ^~~~~~~
packages/framework-arduinoespressif32/libraries/Wire/src/Wire.h:73:5: note:   candidate expects 1 argument, 0 provided
packages/framework-arduinoespressif32/libraries/Wire/src/Wire.h:43:7: note: candidate: 'constexpr TwoWire::TwoWire(const TwoWire&)'
class TwoWire: public Stream
       ^~~~~~~
packages/framework-arduinoespressif32/libraries/Wire/src/Wire.h:43:7: note:   candidate expects 1 argument, 0 provided

Any idea of what I could do to patch this ?
Thanks in advance !

Same Problem Here. I tried to fix it, but no luck/skill...

You can open the library directly and remove the TwoWire derivation on the BQ class name, as shown here


GCYS java.lang.VerifyError: Bad type on operand stack

GregTech CEu Version
2.4.0 GCYS compat
Gregicality Multiblocks Version
1.1.4 GCYS
Gregicality Science Version
0.0.1 a
Modpack Used
No response
Addons Installed
No response
Environment
Singplayer
Side Crashed
Client
New Worlds
No
Steps to Reproduce
start the client with mod that listed in report and it crash
Crash Report
https://gist.github.com/smolljam/827642b3acff507b1d6344c32fd0649c
Additional Information
No response

same problem with different mod combination:
crash-2022-10-02_20.51.51-client.txt

Not actually an issue with GCY:S, but CEu.
Duplicate of GregTech#1169


Make Admin Panel to be able to register users

Currenty the users tab in the UI consist of empty table which should be able to fetch and list all the administrators in the app. Besides that it is needed to be able to edit and create new user from that UI.


No list of backwards-incompatible API changes (UPGRADING)

Is your feature request related to a problem? Please describe.
Our custom website is using Leaflet 0.7.7. We want to update Leaflet to the latest version, but I cannot find a list of backwards-incompatible changes to watch for. The best I found is CHANGELOG.md, which - for version 1.0-beta1 - lists "Other breaking API changes" (and it is not clear what breaking API changes that version brings other than those listed in "Other breaking API changes"). Unfortunately this seems to be the only version which contains such information.
Describe the solution you'd like
A "UPGRADING" document focused on breaking API changes would be best.
Describe alternatives you've considered
It would also be possible to have a "Backwards-incompatible API changes" section in each changelog entry.

v0.7.7 was released 6 years ago, so I don't think we should write a retroactive upgrade guide. We will definitely consider doing one for Leaflet v2 though.


add matrix_mode: False option to sim params yaml to allow vectorized batch params

matrix_mode: False for vectorized batch params instead of meshgrid

Yes, I'm catching up with the roadmap!


Create fetchBuilds function to replace redundant fetch code

Fixes #289
Changes:

Created fetchBuilds function which replaces the mentioned lines of code.
Replaced existing implementations of the fetch lines with the new function.

Thank you @LongyuZhang :smile:. Thank you for taking the time to review this PR.

Thank you for the review @llxia.
I have resolved the merge conflicts and squashed all commits into one.
Here are a few screenshots from local testing:
Pipeline details
Grid view
AllTestsInfo
DeepHistory
Please let me know if additional screenshots are required.

Thanks @avishreekh !

Thank you @llxia for taking the time to review this PR!

Hi @llxia, please let me know if this works. Thank you!


[Metrics Framework] Add enable/disable switch to metrics framework

Is your feature request related to a problem? Please describe
As of today there is no dynamic switch to enable/disable the metrics framework. It is possible that we might require to disable the metrics framework after running into potential issues like high resource consumptions by the framework or facing exceptions while processing or exporting the metrics data. Metrics framework is currently initialised during the Node setup.
Under the scope of this discussion, no metrics being emitted is the expected state when the metric framework is disabled. There are different ways to achieve this state, which are discussed below.
Describe the solution you'd like
Approach no. 1
One such option is to put the counter logic behind a common flag at the framework level. We can create a wrapper around the counters which will use no-op counter instance if flag is disabled. This will temporarily stop the incrementation of counters. However, re-enabling the flag after a period of disablement would cause the counters to resume incrementing from their previous values. This behaviour leads to inaccurate metric values over time.
When the global flag is disabled, the metrics framework can enter a passive state, temporarily stopping the incrementation of counters. During this period, metrics would still be emitted with the existing values.
This can be mitigated by using the delta functionality provided by the OtlpGrpcMetricExporter. At regular intervals, typically every minute, the system examines whether there has been any alteration in the counter values. If a difference is detected, the exporter emits only the varying values corresponding to the respective counters.
Example:
Consider the scenario where the current absolute value of the counter search.query.type.match.count is 5. If, by the end of the minute, this absolute value becomes 8, then the exporter will emit only the counter value of 3 – the difference between the current and previous values.
To summarise, if the common flag is disabled, then counters will not be incremented and since the exporter only emits the metric if their value changes within the last minute, no metrics would be emitted which is a desired state. However it is worth noting that exporter would still be executing the delta logic and evaluating whether it needs to emit the metrics or not. We would only be saving the resources associated with to the exact metric export logic.
Approach no. 2
Another alternative is to stop the exporter dynamically during the runtime but this feature is not yet available in the open telemetry. If we are able to implement it, we would be able to save the computational power consumed by the exporter.
Approach no. 3
Another way to achieve this state is through initializing a proxy plugin during the node boot up and dynamically enable or disable Otel.
Approach no. 4
Otel does not provide the support to reset the counter values. Another approach suggests that we can manage the metrics registry on our side instead of Otel maintaining it. This way we can reset the counter values to 0 if flag is disabled, at any point of time. When re-enabled, counters will start again from 0. This would allow us to emit the absolute values of the counters, instead of computing delta and emitting it.
Related component
Plugins
Describe alternatives you've considered
No response
Additional context
No response

I think most of the cases we need the delta value onlyAggregationTemporality.DELTA.
@reta, your thoughts here?

@atharvasharma61 @Gaganjuneja I would strongly advocate against this feature (which we have been discussed on the initial pull request for metrics integration). Metrics are very often used by SRE teams for alerting purposes, and altering metrics generation or publishing dynamically could have severe consequences.

I agree, You are right it will shut down the entire monitoring/observability system. But this is only needed in the extreme situations where cluster is going bad because of the metric computation logic or something else and we want to take a conscious decision to disable this framework for sometime despite knowing its adverse impacts.

But this is only needed in the extreme situations where cluster is going bad because of the metric computation

Disable plugin, restart nodes one by one. The consequences of the feature far outweigh any benefits (in my opinion).

@reta, Opting for a rolling restart is not a good option for bigger clusters due to potential side effects. Our discussion has highlighted two primary concerns:

Incorrect Metrics: The disabled state may result in inaccurate metrics if increments or updates are not applied. Specifically, OpenTelemetry (Otel) retains the previous metric value during this phase, causing a restart to resume from the prior point. This issue is limited to AggregationTemporality.CUMULATIVE. Notably, Otel's recommended low-memory temporality selector is DELTA for counters and histograms. While incorrect metrics may not pose a problem in most cases, updown counters exhibit limitations, which are clearly outlined in this

https://github.com/open-telemetry/opentelemetry-java/blob/d9f9812d4375a4229caff43bd681c50b7a45776a/sdk/metrics/src/main/java/io/opentelemetry/sdk/metrics/export/AggregationTemporalitySelector.java#L62

Alarms & Alerting: This functionality must be disabled in both rolling restart and metric disablement scenarios, and should be used with caution.

Providing convenient control to disable metrics proves advantageous when managing multiple clusters, particularly when such actions interfere with business-as-usual.

@reta, Opting for a rolling restart is not a good option for bigger clusters due to potential side effects. Our discussion has highlighted two primary concerns:

@Gaganjuneja  I suspect are won't be asking users to go and read Java code to understand the limitation of the disabling metrics. To me, as far as the behaviour has side effects  that could impact operations in underdefined way (ot the ways out of our control) - this is no go. Certainly, opinions and ideas how to deal with that are welcomed.

I suspect are won't be asking users to go and read Java code to understand the limitation of the disabling metrics.

Definitely not, I am referring here to the product documentation we all the settings are described. https://opensearch.org/docs/latest/install-and-configure/configuring-opensearch/configuration-system/

Consider the scenario where the current absolute value of the counter search.query.type.match.count is 5. If, by the end of the minute, this absolute value becomes 8, then the exporter will emit only the counter value of 3 – the difference between the current and previous values.

Doesn't this go against the whole idea of OTel metrics and go back to the abomination that is node stats?
Going forward, shouldn't we abandon monotonically-increasing counters and emit spans related to requests and leave it up to collectors to emit data points for a given interval?

Going forward, shouldn't we abandon monotonically-increasing counters and emit spans related to requests and leave it up to collectors to emit data points for a given interval?

Spans are traces, I think we should not confuse them with metrics

leave it up to collectors to emit data points for a given interval?

I think the problem is we just cannot "erase all metrics", collector will still get metrics that would not be updated

Spans are traces, I think we should not confuse them with metrics.

Yeah... I really need to wrap my head around the OTel terminology.
The model that I'm familiar with (from many years at Amazon) is one where at the start of a request (or more generally an "operation"), you create a Metrics instance and somehow propagate it through the code of the operation (where the exact means of propagation is up to the developer -- some folks do it explicitly. adding a Metrics parameter on every method; others store it in a ThreadLocal, which only works if your operation is processed on a single thread; sometimes it's stored in a request context object that gets be propagated). Throughout the code, whenever someone wants to count something, they can call metrics.addCount(String name, double value, Unit<?> unit). Then, at the end of the request, the Metrics instance gets flushed to an out-of-process collector (which usually happens via a frequently-rotated log file, but could also happen via a named pipe or something; if I understand correctly this is what OTel calls an "exporter"). That collector accumulates all the distinct counters (also called metrics, confusingly) for 1 minute (or whatever sampling period you choose, but in practice it's usually a minute), collecting them in a histogram. Every minute, those histograms are sent off to the time-series metric store (in our case, usually CloudWatch). The service only accumulates stuff for in-flight requests, and the collector only accumulates one period worth of data before flushing. No persistent counters.
I was under the impression that OTel will allow us to do the same thing with OpenSearch. If everything is ephemeral, turning off the metrics framework should just lead to missing datapoints, shouldn't it?

I was under the impression that OTel will allow us to do the same thing with OpenSearch. If everything is ephemeral, turning off the metrics framework should just lead to missing datapoints, shouldn't it?

We don't know what those metrics are used for, right? Is the cluster / node dead? Are there any alerts?

We don't know what those metrics are used for, right? Is the cluster / node dead? Are there any alerts?

Aha... yeah, I agree that turning off metrics is terrible from an alerting standpoint.
I misunderstood the concern as being able to get the cluster into an invalid state if metrics are disabled.

I still think, keep a dynamic flag for experimentation, remove it on general availability (GA) to maintain flexibility without disruptive cluster restarts. This will be helpful in issue handling because of some bugs, increased memory foot prints etc. I realized this necessity while conducting performance tests, with simultaneous testing by other teams on the same cluster.

I agree with @reta  -- if we want to disable metrics during the experimental phase, it should be a static setting (i.e turn off the feature flag). Adding a dynamic flag (even if we intend to remove it before GA) seems really dangerous without offering much benefit.

I still think, keep a dynamic flag for experimentation, remove it on general availability (GA)

Another option is to maintain this as a separate patch that is applied to your development builds to provide a dynamic switch. That may be a bit cumbersome but I think we've got consensus that we don't want this feature on the main branch, even if it is intended to be temporary.

@Gaganjuneja @atharvasharma61 I am closing this issue as per conclusions from maintainers .


Get Text not waiting anymore after upgrade from 3.2.0 to 3.3.1

Describe the bug
When using Get Text  directly after a change of web page is triggered, the "should be" assertion fails directly.
After detecting this behaviour I installed robotframework-browser (3.2.0) again, and performed "rfbrowser init".
After this the test worked as expected.
To be sure the robotframework-browser (3.3.1) was the problem, I installed it again(also with rfbrowser-init), and re-tested. The problem occurred again. At this moment I can't use v3.3.1 of robotframework-browser.
Any reason for this ?

There are couple of changes in 3.3.1 compared to 3.2.0 in Get Text:

input and textarea elements values will be considered as text (these used to return empty innerText)
Optional 4th argument called message has been added to Get Text

Could your problem be related to one of these?

I'm able to reproduce the problem. Thank you for reporting.

https://github.com/MarketSquare/robotframework-browser/pull/783

@all-contributors please add emakaay for bug reporting.

Done.


Need help making overlaying bends [Help wanted]

Hi,
I'm using multiple bends in one mesh in order to have an image like a cream flowing (think soft-serve ice cream). In order to have this imagery, I add one bend deformer to the mesh, move the deformer's transform with the bend angle set to some angle <90, and then set the angle to 180, and do the same move again in the opposite direction with another bend. My problem here is the second layer's bend also affects the first layer.
Here is an image of the problem:

The reason this is happening is because the bend deformer extends infinitely on the xz plane. I designed a lot of these deformers to mimic the ones in Cinema 4D, and that is how the deformer works in the software.

However I totally get that you want to be able to chain them together without worries about them overlapping. I'm not entirely sure the best way to go about it, but I made a modified version of the bend deformer that only modifies vertices within a bounding box. I threw it together really quickly, so if something isn't working the way you need let me know and I'll do my best to improve it for you.
https://gist.github.com/keenanwoodall/105a66e75f4270e83437a804eb823145


MediaQueryList does not inherit from EventTarget on Safari and Safaria on iOS

Request type

[ ] New documentation
[x] Correction or update

Page to change
https://developer.mozilla.org/en-US/docs/Web/API/MediaQueryList#Browser_compatibility
Details
The MDN web docs state that the MediaQueryList objects is inheriting from EventTarget in nearly all modern browsers. Thus you could (and probably should) use addEventListener('change', callback) instead of the alias addListener(callback). But it seems to me that on Safari this isn't the case.
You can verify this by running the following commands:
 // Will work in all browsers
window.matchMedia("foo").addListener(() => null);

// Might throw TypeError on iOS/macOS, complaing that window.matchMedia(...).addEventListener is not a function
window.matchMedia("foo").addEventListener("change", () => null);

Related issues
https://github.com/mdn/browser-compat-data/pull/1235

Any updates on this?  I'm running into this very issue in iOS 12.2.  It was extremely confusing because just about every reference for addEventListener out there implies that it works fine on iOS (Mobile Safari).

I also had a hard time finding this out, and I was just about to submit this bug, when I saw that a discussion already exists. So I'll just paste my message in here, which might be useful, because I looked through the affected pages on MDN. Btw, I also just reported this to caniuse.com
Support for matchMedia is only partial in Safari (Desktop and iOS) including Safari 13 (Technology Preview), because the MediaQueryList object that is returned only supports the legacy .addListener() method, but not .addEventListener().
See: https://developer.apple.com/documentation/webkitjs/mediaquerylist
Test:
const mediaQuery = matchMedia("(min-width: 1000px)");
console.log("addEventListener" in mediaQuery);
This is problematic, because this page says that you can "watch for a change event", which implies using addEventListener:
https://developer.mozilla.org/en-US/docs/Web/API/Window/matchMedia
Also it points to the example on this page, where addEventListener is used:
https://developer.mozilla.org/en-US/docs/Web/API/Window/devicePixelRatio#Example
The table on the page with the example has Safari green and fully supporting, but in fact you just have to open the console to see this: "TypeError: matchMedia(mqString).addEventListener is not a function. (In 'matchMedia(mqString).addEventListener("change", updatePixelRatio)', 'matchMedia(mqString).addEventListener' is undefined)"
On this page, only .addListener() is used, so it is correct, but it says that it would be only an alias for addEventListener "for backward compatibility purposes", without mentioning the lack of support in Safari and the different syntax of the two methods: .addListener needs a function as first argument, not a string like .addEventListener. So "alias" is probably not the correct term:
https://developer.mozilla.org/en-US/docs/Web/API/MediaQueryList
Everything above also is true for .removeEventListener (not supported in Safari) vs. .removeListener.

I've just spent the best part of half a day realising what @makkabi explained. It's very confusing as the errors in Safari don't allude to the how the the problem occurs.
I resolved the issues I was facing by using addListener instead of addEventListener.

This one has been hanging around way too long; @a2sheppy can you take this as a P1 bug in the next sprint?

Will do.

Parts of the changes around this have already been made; the BCD tables have been updated since this issue was filed. However, I'm going to add some text explaining that addListener() and removeListener() are for backward compatibility and that it's generally preferable to use the EventTarget counterparts now.

I've made assorted text improvements, as well as submitted [BCD PR 6403](mdn/browser-compat-data#6403) to add notes to the interface on Safari and Safari iOS to be sure this issue is clear; these notes also mention this should be resolved in iOS 14 and macOS 11 Big Sur. Made some other fixes as well. See the PR for further details.


"Address already in use" occurs in Distributed Estimator.train_and_evaluator when loop training

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): 1.18.0
Python version:  2.7.13
Bazel version (if compiling from source):
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version:
GPU model and memory:
Exact command to reproduce:

Describe the problem
In Distributed ResNet, it need train the model many times, but when train in the second iteration, it fail for below:
{"created":"@1528701271.960402221","description":"No address added out of total 1 resolved","file":"external/grpc/src/core/ext/transport/chttp2/server/chttp2_server.cc","file_line":307,"referenced_errors":[{"created":"@1528701271.960399817","description":"Failed to add any wildcard listeners","file":"external/grpc/src/core/lib/iomgr/tcp_server_posix.cc","file_line":345,"referenced_errors":[{"created":"@1528701271.960371584","description":"OS Error","errno":97,"file":"external/grpc/src/core/lib/iomgr/socket_utils_common_posix.cc","file_line":259,"os_error":"Address family not supported by protocol","syscall":"socket","target_address":"[::]:50992"},{"created":"@1528701271.960399232","description":"Unable to configure socket","fd":74,"file":"external/grpc/src/core/lib/iomgr/tcp_server_utils_posix_common.cc","file_line":203,"referenced_errors":[{"created":"@1528701271.960393654","description":"OS Error","errno":98,"file":"external/grpc/src/core/lib/iomgr/tcp_server_utils_posix_common.cc","file_line":176,"os_error":"Address already in use","syscall":"bind"}]}]}]}

It means that, the worker port 50992 not release when a new iteration start. The train iteration code show as fllow:
--------------------code begin----------------------------------------

train_spec=tf.estimator.TrainSpec(input_fn=input_fn_train,max_steps=1000)

eval_spec=tf.estimator.EvalSpec(input_fn=input_fn_eval,steps=1,throttle_secs=1,start_delay_secs=1)

for cycle_index in range(total_training_cycle):

    print("start a train")

    tf.logging.info('Starting a training cycle: %d/%d',cycle_index, total_training_cycle)

    tf.logging.info('Starting to evaluate.')

    tf.estimator.train_and_evaluate(classifier,train_spec,eval_spec)

    print("end a train")

--------------------code end----------------------------------------

This question is better asked on StackOverflow since it is not a bug or feature request. There is also a larger community that reads questions there.
If you think we've misinterpreted a bug, please comment again with a clear explanation, as well as all of the information requested in the issue template. Thanks!


new Bulma field syntax

I noticed that fields are now wrapped with .field divs to handle things like field addons, see:
http://bulma.io/documentation/elements/form/
So the code from the above page for things like icons and horizontal field placement don't work with the current version of Vue Blu.
Are you updading Vue Blu to the latest version of Bulma? I'm happy as it is, but if you do change I know I'll have to update my templates to match the new wrapper syntax for things like fields (and there's probably other things).

update to bulma 0.4.0

@xiaokaike how did you make vue-blu use 0.4.0?

@stvnmoon I don't think he did, and I don't think it would work without @chenz24 updating the various Vue Blu component HTML markup.

@Youdaman, now that I re-ready his comment, I agree with you. Yes, updating to 0.4.0 is not a trivial task.
Thanks


Table class used by DictDB to create table instances can be overwritten.

Coverage remained the same at 100.0% when pulling ff786f03109ca765fbaf2fae21e39586be6b29b6 on table-cls into c452a60f342cb889f8f79c5ea22fead28c2ab48c on master.

Coverage remained the same at 100.0% when pulling ff786f03109ca765fbaf2fae21e39586be6b29b6 on table-cls into c452a60f342cb889f8f79c5ea22fead28c2ab48c on master.


[Evaluation] Add DiscoveryBench Benchmark

What problem or use case are you trying to solve?
Add DiscoveryBench to OpenHands' evaluation suite. DiscoveryBench contains 264 tasks collected
across 6 diverse domains, such as biology, economics, and sociology. It incorporates discovery workflows from published papers to approximate the real-world challenges faced by researchers.
https://github.com/allenai/discoverybench/
https://x.com/mbodhisattwa/status/1811524569410531333
Do you have thoughts on the technical implementation?
The implementation will consist of:

Inference script to solve a DiscoveryBench task (goal & datasets)
Facetted evaluation script to rigorously evaluate the answers
Documentation for the OpenHands users

Additional context
We are working on a PR for this and will seek OpenHands contributors' input to finalize it. Tagging other contributors to the PR - @Ethan0456, @majumderb and @neubig who helped us chart out the integration.

Read details of the benchmark in this paper: https://arxiv.org/pdf/2407.01725v1
(A new version with more analysis is coming soon to arXiv)


ChatGLM.cpp: Added an option to specify input order

Added two options
--print_inputs_info : show the available inputs length
--select_inputs : to set the order of inputs (e.g., --select_inputs "1,4,1,4")
Show performance summary at the end

@wenyi5608  Hi Wenyi, I am Taylor working for GPU plugin team. Could you have this change in your branch? We have frequent needs to control the input sequences order. Would be great if you could accept the change in this BKM branch!


OO vs native shaped array?

Looking at the implementation everything is row based and OO? Wouldnt it be better to wrap a native shaped array of num64? That way the memory will be the most efficient and you will gain all the benefits of vectorised SSE optimisations that might be made in the JIT around this area.

http://design.perl6.org/S09.html#Compact_arrays and http://design.perl6.org/S09.html#Fixed-size_arrays for some reference.

I have planned to use native shaped array, however, i still encounter some issues with non implemented parts of native arrays, you can see the code there:
https://github.com/pierre-vigier/Perl6-Math-Matrix/tree/shaped-array
Not finished yet, but if you have any inputs, one of the problem i have is in add methods, where:
$.cells >>+<< $b.cells triggers an error:
Type check failed in binding @dims; expected Positional but got Any
Not sure why yet, also, to keep the syntax: $matrix[row][column], i encounter that:
my int @a[2,2] = (1,2),(3,4);
say @a[1][1];

that gives me:
Partially dimensioned views of arrays not yet implemented. Sorry.
  in block <unit> at <unknown file> line 1

However the idea is to use native array, as for now, perfomance are pretty poor with the current implementation

i will look into that next

while i support the notion it will demand some massivly different internals and I think i will outsource this in a module like Math::Matrix::Native

I guess the first think would be to assess if the "glitches" i was seeing then are now solved on new version of perl6. As stated above, my first idea was to do everything with Native array, however, i encountered some blocking issues at the time

yes i looked into it but could not understood it fully what exactly was the glitch?

When trying to access element on shaped array with syntax @a[1][1], program was crashing, as of today, it is still not implemented. However, @a[1;1] .
But more to the point, let's say i have a shaped array for the matrix of 3x3, and i want to get the middle row, @matrix[1] will crash with the same error, @matrix[1;*] as well

are these results of recent tests?

A few hours ago, however, not the latest version of perl6, but still not
too old:
This is Rakudo version 2018.01-100-g156876dbf built on MoarVM version
2018.01-77-g9a029b408
implementing Perl 6.c.
On Thu, Mar 15, 2018 at 9:18 AM Herbert Breunung<EMAIL_ADDRESS>wrote:

are these results of recent tests?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/pierre-vigier/Perl6-Math-Matrix/issues/2#issuecomment-373310566,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHMnhajozSZEBSHBsC6rs5C3BRGVBJyqks5tejH3gaJpZM4G9xUs
.

thanks so i put it on backburner , my main issue for now is raise quality (docs tests consistency of what we have and add some easy things (split join, tensorproduct) and eigenvalues)

its still a hounting idea maybe write a parallel variant to experiment with

On moar 2018.08 , we still have the same "issue":
> my int @a[2,2] = (1,2),(3,4);
[[1 2] [3 4]]
> say @a[1][1];
Partially dimensioned views of shaped arrays not yet implemented. Sorry.
  in block <unit> at <unknown file> line 1

thanks


Getting involved, possible area of work for new contributors

##Possible areas of contributions
Below is a lit of possible new contributions that new developers can contribute.  We are always ready to help you perform new tasks, a good way to get help is to open an issue and state the problem you would like to address and request for help.

Implementing new operations
Improving the performance of current operations
Implementing a performance monitoring benchmark
Improving the documentation (either internal/external/tutorials)
Implementing an ONNX-mlir to ONNX protobuf to enable ONNX to ONNX-MLIR back to ONNX optimization
Integration within MLIR, hooking up onnx-mlir to TensorFlow/Pytorch mlir dialects

1. Implementing new operations
There are plenty of operations to implement, both for the ONNX standard as well as the preprocessing ONNX.ML set of operations. There is an issue #922 where you can record which operation you want to work on, so as to avoid replicated efforts. We have a document page on the various different steps involved in adding a new op (See docs folder or CONTRIBUTING.md for links to relevant pages).
One possible "warmup" task would be to add verifiers to existing ops that are still lacking them. Another is to modernize existing operations to use the newer code generation schemes built on ONNXShapeHelper and code Builder. Look for recently added files as these are more likely to use our preferred code generation schema.
2. Improving the performance of current operations
Many operations may not be lowered using optimizing code generation schemes. May operations can benefit from memory tiling, vectorization,... If you are interested in contributing such performance improvement, look at currently optimized operations (e.g. MatMul, Gemm) in the src/Convertion/ONNXToKrnl subdirectories.
3. Implementing a performance monitoring benchmark
If you have expertise in performance monitoring and/or tools to support performance monitoring, we could use help having one such benchmark to track the performance of simple operations and/or benchmarks.
4. Improving the documentation (either internal/external/tutorials)
If you like documenting, there is plenty of ways to help the current pages. Some maybe just too long and would benefit from splitting, some have redundant information which would benefit from reorganizing. We are also in need to better split the information between what is useful to users as opposed to developers. Tutorial would also be greatly appreciated, if you like to learn how to use the system and then make others benefit from your insights via a tutorial.
Integration with ONNX
Several folks have been interested in using ONNX-MLIR as an ONNX to ONNX tool. We have strong support for ingesting ONNX models into our project, but at this time we have no way to re-generate an ONNX protobuf file out of our ONNX dialect. If you are interested in such a project, I know that this would be greatly appreciated by several folks and projects in the community.
6. Integration within MLIR
MLIR supports also TensorFlow and increasingly Torch dialects. These could be potentially integrated with a bridge to ONNX, if you are interested in pursuing this kind of work.

I will add some possible work items.

Handle control flow for onnx dialect. The current implementation targets at operations in serial. For example, the constProp does not handle the definition from Region parameters, which are used for Loop and IF.  Sometimes, an input tensor can be an output tensor for a region. That should be simple. The shape inference may need more work to merge the shape information from different control flow. IFOp has predicate issue on graph level optimization.
Pass control. The passes for onnx-mlir may have some common controls, such as debugging, target info, and optimization levels. We do not have a systematic way to propagate these options.
Support tensor in gdb. Now we propagate the line number of onnx operations to gdb and can show and step through .mlir file for onnx operations. It would be useful if data at that level (tensors) can be printed in gdb.

List of Learning Resources

https://www.youtube.com/watch?v=cyICUIZ56wQ  (Intro on MLIR)
https://video.ibm.com/recorded/127363418 (ONNX MLIR talk)
https://video.ibm.com/recorded/127363577 (ONNX MLIR Wrap-Up)
https://github.ibm.com/Tian-Jin2/onnx-mlir-lab/ (github repo with example)
https://mlir.llvm.org/ (MLIR documentation)

ONNX standard: https://github.com/onnx/onnx/blob/master/docs/Operators.md
Toy examples from MLIR: https://mlir.llvm.org/docs/Tutorials/Toy/

Simple warmup task: split the current inferShape into a 'verifierthat check the validity of the ops, and leave only the shape inference computation in theinferShape`.
Here are some ops that could benefit from this: PRelu, Pow, BatchNormzlizationInferenceMode, Reshape, Unsqueeze, Squeeze, Constant, Concat, Flatten, Resize, ConstantOfShape...
I would stay away from doing this operations for more complicated ops such as convolutions (some work with verifiers, others do not). Currently, info about verifier and adding them is here: https://github.com/onnx/onnx-mlir/blob/main/docs/HowToAddAnOperation.md


fix: JSON matcher in MockServer is more strict with arrays : expected…

… and actual size now have to be the same

Codecov Report

Merging #64 (e787a51) into main (103da31) will decrease coverage by 0.51%.
The diff coverage is 72.50%.

@@            Coverage Diff             @@
##             main      #64      +/-   ##
==========================================
- Coverage   86.36%   85.84%   -0.52%
==========================================
  Files          28       29       +1
  Lines        2193     2261      +68
  Branches      226      238      +12
==========================================
+ Hits         1894     1941      +47
- Misses        204      219      +15
- Partials       95      101       +6

Impacted Files
Coverage Δ

.../matchers/StrictArrayContentJsonStringMatcher.java
62.00% <62.00%> (ø)

.../java/com/decathlon/tzatziki/utils/MockFaster.java
83.76% <88.46%> (+0.53%)
:arrow_up:

...n/java/com/decathlon/tzatziki/steps/HttpSteps.java
89.65% <100.00%> (ø)

...a/com/decathlon/tzatziki/kafka/SchemaRegistry.java
93.75% <100.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 103da31...e787a51. Read the comment docs.