text:
Add correct AllocatorAwareContainer semantics to move-assignment,copy-assignment,and copy-constructor.

The previous implementation of std::hive here did not follow the correct semantics for the AllocatorAwareContainer concept.
In particular, there is a sequence of operations which depend on the allocator traits (as defined here in 'influence on containers) https://en.cppreference.com/w/cpp/named_req/Allocator
Move assignment operators and copy assignment operators of AllocatorAwareContainer are required to behave in a way consistent with those specifications in the traits.
Particularly, assignment operators are required to check if the current allocator is compatible with the source allocator and based on that and the traits values, optionally destroy, reallocate, or copy the underlying elements.
See the following references:
https://www.foonathan.net/2015/10/allocatorawarecontainer-propagation-pitfalls/
https://stackoverflow.com/questions/40801678/how-is-allocator-aware-container-assignment-implemented
This patch fixes that issue.
In order to implement this correctly, it requires that all allocators in the object are rebound or not depending on the stateful values.   It would have been possible, but much much harder and slower to conditionally load and reset the 3 child ebco objects which are caches of the parent allocator, so those ebcos were removed.
Allocator rebinding and copying is a no-op for stateless allocators and defined to be a lightweight "cheap" operation for stateful allocators.  So removing the ebcos code remains a no-op for stateless allocators and a cheap operation for the stateful operations.  It also will provide a significant space-efficiency benefit for stateful allocators.  Since this implementation did not previously support stateful allocators correctly at all, the base performance should be un-changed.
It's possible as well that a correct implementation of swap() needs to be provided.

Code updated as per last submission

license: Zlib


text:
Items in Buffer ignored while requesting

Hey again!  I noticed that when I have items on arrival, I also have the same items in my buffer that can immediately be used, if I  select "Add to Inventory".
Shouldn't the plugin pull from the Buffered items first instead of requesting more from remote?  I end up with thousands of duplicate items otherwise.
Example with solar panels:

That makes more sense.  I kept spamming Return to Logistics thinking I was helping clear my buffer for new arrivals XD

Wow, this turned out to be a great bug report. I didn't realize it, but anything over 1k requested items were being generated out of thin air (oops). I didn't really notice it because I don't typically do that, but the plan all along was to have lower throughput than actual logistics stations (they can get up to 10x vessel capacity incoming at a time). The idea being that if you want to get a lot of items quickly, it's best to have them available on the local planet to draw from.
So, the fix I'm going with for now is to just hide any items that are in the buffer but that still have incoming requests. Before I landed on that, I tried to do something where buffered items were "locked" but it got to be too much to manage.
At any rate, I created a preview release here if you want to test it out. r2modman has an "Import local mod" option under Settings. Don't worry if you don't have time, I'm planning to release it later tonight after I've the nextrelease branch a last review

source: gharchive/issue

authors: ghostorchidgaming mattsemar

repo: mattsemar/dsp-personal-logistics

license: MIT

license_type: permissive

license_source: github-api


text:
Table views should be sortable

https://datatables.net

Preliminary support on the Events view was added in 1b9cba9

repo: mattstratton/xela


text:
Distinguish between single-segment and multi-segment polylines

This is a small change to allow to distinguish between single-segment and multi-segment polylines:

single-segment polylines will be returned as MKPolyline objects into the results array
multi-segment polylines will be returned as NSArray of MKPolyline objects into the results array

With the original code, each parsed MKPolyline object is independent, thus multi-segment MultiLineString objects are treated as multiple separate polylines.

Thank you for your contributions, @noberasco. I apologize for not responding to them sooner.
Apple has finally added native support for GeoJSON decoding in iOS 13 by way of MKGeoJSONDecoder. As such, I've decided to discontinue this project.

source: gharchive/pull-request

authors: mattt noberasco

repo: mattt/GeoJSONSerialization

license: mit

license_source: bigquery


text:
v1.3.12 - CodeLens and Terraform Explorer doesn't working

Unfortunately both "codelens" and "terraform explorer" aren't working.
Examples:

CodeLens doesn't show variable references.
Terraform Explorer loading forever.

We do not support TF 0.12 yet so this might be the error you are seeing, please update with more information about any errors and the setup you have.

Sure, I downgraded tf'v version. Thank you!

authors: dminella mauve

repo: mauve/vscode-terraform


text:
Add capability to generate a configuration scaffold

This change allows the user to start with a nearly-empty configuration file, and instead of "obfuscate" make a call to "scaffold."  Then instead of obfuscating the input SQL files, the scaffold call finds table names and column names, and outputs a properly formatted snippet that can be used as the basis of a real obfuscator.rb configuration file.  (There's a section in the .rdoc explaining usage.)

Hey @SpencerGreene, thank you, this looks like a great contribution!  I'll look through it and get back to you soon.

@cantino Thanks - and thanks for putting this tool out there in the first place.  I'm now using it in a complex environment with more than 50 tables and a 900-line configuration file (hence the need for a scaffolder).
All that said - this is my first exposure to ruby, so there are likely some newbie issues, let me know what needs attention and I'll address.
cheers
spencer

@cantino OK this second (larger) change was additive to the other one.  I have rebased to master.  There are a whole bunch of new .spec tests as well.  Take a look when you have a chance!  thx, spencer

I like it!
We have the following at the bottom of our configuration.  If any of this is useful to you, feel free to integrate it.
obfuscator = MyObfuscate.new({
...
})

obfuscator.fail_on_unspecified_columns = true
obfuscator.globally_kept_columns = %w[id created_at updated_at]

# Validate against schema.rb
db_schema = File.read(File.expand_path(File.join(File.dirname(__FILE__), "..", "db", "schema.rb")))
table_name = var = error = nil
errors = {}
found_columns = {}
db_schema.each_line do |line|
  if line =~ /create_table (["'])([\w\d_-]+)\1.*?\|(\w+)\|/
    table_name = $2
    var = $3
  elsif table_name
    if line =~ /#{Regexp::escape var}\.\w+\s+(['"])([\w\d_-]+)\1/
      column = $2
      next if errors[table_name]
      case obfuscator.config[table_name.to_sym]
        when nil
          STDERR.puts "Table #{table_name} not found in the obfuscator specification."; errors[table_name] = true
        when :keep, :truncate
          # Looks good
        when Hash
          if obfuscator.config[table_name.to_sym][column.to_sym] || obfuscator.globally_kept_columns.include?(column)
            # valid
            found_columns[table_name.to_sym] ||= {}
            found_columns[table_name.to_sym][column.to_sym] = true
          else
            STDERR.puts "Missing column specification for #{table_name}##{column} in the obfuscator specification."
            errors[table_name + column] = true
          end
        else
          STDERR.puts "Unknown definition for #{table_name}: #{obfuscator.config[table_name.to_sym]}"
          errors[table_name] = true
      end
    end
  end
end

found_columns.each do |table, config|
  obfuscator.config[table].keys.each do |key|
    if !obfuscator.globally_kept_columns.include?(key) && config[key] != true
      STDERR.puts "Unknown column in obfuscator configuration: #{table}.#{key}"
      errors[table] = true
    end
  end
end

exit 1 if errors.length > 0
exit 0 if ARGV[0] && ARGV[0] =~ /validate/

obfuscator.obfuscate(STDIN, STDOUT)

Looks like you have a much more general solution, which is great!  Let me know when it's mergable.  Would you like to be a contributor on this gem?

Ah had I only known - might have saved some time :).  I hope what I did is general though.  The one thing that is a bit difficult with my scaffold workflow is that each time there is a change I am copying the obfuscator.rb file and replacing obfuscator.obfuscate with .scaffold.  I made a shell script for that but it's not ideal.
Let me look at yours and ponder whether there might be a combination.
On Thu, May 7, 2015 at 11:58 AM, Andrew Cantino notifications@github.com
wrote:

I like it!
We have the following at the bottom of our configuration.  If any of this is useful to you, feel free to integrate it.
obfuscator = MyObfuscate.new({
...
})
obfuscator.fail_on_unspecified_columns = true
obfuscator.globally_kept_columns = %w[id created_at updated_at]
# Validate against schema.rb
db_schema = File.read(File.expand_path(File.join(File.dirname(__FILE__), "..", "db", "schema.rb")))
table_name = var = error = nil
errors = {}
found_columns = {}
db_schema.each_line do |line|
  if line =~ /create_table (["'])([\w\d_-]+)\1.*?\|(\w+)\|/
    table_name = $2
    var = $3
  elsif table_name
    if line =~ /#{Regexp::escape var}\.\w+\s+(['"])([\w\d_-]+)\1/
      column = $2
      next if errors[table_name]
      case obfuscator.config[table_name.to_sym]
        when nil
          STDERR.puts "Table #{table_name} not found in the obfuscator specification."; errors[table_name] = true
        when :keep, :truncate
          # Looks good
        when Hash
          if obfuscator.config[table_name.to_sym][column.to_sym] || obfuscator.globally_kept_columns.include?(column)
            # valid
            found_columns[table_name.to_sym] ||= {}
            found_columns[table_name.to_sym][column.to_sym] = true
          else
            STDERR.puts "Missing column specification for #{table_name}##{column} in the obfuscator specification."
            errors[table_name + column] = true
          end
        else
          STDERR.puts "Unknown definition for #{table_name}: #{obfuscator.config[table_name.to_sym]}"
          errors[table_name] = true
      end
    end
  end
end
found_columns.each do |table, config|
  obfuscator.config[table].keys.each do |key|
    if !obfuscator.globally_kept_columns.include?(key) && config[key] != true
      STDERR.puts "Unknown column in obfuscator configuration: #{table}.#{key}"
      errors[table] = true
    end
  end
end
exit 1 if errors.length > 0
exit 0 if ARGV[0] && ARGV[0] =~ /validate/
obfuscator.obfuscate(STDIN, STDOUT)

Looks like you have a much more general solution, which is great!  Let me know when it's mergable.  Would you like to be a contributor on this gem?
Reply to this email directly or view it on GitHub:
https://github.com/mavenlink/my_obfuscate/pull/14#issuecomment-99979933

Yea, we should have contributed ours earlier, but your's is likely more general.

Is there some reason why this could this be merged to master ?

Whoops, definitely forgot about this.  @SpencerGreene, is this done and ready to go?

Yes afaik!

Thanks @SpencerGreene!

authors: SpencerGreene cantino jgwashburn


text:
Uncaught TypeError in StyleUtils function getCurrentStyle()

During mouse events, I'm observing Uncaught TypeErrors in StyleUtils function getCurrentStyle():
export const getCurrentStyle = (element: HTMLElement) => {   return element ? window.getComputedStyle(element, '') : null; };
This appears to be happening when the argument to the function is a document fragment rather than an HTMLElement.  The document fragment is a ShadowDom element.

It seems this duplicates #68.

Fantastic!  Thank you for addressing this!

authors: sdgoldstein tbouffard

repo: maxGraph/maxGraph


text:
optional rule bug?

I got a little problem, I am wondering if I made mistake somewhere or it is a bug.
This code:

  _indent:    -> "\n<"
  _outdent:   -> "\n>"
  terminator: -> "\n"

  # program  ::= block+
  program: -> seq @_indent, repeat(@_statement), @_outdent

  block:   -> seq @_indent, repeat(@_statement), @_outdent

  _statement: -> choice(
    @class
    @block
  )

  # primitive

  identifier: -> /[\a_$][\a\d_$]*/

  # class

  # class ::= 'class' _accessibles  extends? block?

  class: -> seq 'class', @identifier

class TestName

Generates:
(program
  (terminator)
  (terminator)
  (terminator)
  (class (identifier))
  (terminator)
)

While whenever I will add "optional" rule
  class: -> seq 'class', optional(@identifier)

it generates:
(program (class) (class) (class) (identifier) (terminator))

similar bug:
this is not working at all (hangs compiler), or producing similar bug to previous
    _callable: -> choice(
      @identifier
      @accessor
      @this
      @this_property
      )
func_call:  -> prec 3, seq @_callable, @body
invocation: -> prec.right 1, seq  @_callable, ' ',choice @invocation, @_statement

while this works perfectly:

    func_call:  -> prec 3, seq choice(
      @identifier
      @accessor
      @this
      @this_property
      ), @body

    invocation: -> prec.right 1, seq choice(
      @identifier
      @accessor
      @this
      @this_property
      ), ' ',choice @invocation, @_statement

Could you share the whole grammar that includes these rules? I'd like to run compile myself and see what I can figure out.

I had issues with precedences, I was trying to fix it in the evening, and now I cannot reproduce bug :) When it will apear again I will place grammar here ASAP.

Ok thanks @Baael. I'm going to close this out for now, but we can reopen if it happens to you again.

authors: Baael maxbrunsfeld

repo: maxbrunsfeld/node-tree-sitter-compiler


text:
Sample app

Why don't you include a small app for using the tool? or at least a few coding in the introduction?

PDF is not working with Unicode? it's showing wrong order for Arabic letter as example

@omarmallat, I plan on creating an example app, but I do not have time to do it at this moment. Maybe somebody from the community would help with that.
If something is wrong with the PDF formatting then create a separate issue. I am using this library to create reports in Russian and do not think that problem is with Unicode. SimpleWPFReporting relies on third party library to generate PDF, so I am not sure if anybody could help you with that unless you are willing to help yourself.

authors: maximcus omarmallat

repo: maximcus/SimpleWPFReporting


text:
2 Channel Sonoff?

Hello, I have a two channel sonoff device. Does this firmware works with my device as well?
thank you

https://github.com/maximkulkin/esp-homekit-demo/tree/master/examples/sonoff_dual_lights
https://github.com/lzparkma/esp-homekit-demo/tree/master/examples/sonoff_dual_toggle

repo: maximkulkin/esp-homekit-demo


text:
ESP32 - Timout - Waiting for Header

Hi all,
I am trying to work with ESP32 with the most basic header available here on amazon.
However, I am constantly failing to do anything with it.
Checking the voltage on pins:
Pin 3V3 (2) and EN = 3.29.
Pin GPIO0 and GND(1) = GND
Pin GPIO2 - Floating
I am not sure what I am missing as I have tried almost everything but still seems to fail.
Can anyone please help with your hardware setup for successful communication with ESP32?
Much appreciate any pointers.
Thanks,
Kunjal

Just start with something more straightforward

@maximkulkin , Thanks mate.
I did try something very basic of my own on a perforated PCB and it worked out perfectly fine.
Thanks ton.
K


text:
🛑 Home | Canadian Armed Forces is down

In 63391bd, Home | Canadian Armed Forces (https://forces.ca) was down:

HTTP code: 503
Response time: 171 ms

Resolved: Home | Canadian Armed Forces is back up in 46d6423 after 16 minutes.

repo: maxneuvians/etat-status


text:
🛑 Department of Justice / Ministère de la Justice is down

In b949ab6, Department of Justice / Ministère de la Justice (https://justice.gc.ca/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Department of Justice / Ministère de la Justice is back up in 72acec9 after 56 minutes.

repo: maxneuvians/status-statut


text:
alwaysOnTop not working

I'm passing alwaysOnTop: true as an option as documented, but the window still hides on blue every time 😢

Ah it looks like the option still needs to be set as always-on-top, weird-looking for a js object key. I swear earlier it told me that this was deprecated and to switch to camelCase but maybe I'm crazy. Either way, the hyphenated option works, so feel free to close this. Only leaving it open to see if there's a response about the camelCase thing...

alwaysOnTop is used as of 1.0.0 and possibly earlier

Why was it changed to being hyphenated?

It was hyphenated but they changed it to camelCase:
http://electron.atom.io/docs/api/browser-window/#class-browserwindow

Right, but now things don't match up. This library still uses the hyphenated option: https://github.com/maxogden/menubar/blob/master/index.js#L84

Yes, I believe there is a pull request for that
On Jun 3, 2016 8:51 AM, Jeff Escalante notifications@github.com wrote:Right, but now things don't match up. This library still uses the hyphenated option: https://github.com/maxogden/menubar/blob/master/index.js#L84
—You are receiving this because you commented.Reply to this email directly, view it on GitHub, or mute the thread.

v5.0.0 now uses camelCase for options.

authors: jenslind jescalan simonhochrein

repo: maxogden/menubar


text:
ベンチマーク用CI修正

ベンチマーク用のCIがコメント部分で落ちていたので修正した。

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

Comparison is base (dd227b1) 70.25% compared to head (a1041f8) 70.25%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main       #2   +/-   ##
=======================================
  Coverage   70.25%   70.25%
=======================================
  Files           5        5
  Lines         279      279
=======================================
  Hits          196      196
  Misses         70       70
  Partials       13       13

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

authors: codecov-commenter mazrean

repo: mazrean/formstream


text:
Installation error - error[E0658]: arbitrary expressions in key-value attributes are unstable

Tried to install it with both stable and nightly version of rust and got the same error
For more information about this error, try `rustc --explain E0658`.
error: failed to compile `lolcrab v0.1.0`, intermediate artifacts can be found at `/tmp/cargo-installGIyozr`

Caused by:
  could not compile `clap`

Please run rustup update and try installing again.

Unfortunately, it happened again even though I've run "rustup update"
`
❯ cargo install lolcrab
Updating crates.io index
Installing lolcrab v0.1.0
Compiling libc v0.2.101
Compiling getrandom v0.1.16
Compiling proc-macro2 v1.0.29
Compiling unicode-xid v0.2.2
Compiling cfg-if v1.0.0
Compiling syn v1.0.76
Compiling version_check v0.9.3
Compiling ppv-lite86 v0.2.10
Compiling siphasher v0.3.7
Compiling proc-macro-hack v0.5.19
Compiling autocfg v1.0.1
Compiling memchr v2.4.1
Compiling unicode-segmentation v1.8.0
Compiling lazy_static v1.4.0
Compiling hashbrown v0.11.2
Compiling unicode-width v0.1.8
Compiling vec_map v0.8.2
Compiling regex-automata v0.1.10
Compiling os_str_bytes v3.1.0
Compiling termcolor v1.1.2
Compiling strsim v0.10.0
Compiling bitflags v1.3.2
Compiling fastrand v1.5.0
Compiling phf_shared v0.8.0
Compiling proc-macro-error-attr v1.0.4
Compiling proc-macro-error v1.0.4
Compiling indexmap v1.7.0
Compiling textwrap v0.14.2
Compiling heck v0.3.3
Compiling atty v0.2.14
Compiling quote v1.0.9
Compiling rand_core v0.5.1
Compiling bstr v0.2.16
Compiling rand_pcg v0.2.1
Compiling rand_chacha v0.2.2
Compiling rand_xorshift v0.2.0
Compiling rand v0.7.3
Compiling noise v0.7.0
Compiling phf_generator v0.8.0
Compiling phf_macros v0.8.0
Compiling clap_derive v3.0.0-beta.4
Compiling phf v0.8.0
Compiling csscolorparser v0.5.0
Compiling colorgrad v0.5.0
Compiling clap v3.0.0-beta.4
error[E0658]: arbitrary expressions in key-value attributes are unstable
--> /home/v/.cargo/registry/src/github.com-1ecc6299db9ec823/clap-3.0.0-beta.4/src/lib.rs:8:10
|
8 | #![doc = include_str!("../README.md")]
|          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: see issue #78835 https://github.com/rust-lang/rust/issues/78835 for more information
error[E0658]: use of unstable library feature 'osstring_ascii'
--> /home/v/.cargo/registry/src/github.com-1ecc6299db9ec823/clap-3.0.0-beta.4/src/parse/matches/matched_arg.rs:130:19
|
130 |                 v.eq_ignore_ascii_case(val)
|                   ^^^^^^^^^^^^^^^^^^^^
|
= note: see issue #70516 https://github.com/rust-lang/rust/issues/70516 for more information
error: aborting due to 2 previous errors
For more information about this error, try rustc --explain E0658.
error: failed to compile lolcrab v0.1.0, intermediate artifacts can be found at /tmp/cargo-installfcSU7G
Caused by:
could not compile clap
`

Unfortunately, it happened again even though I've run "rustup update"
`
❯ cargo install lolcrab
Updating crates.io index
Installing lolcrab v0.1.0
Compiling libc v0.2.101
Compiling getrandom v0.1.16
Compiling proc-macro2 v1.0.29
Compiling unicode-xid v0.2.2
Compiling cfg-if v1.0.0
Compiling syn v1.0.76
Compiling version_check v0.9.3
Compiling ppv-lite86 v0.2.10
Compiling siphasher v0.3.7
Compiling proc-macro-hack v0.5.19
Compiling autocfg v1.0.1
Compiling memchr v2.4.1
Compiling unicode-segmentation v1.8.0
Compiling lazy_static v1.4.0
Compiling hashbrown v0.11.2
Compiling unicode-width v0.1.8
Compiling vec_map v0.8.2
Compiling regex-automata v0.1.10
Compiling os_str_bytes v3.1.0
Compiling termcolor v1.1.2
Compiling strsim v0.10.0
Compiling bitflags v1.3.2
Compiling fastrand v1.5.0
Compiling phf_shared v0.8.0
Compiling proc-macro-error-attr v1.0.4
Compiling proc-macro-error v1.0.4
Compiling indexmap v1.7.0
Compiling textwrap v0.14.2
Compiling heck v0.3.3
Compiling atty v0.2.14
Compiling quote v1.0.9
Compiling rand_core v0.5.1
Compiling bstr v0.2.16
Compiling rand_pcg v0.2.1
Compiling rand_chacha v0.2.2
Compiling rand_xorshift v0.2.0
Compiling rand v0.7.3
Compiling noise v0.7.0
Compiling phf_generator v0.8.0
Compiling phf_macros v0.8.0
Compiling clap_derive v3.0.0-beta.4
Compiling phf v0.8.0
Compiling csscolorparser v0.5.0
Compiling colorgrad v0.5.0
Compiling clap v3.0.0-beta.4
error[E0658]: arbitrary expressions in key-value attributes are unstable
--> /home/v/.cargo/registry/src/github.com-1ecc6299db9ec823/clap-3.0.0-beta.4/src/lib.rs:8:10
|
8 | #![doc = include_str!("../README.md")]
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: see issue #78835 rust-lang/rust#78835 for more information
error[E0658]: use of unstable library feature 'osstring_ascii'
--> /home/v/.cargo/registry/src/github.com-1ecc6299db9ec823/clap-3.0.0-beta.4/src/parse/matches/matched_arg.rs:130:19
|
130 | v.eq_ignore_ascii_case(val)
| ^^^^^^^^^^^^^^^^^^^^
|
= note: see issue #70516 rust-lang/rust#70516 for more information
error: aborting due to 2 previous errors
For more information about this error, try rustc --explain E0658.
error: failed to compile lolcrab v0.1.0, intermediate artifacts can be found at /tmp/cargo-installfcSU7G
Caused by:
could not compile clap
`

The error happens when trying to compile "clap v3.0.0-beta.4".
I get no error when compiling "clap v2.33.3".
At https://github.com/clap-rs/clap/blob/master/CHANGELOG.md states that
v3.0.0-beta.4 (2021-08-14) Minimum Required Rust As of this release, clap requires rustc 1.54.0 or greater.
When I do rustup update I get:
`
❯ rustup update
info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'
info: syncing channel updates for 'nightly-x86_64-unknown-linux-gnu'
info: checking for self-updates
stable-x86_64-unknown-linux-gnu unchanged - rustc 1.55.0 (c8dfcfe04 2021-09-06)
nightly-x86_64-unknown-linux-gnu unchanged - rustc 1.57.0-nightly (9bb77da74 2021-09-13)
`
If I set rustup default nightly
`
❯ rustup default nightly
info: using existing install for 'nightly-x86_64-unknown-linux-gnu'
info: default toolchain set to 'nightly-x86_64-unknown-linux-gnu'
nightly-x86_64-unknown-linux-gnu unchanged - rustc 1.57.0-nightly (9bb77da74 2021-09-13)
`
But when I check rustc --version
❯ rustc --version rustc 1.51.0

Did you try rustup self update?

I run rustup update then cargo install lolcrab and it is compiled succesfully.

authors: mazznoer valmormn

repo: mazznoer/lolcrab


text:
Phase Three

Alpha Diversity using QIIME.
Beta Diversity using QIIME.
Any Other Analysis.

Primary workflow done.
Explore other tools.


text:
Define a sort order for profiles on team page

What is the sorting order for the profiles in the team page ?

alphabetical ?
Role importance (Principal Investigator > Researcher > Engineer), then alphabetical ?
Title (Prof  > Dr > other ) then alphabetical
other ?

Once defined, we could verify/fix the team page

Initially, I did put the PIs in alphabetical order by last name. However, I do not have a strong opinion about that. Also, overall alphabetical order by first or last name would work for me.

authors: awortmann dvojtise


text:
Any work for STM32?

If not, I can start it.  :)

What's the status of this?  Is there any "official" mbed support for CMSIS-DAP on the STM32 NUCLEO line in the works?

You can see mbed cmsis-dap project here
https://github.com/mbedmicro/CMSIS-DAP

@x893 thanks for the reply.  sorry, maybe a dumb question (I'm new to mbed), but I don't see any support for STM32F103CBT6 on Nucleo F411RE in the repo you linked to.  From the comments above, it looks like you may have added support in https://github.com/x893/CMSIS-DAP but I was wondering if there are plans to merge this work into https://github.com/mbedmicro/CMSIS-DAP ?

Nucleo F111RE contain STLink V2.1 on board (debugger, serial and flash).
Can't say any about merge because i use V2 (see in HW_STM32\CMSIS-DAP-X893 foler).

What's the difference between V2 and V2-1?  Do you know if there is anybody actively working on adding support for ST-LINK/V2-1 into https://github.com/mbedmicro/CMSIS-DAP ?  (it sounds like this is a no...)

V2.1 support serial and flash as disk (see ST or mbed site for details).
Nobody add STLink to CMSIS. STLink close device from ST.

Looks like there is a PR up for the STM32: https://github.com/mbedmicro/DAPLink/pull/133

repo: mbedmicro/CMSIS-DAP


text:
Dockerise app

Wrap the entire app in a Docker image so that it can be run with Docker in a simple manner. This would improve:

Portability as it can be run anywhere as long as Docker is installed
Easier to deploy as less configuration would be needed
Easier to collaborate with other developers
Scalability as the containers can be clustered.

[ ] Next.JS image
[ ] MongoDB image

repo: mbeps/ringmaster-messaging


text:
Update mutant to 0.8.5

Currently:
Bundler could not find compatible versions for gem "anima":
  In Gemfile:
    devtools (>= 0) ruby depends on
      anima (~> 0.3.x) ruby

    devtools (>= 0) ruby depends on
      mutant (~> 0.8.3) ruby depends on
        anima (~> 0.2.0) ruby

this should fix the issue though

@backus thx.

authors: backus mbj

repo: mbj/devtools


text:
Fix ActiveRecord::StatementInvalid error when using UUID as primary key

If using UUID as primary key, the relationships feature raises ActiveRecord::StatementInvalid error when you try something like:
User.first.find_related_skills

ActiveRecord::StatementInvalid: PG::SyntaxError: ERROR:  syntax error at or near "a56f2e"
LINE 1: ...w FROM users, tags, taggings WHERE (users.id != 96a56f2e-393...
                                                             ^

Thank you
We could generate uuid in postgresql and leave integer for mysql and sqlite3

Oh, I see. But I have no idea about how to modify the spec/internal/db/schema.rb that only generate uuid in postgresql and leave integer for mysql and sqlite3.

cherry-picked on #898 .

authors: CalvertYang seuros

repo: mbleigh/acts-as-taggable-on


text:
Support HSV colors

This branch adds support for HSV colors. I implemented most of the API of HSL. What's not implemented (If it's desired), can easily be implemented by converting the HSV to HSL, doing the computation, and converting back.

Neat. I think we'd need to update d3.interpolators as well, so that it can detect HSV colors and interpolate them automatically. You'd probably also want a d3.interpolateHsv method.

I've added support for interpolating HSV colors.

With some help from @brewmook, I’ve created the d3-hsv module. Should be easy to implement d3.interpolateHsv and d3.interpolateHsvLong there, too.

authors: alex mbostock

license: ISC


text:
Firefox required on FormsyText

First - Great library, I was looking at doing the same thing and glad I found this.
Second - Question about Firefox.  I have a form with a few text fileds.  In chrome and IE they show up fine but in Firefox the Fields with required attribute show up with red around my multiLine? Anyone else seen this?
<FormsyText id='Name' key="Name'
name="Name"
floatingLabelText="Name"
floatingLabelFixed={true}
hintText="Name (Required)"
required
validations={{maxLength:255}}
validationErrors={{maxLength}}
multiLine={true}
/>

How was this resolved? I'm getting it on all required fields.

Same as above.

It's a default CSS rule applied by Firefox with the selector :-moz-ui-invalid:not(output). Override with box-shadow: none

authors: bteepell krzykrucz rojobuffalo semiautomatix

repo: mbrookes/formsy-material-ui


text:
Gracefully handle no departures for Line Map

Asana task: [Screens 🐞] Gracefully handle no departures for Line Map
Description
Handles the case when there fewer than two departures with predictions but also no departures without a prediction.

Previously this code would pass nil to Screens.V2.Departure.time/1 which raised an exception

Other changes

Refactors counting of departures with predictions to use a single Enum.count/2

I'm happy to remove this if you all feel like it is out-of-place in this changeset

Known issues / thoughts
This doesn't eliminate all possible errors related to the nilability of departures and the arrival and departure fields within schedules and predictions but is instead focused on the specific error reported to Sentry. A refactor to account for that class of errors would have a much larger surface area. Happy to address this if needed!
I'm not a huge fan of nesting if expressions. This function could further refactored to use a with expression which would also return nil in cases where there are no passed stops, DateTime.shift_zone/2 fails, or Timex.format/2 fails. However, I wasn't sure if those possible runtime errors were desired so I left them in.

I'm not a huge fan of nesting if expressions. This function could further refactored to use a with expression which would also return nil in cases where there are no passed stops, DateTime.shift_zone/2 fails, or Timex.format/2 fails. However, I wasn't sure if those possible runtime errors were desired so I left them in.

with expressions can include = assignments, which behave like "normal" assignments and crash if the pattern doesn't match. So if it improves clarity, it should be possible to reformat it as a with and not change the existing behavior. (I'd say crashes are desirable if they would always indicate a "programmer error", so they will cause a test failure or a Sentry report and we can fix them — and I think at least some of these fall into that category.)

@digitalcora hmmm there were more = than there were <- but i realized that the two if expressions could be combined so i went with that: 44487c8

Looking at the trade-off of the added complexity to log an error and continue anyway in this specific case, versus how likely the errors are to occur... I'd say it's questionably worth it. It's not like we do this in any disciplined fashion everywhere we use e.g. Departure.time currently, and if we suspected this was a data issue worth guarding against, we should build it into the return value of that function. (Given the arguments are in fact valid datetimes and zone names / format strings, I don't think DateTime.shift_zone or Timex.format would ever error.)

authors: digitalcora sloanelybutsurely

repo: mbta/screens


text:
Plugin Name Change

https://github.com/mcarvin8/sfdx-decomposer-plugin/issues/17

Re-doing . Still getting the hang of Github porject


text:
🛑 ChatGenie Client API is down

In 2574f6b, ChatGenie Client API ($CHATGENIE_CLIENT_API) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ChatGenie Client API is back up in b8d36da.


text:
🛑 ChatGenie Client API is down

In 599b8fe, ChatGenie Client API ($CHATGENIE_CLIENT_API) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ChatGenie Client API is back up in 4db7b88.


text:
🛑 ChatGenie Client API is down

In 772bb83, ChatGenie Client API ($CHATGENIE_CLIENT_API) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ChatGenie Client API is back up in 9703105.


text:
🛑 ChatGenie Client API is down

In 26212c9, ChatGenie Client API ($CHATGENIE_CLIENT_API) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ChatGenie Client API is back up in 798ae50.


text:
🛑 ChatGenie Client API is down

In 5e29891, ChatGenie Client API ($CHATGENIE_CLIENT_API) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ChatGenie Client API is back up in 3f36f11.


text:
🛑 ChatGenie Client API is down

In 60b40a0, ChatGenie Client API ($CHATGENIE_CLIENT_API) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ChatGenie Client API is back up in 09165d9 after 16 minutes.


text:
🛑 ChatGenie Client API is down

In 01b3ad4, ChatGenie Client API ($CHATGENIE_CLIENT_API) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ChatGenie Client API is back up in 9f27de9 after 17 minutes.


text:
🛑 ChatGenie Client API is down

In b99a9ee, ChatGenie Client API ($CHATGENIE_CLIENT_API) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ChatGenie Client API is back up in c59e536 after 9 minutes.


text:
🛑 ChatGenie Client API is down

In fdc0c86, ChatGenie Client API ($CHATGENIE_CLIENT_API) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ChatGenie Client API is back up in ae59ab8.


text:
🛑 ChatGenie Client API is down

In f966a98, ChatGenie Client API ($CHATGENIE_CLIENT_API) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ChatGenie Client API is back up in 6c1521f after 10 minutes.


text:
🛑 ChatGenie Client API is down

In f232c2b, ChatGenie Client API ($CHATGENIE_CLIENT_API) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ChatGenie Client API is back up in 809e726 after 9 minutes.


text:
🛑 ChatGenie Client API is down

In 987cf78, ChatGenie Client API ($CHATGENIE_CLIENT_API) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ChatGenie Client API is back up in cf5dac3.


text:
🛑 ChatGenie Client API is down

In dd5a9a4, ChatGenie Client API ($CHATGENIE_CLIENT_API) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ChatGenie Client API is back up in 0567b4c after 11 minutes.


text:
🛑 ChatGenie Client API is down

In e4b7250, ChatGenie Client API ($CHATGENIE_CLIENT_API) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ChatGenie Client API is back up in 47749da after 34 minutes.


text:
🛑 ChatGenie Client API is down

In 03bf73b, ChatGenie Client API ($CHATGENIE_CLIENT_API) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ChatGenie Client API is back up in eca10b6.


text:
🛑 ChatGenie Client API is down

In d1815fd, ChatGenie Client API ($CHATGENIE_CLIENT_API) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ChatGenie Client API is back up in 16d2651.


text:
🛑 ChatGenie Client API is down

In 50df131, ChatGenie Client API ($CHATGENIE_CLIENT_API) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ChatGenie Client API is back up in 8a6a1cf.


text:
Balanced tree

Do this library have any tools for building balanced tree? Auto re-parenting nodeleaves? For buildings binary, ternary, ... *ry tree.

Balanced trees, as far as I understand, can be rebalanced because node
ordering is the only constraint for that data model.
Closure tree has both ordering for siblings as well as hierarchy support,
so rebalancing would be nonsensical. You'd be giving children different
parents than what you originally assigned.

Yes, right. For example, I want build balanced binary tree(not search tree, so
I do not care about the arrangement of the leaves). Node_1 already have 2 children (node_2 and node_3). Each nodes (node_2 and node_3) also have 2 children (node_4..node_7). If I add new node_8 with parent node_1 realy it should be node_4. When I want add node_9 for parent node_1 real parent should be node_4. And so on.. node10->node5.
How I can find node (not leaf) with minimal level (so close for getted parent-node) and minimal number of children?

Please read about the closure tree data structure. Ancestral and descendant
lineages aren't what you are looking for.
In your case, just use a database that has a performant index type for your
sortable column. I suggest postgres.
Good luck.

authors: dexion mceachen


text:
🛑 Reddit Mirror (Redlib) is down

In a0f64da, Reddit Mirror (Redlib) (https://hong-di.eu.org/) was down:

HTTP code: 502
Response time: 536 ms

Resolved: Reddit Mirror (Redlib) is back up in f937f07 after 32 minutes.

repo: mchaNetwork/status


text:
🛑 GitHub Mirror is down

In 8c6c6f4, GitHub Mirror (https://gh.chapro.xyz) was down:

HTTP code: 500
Response time: 190 ms

Resolved: GitHub Mirror is back up in c7c6ccf after 5 minutes.


text:
🛑 Wikipedia Mirror is down

In 96b9b42, Wikipedia Mirror (http://www.wp.chapro.xyz/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Wikipedia Mirror is back up in b07c9ed.


text:
force-pushed low view videos

just some observations to document the filter

all have byline-separated (also shared with sponsored video post)
all have New tag

It is only in the combination of the two that there exists this forced-view element, filtering by views seems to be an alternative (<100)

closed in https://github.com/mchangrh/yt-neuter/commit/60fdbfbdf01e4444a4389d8d1d54e1a9530c264b#diff-0988cd96a4aa3c248e0e22b805c22d1885b1766d3f4ef26e5a4f3d3ba60fc8a4

People are apparently getting these on their home feed and I can't seem to replicate :/

byline-separated is also an indicator, will have to inspect deeper

very janky test filter, they seem to also intersect with style inset:

closing due to inactivity and overall less presence

repo: mchangrh/yt-neuter

license: Unlicense


text:
[Docs] Add search console tag for verification

Description
As part of ticket 1377 on the internal repo.
Adding CYb3cxosCgsN2QDQVaSGQpMQCesqpsGQ3oTM02NtvkY as our tag to enable readthedocs to add it to our hosted docs for verification by Google search console.
Screenshot
Notice

[x] I acknowledge and agree that, by checking this box and clicking "Submit Pull Request":

I submit this contribution under the Apache 2.0 license and represent that I am entitled to do so on behalf of myself, my employer, or relevant third parties, as applicable.
I certify that (a) this contribution is my original creation and / or (b) to the extent it is not my original creation, I am authorized to submit this contribution on behalf of the original creator(s) or their licensees.
I certify that the use of this contribution as authorized by the Apache 2.0 license does not violate the intellectual property rights of anyone else.
I have not referenced individuals, products or companies in any commits, directly or indirectly.
I have not added data or restricted code in any commits, directly or indirectly.

I approved but would also be curious what this actually does?

@antonymilne So when we next do a release, this means mkdocs will build a site verification tag into google search console. The site console will trust that we own the site, and will report on the google search keywords that brought users to the vizro.readthedocs.io pages.
It basically gives us some better insights into what we're ranking for (and what our users are looking for when we surface on Google and they're convinced by the metadata text to follow the link). We can match up if we're delivering in the docs what the user looked for and, if not, plan to improve it.
Sadly, we can't use google analytics since that keeps track of users across the site and there are various European GDPR implications. But search console is safe since it's search data that is kept by google, not tracked by us.

Oh nice, that sounds great. I look forward to hearing what we learn from this tracking 👍

authors: antonymilne stichbury

repo: mckinsey/vizro


text:
Please consider fixing issues detected by repository checker

Notification from ioBroker Check and Service Bot
Dear adapter developer,
I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter weblate-test for common errors and appropiate suggestions to keep this adapter up to date.
Please see the result of the check below.
ioBroker.weblate-test
  -

[ ] :heavy_exclamation_mark: [E029] Node.js 16 is required as minimum, node.js 18 is recommended. Please adapt "{'engines' : { 'node' >= '14' } }" at package.json.
[ ] :heavy_exclamation_mark: [E033] @iobroker/adapter-core 2.6.8 specified. 3.1.4 is required as minimum, 3.1.6 is recommended. Please update dependencies at package.json
[ ] :heavy_exclamation_mark: [E036] @iobroker/testing 4.1.0 specified. 4.1.3 is required as minimum,  4.1.3 is recommended. Please update devDependencies at package.json
[ ] :heavy_exclamation_mark: [E039] "keywords" within package.json must contain some keywords besides "ioBroker, smarthome" related to adapter
[ ] :heavy_exclamation_mark: [E042] "globalDependencies" is misplaced at package.json. Did you mean "common.globalDependencies" at io-package.json?
[ ] :heavy_exclamation_mark: [E046] devDependency must not require a specific version. Use "~1.2.3" or "^1.2.3" syntax. Please update "@alcalzone/release-script-plugin-iobroker:3.5.9"
[ ] :heavy_exclamation_mark: [E046] devDependency must not require a specific version. Use "~1.2.3" or "^1.2.3" syntax. Please update "@alcalzone/release-script-plugin-license:3.5.9"
[ ] :heavy_exclamation_mark: [E162] js-controller 3.3.22 listed as dependency but 4.0.24 is required as minimum, 5.0.19 is recommended. Please update dependency at io-package.json.
[ ] :heavy_exclamation_mark: [E169] "common.keywords" must be an array within io-package.json and contain some useful keywords
[ ] :heavy_exclamation_mark: [E200] Not found on npm. Please publish
[ ] :heavy_exclamation_mark: [E606] Current adapter version 0.0.1 not found in README.md
[ ] :heavy_exclamation_mark: [E802] No topics found in the repository. Please go to "https://github.com/mcm1957/ioBroker.weblate-test", press the settings button beside the about title and add some topics.
[ ] :eyes: [W105] Missing suggested translation into uk of "common.titleLang" in io-package.json.
[ ] :eyes: [W109] Missing suggested translation into uk of "common.desc" in io-package.json.
[ ] :eyes: [W115] "common.tier" is required in io-package.json. Please check https://github.com/ioBroker/ioBroker.docs/blob/master/docs/en/dev/objectsschema.md#adapter.
[ ] :eyes: [W145] Missing suggested translation into uk of some "common.news" in io-package.json.
[ ] :eyes: [W181] "common.license" in io-package.json is deprecated. Please define object "common.licenseInformation"
[ ] :eyes: [W184] "common.main" is deprecated and ignored. Please remove from io-package.json. Use "main" at package.json instead.
[ ] :eyes: [W184] "common.title" is deprecated and replaced by "common.titleLang". Please remove from io-package.json.
[ ] :eyes: [W400] Cannot find "weblate-test" in latest repository
[ ] :eyes: [W510] "/admin/i18n/uk/translations.json" or "admin/i18n/uk.json" not found, but admin support is declared. Please add.
[ ] :eyes: [W523] "package-lock.json" not found in repo! Please remove from .gitignore!
[ ] :eyes: [W606] Could not retrieve timestamp of LATEST revision at npm.
Please review issues reported and consider fixing them as soon as appropiate.

Errors reported by repository checker should be fixed as soon as possible. Some of them require a new release to be considered as fixed. Please note that errors reported by checker might be considers as blocking point for future updates at stable repository.
Warnings reported by repository checker should be reviewed. While some warnings can be considered as a suggestion and be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.
Feel free to contact me (@iobroker-bot) if you have any questions or feel that an issue is incorrectly flagged.
And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.
your
ioBroker Check and Service Bot
Note: This issue replaces issue #33
@mcm1957 for evidence

This issue has been replaced by new isse #35
This issue can be closed.
your
ioBroker Check and Service Bot


text:
Adds support for async file mthods

Adds support for async file mthods
Renames original methods with 'Sync' suffix to match dart io FileSystem methods names
Closes #2

Thanks for the contribution!
Looks like you need to implement the new methods for lib/src/platform/unsupported.dart as well. You can run dart test -p chrome locally to test.

Done!

LGTM!
I don't expect the api to change going forward, but I'll change 1.0.0 to 0.4.0 and release. If this package remains stable for awhile with no issues, I'll release the 1.0.0.


text:
BuiltinExtensions git pull failed

Your question
./launch-linux.sh --launch_mode none --host 0.0.0.0
after the SwarmUI run, BuiltinExtensions git pull failed.Can I skip the git pull process?
Logs
Starting webserver on http://0.0.0.0:7801
14:30:32.642 [Init] Program is running.
14:30:37.991 [Info] Creating new admin session 'local' for 127.0.0.1
14:31:27.292 [Warning] Git process 'fetch' in '/home/deepin/Documents/SwarmUI' has been running for over a minute, something may have gone wrong, allowing 1 more minute to finish...
14:31:27.475 [Warning] Git process 'pull' in '/home/deepin/Documents/ComfyUI' has been running for over a minute, something may have gone wrong, allowing 1 more minute to finish...
14:31:27.526 [Warning] Git process 'pull' in '/home/deepin/Documents/SwarmUI/src/BuiltinExtensions/ComfyUIBackend/DLNodes/ComfyUI-SAI_API' has been running for over a minute, something may have gone wrong, allowing 1 more minute to finish...
14:31:32.100 [Init] Swarm is up to date! You have version 0.9.4.0, and 0.9.4.0-Beta is the latest.
14:31:35.251 [Init] Self-Start ComfyUI-0 on port 7821 is loading...
14:32:50.299 [Error] Self-Start ComfyUI-0 on port 7821 failed to start: The operation was canceled.
14:34:00.550 [Warning] [ComfyUI-0/STDERR] Traceback (most recent call last):
14:34:00.551 [Warning] [ComfyUI-0/STDERR]   File "/root/miniconda3/envs/swarmui/lib/python3.10/urllib/request.py", line 1348, in do_open
14:34:00.551 [Warning] [ComfyUI-0/STDERR]     h.request(req.get_method(), req.selector, req.data, headers,
14:34:00.551 [Warning] [ComfyUI-0/STDERR]   File "/root/miniconda3/envs/swarmui/lib/python3.10/http/client.py", line 1283, in request
14:34:00.551 [Warning] [ComfyUI-0/STDERR]     self._send_request(method, url, body, headers, encode_chunked)
14:34:00.551 [Warning] [ComfyUI-0/STDERR]   File "/root/miniconda3/envs/swarmui/lib/python3.10/http/client.py", line 1329, in _send_request
14:34:00.551 [Warning] [ComfyUI-0/STDERR]     self.endheaders(body, encode_chunked=encode_chunked)
14:34:00.551 [Warning] [ComfyUI-0/STDERR]   File "/root/miniconda3/envs/swarmui/lib/python3.10/http/client.py", line 1278, in endheaders
14:34:00.551 [Warning] [ComfyUI-0/STDERR]     self._send_output(message_body, encode_chunked=encode_chunked)
14:34:00.551 [Warning] [ComfyUI-0/STDERR]   File "/root/miniconda3/envs/swarmui/lib/python3.10/http/client.py", line 1038, in _send_output
14:34:00.551 [Warning] [ComfyUI-0/STDERR]     self.send(msg)
14:34:00.551 [Warning] [ComfyUI-0/STDERR]   File "/root/miniconda3/envs/swarmui/lib/python3.10/http/client.py", line 976, in send
14:34:00.551 [Warning] [ComfyUI-0/STDERR]     self.connect()
14:34:00.551 [Warning] [ComfyUI-0/STDERR]   File "/root/miniconda3/envs/swarmui/lib/python3.10/http/client.py", line 1448, in connect
14:34:00.551 [Warning] [ComfyUI-0/STDERR]     super().connect()
14:34:00.551 [Warning] [ComfyUI-0/STDERR]   File "/root/miniconda3/envs/swarmui/lib/python3.10/http/client.py", line 942, in connect
14:34:00.551 [Warning] [ComfyUI-0/STDERR]     self.sock = self._create_connection(
14:34:00.551 [Warning] [ComfyUI-0/STDERR]   File "/root/miniconda3/envs/swarmui/lib/python3.10/socket.py", line 845, in create_connection
14:34:00.551 [Warning] [ComfyUI-0/STDERR]     raise err
14:34:00.552 [Warning] [ComfyUI-0/STDERR]   File "/root/miniconda3/envs/swarmui/lib/python3.10/socket.py", line 833, in create_connection
14:34:00.552 [Warning] [ComfyUI-0/STDERR]     sock.connect(sa)
14:34:00.552 [Warning] [ComfyUI-0/STDERR] OSError: [Errno 101] Network is unreachable
Other
No response

I'm. very confused about that pile of logs.
But (A) the main problem seems to be network connections failed?
(B) when the comfy backend launches, you seem to have ... python requestlib self-activating and sending something? I'm not sure why the source of the call isn't in the trace at all. But whatever request is trying to happen, is failing and crashing the comfy instance. Normally comfy shouldn't be depending on any external network calls just to launch 0.o

repo: mcmonkeyprojects/SwarmUI


text:
[Feat] No Products on any shop

Description
I would like to add some dummy products to these shops.
Please assign me this issue I will add 5 products to each shop.
Screenshots

Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I'm a GSSoC'24-Extd contributor
[X] I'm a Hacktoberfest'24 contributor
[X] I am willing to work on this issue (optional)

Hey @inkerton products are added by their shop owners only. I think you are not familiar with the project structure and how it works. Please read the README.md file for understanding and then raise an issue. I am closing the issue for now. Please raise another issue, which I am happy to assign to you, but make sure the issue is valid and addresses something important on our website. Otherwise, invalid issues will be closed.
In short and concise, when logged in as a seller, you get the functionality to add your own shop and products. Hope you understand now.
Thank you!


text:
Center-Aligned and Styled Load More Button

Description
This update addresses the issue of the Load More button alignment and enhances its appearance using Tailwind CSS. The Load More button is now centered for a more balanced layout, and additional styling has been applied to round the edges, giving it a cleaner and modern look.

Related Issues

Centered the Load More button to improve the overall design.
Applied Tailwind CSS for rounded edges  to make the button visually appealing and consistent with the page style.

Screenshots / videos (if applicable)

closes #1401


text:
Update scalafmt-core to 3.7.12

About this PR
📦 Updates org.scalameta:scalafmt-core from 3.7.11 to 3.7.12
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

🔍 Files still referring to the old version number
The following files still refer to the old version number (3.7.11).
You might want to review and update them manually.
.github/workflows/format.yml

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalafmt-core" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scalameta", artifactId = "scalafmt-core" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, old-version-remains, commit-count:1

Pull Request Test Coverage Report for Build 5894118205

0 of 0   changed or added relevant lines in 0 files are covered.
13 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-13.3%) to 86.735%

Files with Coverage Reduction
New Missed Lines
%

support/http-circe/src/main/scala/org/mdedetrich/pekko/http/support/CirceHttpSupport.scala
3
62.5%

support/stream-circe/src/main/scala/org/mdedetrich/pekko/stream/support/CirceStreamSupport.scala
3
86.96%

stream-json/src/main/scala/org/mdedetrich/pekko/json/stream/JsonStreamParser.scala
7
88.33%

Totals

Change from base Build 5875720564:
-13.3%

Covered Lines:
85

Relevant Lines:
98

💛  - Coveralls

Superseded by #24.

authors: coveralls scala-steward

repo: mdedetrich/pekko-streams-circe


text:
Sonarr/Radarr Import using script

Sonarr and Radarr now support custom scripts for importing (i.e.. pre-import scripts) https://github.com/Sonarr/Sonarr/pull/5538
All the environmental variables seem the same as OnDownload, and the script should just return exit code 3 after transcoding and they will handle the import.

Shouldn't need any script adjustment then, there was never any specific discrimination between the various calls just the presence of the appropriate environment variables. Are you seeing issues?

https://github.com/Sonarr/Sonarr/blob/60f18249b05daa20523542beef54bc126d963d1e/src/NzbDrone.Core/MediaFiles/ScriptImportDecider.cs#L57

Yeah reading over this it will need its own script I think, a preSonarr.py if you will though I can probably reuse a good portion of postSonarr

https://github.com/Sonarr/Sonarr/pull/5956
Looks like until these features are implemented this new import script probably won't be useful for SMA purposes but I'll keep an eye out for it

Note: I can recommend that you do make some changes to your scripts and remux and transcode from the downloads folder directly to the library folder, as it saves an additional unnecessary copy and thus speeds things up a fair bit(especially for pure remuxing). I can also recommend always requesting a rename, as you don't know whether people might be using say the audio or video codec in their naming scheme. Good to see some potential usages by people other than me though.

Yeah I was mostly referring to these two features

Custom import scripts that generate additional extra files to be imported.
Custom import scripts that remux the original media file to a different container, such that its extension must change

Both of things can and often do happen for SMA processed media, changing containers and ripping or downloading additional subtitles are common so as I understand it that would needed to be supported before adopting the feature
Currently doing things in the download folder is handled by post downloader scripts executed by the downloader before notifying Sonarr/Radarr since they haven't supported this historically, but once this matures it would be nice to offer a script for it

https://github.com/Sonarr/Sonarr/pull/5956 is now merged

authors: JeWe37 mdhiggins tomislav


text:
License change: From GPLv3 to BSD

Overview

Change license from GPLv3 to BSD
Change relative import to absolute import

Good

repo: mdpy-dev/mdpy


text:
Heatshrink incompatibility

Due to an issue in the crate, your crate relies on, this crate is most likely incompatible with the original implementation of heatshrink (https://github.com/atomicobject/heatshrink).
See https://github.com/snakehand/heatshrink/issues/1
Greetings, Christian

Indeed the C version was incompatible with the rust version and created corrupted graphics when mixed
Thank you!

You are welcome :-)


text:
Increas client_max_body_size for Nginx

The default value seems too small, the server throws Nginx Error - 413 Request Entity Too Large even on normal data.

Thanks! 👍

authors: punkstar raivisdejus


text:
feat(config): upgrade angular-bootstrap from 0.13 to 1.0

Moving from 0.13 solves many the many issues with this version, provides a more stable interface.
Migration guide: https://github.com/angular-ui/bootstrap/wiki/Migration-guide-for-prefixes
Closes #1142
Closes #1131

@trendzetter you should review our CONTRIBUTING documentation since it seems you need to squash your commits and change the commit text to our standards.

@lirantal I'm a bit new to this, I tried to "squash" my commits and format my text according to the docs. Am I doing it better now?

@trendzetter This is generally how I squash my commits down to 1 commit.
http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html
You basically squash all your commits, into one.. in your case here (based on the commits) it would be git rebase -i HEAD~5
Also, I see you have merge commits here. It's better to not use merge for contributing, as it will sometimes pull in other changes that have already been merged upstream; thus, making it look like your made the changes & there can be conflicts when merging the PR.
Use rebase instead, as described here http://blog.bigbinary.com/2013/09/13/how-to-keep-your-fork-uptodate.html

checkout master, and rebase from upstream master branch
checkout your PR branch, and rebase from your local master branch
if Git tells you that your branches have "diverged", then you will need to git push --force to force your remote branch to be exactly what your local branch is.

This took some time for me to get comfortable with, but it's really not as scary as it appeared to me at first :) The articles I shared really helped me a lot.

I am grateful for you helpful attitude.
Did I pull it off?

LGTM

@mleanos did you test this as well, or just the change for the commit message?

The squash looks good, and the diffs look fine to me. However, I haven't tested. I wanted to, but I don't have time today.
@trendzetter Have you done a quick once over, and made sure nothing on the UI was adversely affected by this?

I haven't worked with ui-bootstrap after 0.13, so I'm not sure if it will change the CSS and look in addition to the directives and such as well.

@lirantal Yes. All seemed to work after fixing the menu. After more systematic screening the code I have found more directives that need updating where I wasn't aware off. I will update my pr.

I have updated my commit based on a carefully checking all ui-bootstrap components. It took me some wrestling with git. I will take a break and give it some more extensive testing.

Further testing revealed no regressions.

@ilanbiala They renamed their directives. Nothing is deprecated. Some directives are extended with additional options since 0.13. The migration guide sums the breaking changes up:
https://github.com/angular-ui/bootstrap/wiki/Migration-guide-for-prefixes

SGTM, haven't tested, but based on the docs, seems fine.

@trendzetter @ilanbiala
I ran through all the tests, and manually tested this branch. Everything looks good to me, with the exception of the confirm dialog not implemented in the article client controller. After looking at the code, I realized that this branch isn't current with master.
@trendzetter Can you rebase with the upstream master branch, and push? Normally, it wouldn't be much of an issue, since the changes would just be merged on top of master. However, these changes have a wide reach over the UI. I'd like to test with the most up to date code-base, to be sure we don't introduce any bugs/issues.

I've synced with the upstream master. The confirm dialog for delete is correctly displayed. I am not seeing any new issues which is expected as the articles module is not using any of the renamed angular-bootstrap directives.

@trendzetter LGTM, just maybe change the scope of the commit message? @codydaig suggestions?

@ilanbiala I'm going to pull this branch down tomorrow and test. I'll ping back tomorrow with any comments.

@codydaig Did you find any issues that I need to look in?

@codydaig is this good to merge?

authors: codydaig ilanbiala lirantal mleanos trendzetter

repo: meanjs/mean


text:
box_scroll_with_you

Commit Message Guidelines
Header
Blank Line
Body
Blank Line
Footer

The header should look like:
<type>(<scope>): <subject>

The body should have any necessary detailed info about the commit:
An example, references as to where this idea came from, etc.

The footer should have all the issues tagged:
Fixes #123, Fixes #456

So a commit should look like:
feat(users): Add new Yahoo authentication

Yahoo authentication idea proposed by @codydaig
Example implementation in file.js

Fixes #82

Types:

feat - Features, Enhancements, and overall Improvements
fix - Fixes, Bugs, HotFixs, etc...
doc - Changes to the Documentation and doesn't actually touch any code.

Scope:

The scope should be where the change took place.
Examples: users, core, config, articles

Subject:

The subject line should be clear and concise as to what is being accomplished in the commit.

General Rules:

No Line in the Commit message can be longer than 80 characters.

Reference: Angular Conventions

@tdtran20 Can you please stop make your PR on MEANJs official repo.
https://github.com/meanjs/mean/pulls?q=is%3Apr+is%3Aclosed you actually spam notification of everybody who work on Meanjs ...

All your PR are both here and on your fork ....

@PierreBrisorgueil, sorry about this. I have mentioned to my team to not open any PR’s to the main meanjs repo (even though I made a mistke earlier in the semester and quickly closed it myself).
Thank you for tagging me. I didn’t realize so many of my classmates kept opening PR’s here. I mentioned it to the professor and she just sent everyone an email to (hopefully) stop it. I also switched my team from a forked repo to downloading it and pushing it to our own repo so that way my team will (hopefully) not make anymore PR’s here 😃.
Please share with everyone who has been working hard to deal with these my extreme thanks for all their patience and for dealing with all of us learning!

Hello,no problem, thanks :)


text:
Would you like to implement a reliable message queue using RPOPLPUSH?

similar project: https://github.com/adjust/rmq

Looks like one already exists :P You could also check out https://github.com/mc0/okq which I worked on with some other friends, it's currently being used in production at my current company and it's working out pretty great. Hope this helps!

Also I should say that antirez is discussing adding kafka-style queues to redis as a builtin type, which will be interesting and is definitely something to keep an eye out for, as that would probably cover your use-case as well once it's out.


text:
UI timeRestriction does not match json schema for StructuredQuery

Structured Query Validation schema does not macht output from UI:
UI sends the following time restriction strings: 2022-08-12T22:59:59.999Z
but the query-schema.json does not expects "date"
https://github.com/medizininformatik-initiative/feasibility-backend/blob/develop/src/main/resources/query/query-schema.json
=> either the UI or the query schema has to be adjusted
@geloro94 , @thkoehler11
@geloro94  - it has to be ensured, that cql as well as flare will function with this format

At the current state, it's easier to adjust the schema. From a logical standpoint using 'date' is better suited. Since datetimes cannot be set in the UI.


text:
Build error : call of overloaded ‘abs(double&)’ is ambiguous

i just update my xcode to 9.3beta,  then i find build error after i update my xcode.

./media-server/src/remoteratecontrol.cpp:113:65: error: call to 'abs' is ambiguous
        if (hypothesis!=OverUsing && (fmin(fpsCalc.GetAcumulated(),60)*std::abs(off...
                                                                       ^~~~~~~~
/usr/include/stdlib.h:137:6: note: candidate function
int      abs(int) __pure2;
         ^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/stdlib.h:111:44: note:
      candidate function
inline _LIBCPP_INLINE_VISIBILITY long      abs(     long __x) _NOEXCEPT {re...
                                           ^
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/stdlib.h:113:44: note:
      candidate function
inline _LIBCPP_INLINE_VISIBILITY long long abs(long long __x) _NOEXCEPT {re...
                                           ^
../media-server/src/remoteratecontrol.cpp:119:7: error: call to 'abs' is ambiguous
                if (std::abs(residual)<3*sqrt(varNoise))
                    ^~~~~~~~
/usr/include/stdlib.h:137:6: note: candidate function

0.20.0   works fine

@murillo128
i change  remoteratecontrol.cpp
#include <math.h>

to
#include <cmath>

fix this problom.   thanks
ps:  can you have a look on https://github.com/medooze/media-server-demo-node/issues/7
i can not make raw rtp input work.

thanxs! commited, will push new version next week and check the other issue

cmath not found on ubuntu, can you try with the std::fabs?

can not find fabs on mac
error: no member named 'fabs' in namespace
      'std'

i mean    not  <cmath.h>

This should work..
https://godbolt.org/g/bMJ6nv
could you confirm which clang version does the xcode use?

Could you try latest version and check if works for you? (sorry but I don't have other way of reproducing the issue)

does not work.   can not find  std:fabs
clang version: clang-6.0
#include  <cmath>   works

Could you try to compile latest master head?

build ok now,  thanks

pushing new ver then, thank you all for your patience!

repo: medooze/media-server-node


text:
Fixes #2971 - update Questionnaire reference inputs

Support both valueCode and valueCodeableConcept in "http://hl7.org/fhir/StructureDefinition/questionnaire-referenceResource" extensions
a. Use valueCode for single resource type (technically, this is the only one in the spec)
b. Use valueCodeableConcept for multiple resource types
Added special case in <ReferenceInput> when only one resource targetType - don't show resource type selector
Added <ResourceTypeInput> component specifically for capturing resource types
Use <ResourceTypeInput> in QuestionnaireBuilder

coverage: 94.041% (-0.01%) from 94.052% when pulling 6403e3069d805ddf836fb9b6c0c8f9efdbc44af9 on cody-improved-questionnaire-reference-input into ffc7333f90052e5012ce8b10bb76a7e539244478 on main.

authors: codyebberson coveralls

repo: medplum/medplum


text:
IP Contact address field isn't parsed.

Hi,
IP Address contacts don't appear to be getting parsed.
Looks like they aren't in the expected fields? Not sure if this is common to all IP records or just the 10 or so I've looked at.
eg; for 8.8.8.8 - https://rdap.arin.net/registry/entity/ABUSE5250-ARIN
import whoisit
>>> whoisit.version
'3.0.4'
>>> whoisit.bootstrap()
>>> r = whoisit.get('8.8.8.8')
>>> r.get('entities').get('abuse')[0].get('address')
{'po_box': '', 'ext_address': '', 'street_address': '', 'locality': '', 'region': '', 'postal_code': '', 'country': ''}

>>> raw = whoisit.get('8.8.8.8', raw=True)
>>> raw.get('entities')[0].get('entities')[0].get('roles')
['abuse']
>>> raw.get('entities')[0].get('entities')[0].get('vcardArray')[1][1]
['adr', {'label': '1600 Amphitheatre Parkway\nMountain View\nCA\n94043\nUnited States'}, 'text', ['', '', '', '', '', '', '']]

Might be able to check if the vcard it makes from the expected field is empty and then try to parse the entry_data field like so.
splits = entry_data.get('label').split('\n')
  v_card_array_data_dict['address'] = VCardArrayAddressDataDict(
      po_box=clean_address(entry_label[-7]),
      ext_address=clean_address(entry_label[-6]),
      street_address=clean_address(entry_label[-5]),
      locality=clean_address(entry_label[-4]),
      region=clean_address(entry_label[-3]),
      postal_code=clean_address(entry_label[-2]),
      country=clean_address(entry_label[-1])
  )

Could be a bit dodgy as \n separated data might vary?

Yeah this is because in your example the address is just stuffed into a label string which is pretty much impossible to reliably parse rather than have them split out properly in the vcard. Different localities have different address formats. For example, these are the adr element labels for 1.1.1.1 (all of these are returned from whoisit.ip('1.1.1.1', raw=True)):
'6 Cordelia St South Brisbane QLD 4101'
'6 Cordelia St'
'PO Box 3646\nSouth Brisbane, QLD 4101\nAustralia'
Basically trying to parse these into a sensible street, locality postcode etc. is near impossible so the library doesn't bother attempting it.
With IP lookups if you need the address your best bet is probably to just use raw=True and look for adr labels yourself manually unfortunately.

Would it be difficult to include the raw, unparsed label alongside the structured data?

No, but that would go against what the parsed output was meant to do in the first place and what raw=True is for. If you need the raw data use that.

Makes sense to me. It's unfortunate that the RIR implementation is so lacking here, I have to imagine they could at least try to map some of these fields properly into the vcard.

Yeah it would be nice the data was all parsed and segregated correctly with the correct labels. My irritation with the weird formats used by different RDAP endpoints is why the parser module in whoisit is as expansive as it is already.
Are you OK if I close this or would you like to raise anything else?

Nah close it off, I'll just grab the raw data parse it manually and shove that address string in somewhere.
ip='8.8.8.8'
raw = whoisit.ip(ip, raw=True)
praw = whoisit.parse(whoisit._bootstrap, 'ip', ip, raw)

Cheers for your help/.

No problem. If RDAP endpoints ever do start returning addresses in a sane format it'll get added to the whoisit parser.

authors: insignia96 jwahsnakupaku meeb

repo: meeb/whoisit


text:
Debian packaging, any plans?

https://carml.readthedocs.io/en/latest/installation.html#signatures

Note: a much easier and arguably better way to get this on Debian or Ubuntu would be for someone to package it in Debian…

Any plans to package it to debian of someone else to do it still stands?

I would be happy to see this packaged in Debian, but I am not myself a Debian Developer. If you'd like to start the process of getting it packaged, that would be great!
I'm also happy to make sensible changes that help packagers.

Started something on https://github.com/nyxnor/carml-deb to be contributed to whonix, but it works on any debian.

Ah, I see. So, first off: cool!
If you want to prepare a PR for this repo at least pointing to that, I'm happy to merge it :)
...and if it helps with making apt install carml work one day, also cool :)

Requested to debian privacy pkgs maintainers for inclusion, let's see.
https://alioth-lists.debian.net/pipermail/pkg-privacy-maintainers/2022/004003.html

authors: meejah nyxnor

repo: meejah/carml

license: unlicense


text:
Cut option on CLI (no colour)

Hello, as I found out through a post on Reddit, it's not possible to issue a cut command in the CLI if the colour of the SVG is not correct.
I don't know if this counts as an issue or a request, but here is my suggestion.
Meerk40t could have an argument in the CLI command so that it knew what was the operation, e.g
-c for cutting or -e for engraving
I don't know if this would work, but here's my reasoning for it.
At the moment when you input an SVG, Meerk40t looks at the "stroke" parameter and finds out what the operation is based on the colour (I assume it's blue for engraving and red for cutting.
My proposal was that when receiving the '-c' argument in the CLI command it would cut every thing on the SVG regardless of the "stroke" value, and would bypass that "colour recognition to match operation" feature.
It would look something like:
MeerK40t -zacS 10 drawingexample.svg
And regardless of the object colours in the svg (stroke values), it would cut everything.
Here's one of the svg files that I have:

<rect fill="none" stroke="#DA2724" stroke-width="7.62" x="8004.9" y="562.3" width="1054.7" height="5910.3"/>
<ellipse fill="none" stroke="#DA2222" stroke-width="7.62" cx="8582" cy="6383.05" rx="955.2" ry="527.35"/>

And it would be nice if it would cut both these item whether the stroke value is "DA2222"/"DA2724"/"black"/"red"/"blue"/etc...
Thank you guys, and keep up the good work

Btw, at the moment I created a script to overcome the issue by receiving the file, replacing all stroke values and issuing the meerk40t command with the new file (new file has all stroke ="red") but the weird thing is that after the cutting is done the terminal still seems to be flooded with messages from MeerK40t. I'm running in verbose mode.

In theory this should all default to running a engrave without the ability to do the only operation that makes an engrave not an engrave. Namely it doesn't do the cut_inner optimization of the file to make sure the inner parts are cut first. The only actual difference beyond that is speed.
Cuts really are the same operation as Engrave except for them doing an optimization to ensure we do cut inner first. I don't think it cares what color it is but let me double check.

(venv) C:\Users\Tat\PycharmProjects\meerk40t-64>MeerK40t.py -zcS 10 ktest.svg
>operation
operation
----------
Operations:
0: Image 140mm/s =T2B 1000ppi ±20
1: Raster1 140mm/s =T2B 1000ppi ±20
2: Engrave 35mm/s 1000ppi
3: Cut 10mm/s 1000ppi
----------
>element
element
----------
Graphical Elements:
0: m 10871.5401555,13.8297716902 l 0,115.104239068 l ...
1: m 2357.58719106,5.41665664163 l 0,115.104239068 L ...
2: m 308.750215975,5.41665664163 l 0,115.104239068 l ...
3: m 9273.70971401,5.41665664163 l 0,115.104239068 l ...
----------
>stroke
stroke
----------
Stroke Values:
0: stroke = #ffff00 - m 10871.5401555,13.8297716902 l 0,115.104239068 l ...
1: stroke = #00ff00 - m 2357.58719106,5.41665664163 l 0,115.104239068 L ...
2: stroke = #0000ff - m 308.750215975,5.41665664163 l 0,115.104239068 l ...
3: stroke = #ff00ff - m 9273.70971401,5.41665664163 l 0,115.104239068 l ...
----------
>element *
element *
Selecting all elements.
>classify
classify
>operation
operation
----------
Operations:
0: Image 140mm/s =T2B 1000ppi ±20
1: Raster1 140mm/s =T2B 1000ppi ±20
2: Engrave 35mm/s 1000ppi
3: Cut 10mm/s 1000ppi
4: Engrave 35mm/s 1000ppi
5: Engrave 35mm/s 1000ppi
6: Engrave 35mm/s 1000ppi
----------
>shutdown

You appear to be right. I don't know why but this thing isn't actually classifying the operations you have. When they were loaded from the CLI they should have been classified automatically into their own little engrave and doing a -S should have set the speed.

Wait, it actually needs the -a flag.
----------
Operations:
0: Image 10mm/s =T2B 1000ppi ±20
1: Raster1 10mm/s =T2B 1000ppi ±20
2: Engrave 10mm/s 1000ppi
3: Cut 10mm/s 1000ppi
4: Engrave 10mm/s 1000ppi
5: Engrave 10mm/s 1000ppi
6: Engrave 10mm/s 1000ppi
----------
>stroke
stroke
----------
Stroke Values:
0: stroke = #ffff00 - m 10871.5401555,13.8297716902 l 0,115.104239068 l ...
1: stroke = #00ff00 - m 2357.58719106,5.41665664163 l 0,115.104239068 L ...
2: stroke = #0000ff - m 308.750215975,5.41665664163 l 0,115.104239068 l ...
3: stroke = #ff00ff - m 9273.70971401,5.41665664163 l 0,115.104239068 l ...
----------
>

The -a sets the speed of all the operations to that value given. This will result in everything running at 10mm/s. The operations being Engrave rather than Cut can't make a difference because I think in this mode they actually can't run the pre-processing stuff anyway. It would just run the Cut as Engrave anyway since it won't do the inner-first optimization and that's the only difference between the two. That and cut goes last. But, that assumes you didn't create other items first.

As for the other issue this should work in 0.7.x if all goes to plan. The plan would be rather than just give you a strict CLI environment you should be able to launch most things through the Console directly, and via a batch file. The option for -b  already exists as does -c for Console mode. the difference here would be that you'd be given a bit more access so you could define your operation directly, classify it, and start it running in the console. And also have access to things like a evg-server thing where you could send data fairly directly to your laser. So you could do the work on your laptop and send the precompiled egv code to your laser over your network connection or whatever.

authors: egasz tatarize


text:
Tweedeck white screen before login (blank screen)

I recently download and installed Franz. I activated four services: WhatsApp, facebook messenger, Gmail inbox and TweetDeck. However, TweetDeck shows a blank screen after clicking Log in.

Expected Behavior

Be able to log in to TweetDeck
Current Behavior

After clicking Log in on TweetDeck (before giving my username and password) the screen goes white.
Screenshots (if appropriate):
Before clicking Log in

After clicking Log in

Possible Solution

Steps to Reproduce (for bugs)

I don't have steps to reproduce as this is happening since I installed Franz.
Context

Your Environment

Franz Version used: 5.0.0-beta.14 Release: 1.7.9 / linux / x64
Operating System and version:  Ubuntu 16.04

Duplicate of #253

repo: meetfranz/franz


text:
Add Twitter Dashboard

This pull request adds the Twitter tool: Twitter Dashboard.
Current issue: #124

PSA:

Goodbyes are never easy
Twitter Dashboard will be closing down in January. In the future, we hope to bring the best features from Dashboard to the broader Twitter community. Thanks for making Dashboard part of how you use Twitter. 💚, the @dashboardapp team

Ok, thank you very much for informing me about that.
@gingerbeardman

authors: gingerbeardman julianYaman

repo: meetfranz/plugins


text:
error with distributed training

Hi,
Thank you for this great work and code!
When I tried to run the code with multi-gpus, I got an error in the following line.
https://github.com/megvii-model/WeightNet/blob/ea318d8c6d51a5f12fffbcc2ca17a1e6feef1a1d/train.py#L156
And the error log is as follows:
loss = dist.all_reduce_sum(loss, "train_loss") / dist.get_world_size()
File "/opt/conda/lib/python3.7/site-packages/megengine/distributed/functional.py", line 238, in all_reduce_sum
assert _group_check(key, nr_ranks), "key, nr_ranks should be set at the same time"
AssertionError: key, nr_ranks should be set at the same time
I'm new to using MegEngine and could not find any related issues by googling.
Please let me know how to resolve this error.
Thank you!

This is a known issue since we've changed the API of distributed operators. In newer versions of megengine, i.e. > 0.5.0, just call
loss = dist.all_reduce_sum(loss) / dist.get_world_size()  without the "train_loss" argument

Now it works! thank you 👍

repo: megvii-model/WeightNet


text:
GetIndex should return the same object as CreateIndex

According to the Getting Started, I can write:
MeilisearchClient client = new MeilisearchClient("http://localhost:7700", "masterKey");
var index = client.CreateIndex("movies");
var documents = new Movie[] {
    new Movie {Id = "1", Name = "Batman"},
    new Movie {Id = "2", Name = "Interstellar"},
    new Movie {Id = "3", Name = "Batman Begins"}
};
var updateStatus = await index.AddDocuments<Movie>(documents);

but I cannot write:
MeilisearchClient client = new MeilisearchClient("http://localhost:7700", "masterKey");
var index = client.GetIndex("movies");
var documents = new Movie[] {
    new Movie {Id = "1", Name = "Batman"},
    new Movie {Id = "2", Name = "Interstellar"},
    new Movie {Id = "3", Name = "Batman Begins"}
};
var updateStatus = await index.AddDocuments<Movie>(documents);

Because 'Task<Index>' does not contain a definition for AddDocuments.
If the index is already created, I should have the possibility to use GetIndex instead of CreateIndex to manipulate my already existing index in the same way 🙂
Both methods should return the same object.
TODO:

[ ] Add this feature in the code
[ ] Add tests

GetIndex should return the same object than CreateIndex.

Are you missing await keyword.

My baaaad! Thanks @satish860 and sorry! 😁

repo: meilisearch/meilisearch-dotnet


text:
Update version for the next release (v0.14.0)

This PR is auto-generated.
The automated script updates the version of meilisearch-dotnet to a new version: "v0.14.0"

bors merge


text:
Drop illuminate/collections

Pull Request
Related issue
Fixes #184
What does this PR do?

Continues work from #190

I've extracted all necessary methods to a custom Collection class not to break any test.
At least the dropped dependency now won't block other dependencies to update in apps.
PR checklist
Please check if your PR fulfills the following requirements:

[x] Does this PR fix an existing issue, or have you listed the changes applied in the PR description (and why they are needed)?
[x] Have you read the contributing guidelines?
[x] Have you made sure that the title is accurate and descriptive of the changes?

OMG that's amazing @norkunas 🎉
I'll review it soon!

This message is sent automatically
Thanks again for contributing to Meilisearch :heart:
If you are participating in Hacktoberfest, and you would like to receive some gift from Meilisearch too, please complete this form.

authors: brunoocasali norkunas

repo: meilisearch/meilisearch-symfony


text:
Example: Update locale.js

Pull Request
Related issue
Fixes #<issue_number>
What does this PR do?

Fix locale.js for entriesQuery example

PR checklist
Please check if your PR fulfills the following requirements:

[ ] Does this PR fix an existing issue, or have you listed the changes applied in the PR description (and why they are needed)?
[ ] Have you read the contributing guidelines?
[ ] Have you made sure that the title is accurate and descriptive of the changes?

Thank you so much for contributing to Meilisearch!

Thanks so much for finding out about this 🙏 I'm happy to see that these example files are used

authors: bidoubiwa lodisy

repo: meilisearch/strapi-plugin-meilisearch


text:
raw vs. processed vs. source data

(Archiving some conversations from the google doc here: I think we're settling on a decision to specify raw, source, and processed data like this, but chime in if you disagree!

processed_data/
--derivatives of to-spec datasets go here, including both subsetting (I dropped all subjects who didn't meet N criteria, I dropped the training trials) and aggregation/analysis (Cross tabs, means by subject/site/task, etc.)

raw_data/
-- expect to find to-spec data in here  and in any subdirectory, EXCEPT
--source_data/
---a special folder that contains anything that is PRIOR to the to-spec raw data and cannot be converted to that format (e.g. pictures of written data entry, obnoxious balls of proprietary data, etc.)

Below copying some archived comments from the draft.

@tyarkoni  This division makes a lot of sense in the fMRI context, where datasets are usually massive, preprocessing generally produces files as big as the originals, and it's not usually possible to do analysis directly on the "raw" data. For psych, I'm not sure this makes as much sense. Most analyses, including data preprocessing, amount to at most a few hundred lines of code, and few large files are generated. I think we may want to reconsider this and instead introduce a standardized way of structuring results (e.g., put everything under results/ or analyses/). This will also facilitate distribution of datasets that include all results, generated figures, etc., which the current approach would discourage.
@mekline  The particular workflow I have in mind here is one I encounter a fair amount where a researcher has one original dataset, then makes a new excel sheet/doc where they drop outlier participants, and then they make another one with just participants who scored above some threshold, but then another one with all scores but just the male participants, etc. This is maybe not a desirable workflow, but it's one that exists, and a good incremental improvement on it is to at least ensure that the original/full version is in a special/protected location.
@jodeleeuw  I’d like to see this distinction present. A workflow that I often use is to generate intermediate CSV files from R so that I can complete portions of an analysis without rerunning what could be a pre-processing step. I usually stick all my data in /data and then have /data/raw and /data/generated. Sometimes this step is important for computational efficiency if I am dealing with a very large N data set and a moderately expensive computation. (Admittedly, many time this isn't necessary and instead just helps me separate the analysis scripts into manageable chunks).
@tyarkoni This appears to contradict point (3) above. FWIW, I generally favor allowing inclusion of processed data. But I think we should formalize this a bit more. E.g., one approach would be to reserve data/ for raw data and processed/ for any derivative/aggregated/processed datasets.
@mekline  : Terminology is hard and I may be missing the mark, but I'm thinking of 'raw' as some data that cannot be converted to spec, e.g. because it is an image rather than a set of variable values. And I'm thinking of 'processed' as any alternate forms of the dataset that get produced after the initial to spec version. Is this coherent?
@jodeleeuw  I think of raw as untouched output from the data generating source. Sometimes the source generates spec-compliant data, sometimes not.

@tyarkoni  This division makes a lot of sense in the fMRI context, where datasets are usually massive, preprocessing generally produces files as big as the originals, and it's not usually possible to do analysis directly on the "raw" data. For psych, I'm not sure this makes as much sense. Most analyses, including data preprocessing, amount to at most a few hundred lines of code, and few large files are generated. I think we may want to reconsider this and instead introduce a standardized way of structuring results (e.g., put everything under results/ or analyses/). This will also facilitate distribution of datasets that include all results, generated figures, etc., which the current approach would discourage.
@mekline  The particular workflow I have in mind here is one I encounter a fair amount where a researcher has one original dataset, then makes a new excel sheet/doc where they drop outlier participants, and then they make another one with just participants who scored above some threshold, but then another one with all scores but just the male participants, etc. This is maybe not a desirable workflow, but it's one that exists, and a good incremental improvement on it is to at least ensure that the original/full version is in a special/protected location.
@jodeleeuw  I’d like to see this distinction present. A workflow that I often use is to generate intermediate CSV files from R so that I can complete portions of an analysis without rerunning what could be a pre-processing step. I usually stick all my data in /data and then have /data/raw and /data/generated. Sometimes this step is important for computational efficiency if I am dealing with a very large N data set and a moderately expensive computation. (Admittedly, many time this isn't necessary and instead just helps me separate the analysis scripts into manageable chunks).
@tyarkoni This appears to contradict point (3) above. FWIW, I generally favor allowing inclusion of processed data. But I think we should formalize this a bit more. E.g., one approach would be to reserve data/ for raw data and processed/ for any derivative/aggregated/processed datasets.
@mekline  : Terminology is hard and I may be missing the mark, but I'm thinking of 'raw' as some data that cannot be converted to spec, e.g. because it is an image rather than a set of variable values. And I'm thinking of 'processed' as any alternate forms of the dataset that get produced after the initial to spec version. Is this coherent?
@jodeleeuw  I think of raw as untouched output from the data generating source. Sometimes the source generates spec-compliant data, sometimes not.

repo: mekline/psych-DS


text:
plugins: update asyncio and aiohttp interfaces on custom plugins

Python modules were updated and some changes were necessary regarding asyncio and
aiohttp modules on custom plugins in order to make them work again.

thanks @julianolf !

repo: meleca/mr-roboto


text:
Encourage use of #thanks channel

Migrated from GitLab: https://gitlab.com/meltano/handbook/-/issues/55
Originally created by @therebbie on 2022-02-02 15:19:58

Encourage everyone to use the #thanks channel even more than they are now.  Also, possibly encourage more thanks to be given in other channels.

View 4 previous comments from the original issue on GitLab

repo: meltano/handbook


text:
add api schema tests back in

@tayloramurphy as part of adding hidden flags to files bundles we got a test failure because the schemas dont accept those flags. This also raised to me the fact that we stopped testing the schema of the generated API which is concerning because what we allow in the plugin definitions and in the API are not the same e.g. usage, next_steps, etc. Luckily nothing is violating the schema though 😅 .
I can make hidden an acceptable attribute in the plugin definition but I'm not sure if we want it to be exposed as part of the API, like it is today with extractors/loaders. I'd lean towards no because we're mostly using the flag to hide or show in the hub but I know the hidden attribute also affects what shows up in the deprecated meltano UI.

I think it makes sense to leave it out. It's primarily for the UI like you said.

repo: meltano/hub


text:
Dogfood Fastly and update documentation with UI instructions

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/1487
Originally created by @dmor on 2019-12-17 21:28:27

[ ] Set up a test account and add credentials to 1Password
[ ]  Populate the test account with fake data
[ ] Go through the process of setting up Fastly as an extractor
[ ] Record a video
[ ] Update documentation

View 4 previous comments from the original issue on GitLab

repo: meltano/meltano


text:
Let Meltano itself and Meltano UI be configured using meltano config and meltano.yml just like plugins

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/2099
Originally created by @DouweM on 2020-06-16 16:13:09

View 7 previous comments from the original issue on GitLab


text:
Demo day videos should be on a Meltano-team hosted instance

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/958
Originally created by @emilie on 2019-09-05 14:47:07

instead of on localhost. I'm not totally sure how this would work, for example would it be an alpha cut of the release? I'm not sure, but it is confusing to watch a demo day video and watch people switch branches during it. It makes it unclear about if these things are actually ready and/or work together.
Especially because the demo day videos are paired with the release post.

View 11 previous comments from the original issue on GitLab


text:
Swift 3.0 compatibility

Hi,
You forgot to push v3.5.0 to Cocoapods. Project doesn't compile with 3.4.2

Please push 3.5.0 asap

I keep having issues with cocoa pods not passing lint test so please download manually in the meantime.

year got the same issue, can you push the branch swift 3 to cocoapod?

I managed to make it work by putting "Use legacy Swift language version" to YES in Build Settings of the pod

got it working now

authors: LivioGama dlpigpen kaunteya melvitax

repo: melvitax/AFDateHelper


text:
seccomp: extend allowed rules for extended usage

This puts syscalls into the allow list that were triggered on latest
systems including extended usage tests, signal and systemd handling.

Thanks!

Out in 1.6.10

authors: anthraxx dormando

repo: memcached/memcached


text:
Create a constructor with a float

The following spec
class TestSpec extends ObjectBehavior
{
    function it_floats()
    {
        $aFloat = 3.44;
        $this->beConstructedWith($aFloat);
        $this->floatMe()->shouldReturn($aFloat);
    }
}

generates the following class:
use float;

class Test
{
    private $argument;

    public function __construct(float $argument)
    {
        $this->argument = $argument;
    }
}

which generates the following error:
PHP Fatal error:  Cannot use float as float because 'float' is a special class name in /var/www/test/src/Test.php on line 5

Looks like we also have dependency issues on php 7.0

Looks like phpunit is causing the php7.0 build to fail should we lower the phpunit version?

Hi @ItsKelsBoys, thanks for your contribution!
However I'd rather go with a fix that makes $fullyQualifiedName->getFullyQualifiedName(); return double: as you can see GenerateConstructorHandler::NON_OBJECT_TYPES doesn't contain integer and boolean, because I decided to go with int and bool only.
I'd like to continue favouring double over float, do you think you could identify and fix the issue in FullyQualifiedName instead?
Also, Travis is failing because phpunit 7 isn't compatible with PHP 7.0. Rather than having to choose between bumping the minimum version of spec-gen to 7.1 or tolling back to PHPUnit 6, this can be fixed by changing dependency on PHPUnit to ^6.0 || ^7.0: when the Travis build runs on PHP 7.0, it will install PHPUnit 6, and when it runs on PHP 7.1, it will install PHPUnit 7.

Sure.

If things should be done differently let me know (im new to all of this) your guidance is desired and much appreciated :)
P.S
Started reading your blog its awesome :)

We had a first fix for that exact same issue a while ago, but it looks like we missed a few edge case. Now thanks to you it's definitely fixed!
You did a perfect job, thank you very much for contributing :+1:
P.S thanks! I should probably start updating it again :thinking:

authors: ItsKelsBoys gnugat

repo: memio/spec-gen


text:
更新4.4.1後LINE機器人回復400錯誤

今天更新玩4.4.1後跟機器人聊天回答400錯誤

換一支openai的API KEY也是一樣 但我的openai方案還有餘額

這個指的是你上下文整體發送過去的量超過了限制，而不是你方案的餘額問題喔．
token 的相關限制可以看這邊：https://platform.openai.com/docs/guides/chat/managing-tokens

as total tokens must be below the model’s maximum limit (4096 tokens for gpt-3.5-turbo-0301)

可以參考 token 算法：https://platform.openai.com/tokenizer

所以我變數的上下文參數要降低嗎? 我現在是設定官方白皮書說的最大值4096

你可以嘗試縮短你發送的內文，或調整這三個參數

名稱
預設值
說明

APP_MAX_PROMPT_MESSAGES
12
上下文語句的數量上限。

APP_MAX_PROMPT_TOKENS
1024
上下文單詞的數量上限。

OPENAI_COMPLETION_MAX_TOKENS
160
詳見 max_tokensopen in new window 參數說明。

這三項我刪掉後就回復正常了 ， 但如果我希望她回復的內容可以長一點，要如何設定這三項才有辦法優化?
OPENAI_COMPLETION_MAX_TOKENS 剛才是單純這項改成4096  那另外兩項要如何修改才能跟得上呢...  有試過三個都改成4096 但一樣會400錯誤

這三項主要是你提供給 AI 的一些資訊，主要能夠使得 AI 更了解前情提要，而讓 AI 能更好的回答問題．
如果你只是希望 AI 回覆的內容可以更長，可以試試看在 AI 回覆完之後，你給出 繼續 讓他繼續回覆產生下文

如果這邊的環境變數的 max_token 跟 openai 的 max_token 是同一個的話，可以嘗試調大這個值．
不過，這個設定是調整最大可回覆長度，如果 AI 判斷不需要長回覆則這個設定就沒有效果了．
你可以試試看在提問時指明你需要的回覆長度，或許會有幫助

感謝 @kindomLee 提供資訊。
@jimmy8399
嗨。
如果你希望機器人回覆你很長的訊息的話，可以把 OPENAI_COMPLETION_MAX_TOKENS 設置成 4096。
至於 APP_MAX_PROMPT_TOKENS 指的是，傳送給 OpenAI 的提示詞的最大 tokens 數，這代表 AI 能夠更理解你的上下文脈絡，與回應無關。不要設太接近 4096 很容易爆。


text:
state-script documentation cleanup

Most significantly:
Moved the bulk of the description (updated) of the variables listed below to the Mender
client configuration section, mostly to avoid duplication of default settings and to avoid
repeating the information. This is after all an more advanced topic of the Mender client,
and does not need be covered in one single page.

StateScriptRetryIntervalSeconds
StateScriptRetryTimeoutSeconds
StateScriptTimeoutSeconds

Signed-off-by: Mirza Krak mirza.krak@northern.tech

Thanks for the review @oleorhagen, pushed an update which fixes the typos spotted by you and some re-wording based on your suggestions.

Pushed a new update with fixes based on @drewmoseley  suggestions.

Would like an approval from you @drewmoseley before merging.

repo: mendersoftware/mender-docs


text:
Add hostname instance count evaluation when deploying on Kubernetes

For Kubernetes try to determine the instance index based on the hostname which is set to a numeric suffix when using a StatefulSet.

Reviewed.

authors: carlos-salinas cwesdorp

repo: mendix/docker-mendix-buildpack


text:
using-version-control-in-studio-pro

Please use the form below, leaving the prefilled data to help us. Thank you.
Page link: using-version-control-in-studio-pro
Document link: _index.md
My Issue/Suggestion
The SVN URL should be https://svn.home.mendix.com/ and SVN password should be PAT too.

See also #6883

Hi @milu777,
Thank you for your feedback!
I verified with the team that only companies that use BYOIDP cannot access the https://teamserver.sprintr.com/ with their Mendix credentials and they have to use https://svn.home.mendix.com/ with PAT. I have added a note to the documentation and a link to the document for more details in this PR. I hope it helps.
Best regards,
Maria

authors: MariaShaposhnikova MarkvanMents milu777

repo: mendix/docs


text:
Note difference in size between backup and database

Added disclaimer that backup size does not equate to the database size

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant MarkvanMents


text:
La version del SDK no se actualiza en cada release

Si no me equivoco, la versión del SDK se debería actualizar en cada release, en esta linea:
https://github.com/mercadopago/dx-php/blob/615f97f577adc404e84126e121af6820e8250d38/src/MercadoPago/Version.php#L6
Sino no veo de que forma se puede saber que versión del SDK se está usando.
Gracias.

Ahi propuse el cambio https://github.com/mercadopago/dx-php/pull/200 en un PR

@nicoandrade
Pasamos a actualizar la version en todos los releases.
Gracias por el reporte!

authors: joelibaceta nicoandrade phgoncalves

repo: mercadopago/dx-php