[Extra Metadata Loader] Missing micro video tag not working correctly

Extension
Extra Metadata Loader
Describe the bug
The function to tag games with missing micro videos is not working as all games get the tag no matter what.
To Reproduce
Make sure you have a game that doesn't have micro video and no missing micro video tag.
Go to Add-ons and go to settings for the plugin. Make sure that checkbox "Update tag that indicates if a game is missing micro video on library update" is checked.
Expected behavior
A game that already has a micro video should not get a missing micro video tag, but right now all games get that tag no matter if it has a video or not.
Screenshots

Extensions log
extensions.log

Fixed


Replaced unittest and it's classes with pytest and functions

Did you update the .run_tests() function in utils?

Do you think I can merge this branch now?


Take screenshot of the browser rendered HTML and convert it to pdf

Hi
My company has html documents that take signatures from end-users, using canvas.
After the end user completes giving all his signatures, we want to enable him to download
a copy of the signed document in PDF format that includes the signatures. is it possible using this tool?

You can convert a canvas to an image using native functions and then insert that image into the pdf document if that's what you are asking.
Also, I stumbled on this: https://www.npmjs.com/package/dom-to-image
Maybe it is useful to you?

We've done that: using html2canvas, we take a screenshot of the html and receive a .png image.
However the image has its flaws, if the html page is long, the output is a long and vey narrow image.
We are looking for a tool that can convert the canvas to PDF and preferably slice the output to pages.

You could setup a canvas that has the size of the desired page (i.e. Letter, A4...). Then draw the screenshot onto that canvas using x-times the page height offset. Eventually, draw the canvas back to an image and insert that image into the pdf.

@omeriko Experiencing similar issue here, did you manage a way with this library?


retargetting problem  with laptop's built-in camera

Very nice work！
And when I used the show_realtime_retargeting.py example with the laptop's built-in camera, the retargeting performed normally when my hand was facing the camera. However, as I gradually rotated my right hand, the retargeting showed a significant deviation. How can we solve this problem? Would using an RGBD camera, like Realsense, resolve it? If so, could you please provide an example code? Thank you very much.
Here is the testingmethod：
python3 show_realtime_retargeting.py   --robot-name allegro   --retargeting-type dexpilot   --hand-type right

Hi @dbdxnuliba
That is an unexpected issue. To further debug this problem, could you help to provide the original RGB video (without mediapipe markers) or image sequences so that I can take a deeper look at the problem you mentioned above?

@yzqin ,sure,could you please tell your email address ,I can send the RGB video to you

https://github.com/user-attachments/assets/3e77cb76-add3-4ca7-8d7f-11a597e9c29b

test_result.zip
and this is the test result by run
'''
python3 show_realtime_retargeting.py --robot-name ability --retargeting-type dexpilot --hand-type right
'''

Hi @dbdxnuliba
Sorry I find that I can not open/download your original RGB video record. Can you send me again.

test.zip
this is the original RGB video record

Hi @dbdxnuliba
Sorry I find that I can not open/download your original RGB video record. Can you send me again.

Dear @dbdxnuliba,
Thank you for sharing this example. I've successfully reproduced the issue on my system. The core problem stems from the poor quality of 3D fingertip position detection in the hand pose estimation.
In the video, even when the thumb and index fingertips are visibly touching, the detected distance between them remains quite large, approximately 0.08 units.
I've made updates to the dex-urdf repository to enhance the fingertip definition for the Allegro hand. While this offers some improvement, the issue persists.
You might want to experiment with the retargeting configuration I've provided below. It includes an increased margin for the finger touching prior. This adjustment helps to some extent, but the results are still unsatisfactory due to the significant detection errors from MediaPipe.
retargeting:
  type: DexPilot
  urdf_path: allegro_hand/allegro_hand_right.urdf

  # Target refers to the retargeting target, which is the robot hand
  wrist_link_name: "wrist"
  finger_tip_link_names: [ "link_15.0_tip", "link_3.0_tip", "link_7.0_tip", "link_11.0_tip" ]
  scaling_factor: 1.6

  # DexPilot parameters
  project_dist: 0.05
  escape_dist: 0.07

  # A smaller alpha means stronger filtering, i.e. more smooth but also larger latency
  low_pass_alpha: 0.2

I will continue investigate this issue. Maybe replace the mediapipe with a better hand pose detector in the example.

Thank you for your  reply. Looking forward to the progress.

Hello！Glad to see this great work, i also want to run the real time simulation on my laptop, however, my PC has an AMD cpu and doesn't have a NVIDIA GPU
My Question is : is my computer able to run the real time sim using the build-in camera?
THX


Saved Models?

Is there a way to view the models saved after the training? I can't open the .pyc files even though they have the Python logo.

I think you need to call torch.save(model.state_dict() to save the model and call torch.load to reload the model. See tutorial here: https://pytorch.org/tutorials/beginner/saving_loading_models.html
pyc file are "python cache" files. They are not checkpoints.


fix: Failed to run serverpod. You need to have dart installed and in your $PATH

On Windows, this is the check that's being run to verify that Dart is indeed present in the PATH:
https://github.com/serverpod/serverpod/blob/e529b9333ce6057fd53d16d86597c14c34bc142c/tools/serverpod_cli/bin/serverpod_cli.dart#L44
This will cause an error, as the file is not named just dart, but dart.exe

Which version of Windows are you running?

Windows 11, Version 10.0.22000 Build 22000.

Thanks! Will try to fix in version 0.9.11

@tomassasovsky Looks like both works.

My Sys Configs
Device name	Minnu
Processor	AMD Ryzen 7 2700X Eight-Core Processor            3.70 GHz
Installed RAM	16.0 GB
Device ID	3F583939-41AA-4002-BBCE-E80160D264B6
Product ID	00330-80000-00000-AA902
System type	64-bit operating system, x64-based processor
Pen and touch	No pen or touch input is available for this display
Edition	Windows 11 Pro Insider Preview - Version 22H2
Installed on	19-08-2022
OS build	25182.1000
Experience	Windows Feature Experience Pack 1000.25182.1000.0

Can you please cross-check that with a sample test file as mentioned below and LMK
tools/serverpod_cli/test/main.dart
import 'package:test/test.dart';

import '../bin/util/command_line_tools.dart';

void main() {
  group('CommandLineTools test', () {
    test('for dart existsCommand', () async {
      var dartExists = await CommandLineTools.existsCommand('dart');
      expect(dartExists, true);
    });
    test('for dart.exe existsCommand', () async {
      var dartExeExists = await CommandLineTools.existsCommand('dart.exe');
      expect(dartExeExists, true);
    });
  });
}

Same error occurs when someone is using FVM for flutter. When flutter and dart is installed using fvm then the installation is done at $HOME->fvm->stable->bin  (in case you are not using stable ,then replace stable with that version name, you will find it when you browse it ) on Mac.
if we run 'which' command it returns empty in terminal. it will print nothing.
then only one thing to do, you need to enter the path by following this guide update path
in my case it was $HOME/.bash_profile just open it using vim
vim $HOME/.bash_profile
and add a path like this.
export PATH=$HOME/fvm/versions/stable/bin:$PATH
replace 'stable' in case you are using different version.

close the terminal and reopen it. then run command 'serverpod' it will always work.Thanks @vlidholt for great framework.

@sanjeevbishnoi Can you check which dart and see if you get any output?

@yahu1031  echo $PATH and make sure it contains the highlighted area, these things may vary on mac m1 series and intel series.  Main idea is to provide serverpod access to dart and flutter which is installed using FVM.

@sanjeevbishnoi Okie, could you please share the error too?

Error : Failed to run serverpod. You need to have dart installed and in your $PATH

@sanjeevbishnoi will check this. Please open this as a new ticket. I will follow it up.

@yahu1031  after following the steps mentioned in my first comment I was solved. Now everything is working. Only thing that is surprising is that when I was typing flutter or dart in the terminal the since last three years It was working. But when I typed 'serverpod' it did not pick the same dart and flutter which was being picked by terminal. I browsed the path of dart and flutter excutables from folder generated by fvm and inserted into PATH and restarted the terminal and everything worked. It is one of the weird bug which can not be replicated on same system again. A user has already  have pull request Check fvm installed #488 for same bug.

@sanjeevbishnoi yes that was an enhancement for fvm case. But that was very less % case. But still it was taken into the case and was PR'ed.


MAINTAINERS: add Hanchin Hsieh (yuchanns) as a REVIEWER

Hanchin Hsieh (@yuchanns) has been very actively contributing to the project:
https://github.com/containerd/nerdctl/pulls?q=author%3Ayuchanns+
So I'd like to invite @yuchanns as a reviewer.
Needs explicit LGTM from @yuchanns and 1/3 of the nerdctl Committers ( $ceil \left( 1 \times \frac{2}{3} \right) = 1$ ), according to https://github.com/containerd/project/blob/main/GOVERNANCE.md :

After a candidate has been informally proposed in the maintainers forum, the
existing maintainers are given seven days to discuss the candidate, raise
objections and show their support. Formal voting takes place on a pull request
that adds the contributor to the MAINTAINERS file. Candidates must be approved
by 2/3 of the current committers by adding their approval or LGTM to the pull
request. The reviewer role has the same process but only requires 1/3 of current
committers.
If a candidate is approved, they will be invited to add their own LGTM or
approval to the pull request to acknowledge their agreement. A committer will
verify the numbers of votes that have been received and the allotted seven days
have passed, then merge the pull request and invite the contributor to the
organization.
For non-core sub-projects, only committers of the repository that the candidate
is proposed for are given votes.

[x] @yuchanns
[x] @ktock (nerdctl Committer)
[x] @fahedouch (nerdctl Committer)

I'd also like to get a few LGTMs from the Core Committers too. (not necessary)
This PR will remain open for 7 days.

LGTM

LGTM, Welcome～

欢迎加入～ @yuchanns


Add modulo operator

Coverage increased (+0.04%) to 47.57% when pulling a0c8a245f67a06df2567aaa82a1c24147deb0238 on features/builder-2 into 1cd4c2bf749ea31907f87ff1cdc1f25f431e7182 on master.


Doc: add lists of the deprecated functionalites

Just document the stuff that is already deprecated. Added:

a new document for the deprecated stuff in the el7toel8
leapp repository
a new section about deprecated stuff in leapp itself

The main deprecation document is pretty long now and the section
for the deprecated list in leapp is not good there. However I do not
see better way how to do it right now. The doc needs to be split
for sure in future, but this is not scope of this PR.

Can one of the admins verify this patch?

review please


CA library not safe to use when shutting down

Following up on the recurring unexpected exceptions/segfaults during teardown:
@danielballan and @dmgav and I chatted about this a bit this morning and in a nutshell concluded:

Solving this in pyepics, along the lines of what @klauer you proposed here, is ultimately the correct way to tackle this. It will need some fleshing out though, to address the additional exceptions I mentioned here https://github.com/bluesky/ophyd/issues/834#issuecomment-615480304.
Alternatively, or additionally, to make ophyd play nice with current versions of pyepics, it may be a good idea to have ophyd avoid making any calls that involve libCA once it detects that Python is shutting down, since it is no longer safe to do so at that point.

The change in this PR is an idea on how to achieve point 2.
It appears to work, in that the caproto tests run without problems with this in place.
It feels a bit dirty though, and makes me question my sanity, so I welcome any and all critical comments and thoughts on why this is a horrible idea.

I was about to make the exact same comment as @danielballan (but with a global bool flag rather than a list).

I was going to ask: Is there an advantage to using a list over a bool?

Surprisingly, I thought about the separate bool flag too, but then I noticed that ca is used a few more times throughout the module, so ideally we should check if the flag is set in every function that is using ca.

I was hoping to get away with only checking in release_pvs (for now?), since I think that's the only one that could realistically be called during shutdown... is it safe to tentatively assume that, until proven otherwise?

I was going to ask: Is there an advantage to using a list over a bool?

I have no idea, but I know a few projects use list. I'm interested too.

The advantage is that if you do:
# modue.py
global_state = True

def change_state():
    global_state = False

and some other package in the module does
from .module import global_state

it will not get up to date information, where if you mutate global_state itself the reference remains useful. But that is not applicable here and I think the current implementation is good.

Power-cycled to re-run CI now that #864 is merged, which fixed some flake8 issues that appeared on master due to flake8 becoming stricter.

from .module import global_state

it will not get up to date information

Yeah I think some style guides forbid importing module variables for exactly this reason.

Thanks for the explanation @danielballan!
I modified it to work the way you suggested. Seems safer / a good habit to encourage, even if not strictly needed the way it is used here.

Will merge/release by end of week if there are no objections.

This still isn't quite right. Downstream library typhos test suite is hanging due to ophyd cleanup even with this PR:
Thread 0x00000001133fedc0 (most recent call first):
  File "/Users/klauer/docs/Repos/pyepics/epics/ca.py", line 882 in pend_io
  File "/Users/klauer/docs/Repos/pyepics/epics/ca.py", line 544 in wrapper
  File "/Users/klauer/docs/Repos/pyepics/epics/ca.py", line 905 in poll
  File "/Users/klauer/docs/Repos/pyepics/epics/ca.py", line 544 in wrapper
  File "/Users/klauer/docs/Repos/pyepics/epics/ca.py", line 1053 in connect_channel
  File "/Users/klauer/docs/Repos/pyepics/epics/ca.py", line 570 in wrapper
  File "/Users/klauer/docs/Repos/pyepics/epics/pv.py", line 437 in connect
  File "/Users/klauer/docs/Repos/pyepics/epics/pv.py", line 48 in wrapped
  File "/Users/klauer/docs/Repos/pyepics/epics/pv.py", line 422 in wait_for_connection
  File "/Users/klauer/docs/Repos/pyepics/epics/pv.py", line 48 in wrapped
  File "/Users/klauer/docs/Repos/pyepics/epics/pv.py", line 729 in get_ctrlvars
  File "/Users/klauer/docs/Repos/pyepics/epics/pv.py", line 48 in wrapped
  File "/Users/klauer/docs/Repos/ophyd/ophyd/_pyepics_shim.py", line 103 in _getarg
  File "/Users/klauer/docs/Repos/pyepics/epics/pv.py", line 963 in count
  File "/Users/klauer/docs/Repos/pyepics/epics/pv.py", line 357 in _check_auto_monitor
  File "/Users/klauer/docs/Repos/pyepics/epics/pv.py", line 48 in wrapped
  File "/Users/klauer/docs/Repos/pyepics/epics/pv.py", line 409 in auto_monitor
  File "/Users/klauer/docs/Repos/pyepics/epics/pv.py", line 48 in wrapped
  File "/Users/klauer/docs/Repos/pyepics/epics/pv.py", line 444 in clear_auto_monitor
  File "/Users/klauer/docs/Repos/pyepics/epics/pv.py", line 48 in wrapped
  File "/Users/klauer/docs/Repos/ophyd/ophyd/_pyepics_shim.py", line 136 in release_pvs
  File "/Users/klauer/docs/Repos/ophyd/ophyd/signal.py", line 1708 in destroy
  File "/Users/klauer/mc/envs/lucid/lib/python3.6/weakref.py", line 548 in __call__
  File "/Users/klauer/mc/envs/lucid/lib/python3.6/weakref.py", line 624 in _exitfunc

Note that release_pvs clears auto monitor, which tries to connect because count isn't available. I had tried to fix this on pyepics's side, but apparently it was a huge can of worms (https://github.com/pyepics/pyepics/pull/203)

Thanks, @klauer. Will hold off in that case.

@hhslepicka with the new pyepics master, is your test suite still failing?

Not failing anymore

Just checking that I understood correctly: Typhos tests pass okay with both the latest pyepics master and this branch of ophyd, correct?
To be sure we're not ending up with redundant fixes I tried various on/off combinations of:

this branch
https://github.com/pyepics/pyepics/pull/204
https://github.com/pyepics/pyepics/commit/1bb4a68c81d5fe128cfdd43aa9cebf5d4bdeb9a2
https://github.com/bluesky/ophyd/pull/866

Caproto's tests pass with both 1+4 and 1+2+4. They fail with 2+4, 2+3, and 2+3+4.
If I understood correctly, Typhos tests pass with 1+2+4, but fail with just 1+4.
In summary: This PR should still be merged, but some downstream projects may experience failures unless they also have pyepics at the current master or later. 2 and 4 are needed and already merged, so no action required. 3 is not merged and doesn't need to be, so no action required.
Is this consistent with everyone else's understanding?

I think that's probably about right. Though any project with many disconnected PVs will greatly increase the possibility of the teardown hanging without (2) and (3). It certainly may happen with the ophyd test suite. Try even the simple:
import ophyd

sigs = {
    i: ophyd.EpicsSignal(f'sim:mtr{i}', name=f'sig{i}')
    for i in range(10000)
}

Hangs with pyepics/pyepics@9371da8 (on clear_auto_monitor)
Succeeds with pyepics/pyepics@master
This, in my opinion, indicates that there should be a new push for a pyepics tag and a bump in ophyd's requirement of it.

Typhos pass with:

pyepics - fixed from 204
ophyd - master

Okay, so we probably want to merge this and maybe beta tag it so we can fix caproto tests, but hold off on a full ophyd release until (3) is merged and pyepics has a new tag.
It would be great to confirm this branch doesn't break Typhos tests as well.

And a heads up on the pyepics side of things, with the current master the following snippet still triggers an uncatchable exception on teardown:
import epics

class Broken:
    def __init__(self, pv):
        self.pv = epics.get_pv(pv)
    def __del__(self):
        self.pv.clear_auto_monitor()

mypv = Broken('sim:mtr1')

Adding (3) replaces the exception with the RuntimeError that is introduced there. But that is a big improvement, because this one can be caught in del.
Using weakref.finalize in a simple example like this sidesteps the issue entirely, but as we've seen that's not enough by itself in more complex situations.

I also tried replacing, in epics/ca.py:
    if AUTO_CLEANUP:
        atexit.register(finalize_libca)

... with ...
    if AUTO_CLEANUP:
        weakref.finalize(sys.modules[__name__], finalize_libca)

... hoping that this would delay finalization enough to avoid the problem altogether, because the module shouldn't go out of scope until nothing needs it, ergo after del and any other finalizers referencing things in ca ran.
Unfortunately it made no noticeable difference. :(

@MikeHart85 why not pursue the fix for that at pyepics instead of patching here?
Seems like the best way despite not being the easier way.

That would be ideal, agreed. Initially it just wasn't really clear to me whether the error was on our end (calling functions we shouldn't be during teardown) or in pyepics (failing on function calls that should succeed or fail more gracefully).
Now I think it's fair to say it's the latter, but we already have these workarounds, and not yet any complete solution in pyepics. If we can find one, I'd certainly prefer that to this.

The pyepics PR referenced above would make this PR obsolete, but let's see if it is accepted before closing this.

With the pyepics PR merged, this PR is likely obsolete and can be closed without merging.
I'm not seeing Caproto test failure anymore locally, when using Ophyd 1.5.0 and the latest pyepics master. Would be great to confirm that this is also the case in CI and other projects that had similar issues.


NoMethodError: undefined method `deduplicate' with ActiveRecord 6.1

Date and time validations raise NoMethodError when used with transient attributes in Rails 6.1.
Executable Test Case:
# frozen_string_literal: true

require 'bundler/inline'

gemfile(true) do
  source 'https://rubygems.org'

  git_source(:github) { |repo| "https://github.com/#{repo}.git" }

  # Activate the gem you are reporting the issue against.
  gem 'activerecord', '6.1.0'
  gem 'sqlite3'
  gem 'validates_timeliness'
end

require 'active_record'
require 'minitest/autorun'
require 'logger'

# This connection will do for database-independent bug reports.
ActiveRecord::Base.establish_connection(adapter: 'sqlite3', database: ':memory:')
ActiveRecord::Base.logger = Logger.new(STDOUT)

ValidatesTimeliness.setup do |config|
  # Extend ORM/ODMs for full support (:active_record included).
  config.extend_orms = [:active_record]
end

ActiveRecord::Schema.define do
  create_table :events, force: true do |t|
  end
end

class Event < ActiveRecord::Base
  attribute :date, :date
  attribute :time, :string

  validates :date, presence: true, timeliness: { date: true }
  validates :time, presence: true, timeliness: { time: true }
end

class BugTest < Minitest::Test
  def test_timeliness_validation
    event = Event.new(
      date: '2020-12-31',
      time: '12:00'
    )

    assert_equal true, event.valid?
  end
end

Expected Result:
Validations are performed:
# Running:

.

Finished in 0.003041s, 328.8284 runs/s, 328.8284 assertions/s.

1 runs, 1 assertions, 0 failures, 0 errors, 0 skips

Actual Result:
A NoMethodError is raised from inside ActiveRecord:
# Running:

E

Finished in 0.004236s, 236.0718 runs/s, 0.0000 assertions/s.

  1) Error:
BugTest#test_association_stuff:
NoMethodError: undefined method `deduplicate' for #<ActiveRecord::Type::DateTime:0x00005635a512e180>
Did you mean?  duplicable?
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activerecord-6.1.0/lib/active_record/connection_adapters/column.rb:93:in `deduplicated'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activerecord-6.1.0/lib/active_record/connection_adapters/deduplicable.rb:19:in `deduplicate'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activerecord-6.1.0/lib/active_record/connection_adapters/deduplicable.rb:14:in `new'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/validates_timeliness-4.1.1/lib/validates_timeliness/orm/active_record.rb:21:in `block in timeliness_column_for_attribute'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/validates_timeliness-4.1.1/lib/validates_timeliness/orm/active_record.rb:19:in `fetch'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/validates_timeliness-4.1.1/lib/validates_timeliness/orm/active_record.rb:19:in `timeliness_column_for_attribute'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/validates_timeliness-4.1.1/lib/validates_timeliness/orm/active_record.rb:10:in `timeliness_attribute_timezone_aware?'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/validates_timeliness-4.1.1/lib/validates_timeliness/validator.rb:110:in `timezone_aware?'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/validates_timeliness-4.1.1/lib/validates_timeliness/validator.rb:67:in `validate_each'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activemodel-6.1.0/lib/active_model/validator.rb:153:in `block in validate'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activemodel-6.1.0/lib/active_model/validator.rb:149:in `each'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activemodel-6.1.0/lib/active_model/validator.rb:149:in `validate'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activesupport-6.1.0/lib/active_support/callbacks.rb:427:in `block in make_lambda'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activesupport-6.1.0/lib/active_support/callbacks.rb:198:in `block (2 levels) in halting'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activesupport-6.1.0/lib/active_support/callbacks.rb:604:in `block (2 levels) in default_terminator'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activesupport-6.1.0/lib/active_support/callbacks.rb:603:in `catch'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activesupport-6.1.0/lib/active_support/callbacks.rb:603:in `block in default_terminator'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activesupport-6.1.0/lib/active_support/callbacks.rb:199:in `block in halting'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activesupport-6.1.0/lib/active_support/callbacks.rb:512:in `block in invoke_before'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activesupport-6.1.0/lib/active_support/callbacks.rb:512:in `each'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activesupport-6.1.0/lib/active_support/callbacks.rb:512:in `invoke_before'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activesupport-6.1.0/lib/active_support/callbacks.rb:105:in `run_callbacks'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activesupport-6.1.0/lib/active_support/callbacks.rb:824:in `_run_validate_callbacks'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activemodel-6.1.0/lib/active_model/validations.rb:406:in `run_validations!'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activemodel-6.1.0/lib/active_model/validations/callbacks.rb:117:in `block in run_validations!'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activesupport-6.1.0/lib/active_support/callbacks.rb:98:in `run_callbacks'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activesupport-6.1.0/lib/active_support/callbacks.rb:824:in `_run_validation_callbacks'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activemodel-6.1.0/lib/active_model/validations/callbacks.rb:117:in `run_validations!'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activemodel-6.1.0/lib/active_model/validations.rb:337:in `valid?'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activerecord-6.1.0/lib/active_record/validations.rb:68:in `valid?'
    timeliness.rb:49:in `test_association_stuff'

1 runs, 0 assertions, 0 failures, 1 errors, 0 skips

This happens with ActiveRecord 6.1.0 but not with <IP_ADDRESS>.
Curiously, this issue only occurs with transient attributes (those declared using attribute), and stops happening if the config.extend_orms = [:active_record] configuration is removed.
My guess is that the ActiveRecord extensions relied on internal functionality that was changed in between 6.0 and 6.1.
Environment:
Rails Version: 6.1.0
Ruby Version: 2.6.5
Validates Timeliness Version: 4.1.1

Update:
I tried upgrading to 5.0.0.beta2, but this still fails. However, a different error is produced:
# Running:

E

Finished in 0.004895s, 204.2817 runs/s, 0.0000 assertions/s.

  1) Error:
BugTest#test_timeliness_validation:
NoMethodError: undefined method `parse' for nil:NilClass
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/validates_timeliness-5.0.0.beta2/lib/validates_timeliness/converter.rb:74:in `parse'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/validates_timeliness-5.0.0.beta2/lib/validates_timeliness/validator.rb:62:in `validate_each'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activemodel-<IP_ADDRESS>/lib/active_model/validator.rb:152:in `block in validate'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activemodel-<IP_ADDRESS>/lib/active_model/validator.rb:149:in `each'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activemodel-<IP_ADDRESS>/lib/active_model/validator.rb:149:in `validate'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:428:in `block in make_lambda'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:200:in `block (2 levels) in halting'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:605:in `block (2 levels) in default_terminator'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:604:in `catch'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:604:in `block in default_terminator'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:201:in `block in halting'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:513:in `block in invoke_before'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:513:in `each'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:513:in `invoke_before'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:134:in `run_callbacks'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:825:in `_run_validate_callbacks'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activemodel-<IP_ADDRESS>/lib/active_model/validations.rb:406:in `run_validations!'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activemodel-<IP_ADDRESS>/lib/active_model/validations/callbacks.rb:117:in `block in run_validations!'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:101:in `run_callbacks'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:825:in `_run_validation_callbacks'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activemodel-<IP_ADDRESS>/lib/active_model/validations/callbacks.rb:117:in `run_validations!'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activemodel-<IP_ADDRESS>/lib/active_model/validations.rb:337:in `valid?'
    /home/mintyfresh/.rbenv/versions/2.6.5/lib/ruby/gems/2.6.0/gems/activerecord-<IP_ADDRESS>/lib/active_record/validations.rb:68:in `valid?'
    timeliness.rb:49:in `test_timeliness_validation'

1 runs, 0 assertions, 0 failures, 1 errors, 0 skips

However, unlike the previous error, this one occurs in both ActiveRecord <IP_ADDRESS> and 6.1.0.
Looks like the beta version for v5 really doesn't like transient attributes.

Found the issue. A timezone wasn't set for my testcase with v5.0.0.beta2.
Upgrading to 5.0.0.beta2 and setting a timezone seems to have resolved the issue.

Haven't looked Rails v6 support yet. So it's interesting that it even works, but be careful as there might be hidden issues.


couldn't find "libimojigraphics.so"

The application crashes (I have no idea where) with the following exception. Occurs on multiple devices and on Android versions 4-6.
Fatal Exception: java.lang.UnsatisfiedLinkError: dalvik.system.PathClassLoader[DexPathList[[zip file "/data/app/xxx.yyy.app-1/base.apk"],nativeLibraryDirectories=[/data/app/xxx.yyy.app-1/lib/arm64, /data/app/xxx.yyy.app-1/base.apk!/lib/arm64-v8a, /vendor/lib64, /system/lib64]]] couldn't find "libimojigraphics.so"        at java.lang.Runtime.loadLibrary(Runtime.java:367)        at java.lang.System.loadLibrary(System.java:1076)        at io.imoji.sdk.graphics.IG.(IG.java:33)        at io.imoji.sdk.graphics.IGEditorView.resetEditor(IGEditorView.java:221)        at io.imoji.sdk.graphics.IGEditorView.access$600(IGEditorView.java:46)        at io.imoji.sdk.graphics.IGEditorView$8.run(IGEditorView.java:293)        at io.imoji.sdk.graphics.IGEditorView.onDrawFrame(IGEditorView.java:101)        at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1649)        at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1354)

compile is successful, but run time crash issue occurred.  Android Studio 2.1.2 , AVD api level 24.
at java.lang.Runtime.loadLibrary0(Runtime.java:972)
at java.lang.System.loadLibrary(System.java:1530)
at io.imoji.sdk.graphics.IG.(IG.java:33)
at io.imoji.sdk.graphics.IGEditorView.resetEditor(IGEditorView.java:221)
at io.imoji.sdk.graphics.IGEditorView.access$600(IGEditorView.java:46)
at io.imoji.sdk.graphics.IGEditorView$8.run(IGEditorView.java:293)
at io.imoji.sdk.graphics.IGEditorView.onDrawFrame(IGEditorView.java:101)
at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1553)
at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1253)

Something seems to have broken my NDK C code. If my services are needed, please inform your manager.

Ok... it seems like this happens on starting image editing

I solved the crash issue by adding following codes in gradle.
defaultConfig {
applicationId "com.tahaclay.gifselfiecam"
minSdkVersion 15
targetSdkVersion 25
versionCode 1
versionName "1.0"
    // this is for targeting custom libs for 32 bit core when you have not prepared 64 bit
    ndk {
        abiFilters "armeabi", "armeabi-v7a", "x86"//, "mips"
    }
}

@DoubleRockStar, your solution worked. Though, I have no idea what it does. Won't it harm 64-bit devices?

I think it will be fine for 64-bit as well

could you please add arm64-v8a libs as well ?


All integers are treated a u64

Sway currently only handles overflow for u64. Other integer types are just treated like a u64 and can contain larger values than they should be allowed to represent.
For instance this test does not panic and instead logs a value that is larger than U32_MAX:
#[test]
fn test_over_flow_works() {
    let a: u32 =<PHONE_NUMBER>;
    let b: u32 = 10000;

    let result: u32 = a + b;
    log(result);
}

It seems to me this issue needs to be split into two PRs.
One PR would fix the integer conversion during IR generation as per the
following comment in the sway-core/src/ir_generation/convert.rs file:

// In Sway for now we don't have as casting and for integers which may be implicitly cast
// between widths we just emit a warning, and essentially ignore it.  We also assume a
// 'Numeric' integer of undetermined width is u64.  The IR would like to be type
// consistent and doesn't tolerate mising integers of different width, so for now, until we
// do introduce explicit as casting, all integers are u64 as far as the IR is
// concerned.

We might want to first get rid of implicit integer conversions (https://github.com/FuelLabs/sway/issues/3470) while handling this issue.
And the other PR would fix assembly generation, because currently all basic
integer binary operations in IR get compiled as native (u64) FuelVM
instructions, so e.g. u32 overflows are not handled during this stage.
The trickier part would be to emulate at the level of VM instructions arithmetic overflows/underflows for bit widths strictly less than 64.
cc @vaivaswatha

In an internal discussion @vaivaswatha commented that another approach would be to only have 64-bit arithmetic operations in the compiler and handle the issue at the Sway level by implementing overflowing 8/16/32-bit operations in the standard library. This simplifies the compiler a lot and if generated assembly is not efficient enough this is going to be an optimizer issue. This also eliminates the need to change IR generation.
Also, it seems 8/16/32-bit operations are not going to be a common use-case so introducing some overhead here should be fine (this overhead is unavoidable for a 64-bit VM anyways).


Rubocop Configuration

[x] Exclude proto_docs directory
[x] Add Naming/FileName exclude for dashed gem name (lib/google-cloud-language.rb)
[x] Disable Style/CaseEquality for all files that define a Configure class. (verify if this is needed with google-style 1.24, because this is super useful in the configuration code and its stupid that rubocop enables this!)
[x] Exclude Metrics/ClassLength for generated client.rb files. These files have the potential to have too many methods for the rules.
[x] Exclude Metrics/LineLength for generated client.rb files. These files have the potential to have documentation strings too long for the rules. Excluding is easier than adding appropriate line breaks. (or we can generate the docs only in proto_docs instead...)

@blowmage Can this be closed?


[WIP] feature store marketplace operator

early review looks good. thanks for taking care of this end to end. 💯  is it possible to add a description of steps to the pr on the steps the reviewer needs to follow to validate the changes?


Update README.md to include updated Vundle command

Using updated Vundle commands 'Plugin' instead of bundle.

Thanks @121watts :balloon:


Protoc generated CPP files should not be dependent on the specific Protobuf version.

in the high version, building the project generate error as follow:

try to cancel general_cpp.sh comments in build script

in the high version, building the project generate error as follow:

try to cancel general_cpp.sh comments in build script

in the high version, building the project generate error as follow:

try to cancel general_cpp.sh comments in build script

get it., thanks.


Testing Challenges

Is there a way to initiate/force a challenge when logging in with this API? I cannot seem to reproduce one so I'm not able to test my challenge code flow and UI.

Just try logging in from unusual place

It's not about location. but about IP. You need to use proxy-server


Feature Request: Install as Admin

Hello!
Could you add a property that allow to disable starting the installer as admin, please?
Currently I inject a property into your dll using dnSpy.
And I use it like that:

Thanks!

Hi,
yes, I actually wanted to implement this in the last update, but I forgot it due to all the stuff with the secflaw.
I will have a look at this tomorrow. :)
Best,
Dominic

Thank you very much! 👍

Hi there,
how much do you need this at the moment? As I see you've got a solution for now.
Currently, I am pretty busy and it may take 2 weeks until I can really release a new version.
Best,
Dominic

Hi,
no problem, I can understand you.
Yes, i found a solution that is working well but I have to repeat the stepts to enable for every update. So, i would be happy if you can implement it with the next update.
Thanks!

Thanks. I will have a look at it the next weekend then.


Return registration_endpoint in OidcProviderConfigurationEndpointFilter

Fixes gh-370

Hi @jgrandja thanks for the feedback, I have made the recommended changes and squashed all the commits

@bibibiu2017 Based on the updates in gh-398, more changes are required in this PR.
OidcProviderConfigurationEndpointFilter should return the registration_endpoint only if OidcClientRegistrationEndpointFilter is enabled. The default is disabled based on gh-398.
I'm going to push this out for the 0.2.1 release.

@bibibiu2017 I'm going to close this PR as the requested changes have not been applied. If you have time please submit a new PR with the requested changes and rebase on latest main. Thanks.


Galera wsrep_sst_method=xtrabackup causing cluster failures when nodes attempt to rejoin

This is an osad bug that will need to be fixed for upgrades in rpc-openstack
https://bugs.launchpad.net/openstack-ansible/+bug/1478105

it's being worked upstream, already double +2'd

Reopened because GitHub.

All merged, closing.


python312Packages.b2sdk: 1.32.0 -> 1.33.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.b2sdk is: Client library and utilities for access to B2 Cloud Storage (backblaze)
meta.homepage for python312Packages.b2sdk is: https://github.com/Backblaze/b2-sdk-python
meta.changelog for python312Packages.b2sdk is: https://github.com/Backblaze/b2-sdk-python/blob/v1.33.0/CHANGELOG.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.33.0 with grep in /nix/store/n5y7a900qhijp9bjc2jkarh8bh4k2rjb-python3.12-b2sdk-1.33.0
found 1.33.0 in filename of file in /nix/store/n5y7a900qhijp9bjc2jkarh8bh4k2rjb-python3.12-b2sdk-1.33.0

Rebuild report (if merged into master) (click to expand)

6 total rebuild path(s)

6 package rebuild(s)

First fifty rebuilds by attrpath
backblaze-b2
deja-dup
duplicity
duply
python311Packages.b2sdk
python312Packages.b2sdk

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/n5y7a900qhijp9bjc2jkarh8bh4k2rjb-python3.12-b2sdk-1.33.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python312Packages.b2sdk https://github.com/r-ryantm/nixpkgs/archive/156fd49d756e24efa8e985db78c2a1dc28f73ebe.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/156fd49d756e24efa8e985db78c2a1dc28f73ebe#python312Packages.b2sdk

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/n5y7a900qhijp9bjc2jkarh8bh4k2rjb-python3.12-b2sdk-1.33.0
ls -la /nix/store/n5y7a900qhijp9bjc2jkarh8bh4k2rjb-python3.12-b2sdk-1.33.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

2 packages failed to build:

backblaze-b2
backblaze-b2.dist

8 packages built:

deja-dup
duplicity
duplicity.dist
duply
python311Packages.b2sdk
python311Packages.b2sdk.dist
python312Packages.b2sdk
python312Packages.b2sdk.dist

Maintainer pings

Done in #299757


Create adapter to cast occurrences and suboccurrences to for common member access

Need to be able to access common members of occurrences and suboccurrences in a single code path. Create adapter that implements common members.

Initial implementation pushed in 646c0b3.
Need to fill out common members in IOccurrenceEsx. After they're implemented, need to take a look at TraverseAssemblyWithAction and TraverseOccurrencesWithAction extension methods to see if there is any utility in maintaining both.

Basic testing complete. Also added OccurrenceDocument property to SubOccurrenceAdapter to directly get an occurrence document so it can be cast to a Solid Edge document with the GetDocumentEsx extension method.


check main branch by default when cargo install --git executed

Due to recent changes default branch of new git projects will be set to main instead of master, so it is probably good idea to check both default branch names. Attempt to install project with main default branch with just cargo install --git currently will fail with
error: failed to find branch `master`

                                     Caused by:
                                                 cannot locate remote-tracking branch 'origin/master'; class=Reference (4); code=NotFound (-3)

Current workaround requires explicitly pass --branch main to cargo.
last tested on
cargo 1.47.0 (f3c7e066a 2020-08-28)

Thanks for the report.  Closing as a duplicate of #3517.


chore: release v1.0.2

This pull request prepares the following release:

Repository
Branch
Update
Change

react-translate
releases/v1.0.2
patch
1.0.1 → 1.0.2

Release Summary
This is going to be published with the following command:
npm publish --tag latest
Merging Instructions
When merging this pull request, you need to Squash and merge and make sure that the title starts with chore: release v1.0.2.

See details
After that, a commit chore: release v1.0.2 will be added and you or your CI can run shipjs trigger to trigger the release based on the commit.

This pull request is automatically generated by Ship.js.

Pull Request Test Coverage Report for Build 428282633

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

Totals

Change from base Build 428275481:
0.0%

Covered Lines:
129

Relevant Lines:
129

💛  - Coveralls


Simplify handling of fragments in net_buf

Today, fragment support in net_buf uses the frags pointer which is unioned with the node one to save 4 bytes (in a structure of 24 bytes without the optimization).
https://github.com/zephyrproject-rtos/zephyr/blob/1217d850f5c5cb4f76b842b3e3250f4106d2d1eb/include/zephyr/net/buf.h#L915-L921
This forces the net_buf code to provide special net_buf_get and net_buf_put functions instead of being able to call k_fifo_get and k_fifo_put directly:
https://github.com/zephyrproject-rtos/zephyr/blob/1217d850f5c5cb4f76b842b3e3250f4106d2d1eb/subsys/net/buf.c#L508-L520
https://github.com/zephyrproject-rtos/zephyr/blob/1217d850f5c5cb4f76b842b3e3250f4106d2d1eb/subsys/net/buf.c#L412-L439
This implies that net_buf_get is not atomic when using fragments (although net_buf_put is) which is a problem. It also forces the net_buf layer to duplicate existing k_fifo/lifo APIs due to this behavior. This is because today all fragments are actually placed in the fifo, instead of just the "head" one.
This issue suggests reverting this optimization:
struct net_buf {

		/** Allow placing the buffer into sys_slist_t */
		sys_snode_t node;

		/** Fragments associated with this buffer. */
		struct net_buf *frags;
...

to simplify the code, increase execution speed at the cost of 4 bytes per net_buf.
Important note: this would not constitute an API change, because none of the public APIs would have to be modified at all.

                            .....
                          ......'..
                         .,.......''
                         .,........''
                         .,'........,.
                          ''........',
                          .,........';.
                          .,........':.
                           '........':.
                           '.......';;
                          .'.......';'
                         .'........';.
                        .''........',
                        ''.........',.
                       ''..........','
                     .''............',,'..
                   .,,...............,,,,,,'...........
                  .,'..............',,,''............'''
      .'''.......''...............',''''...............''
     .''.......''................';''''''..............';
    .............................,:,''''''...........'';;
    ............................';lc;;,,,,'''''''',,;::;.
   ............................',;lddollccc:::::cclodd:.
   ...........................'',;cloc::::;;;;;;:::;;,,,.
   ...........................'',,:c;,''''.............',.
   ..........................''',,::,,,,,''...........',:.
   ..........................''',,:c;,,,,,''......'''',;:.
   ...........................'',,;ll::::;;,,,,,,,,,,;;:.
   ...........................'',,,:oollllllllllllcclc,.
   ...........................''',,:c;;,;,,,''''''''',,.
   .............'..............''',:;,,,,,'..........','
   .......''''',,,''''''''.....''',:;,,,,,''........'',,
    .'''''',,,,;:cc;,,,''''''''''',cc:;;;;,''''''''',;:.
    .'',,;;;;::ccodoc;,,,,,,'''''',:odolcc:;;;;;;;:::;.
     .,;:ccloodddddoccc:;,,,,,,,,,;:lollllllllllloo;.
       ':oool:;'..   .,lcc:;;;;;;;;:c;,,,,''''''',;;.
         .             .;lollccccc:cc:;,,,''.''''',;.
                          .';clodddddl::;;,,,,,,;:c;
                                ....'.';:::cccccc;'
                                         .',,,,..

@jfischer-no thanks, I guess that means this would be welcome for USB
@jhedberg @jori-nordic any objections for Bluetooth?
@rlubos @jukkar would you OK this for networking?

This proposal LGTM.

@jhedberg @jori-nordic any objections for Bluetooth?

I'm ok with it

okay too


Discovery mode without results

Since 3 days I do not get any result running the discovery mode. The discovery starts and runs for 5 min but the end result is that 0 hotspots do respond. But luckily this is not the truth because I do have daily rewards. I do have 2 hotspots and the result (zero respond) is same for both of them. Both are healthy and fully synched and online.
Screenshot I cannot provide, sorry, this is not possible since the last app update
Samsung Galaxy S8 Model SM-G950F
Android version 9

going to close this issue for now. please reopen if this still occurs when we re-enable discovery mode in the future. My initial thoughts are that discovery mode was so popular that it overwhelmed the router instance and state channels, such that some users were unable to see consistent results.
we'll be revisiting the how we can make discovery mode available to users in a better, future-proof, and consistent manner.


Consider renaming Link#context -> Link#spanContext

Span#context was renamed in https://github.com/open-telemetry/opentelemetry-js-api/pull/45. For consistency, it would be nice if link did the same. https://github.com/open-telemetry/opentelemetry-js-api/blob/9b3f9c75a57190841b5f091933932386f63a62ac/src/trace/link.ts#L37
This is a minor ask – if we don't want to create more API churn this can be closed 🙂

This will not make it into the 1.0 release. We can add it after 1.0 as a minor addition and mark the previous property as deprecated.

Is there already a deprecation workflow defined?
For example node.js has 3 types of deprecations where doc deprecated is the only one which is not semver major.

The spec versioning doc has only made affordances for deprecating whole signals, not individual API methods and properties.
I will open a PR with an official deprecation strategy along these lines:

Add @deprecated tsdoc flag with a note pointing to the new function or some upgrade strategy if applicable.
In the next major release, all previously @deprecated functions are removed. This will likely be much later.

Good suggestion. I think at least a whole major cycle is likely to be extremely long. How about next major release unless the release happens within 6 months of deprecation, else the removal must wait for the next major release after that.

I would also say introducing a @deprecated flag is a semver-minor change, not patch, and it must come along with a documented alternative solution.

This rename is a breaking change and I don't see a strong benefit to deprecate the old name. If someone thinks this is causing unnecessary confusion they can open an issue in https://github.com/open-telemetry/opentelemetry-js as this package is moving there.


Improve typings in MaxPool2D

Small change with some minor corrections to the typings in MaxPool2D.

This API is removed in UNet, closing since it will be removed.


File not Found Error. Similar issue to #240

          Hi there, I think I am having a similar error here. ```

Traceback (most recent call last):   File "/Library/Frameworks/Python.framework/Versions/3.13/bin/bandcamp-dl", line 8, in <module>     sys.exit(main())              ~~~~^^   File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/bandcamp_dl/__main__.py", line 34, in main     conf = config.Config()   File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/bandcamp_dl/config.py", line 44, in __init__     self._read_write_config()     ~~~~~~~~~~~~~~~~~~~~~~~^^   File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/bandcamp_dl/config.py", line 60, in _read_write_config     with pathlib.Path.open(CONFIG_PATH, mode="w") as fobj:          ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^   File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/pathlib/_local.py", line 537, in open     return io.open(self, mode, buffering, encoding, errors, newline)            ~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ FileNotFoundError: [Errno 2] No such file or directory: '/Users/ojinika/.config/bandcamp-dl.json'

please help

_Originally posted by @ojinikaudeze in https://github.com/iheanyi/bandcamp-dl/issues/240#issuecomment-2518768666_

I think I may have resolved this issue by creating a .config file but I am not hit with a new error when I try to run the bandcamp-dl command.
`Malformed configuration file `/Users/ojinika/.config/bandcamp-dl.json'. Check json syntax.
Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/urllib3/connectionpool.py", line 466, in _make_request
    self._validate_conn(conn)
    ~~~~~~~~~~~~~~~~~~~^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/urllib3/connectionpool.py", line 1095, in _validate_conn
    conn.connect()
    ~~~~~~~~~~~~^^
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/urllib3/connection.py", line 730, in connect
    sock_and_verified = _ssl_wrap_socket_and_match_hostname(
        sock=sock,
    ...<14 lines>...
        assert_fingerprint=self.assert_fingerprint,
    )
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/urllib3/connection.py", line 909, in _ssl_wrap_socket_and_match_hostname
    ssl_sock = ssl_wrap_socket(
        sock=sock,
    ...<8 lines>...
        tls_in_tls=tls_in_tls,
    )
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/urllib3/util/ssl_.py", line 469, in ssl_wrap_socket
    ssl_sock = _ssl_wrap_socket_impl(sock, context, tls_in_tls, server_hostname)
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/urllib3/util/ssl_.py", line 513, in _ssl_wrap_socket_impl
    return ssl_context.wrap_socket(sock, server_hostname=server_hostname)
           ~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/ssl.py", line 455, in wrap_socket
    return self.sslsocket_class._create(
           ~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
        sock=sock,
        ^^^^^^^^^^
    ...<5 lines>...
        session=session
        ^^^^^^^^^^^^^^^
    )
    ^
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/ssl.py", line 1076, in _create
    self.do_handshake()
    ~~~~~~~~~~~~~~~~~^^
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/ssl.py", line 1372, in do_handshake
    self._sslobj.do_handshake()
    ~~~~~~~~~~~~~~~~~~~~~~~~~^^
ssl.SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1018)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/urllib3/connectionpool.py", line 789, in urlopen
    response = self._make_request(
        conn,
    ...<10 lines>...
        **response_kw,
    )
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/urllib3/connectionpool.py", line 490, in _make_request
    raise new_e
urllib3.exceptions.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1018)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/requests/adapters.py", line 667, in send
    resp = conn.urlopen(
        method=request.method,
    ...<9 lines>...
        chunked=chunked,
    )
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/urllib3/connectionpool.py", line 843, in urlopen
    retries = retries.increment(
        method, url, error=new_e, _pool=self, _stacktrace=sys.exc_info()[2]
    )
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/urllib3/util/retry.py", line 519, in increment
    raise MaxRetryError(_pool, url, reason) from reason  # type: ignore[arg-type]
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='flipseason.bandcamp.com', port=443): Max retries exceeded with url: /album/flip-season-4 (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1018)')))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/Library/Frameworks/Python.framework/Versions/3.13/bin/bandcamp-dl", line 8, in <module>
    sys.exit(main())
             ~~~~^^
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/bandcamp_dl/__main__.py", line 117, in main
    album_list.append(bandcamp.parse(url, not arguments.no_art, arguments.embed_lyrics,
                      ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
                                     arguments.debug))
                                     ^^^^^^^^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/bandcamp_dl/bandcamp.py", line 95, in parse
    response = self.session.get(url, headers=self.headers)
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/requests/sessions.py", line 602, in get
    return self.request("GET", url, **kwargs)
           ~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/requests/sessions.py", line 589, in request
    resp = self.send(prep, **send_kwargs)
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/requests/sessions.py", line 703, in send
    r = adapter.send(request, **kwargs)
  File "/Library/Frameworks/Python.framework/Versions/3.13/lib/python3.13/site-packages/requests/adapters.py", line 698, in send
    raise SSLError(e, request=request)
requests.exceptions.SSLError: HTTPSConnectionPool(host='flipseason.bandcamp.com', port=443): Max retries exceeded with url: /album/flip-season-4 (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1018)')))`

This is a duplicate of #240


Adding CreateTable to QueryBuilder

Adding CreateTable to QueryBuilder for creation of tables from Structs based on gocqlx snake case based naming
it has been tested and used with ScyllaDB

This is an interesting POC, thanks for sharing!
I think that it's somewhat similar to https://github.com/scylladb/gocqlx/issues/4, I'd rather have the code generation for model creation in a separate package. I have some doubts regarding production readiness of this code. Currently it supports only few types, there are questions about primary, sort keys and create table has much more features...
Overall I think it could make an interesting CLI tool that would consume go source file and produced some kind of cql.

thanks for the comment, i used it for my own cluster i decided to share it

This is an interesting POC, thanks for sharing!
I think that it's somewhat similar to #4, I'd rather have the code generation for model creation in a separate package. I have some doubts regarding production readiness of this code. Currently it supports only few types, there are questions about primary, sort keys and create table has much more features...
Overall I think it could make an interesting CLI tool that would consume go source file and produced some kind of cql.

thanks for the comment, i used it for my own cluster i decided to share it


Run PostCSS plugin to remove redundant media queries during production build

I like that we're adding this, but I'm a little concerned about this:

CSS MQPacker changes rulesets’ order. This means the processed CSS will have an unexpected cascading order
Source: https://github.com/hail2u/node-css-mqpacker#css-cascading-order

At the scale of AEM projects, which are usually large code bases, styles being re-ordered unexpectedly could be a big issue.
I'm also interested to see how this affect build time.
You're clear to merge this. I'm going to test this on one of my large projects to see check for issues and test build time.
Thanks!

Thank you, I'm looking forward to your report.

@kevinweber and I discussed this offline, but I'll catch up anyone who finds this thread.
MQPacker is probably great to use on new project, but I would not recommended to add to an existing project. I tested this on a project with ~150 components and had issues certain components not having the desired styling. This could be fixed by rewriting the styles for those component, but that was out of scope for this test.
On a positive note, MQPacker trimmed down output css files files 5–10% (on ~200kb files) and also sped up the build time by ~20%. (55 sec down to mid 40s)
Moving forward, I'd recommend that we continue to keep this repo as a starter kit, and not a Swiss army knife. We will work on having a recommended list of PostCSS plugins, but will not preconfigure them into the build.


Add more troubleshoot instructions

Learn Build status updates of commit 4cdb592:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/cognitive-services/language-service/custom-text-classification/includes/resource-creation-azure-portal.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


api/clients is blocked by CORS policy

Hi,
I have been watching your Pluralsight Course and thought I would run the code locally in docker.  The docker build seemed to work OK, as did the compose up.
However, when I launch the front end, I get the following error:

Maybe I am missing something, but as far as I can see, i have followed the instructions.
Thanks.

@roysbailey  this is a known issue with chrome, you will either need to add a cors header to the backend, or add the CORS plugin to chome

This one keeps biting me - but not all the time - as well. @Jamanya do you have more info on why Chrome is the culprit here?

Related:
https://stackoverflow.com/questions/66534759/chrome-cors-error-on-request-to-localhost-dev-server-from-remote-site
Possible solution:
https://web.dev/cors-rfc1918-feedback/#step-2:-sending-preflight-requests-with-a-special-header

It's weird because I ran into this (again) today. Changed nothing. Restarted docker services and tried again (getting ready to try to apply some of the fixes noted above) and everything worked fine the second time.

I ran into the same? problem with Firefox (103.1).
In Clinic Management I was able to change a Clients preferred name (from David to Dave) without problem, but when I tried to change doctor Who's name (to WhoIs), I got an exception thrown in Blazor (see console screenshot and the log indicated an exception on the Doctor constructor (see log screenshot).
The link to the explanation in the console is: https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS/Errors/CORSMissingAllowOrigin.
Basically it says: "CORS header 'Access-Control-Allow-Origin' missing".

.

Yeah it's an intermittent issue. I'd welcome any insight into how to fix it permanently. Usually I can get around it by nuking the containers and rebuilding everything, but I haven't yet tracked down a root cause.


Reference to a non-exported function in 'SocketIOModule'

Error: Failed to compile.
ERROR in Error during template compile of 'AppModule'
Reference to a non-exported function in 'SocketIOModule'
'SocketIOModule' contains the error at nativescript-socketio/angular/index.ts(25,10).

below are the details of package json
"tns-android": {
"version": "5.0.0"
},
"tns-ios": {
"version": "5.1.0"
}

"@angular/compiler-cli": "~7.1.0",
"@ngtools/webpack": "~7.1.0",

we are facing above issue only in IOS when we execute following command
tns build ios --bundle --env.aot --env.uglify;

Has anyone ever had this problem? Need help.

@Dhruvi109 the issue seems related to a plugin you are using (nativescript-socketio) - can you provide a sample project that can reproduce the issue so we could investigate this one?

Duplicate of https://github.com/NativeScript/NativeScript/issues/6716


[5.5] Be less strict for risky tests in PHPUnit 6.

PHPunit 6 echoes all risky tests for not actually testing anything. This turns the output into something very unfriendly:

This PR allows not to display them.

👎 Tests should instead be annotated with the has no assertions annotation.

No, annotating all tests would result in a too big PR to review, that would not be merged anyway

Would be easy to review.


win-acme renew gives error 0x80131500

Why does the automated renewal in the scheduled task give this error?
0x80131500

Please check the log files, or Windows Event Viewer, for more details.

Take this with a grain of salt right now, but I've had similar issues with the same error; and I think it might be the command of the Action. Could be wrong though.
On the task's Actions tab, it shows the wacs program path surrounded by double quotes.

However, when I went to edit it, the quotes weren't there.

Before I made any changes, I ran the renewal manually on the command line, and it may have confirmed this.
Scheduled task points to a different location

Back on the edit screen, I didn't manually change anything, but I think when I hit OK, it prompted me with something like, "do you want to run C:\Program blah blah. In other words, it was seeing the space between 'C:\Program' and 'Files...' and messing up the path. I clicked 'no' on this prompt, and then the double quotes were there.
Might check yours, and add the double quotes?

Some issues with spaces in paths were solved in recent releases. You can always make the task manually or make the program re-create it from the main menu > more options > recreate scheduled task.

thanks
Regards,
[https://1fngs728ht1l1kzsj51m7e85-wpengine.netdna-ssl.com/wp-content/uploads/2017/01/logo_new.png]http://www.stl.com.mt/
EVAN CAMILLERI | Chief Software Architect
Smart Technologies Limited
O +356 22584300 | M +356 99450455
webhttp://stl.com.mt |  @.,14.436053,17z/data=!3m1!4b1!4m2!3m1!1s0x130e5028153e798b:0x94edba5d09d54dfd> | @.> | facebookhttps://www.facebook.com/stl.com.mt
The information transmitted, including attachments, is intended only for the person(s) or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and destroy any copies of this information.
Covid-19 preventive measures https://www.stl.com.mt/2020/03/09/covid-19-preventive-measures/
From: Wouter Tinus @.>
Sent: 16 November 2021 10:01
To: win-acme/win-acme @.>
Cc: Evan Camilleri @.>; Author @.>
Subject: Re: [win-acme/win-acme] win-acme renew gives error 0x80131500 (#1925)
Some issues with spaces in paths were solved in recent releases. You can always make the task manually or make the program re-create it from the main menu > more options > recreate scheduled task.

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fwin-acme%2Fwin-acme%2Fissues%2F1925%23issuecomment-970059936&data=04|01|evan.camilleri%40stl.com.mt|93edd1b6440b4f3defd608d9a8df928c|a8e46fe346494c38b5dfec70ad239972|0|0|637726500513179581|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=R9XSsb4K6tQ5m6BHAPWGce2nBVkKqLjBlLbh%2Bad6OjE%3D&reserved=0, or unsubscribehttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAHMFWRAV3Z4MYLYWSKCPFY3UMIMTVANCNFSM5EM6HOZA&data=04|01|evan.camilleri%40stl.com.mt|93edd1b6440b4f3defd608d9a8df928c|a8e46fe346494c38b5dfec70ad239972|0|0|637726500513189575|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=%2FhrbYXK%2Bn5nf9aONJstoUufDS8J74fBTbBORO%2BbT7UQ%3D&reserved=0.
Triage notifications on the go with GitHub Mobile for iOShttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapps.apple.com%2Fapp%2Fapple-store%2Fid1477376905%3Fct%3Dnotification-email%26mt%3D8%26pt%3D524675&data=04|01|evan.camilleri%40stl.com.mt|93edd1b6440b4f3defd608d9a8df928c|a8e46fe346494c38b5dfec70ad239972|0|0|637726500513189575|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=k%2FFUjsdiR7xEYmQZIIyOri5GqOQVMAc1fFb356j0eqk%3D&reserved=0 or Androidhttps://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.github.android%26referrer%3Dutm_campaign%253Dnotification-email%2526utm_medium%253Demail%2526utm_source%253Dgithub&data=04|01|evan.camilleri%40stl.com.mt|93edd1b6440b4f3defd608d9a8df928c|a8e46fe346494c38b5dfec70ad239972|0|0|637726500513199572|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000&sdata=iwLuX1NWeJ00llFS6yjEXzko31Y%2Bxt0CdYHQ97s8Sn4%3D&reserved=0.


Python: Teach py/unused-local-variable about nonlocal.

Fairly straight-forward. If a local variable is marked as nonlocal, then it's reasonable to assume that it will be used non-locally (and thus "useless" assignments may in fact be useful after all).
A more fine-grained analysis would link up the two variables so that we can verify that there is indeed an access of the variable in the outer scope. This will require a larger extension of the SSA code, however, and will have to be future work for now.

Tests should stop failing once the nonlocal extractor fix has been merged. (See also #2074.)


Added A Pokemon card Tauros

Just added a card of my favourite pokemon Tauros and formatting is done from my side to make it look more readable.
A preview of my card is:

I have followed the community guidlines and also a correct image size is used so that it does not cause any problem

Due to the recent PRs that i merged, the code that you wrote is conflicting. It might not be your fault, it's just that the new PRs would have messed it. Could you please re clone it and make a PR again? I would love to include it

Ok i will do it again.. no problem

Ok i will do it again.. no problem

Thank you!


Progress bar could be useful in omz_downloader

There is no progress bar during model downloading in 208-optical-character-recognition (third code cell). Currently, there is no information when downloading ends.
Progress bar could be useful when someone (like me) has not so fast internet connection. It's even better to print into console every 10% than nothing.

Thanks, I agree that that would be useful. We are looking into it. The issue is that omz_downloader is an external command line tool that we call with ! in Jupyter. In the future there will be a Python API for OMZ-downloader, that would make it easy to add a progress bar. We are looking into either wrapping omz_downloader and adding a progress bar, or switching the model in 208 with another OCR model that we can download directly.


missing script build react

i notes there is no build in the secript section in package.json file
 "scripts": {
    "dev": "cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js",
    "watch": "cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --watch --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js",
    "watch-poll": "cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --watch --watch-poll --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js",
    "hot": "cross-env NODE_ENV=development node_modules/webpack-dev-server/bin/webpack-dev-server.js --inline --hot --config=node_modules/laravel-mix/setup/webpack.config.js",
    "production": "cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js"
  },

i think by default when you create project using create-react-app it should add it there
im asking because i run into issue when i try to run: npm run build
it show: missing script build react
what do you suggest?

I guess npm run production could be used instead.

yes, this work and it show me compiled successfully, but there is no build folder or anything new in the project structure

@ahmdabos This line https://github.com/moeen-basra/laravel-react/blob/master/webpack.mix.js#L27 defines where the build output is placed. Basically, project-root: ./public/js and there should be files like vendor.js, app.js in it. As well as chunks directory.
Please remember, this is Laravel application and assets are managed by Laravel-mix tool, and some things could be different than for example with react-scripts.

@ahmdabos I don't like when someone edit own comments. Now it looks like I've answered and unasked question.

@ahmdabos
"...but I'm confusing now where is the HTML index" --> here

@jack thats what it exactly is..
This project is only based on laravel and I designed it according to laravel standards.


Provide ability to run PBKDF2 and scrypt key derivation from command line

it's possible to do key derivation for TLS KDF and for HKDF using openssl pkeyutl -kdf utility.
Extend it to support also PKCS#5 PBKDF2 algorithm and scrypt algorithm.
See #1533 for the discussion and earlier attempt.

There is a promising WIP branch that implements this for scrypt (which is the hardest case) but not a PR yet. I'm awaiting the PR so it can be integrated.

For reference, this is now a PR: https://github.com/openssl/openssl/pull/4026

This has been automatically closed because the scrypt part of the PR has been merged to master. However, the PBKDF2 that the OP asked about is still a PR: https://github.com/openssl/openssl/pull/4087


Auto Incrementing Ids

If I see this correctly, there is currently no way to have auto incrementing ids for rows in an entity. I would find it tremendously useful to have such a thing. Since this would require a change in the column definition, would it make more sense to have dedicated types like the SERIAL type in PostgreSQL or a column property like AUTO_INCREMENT such as it is implemented in MySQL?

I would argue for a SERIAL and a BIGSERIAL type (INT and LONG).  Actually, the basic facilities to support this (serials) are already integrated. We only need to add the type and handle them upon insert.
Do you know if SERIAL types in PostgreSQL can be updated, i.e., the value can be changed after the fact?

There now is a prototype for this feature on feature/serial. I have updated the DMLServiceTest unit-test to include this feature by adding an auto-increment column. Few remarks:

I have decided against using dedicated types and instead introduced the autoIncrement flag for columns (only works for Integer and Long). The reason for this is that adding new types would have had serious implications across the entire type system.
Technically, this change is incompatible with existing Cottontail DB instances due to the need to serialize the flag to the catalogue.

Based on this and depending on how urgent this feature request is, I would propose to integrate this into the next major release of Cottontail DB, which should see yet another change to the storage engine.

Hey, great, thanks a lot for the quick reaction. I'll play with this a bit over the next days and provide feedback. I can't comment on the suggested timeline, since I don't know what the target is for the next major release. For my current use case, working from a feature branch is not a problem for the short or medium term.

As a follow-up on this: the functionality that exists on the serial branch works quite well. The only issue with the current implementation is that there is no way to get the newly generated id directly from an insert, but it requires a second query. This is rather inefficient, especially when multiple rows need to be inserted into multiple entities that use such serial ids as keys. It would be much nicer if one could request the latest values of the serial fields to be returned from the insert call directly, as this would alleviate the need for additional queries. Since they create quite some overhead, this would also result in a non-negligible speedup.
Also, what is the timeline for this feature branch to be merged?

I built something along those lines in https://github.com/vitrivr/cottontaildb/commit/f3d5d9f1d0dcde0c5620880f43a8e5e582a8530d. It works, but I'm sure there's a way to make it prettier.

This is possible with version 0.16.0.


chore: add initial configs / workflows / templates for the repository

Description
Prepares the repository with all initial configs, workflows & templates.
Verification
Compare with configs from Repository-Templates default directory
Checklist

[x] My code follows the style guidelines of the project
[x] I have performed a self-review of my own code
[x] I have made corresponding changes to the documentation

Seems that the Dockerfile is missing.

Will be added in a future PR after this one is merged. Not sure how Workflows will behave otherwise and it is less code to review per PR.

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


having seconds in the timepicker

Is it possible to add a seconds field in the timepicker? It would be very useful.
Thanks

keeping #2326 and closing this one as duplicate


Allow ConfZFileSource to be Optional

With the flexibility offered by ConfZ, there are cases where a file may be used in one context and not used or present in another.  Currently, if a file is not found at the specified path, then an exception is triggered.  It would be nice to have an added parameter in the signature like optional=True to allow for ignoring the exception and moving to the next source.

This would definitely be nice! I don't have the time to work on it right now, but if anyone wants to contribute, a PR would be very welcome! (We now also have mypy, black and pylint to support from the dev-side in this 😉)

I like this idea. 👍 Because I think it would also allow the following use-case: Having multiple locations for the configuration with different priorities. Something like a local configuration and a default configuration (both file based) where the local configuration would have priority over the default configuration. If the local configuration would not be present the lib would silently parse the default configuration without an error.


yafc-ce: 2.1.0 -> 2.3.0

Updated yafc-ce to version 2.3.0.
Release: https://github.com/shpaass/yafc-ce/releases/tag/2.3.0
(We skipped over version 2.2.0!)

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review run on x86_64-linux 1

1 package built:

yafc-ce

Same build results as above, tested basic functionality added in 2.2.0 and 2.3.0, no issues found.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 355085

x86_64-darwin

:x: 1 package failed to build:

yafc-ce

aarch64-darwin

:white_check_mark: 1 package built:

yafc-ce

Hm - I'm not able to test on Darwin, so I can't reproduce this. Should I mark the package as broken on x86_64-darwin for now?

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 355085

x86_64-linux

:white_check_mark: 1 package built:

yafc-ce

aarch64-linux

x86_64-darwin

:x: 1 package failed to build:

yafc-ce

aarch64-darwin

:white_check_mark: 1 package built:

yafc-ce

Looks like dotnet 8 SDK is broken on x86 darwin, so not this PR's fault.

I see, thanks for looking into it @khaneliman :)


Remove version: wiznote.wiznotelite version 1.6.0

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://get.wiz.cn/Lite/WizNoteLite-x64-1.6.0.exe
Response status code does not indicate success: 404 (Not Found).
(Automated message - build 897)


graph api V2.1 is no longer available after october 30th, 2016

just updating this as an issue. I'll look into a fix this weekend if its not solved already. ref: https://developers.facebook.com/docs/apps/changelog

Hey @BabbagesCabbages, for any potential breaking changes the issue should be opened with the respective libraries which in this case is passport-facebook that handles Facebook authentication and fbgraph that handles Facebook API.


observation not an issue

with exactly the same hardware & options i've noticed that since you fixed issue #94 I seem to be getting a lot less pmkid's/MP's over the same timeframe. I was getting something like 1000+ PMKIDs & 200 or so MPs (works out at about 20 or 30 of crackable both) according to --enable_status=127 (internal stats) since the fix the internal stats over the same time from are in the 10s. no changes to hardware, software or positioning of the pi (running kali 2019.3 rolling)

Good observation. The counted PMKIDs and MPs in status line are raw values.
Now we should get much less PMKIDs and MPs here, because we're making much less noise.
INFO ERROR:0 INCOMING:958 OUTGOING:522 PMKID:17 MP:0 GPS:0 RINGBUFFER:3
To identify if it is really an issue or not, please run
old version for at least 15 minutes
than convert with hcxpcapngtool and check how many PMKIDs and MPs are written to output file.
now run
new version for at least 15 minutes
than convert with hcxpcapngtool and check how many PMKIDs and MPs are written to output file.
If we have the same value +/- 5, everything is ok. If not, I've to hunt for that issue.

ran both for about an hour each and usable pmkids and mp's is within 2 so think all is good

Great. Goal is to reduce the noise on the current channel. The less noise the more we can receive. Additional I added a new attack vector.


Reenable float tests on powerpc64le for ToCompactStr

Last time I tried to reproduce the bug on nightly, it is already fixed.
Signed-off-by: Jiahao XU<EMAIL_ADDRESS>

Turns out that ryu still cannot properly format 3.2_f32 but can format f64 correctly https://github.com/dtolnay/ryu/issues/47
Also, the tests cannot be compiled on 1.49 due to structmeta requires 2021 edition.

I also discovered some new bugs on rustc nightly, which formats f32::NEG_INFINITY as inf instead of -inf.

Also, the tests cannot be compiled on 1.49 due to structmeta requires 2021 edition.

I fixed this by running cargo-check instead of cargo-test in workflow msrv1.

This PR has been very out of date and the regression still happens from time to time, so I am closing it for now.


hls can not be played

Browser: Chrome Version 47.0.2526.111 (64-bit)
OS:Linux  4.3.3-300.fc23.x86_64 #1 SMP Tue Jan 5 23:31:01 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Clappr Version: 0.2.25

download http://bugger.ieparse.com:8080/app/hls/1.avi
convert it to ts stream with ffmpeg, I wrote the ffmpeg in a shell scrit like this:
#!/bin/sh
function ffmpeg_hlsEncode() {

IN="1.avi"
VCODEC="libx264"
WIDTH=920
HEIGHT=540
VBITRATE="500k"
FRAMES="15"
ACODEC="libfaac"
ABITRATE="128k"
ffmpeg -i $IN
-map 0
-vcodec $VCODEC
-s ${WIDTH}x${HEIGHT}
-b:v $VBITRATE
-r $FRAMES
-acodec $ACODEC
-b:a $ABITRATE
-bsf:v "h264_mp4toannexb"
-hls_time 30
-hls_list_size 0
-bf 0
-f hls
XXXX.m3u8
}
ffmpeg_hlsEncode

then set the clappr source as http://bugger.ieparse.com:8080/app/hls/XXXX.m3u8 ,the clappr only load two ts segments ,and can not play !

ps:

This issue is caused by the audio sample rate . The audio sample rate is 22050 Hz, It seems like that the video element can not support this rate. When I resample the audio as 44100 Hz or 38000 Hz , The clappr play the stream fluently.

@ieworks hi can you try to run this here http://dailymotion.github.io/hls.js/demo/ ? it might be a restriction of hls.js

ping @ieworks


wireguard: Improve logging

See commit msgs.

Reviews are in and the code is building. I don't think we need to run the full CI as it's only minor logging changes. Merging.


how to use one server to manage multiple service

@server (
        middleware : temp
        group: [fruit, vegetable]
)

service one {
        @server(
            handler: apple
            group: fruit
        )
}

service two {
        @server(
            handler: cabbage
            group: vegetable
        )
}

right?


Overflow scrollbar in column filter's custom tab covers remove buttons

PR here: https://github.com/xh/hoist-react/pull/2852


I Get Negative Number for Siacoin Rewards

Bug Report
Check to see if a bug report already exists.  If you still want to create a new issue please include the information below.
Stack Trace or error message
Environment

Sia version:1.3.0
OS:Ubuntu16.0.4

Any useful logs
I have used the display card to mine Siacoin, but the rewards are minus 2512706 as showing in the screenshot. Could you please check for me ? It’s urgent situation, I need you help!

Could you put the transactions here as text instead of a screenshot?


Time range resets after MW scrolldown.

Expected behavior
When using datazoom in options object (echarts options parameter):
options = {
  // ...
  dataZoom: [
    {
      show: true,
      realtime: true,
      start: 30,
      end: 70,
      xAxisIndex: [0, 1]
    },
    {
      type: 'inside',
      realtime: true,
      start: 30,
      end: 70,
      xAxisIndex: [0, 1]
    }
  ],
  // ...
}

And scrolling wheel down, the panel is expected to zoom out on already zoomed in part of data. Check out apache echarts example.
Actual behavior
The scrolldown button causes the whole dashboard to reset the time range.
In my case it resets to last 30 minutes even though I have set it to specific time range beforehand.
I also use the following code to allow data zoom in every echarts panel:
/**
 * Enable Data Zoom by default
 */
setTimeout(() => echartsInstance.dispatchAction({
  type: 'takeGlobalCursor',
  key: 'dataZoomSelect',
  dataZoomSelectActive: true,
}), 500);

/**
 * Update Time Range on Zoom
 */
echartsInstance.on('datazoom', function (params) {
  const startValue = params.batch[0]?.startValue;
  const endValue = params.batch[0]?.endValue;
  locationService.partial({ from: startValue, to: endValue });
});

Also this problem is not reproducible while editing the panel, only while using it in dashboard view.

@cringoleg The datazoom feature provides the same functionality by updating the time range as the native Time Series panel. This is what causes updating the Time Range.
If you don't need to update the time range and use native Data Zoom functionality, you can remove this event handler:
/**
 * Update Time Range on Zoom
 */
echartsInstance.on('datazoom', function (params) {
  const startValue = params.batch[0]?.startValue;
  const endValue = params.batch[0]?.endValue;
  locationService.partial({ from: startValue, to: endValue });
});

@cringoleg I hope it's clear.
Let us know if there is anything else.


Editorial fixes and remove out-dated screenshot

Remove out-dated screenshot (#21927) for Single Sign-On URLs

@javierruizjimenez : Thanks for your contribution! The author, @CelesteDG, has been notified to review your proposed change.

@javierruizjimenez - Thank you for your suggestion. This content just transitioned to my team and we'll be reviewing it in more detail. At this time, some of the suggested changes here do not conform to our styles (periods only at the end of complete sentences, not phrases) and we'll be reviewing the screenshot. I'm tracking the last as part of a work item. Thank you.

No changes at this time. Tracking the screenshot suggestion as part of a work item and will be reviewing it with the feature team once I've fully transitioned.
#please-close

Thanks @CelesteDG I was applying the Microsoft Style Guide / Punctuation / Periods, but the rules are not always clear to me as I see different interpretations depending on the author, so I will ignore periods and focus more on technical issues that I might find while reading the docs. Thanks.

Thank you, @javierruizjimenez  :) We absolutely appreciate your contributions and it would be great to have your feedback/input on the technical accuracy of our docs.


raft-engine: implement dump from old raftdb

Signed-off-by: Xintao<EMAIL_ADDRESS>
What problem does this PR solve?
When users enable raft-engine on the old database, it needs to dump data from old raftdb into new raft-engine.
What is changed and how it works?
scan keys from raftdb and judge the type of value through suffix, convert it to protobuf data format and save into raft-engine.
Release note

Implement dump from raftdb to raft-engine.

Store all data in an in-memory hashmap may cost a lot of memory. Sometimes the raftdb may occupy a large space (more than 2GB). I suggest that scan and move data to raft-engine in pipline

Store all data in an in-memory hashmap may cost a lot of memory. Sometimes the raftdb may occupy a large space (more than 2GB). I suggest that scan and move data to raft-engine in pipline

There may be a panic (or just a power failure) happens when you dump data to raft-engine. We must think about how to deal with the failure which may happen during dump.

we shall write one special key after finished dumping all data into raft-engine.
Delete all sst files of the raftdb except the special key by delete_files_in_range.
Delete all data of raftdb key by key except the special key.
At last we can remove the whole directory of raftdb.
When we start TiKV, we must check the special key of raftdb at first. If the special key exsits, it means that the data of raftdb may be incomplete because some failure happened before. So we can continue removing the raftdb since step2.

Just curious, instead of dumping rocksdb-raft into raft-engine, can we apply all raft log to drain rocksdb-raft?

Just curious, instead of dumping rocksdb-raft into raft-engine, can we apply all raft log to drain rocksdb-raft?

Not all entries store in rocksdb-raft could be applied to rocksdb-kv, because some of them may have not been committed.

Just curious, instead of dumping rocksdb-raft into raft-engine, can we apply all raft log to drain rocksdb-raft?

Not all entries store in rocksdb-raft could be applied to rocksdb-kv, because some of them may have not been committed.

Got it. Another option might be writing to raft-engine, but double read from both rocksdb and raft-engine. Benefits:

we don't suffer from more recovery time to migrate the data.
it works better to switch back-and-forth between rocksdb and raft-engine, because there would be no intermediate state of data dump. It shouldn't happen normally, but might happen if someone turn on raft-engine but immediately want to switch back?
If the old raft log goes away fast, then we can turn back to read raft-engine only mode thereafter and avoid the additional double-read latency.

For deleting rocksdb, it may be safer to rename the dir name first, then run the file deletion. As pointed out by @Little-Wallace  offline, a crash in the middle of deletion will leave an unclean rocksdb behind.

/run-integration-common-test

Have we test or do we have estimation of how much delay the dumping adds to restart?

Just a suggestion. I think we could add a benchmark for it.

why bench for dump?

@hunterlxt you can put your local test result here, just for reference later.

For 2GB raftdb directory, I collected time consumption. From scan to dump and sync successfully, it's about 16~20s.

/merge


Cuda out of memory!

I am getting cuda out of memory error even inspite of changing the batch sizes and image sizes. Nothing is working out. Help needed!

Which task are you running? Are you using fp16 training? Additionally, have apex and xformers been installed successfully?

I am running one_peace_vision. Here's my run command:

I am enabled fp16_compression and also installed apex and xformer.

What are the current batch size and image resolution? Can you adjust them to smaller values to see if it runs normally?


Angular material 2 tooltip issue

Tool Tip content is showing fine but still in chrome debug console Im facing this issue.
ERROR TypeError: Cannot read property 'matches' of null
at Object.eval [as updateRenderer] (TooltipComponent.html:1)
at Object.debugUpdateRenderer [as updateRenderer] (core.js:22503)
at checkAndUpdateView (core.js:21878)
at callViewAction (core.js:22114)
at execComponentViewsAction (core.js:22056)
at checkAndUpdateView (core.js:21879)
at callViewAction (core.js:22114)
at execEmbeddedViewsAction (core.js:22077)
at checkAndUpdateView (core.js:21874)
at callViewAction (core.js:22114)

Closing this issue as it does not follow the issue template. Please file a new issue that follows the template, which gives the team the information needed to investigate.


FontForge download missing

$ brew cask install fontforge
==> Satisfying dependencies
complete
==> Downloading https://github.com/fontforge/fontforge/releases/download/20150824/FontForge-20150824.dmg

curl: (22) The requested URL returned error: 404 Not Found
Error: Download failed on Cask 'fontforge' with message: Download failed: https://github.com/fontforge/fontforge/releases/download/20150824/FontForge-20150824.dmg

I tried to look for the an updated release, but couldn't find one. Their website still references the URL, but I don't see it under Github Releases

I don't know, but just perusing their page it looks like they had a serious unknown error, and most likely renamed FontForge-20150824.dmg to FontForge-20150824-Terminal_only.dmg to warn people.  The cask file could be updated with a new dl link and a caveat, but IMO this is an upstream error that needs fixing on their end.

https://github.com/caskroom/homebrew-cask/pull/16020.


ES: Illegal transliteration and value set violations

In 501.json:
Transliterated names containing blanks. Illegal.
ma field of test entry is invalid. Violates covid-19-lab-test-manufacturer-and-name.
In 502.json:
Transliterated names containing blanks. Illegal.
In 503.json:
Transliterated names containing blanks. Illegal.
In 1201.json:
vp field of vaccination entry is invalid. Violates sct-vaccines-covid-19.
dn (2) is larger that total number of doses in series sd (1). This doesn't make sense.
In 1202.json:
t[0].ma="Value 'BIOSYNEX COVID-19 Ag BSS' is not allowed according to the 'covid-19-lab-test-manufacturer-and-name' value-set"
t[0]="sc (sample collection) is after dr (date of result). This doesn't make sense"
t[0].tr="Value '1240591000000102' is not allowed according to the 'covid-19-lab-result' value-set"
In 2001.json:
t="Empty array in 't' - not allowed"
r="Empty array in 'r' - not allowed"
In 2002.json:
v="Empty array in 'v' - not allowed"
t="Empty array in 't' - not allowed"

I have remove that invalid test and I have created a new pull request with new tests looking your comments.

Closed in #87