feat: Add a Keysight_34465A driver

Add a driver for the Keysight 34465A DMM and a
benchmarking notebook comparing the Agilent 34411A to the Keysight 34465A
Changes proposed in this pull request:

Add driver
Add notebook

Changes added during review:

Array like parameter

@giulioungaretti

Replace by  #556


Add a section on model parameters to the documentation

Note: please do a content review only of the following files: model_parameters.md, documentation.md, db_handler.md. All other changes are related to rst/markdown issues - this will be superseded by pull request #940
This adds to the documentation:

a general description of simulation model parameters
schemas and their meaning
organisation of ArrayModel, TelescopeModel, SiteModel, etc
where and how to add or update new parameters (e.g., that the model_parameters gitlab should be used to define model_versions and that there are simtools to upload a gitlab repo to the database)
how to derive a set of model parameters from sim_telarray
split of documentation section out of the Developers Guildelines into its own section. I try to collect here the little tricks requires typically to write documentation.

The markdown - rst connection is kind of ok, but some links don't work (this is why I have removed them for now). This is addressed in #940, so we can ignore it here.

@VictorBarbosaMartins - thanks for a lot for the careful reading and the very useful comments. Improved this significantly!
Note that I don't want to add here details on the individual applications. These should be in the application docstring (so we can access in different places).
I also know that the relationship between simtools and CTAO simulation team and who is responsible for what is not finalized. But in general is our team responsible to write the software and the simulation team will use it (so we are responsible for how it works; but the CTAO simulation team is responsible for what it generates).
Let me know if there is anything to be improved / clarified (documentation is never complete....)


[mongo-cxx-driver] build failure for feature std-experimental

OS: Windows
Compiler: Visual c++ 2019

Steps to reproduce the behavior:
./vcpkg install mongo-cxx-driver[std-experimental]
Failure logs
install message:
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:108 (message):
Command failed: ninja -v
Working Directory: E:/vcpkg/buildtrees/mongo-cxx-driver/x64-windows-rel/vcpkg-parallel-configure
Error code: 1
See logs for more information:
E:\vcpkg\buildtrees\mongo-cxx-driver\config-x64-windows-out.log
Call Stack (most recent call first):
scripts/cmake/vcpkg_configure_cmake.cmake:319 (vcpkg_execute_required_process)
ports/mongo-cxx-driver/portfile.cmake:42 (vcpkg_configure_cmake)
scripts/ports.cmake:128 (include)
config-x64-windows-out.log:
CMake Error at src/bsoncxx/CMakeLists.txt:69 (message):
Can only use BSONCXX_POLY_USE_STD_EXPERIMENTAL if CMAKE_CXX_STANDARD is 14
or higher
Additional context
Shouldn't vcpkg should set CMAKE_CXX_STANDARD, if not How to set it as default is 11 in mongo-cxx-driver

@prateek9623, vcpkg doesn't set that variable, you need to create a overlay or custom ports to implement it.

You can add set(CMAKE_CXX_STANDARD 11) to mongo-cxx-driver CMakeLists.txt file.
Or you can pass the option via VCPKG_CXX_FLAGS in mongo-cxx-driver portfile.cmake file.

@prateek9623, vcpkg doesn't set that variable, you need to create a overlay or custom ports to implement it.

You can add set(CMAKE_CXX_STANDARD 11) to mongo-cxx-driver CMakeLists.txt file.
Or you can pass the option via VCPKG_CXX_FLAGS in mongo-cxx-driver portfile.cmake file.

ok, what can i do in my manifest file to pass flags

@prateek9623, AFAIK, there is no way to pass the option in manifest file, another workaroud may be set the VCPKG_CXX_FLAGS in toolchain file, however it only works when using vcpkg's built-in toolchains, See https://github.com/microsoft/vcpkg/blob/master/docs/maintainers/maintainer-guide.md#prefer-patching-over-overriding-vcpkg_variable-values

ok so maybe we need to update the port file for this, but is there a way to detect supported standard in port file?

You can try to set VCPKG_CXX_FLAGS in mongo-cxx-driver portfile.cmake file like:
On windows:
set(VCPKG_CXX_FLAGS "${VCPKG_CXX_FLAGS} -std:c++14")
On Unix:
set(VCPKG_CXX_FLAGS "${VCPKG_CXX_FLAGS} -std=c++14")

@prateek9623
Is this still a problem for you now?

@NancyLi1013 issue is still there, but I am using boost now


Add Parsing for Assignment Shift Right  Token

Update the parser to handle the ASSIGN_SHIFT_RIGHT token, allowing it to correctly parse expressions involving the >>= operator.

@anshikavashistha  working on this


config: Centralize default YAML.

Test scenario configuration is fairly lean since all configuration values have some default value. In the good old days, the default values for configuration items could be dictated solely in ovn-tester.
With the containerization of the tester, now do.sh sometimes needs to use configuration values as well. This means that do.sh sometimes also needs to be able to use the default values. However, do.sh has no idea what these default values are, so they end up getting duplicated by developers.
This change seeks to solve this problem. A new python script is now the arbiter of default values. When running a test, do.sh will take the test configuration, run it through this script, and generate a yaml file that has all default values filled in. This is then passed to ovn-tester as the configuration file. ovn-tester can now accept the configuration file as-is and not have to try to fill in any default values.

Sorry @putnopvut for lack of reviews on this one.  It still seems to apply cleanly.  I triggered a re-run of the cirrusCI here: https://cirrus-ci.com/task/6388560614391808
The changes look OK to me. @igsilya what do you think?

@dceara  I didn't test, but looks OK on a quick glance.
We may want to rebase this PR, because simple re-run of checks doesn't rebase things, it just runs using the same old branch that might not have some recent CI changes.

I just pushed new changes. The main changes are:

I addressed Ilya's comment about adding pyyaml on the orchestrator. I added pyyaml to the requirements.txt file, which is installed in the local venv by do.sh
I changed some of the checks in translate_yaml.py so that we now explicitly check calculated values against "None" instead of using "not". This way, if someone purposely wants to have an empty VIP list, for instance, they can do that.
I updated a comment in the GlobalConfig dataclass where it erroneously said to add cluster level options there.

Thanks @putnopvut and @igsilya!


undefined is not an object (evaluating 'ChromeManager.openURL')

Trying to run on iOS. if I delete chrome app on my iphone the code works perfectly but opens up in Safari.

+1 I have same issue.

I ended up not using it for the application and used a WebView wrapper to open the url instead.

+1, Same issue

In case someone's here due to a similar issue undefined is not an object (evaluating 'ChromeManager.default.openURL'), make sure your import is correct.
It should be
import {Customtabs} from 'react-native-custom-tabs';

Not
import Customtabs from 'react-native-custom-tabs';

@nadav2051 where did you put DBChromeManager.h file exactly? I am having same problem

In case someone's here due to a similar issue undefined is not an object (evaluating 'ChromeManager.default.openURL'), make sure your import is correct.
It should be
import {Customtabs} from 'react-native-custom-tabs';

Not
import Customtabs from 'react-native-custom-tabs';

no it is now working


RichTextRenderer::Renderer#render should not raise an error when provided argument nil

Objects in contentful with rich text fields where no rich text is added at all will cause an error when attempting to render rich text with this gem.
This is caused by https://github.com/contentful/rich-text-renderer.rb/blob/master/lib/rich_text_renderer/base_node_renderer.rb#L13
But https://github.com/contentful/rich-text-renderer.rb/blob/master/lib/rich_text_renderer/renderer.rb#L13 makes it seem that nil should be an accepted arg.
PR: https://github.com/contentful/rich-text-renderer.rb/pull/21

any movement on this?
The issue is either that the contentful gem returns nil for rich text fields when there is no content at all, or that this gem cannot handle nil nodes. I've added the PR here to handle nil nodes.

fixed in #21


Enable Helm chart testing with config file

GitHub tests action couldn't find MeiliSearch chart. For that reason, it wasn't taken into account for linting and install actions.  This has been solved by creating and linking a config file.
Lint: Added home and maintainers fields to chart
Everything seems to be working now

@renehernandez Do you want me to put your name / email into the maintainers field?

@eskombro Nice work!


Fix for Issue 315

HandleLogger now sets all its source positions and generatedBy's.
convertToFieldDeclaration now also marks the resulting FieldDeclaration as "isGenerated"

based this pullrequest on the one for issue 308, since it uses the same visitor


Fix /probot and switch to hbs

I don't know who installed ejs (it was me) but I hate ejs. The syntax is very verbose, and a lot of the logic doesn't do what its supposed to do. For example, if statements that should have prevented #323 just weren't working as expected.
So, in this PR I've switch the templating view to handlebars (technically hbs). The syntax is much cleaner and it actually works.
Note: This is technically a breaking change, which I realize is not ideal. I don't want to bump to v4.
I'm more than happy to look at other templating packages if anyone has a preference. I've used nunjucks in the past and loved it, but I know that Handlebars is more common so I've used it here (and also it's perfectly good).
Closes #323.

@bkeepers my desire to switch to hbs came out of trying to fix #323 and getting annoyed with all the <%= I had to type, and the if statements that just weren't working. This PR will fix #323, even though yeah it does some other stuff 😛

It'd be great to see some tests added for the /probot route

Agreed. I added the route pretty quickly and hastily. I won't merge this in without some new tests

Is this going to be the only route with a view? If so, why not just use ES6 string templates?

@rtsao that's a fair point, but based on our future plans (which are very abstract), we can see UIs as something that a lot of people will find a use case for. You can see some of the discussion in #262.
That said, I'm not opposed to using an ES6 template string for this view - I guess my thought is that if Probot has more than 1 view it would benefit from having a template system, so I'm pre-planning.

hbs ftw

@bkeepers (and everyone else) I've added some tests, please let me know if they're sufficient 💖 .

Turns out snapshots work just fine, I was fighting with something else at the dep. Once CI passes I'll merge this in. This is technically a breaking change, but I don't think anyone is using the view engine (as ejs). I'd rather not publish v4 - any objections if I merge as refactor: switch ejs for hbs?

any objections if I merge as refactor: switch ejs for hbs?

That's fine with me. ejs wasn't a documented feature, so I don't think it'll be an issue.


Fixer for changing array_push($a, $b) to $a[] = $b

Note: If you use array_push() to add one element to the array it's better to use $array[] = because in that way there is no overhead of calling a function.

Source: https://secure.php.net/manual/en/function.array-push.php
I think this fixer may be risky because there is a change in behaviour:

Note: array_push() will raise a warning if the first argument is not an array. This differs from the $var[] behaviour where a new array is created.

added in https://github.com/FriendsOfPHP/PHP-CS-Fixer/pull/4790


remove windows account requirement

Removed part of the important note as it was misleading: Users can use a completely different account to login to their windows device, they only need to provide these credentials when creation the gateway connection.

@raaourik : Thanks for your contribution! The author(s) have been notified to review your proposed change. @olegmelnykov


[Bug]: Improvement needed in Trip gallery section

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
The Trip Gallery section of the application is not functioning as expected the images are not loading properly and the UI is not looking good changes in UI is required.
Expected behavior
Images should display in the correct resolution without distortion and loading time for the gallery should be optimal.
Users should be able to navigate the gallery easily, with images ordered appropriately and sections should be fully responsive properly on both devices mobile and laptop .
Add ScreenShots

On which device are you experiencing this bug?
Windows
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I'm a VSOC'24 contributor
[X] I have starred the repository

@patilchaitali27 u are assigned . good issue

@apu52 can i work on this issue

@SanikaBhalerao1345 i have assigned you , you can work on this issue .

Can I work on this issue

Can I work on this issue

@soumya778 will u be contributing under KWOC???

@soumya778 Actually i want to inform u one thing , that the contribution period of kwoc will start from 5 th dec , so any contributions before that timeline will not count towards KWOC , so please try to start contributing after 5th DEC .
& regarding this issues which u have raised prior , don't worry about it , i will review & assign u this issues after the contribution period starts


reject AppName ClusterName ApplicationName field length to 500

Coverage increased (+0.05%) to 45.844% when pulling 636d4c9d79468aad1ba14763e481503f4601e1ed on lepdou:modify_sql into 57c0e019fd8433d2682dfb6c9b74af56d15cef5d on ctripcorp:master.

Current coverage is 42.78% (diff: 100%)

Merging #511 into master will increase coverage by 0.02%

@@             master       #511   diff @@
==========================================
  Files           307        307
  Lines          7916       7916
  Methods           0          0
  Messages          0          0
  Branches        921        921
==========================================
+ Hits           3385       3387     +2
+ Misses         4292       4288     -4
- Partials        239        241     +2

Powered by Codecov. Last update 57c0e01...636d4c9


Typed xState Guards

Feature request
Typed xState Guards
Description:
I want to be able to provide Guard type (like PropertyEqualsGuard here in the example) to the Machine function and xState types covering guards. So the conds in action in the machine config is typed.
Expected usage:
interface PropertyEqualsGuard<TProps, TContext, TEvent> extends Guard<TContext, TEvent]> {
    type: 'PropertyEquals'
    props?: {
        [TPropertyName in keyof TProps]?: TProps[TPropertyName]
    }
}

This way I will be able to define types for my Guards like this, so I can make a guard that like in this example checks if property defined in the guard is equal to provided value.
Those properties we are comparing with can be for example in the state context.

Hey, not sure what you're asking, can you give me a realistic usage example?

I'm sorry, I've changed the description. Is it clear now?

This is for parameterized guards, right?

Yes.

custom guards exactly: https://xstate.js.org/docs/guides/guards.html#custom-guards

Could you prepare a "full" pseudo-code of how would you like to use the proposed feature in the code assuming it would be implemented? It's very hard for me to assess what you are actually asking for from the given description.

Can't speak for OP and from the question I'm not sure if we are on the same page here, but I was hoping I could type my custom guards like this:
cond: (context: IContext, event: IEvent, stateGuard: StateGuard<{ maxNumberOfItems: number }>) => context.items.length <= stateGuard.cond.maxNumberOfItems

The second and third generic TypeScript argument of StateGuard could be used to pass in the context and event again with which it could type the state: State<Context, Event> of the stateGuard.
Arguably it should only allow a second type argument which can be State | undefined as this would allow to explicitly define a guard that can be invoked by initial transitions of a machine where the state is not yet available.
stateGuard: StateGuard<{ maxNumberOfItems: number }, State<IContext, IEvent> | undefined>

@CodingDive That's it, I have a react component which properties are reflected to the state context.
What you can see in the expected usage section is an abstract type for a guard that can for example check if the disabled property equals true.

Hello,
Any news on the Guard typing? It seems that I'm still forced to cast cond as any using the Condition type for the guards.

@FloValence  I'm not sure if your issue is exactly the same as the one outlined in this issue. We are working on improving TS experience in https://github.com/statelyai/xstate/pull/2674

Closing as this is now improved in #2674


Avoid copying between processes

Minimize the copying of data between processes. Do as much as possible in the calling process.

One idea is to make a separate benchmark repo where we test ered vs eredis_cluster and maybe include other erlang redis cluster clients.
As we have discussed before, it would be interesting to try out some more optimized way of of doing things. One thing we could do is to remove the ered and ered_client process and instead use atomics for the slot map lookup, persistent term for the connection lookup and the counters module for keeping track of the queue size.
slot -> connection index (atomics)
connection index -> queue size (counters)
connection index -> connection pid (persistent term, local pid fits in a word so no global GC to update)
The connection module would have to handle reconnect and status reporting to the cluster module. The queue would be the connection send process message queue.
Avoid gen_server:call since setting up the link is expensive, rely on a timeout instead.
Not sure if it will work, there might be a catch, but if it works I think it would be quite efficient.

Benchmarking is a good idea. We should include ecredis in the comparison.
Atomics and counters are probably good, but I'm not sure about persistent term. It's true that replacing a pid doesn't trigger a global GC, but it still rewrites the whole persistent term table, which may contain stuff out of control of this lib. Perhaps an ETS table is an acceptable choice for connection index -> pid lookup?

Avoid gen_server:call since setting up the link is expensive, rely on a timeout instead.

You mean gen_server:call's monitor is expensive? With timeout you mean we use cast + receive after?

but it still rewrites the whole persistent term table, which may contain stuff out of control of this lib.

Yes you are right, I did not realize the persistent term table was global. Better not go that way.

You mean gen_server:call's monitor is expensive?

Yes, I meant monitor. I remember it  showed up when I did some profiling and bang/cast + receive performed better. It is hackish but might be worth if we are going all in for speed. At least we could profile it and see if it makes any difference.

Perhaps an ETS table is an acceptable choice for connection index -> pid lookup?

A process dict might also be an option, it has the same lifetime as ETS tables (dies with the owner process). If doing only simple key lookups it should be faster than ETS I guess.

Ideally the lookup should happen in the caller (user's) process before the first gen-server call. We don't want to pollute the process dictionary of the user's process.


Filter Documentation improvements

I've been reviewing the Gateway Filters and Global Filters documentation and I think we can apply some improvements.
Besides from fixing some grammatical errors, I've standardized the titles of each of the filters and organized them alphabetically (no content modified)
I've also added information about the global Local Cache Response filter, which we had not added in the associated PR.

@Buzzardo Thanks for your suggestions, I have applied all of them in this commit


Add a searching/autocomplete filter value/controller

This will need to be somewhat generic as we don't know:

How searching the values is done
How searched values should be displayed

However, we can handle some of the common logic for users by:

Introducing a new interface a la IFilterSelectValue which will let controllers use advanced value functionality
This should encapsulate the ability to search some T values using a string
Contollers will need common base logic for hooking into the value and searching, but will need to be more custom than other controllers are there are too many variables in their usage to encapsulate in an out-of-the-box component

Added in v3.1.0-rc.4.


Room contents is playing before  _on_room_entered()  has executed when no transition is enabled

Bug description
This function is supposed to run when "the room is in the tree but it is not visible".
If you change room with no transition (e.g. "R.goto_room("Locker", false)") then you can see the contents of the new room ("Locker") briefly while its _on_room_entered() function executes. I can tell this as I have calls in _on_room_entered() to disable various things
e.g.
	if C.player.state.WearingTowel == false:
		R.get_prop("Towel").show()
		R.get_prop("Uniform").hide()

The Uniform prop displays for a brief period before disappearing.
Steps to reproduce
Steps to reproduce the behavior:

Create a room with a prop
In its _on_room_entered() function, hide the prop
Create a second room, with a "goto_room" function in it that takes you to the first room without a transition
Play the game. Observe when you move from the second room to the first room that the prop displays temporarily before disappearing

Expected vs observed behavior
Everything in _on_room_entered should complete before the room is drawn to the screen
Environment information (please complete):

Windows 10
4.3 dev 3
Latest development branch of Popo

Additional context

I'll take a look on this.


Update Character “tibar”

Automatically generated by Netlify CMS

👷 Deploy Preview for dynamic-cheesecake-5fbd8b processing.

Name
Link

🔨 Latest commit
0ba2f6ecb14c5d3b7a8d2bbf3dc8d85c5c6a0c5f

🔍 Latest deploy log
https://app.netlify.com/sites/dynamic-cheesecake-5fbd8b/deploys/63372c3b943c95000885665f


Switch to Podman v4

What type of PR is this?
/kind dependency-change
What this PR does / why we need it:
Update podman to the latest v4 release.
Which issue(s) this PR fixes:

None
Special notes for your reviewer:
None
Does this PR introduce a user-facing change?

- Require Podman v4 as golang dependency.

/lgtm


Grouping New Pieces in the Admin Bar

How can I Group New Pieces in the Admin Bar?
When I create new piece types, I get a link to manage that piece type in the admin bar.
I would like to be able to group these new pieces - and potentially existing default pieces - into dropdowns in the admin bar, for example:
Page Content

Reviews
Testimonials
Offices

Imagery

Images
Image Tags

Etc...
Is this something that is already possible?
I have not found it covered in the docs.
Thanks

cc @BoDonkey

Hi @LeviticusMaximus,
Thanks for the question. This is definitely possible. One of the options for the admin-bar module is groups. This option lets you add new menu items with current pieces - both default and custom - grouped inside. Here is the link.


Added htmlhint and stylelint linter to pre-commit hook

This PR resolves issue #110
Along with the linters, I've also added an installation script which prompts the user to install the linters if they are not already available.
These linters have also been added as dev dependencies in the package.json file so if someone wants to install them manually, simply run: npm install -D and the linters will be installed.
cc: @SID262000

Thanks for taking your time to review @N3v1

This appears satisfactory to me; however, the ultimate decision rests with @SID262000.
Waiting for @SID262000

So, need to add @SID262000 as a reviewer.


[Flow] Make sink reshapes changes less conservative.

While deciding if a reshape needs "sinking", for a tensor.expand_shape -> linalg.*, first check was to check that the linalg.* operation could already fuse with one of its existing producers. That check was broadly aggressive. The fusion only kicks in when the iteration domains match. Eventually the actual dispatch formation logic needs to be commoned to a single place to do this better, but kicking that to a follow up.

Have been trying to repro it. Can't repro locally.

I think the regression can be seen here:
After
full after change
ir before commit
  %expanded_181 = tensor.expand_shape %43 [[0, 1], [2]] output_shape [1, 4, 768] : tensor<4x768xf32> into tensor<1x4x768xf32>
  %expanded_182 = tensor.expand_shape %46 [[0, 1]] output_shape [1, 4] : tensor<4xf32> into tensor<1x4xf32>
  %expanded_183 = tensor.expand_shape %45 [[0, 1]] output_shape [1, 4] : tensor<4xf32> into tensor<1x4xf32>
  %47 = linalg.generic {
    indexing_maps = [affine_map<(d0, d1, d2) -> (d0, d1, d2)>, affine_map<(d0, d1, d2) -> (d0, d1)>,
	  affine_map<(d0, d1, d2) -> (d2)>, affine_map<(d0, d1, d2) -> (d2)>, affine_map<(d0, d1, d2) -> (d0, d1)>,
      affine_map<(d0, d1, d2) -> (d0, d1, d2)>],
    iterator_types = ["parallel", "parallel", "parallel"]}
    ins(%expanded_181, %expanded_182, %cst_60, %cst_59, %expanded_183
      : tensor<1x4x768xf32>, tensor<1x4xf32>, tensor<768xf32>, tensor<768xf32>, tensor<1x4xf32>)
    outs(%7 : tensor<1x4x768xf32>) {
  ^bb0(%in: f32, %in_584: f32, %in_585: f32, %in_586: f32, %in_587: f32, %out: f32):
    %355 = arith.divf %in_584, %cst_9 : f32
    %356 = arith.addf %355, %cst_8 : f32
    %357 = math.rsqrt %356 : f32
    %358 = arith.mulf %357, %in_585 : f32
    %359 = arith.mulf %in_587, %358 : f32
    %360 = arith.subf %in_586, %359 : f32
    %361 = arith.mulf %in, %358 : f32
    %362 = arith.addf %361, %360 : f32
    linalg.yield %362 : f32
  } -> tensor<1x4x768xf32>
  %collapsed_184 = tensor.collapse_shape %47 [[0, 1], [2]] : tensor<1x4x768xf32> into tensor<4x768xf32>

It should be possible to sink the expanded dims and fold with the collapse shape, but since each input indexing map is a projection https://github.com/MaheshRavishankar/iree/blob/5c9dac66000f312854a016228633b8b3b52a1282/compiler/src/iree/compiler/Dialect/Flow/Transforms/SinkReshapes.cpp#L73C1-L77C2)

Thanks Ian... let me look into this a little bit more.

Ok, folks. I am landing this with the one regression in number of dispatches. I am checking some out of tree models and this seems to do better.


how many active connection can we establish with this library ?

Hello @Mohammed-khurram-Ahmed,
please check out my response on the issue #340
Greetings
marci4


[BugReportTool] Report if admin flags are set for executables

Summary of the Pull Request
What is this about:

What is include in the PR:

Report admin flags info
Rename ReportRegistry files to RegistryUtils

How does someone test / validate:

Create bug report
Check the existence of the admin-flags-info.txt file in the report
Verify if flags are set correctly

Quality Checklist

[X] Linked issue: #11256
[ ] Communication: I've discussed this with core contributors in the issue.
[ ] Tests: Added/updated and all pass
[ ] Installer: Added/updated and all pass
[ ] Localization: All end user facing strings can be localized
[ ] Docs: Added/ updated
[ ] Binaries: Any new files are added to WXS / YML

[ ] No new binaries
[ ] YML for signing for new binaries
[ ] WXS for installer for new binaries

Contributor License Agreement (CLA)
A CLA must be signed. If not, go over here and sign the CLA.

@mykhailopylyp

Are you only checking if the exe is listed in the reg key? The you get false positives.
The key exists in HKLM too. Is this key not used?

@htcfreek

Are you only checking if the exe is listed in the reg key? The you get false positives.

I am checking if file exists in Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers. What do you mean by false positives? Can you elaborate?

The key exists in HKLM too. Is this key not used?

This is inherited by current user, right? so we need to check it there as well.

@htcfreek

Are you only checking if the exe is listed in the reg key? The you get false positives.

I am checking if file exists in Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers. What do you mean by false positives? Can you elaborate?

In Germany we say "Pictures are better than thousand words 😉:

The values are contain all flags. So it makes more sense to name the file somethign like CompatFlags and export the value to the text file.
(INVENTED EXAMPLE)
PTRun : IsAdmin
PTSettings.exe : None
PTKBM.exe : Win7, IsAdmin

@htcfreek
Thank you for your clarification

@mykhailopylyp

Thank you for your clarification

Example of an configured exe: ~ REGISTERAPPRESTART DISABLEDXMAXIMIZEDWINDOWEDMODE RUNASADMIN 640X480 PERPROCESSSYSTEMDPIFORCEON DPIUNAWARE 256COLOR WIN7RTM

@htcfreek
good point, thanks.
@mykhailopylyp
let's report all the flags for the PowerToys apps.


Bug with select step - original design of containing value fail for edge cases

In tagui_header.js, the following line
if (!found && opt.value.indexOf(valueToMatch) !== -1)

has to be changed to the following
if (!found && opt.value == valueToMatch)

The original design was to match when the option contains the value provided. But this loose definition clearly now encounters an edge case where the values are '-1', '0', '1', '2', '3'..
Providing '1' as value would match with '-1' since '-1' contains '1'). Making this change may cause some existing user scripts to fail (assuming that the search is based on contains).
But is necessary change, otherwise, there is no way to click on the option with '1', as first spotted in this edge case - https://github.com/tebelorg/TagUI-Python/issues/71

Bug fixed with above commit. Fix now available in cutting edge version -
https://github.com/kelaberetiv/TagUI#set-up


Send all VA's an email when survey concludes

Need to setup an email that is sent to all VA’s after the survey finishes announcing the winners of the RFP survey.

Pushed an update for this in previous patch.


use test preparer

tests.yml changes LGTM. Someone else should review the other changes.

/azp run python - appconfiguration - tests

/azp run python - appconfiguration - tests

Can one of the admins verify this patch?

/azp run python - appconfiguration - tests

Will do PS preparer from @seankane-msft solving #13987 instead


Allow start.sh to dynamically pick its channel

Signed-off-by: Joshua Packer<EMAIL_ADDRESS>
Description of the change:
multiclusterengine/start.sh did not work for 2.1.0-backplane snapshots. Did not set the correct subscription channel.
Motivation for the change:

I required the deployment of the 2.1.0-backplane snapshot.

@gurnben

/lgtm


st-flash.exe app crash, scons: *** [upload] Error 309

Image of app crash
Terminal log
I have tried replacing the libusb dll with an updated one but then I just get error 123, so I reverted back to the original libusb. I am able to successfully program the stm32f4discovery with the .bin platformio generates using the stm32 ST-LINK Utility. Any idea why platformIOs st-flash tool is crashing?

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/29253646-st-flash-exe-app-crash-scons-upload-error-309?utm_campaign=plugin&utm_content=tracker%2F2014790&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F2014790&utm_medium=issues&utm_source=github).

Hi @Seep1959
What is wrong with default libusb-1.0.dll?

Nothing what wrong with it, I thought it might fix it.

@Seep1959 Please, update your st-link package via platformio update

@Seep1959 please reopen this issue if it doesn't work.


Fix tests

Codecov Report

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

@@            Coverage Diff            @@
##             master      #49   +/-   ##
=========================================
  Coverage          ?   91.93%
=========================================
  Files             ?       22
  Lines             ?     1525
  Branches          ?       93
=========================================
  Hits              ?     1402
  Misses            ?      119
  Partials          ?        4

Impacted Files
Coverage Δ

tests/test_wallet.py
100% <ø> (ø)

bitcash/network/services.py
68.25% <100%> (ø)

tests/network/test_services.py
100% <100%> (ø)

Continue to review full report at Codecov.

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

Awesome work! Do you want me to cut a new release or hold off for a bit?

Hmm I think we can wait a bit as there was almost no change in the bitcash folder

Ah right, my bad. Just tests here :).


Branding compliance and edits

Fixes #30, #61, #80
@swormke
What's this change do?
Edited repo docs for branding compliance; updated CLA link; edited CONTRIBUTING.
Where should the reviewer start?
Review changes below.
Any background context?
This PR replaces #62 & #63.

@swormke - Do you have time to look at this, or should I assign it to someone else?


chore: rename bin

We can use ./target/{debug, release}/yazi now.

Thanks, that makes sense. I'm wondering if that will affect the current packaging of Nix? @XYenon

Thanks, that makes sense. I'm wondering if that will affect the current packaging of Nix? @XYenon

Yeah I can remove mv $out/bin/app $out/bin/yazi.

Okay, merged!


getObject returning empty strings instead of nil for absent values

I noticed the getObject behavior changed a bit with the XMLRPC calls.  Key without values used to return nil but are now returning as empty strings like "".  There are a few cases where we had to alter logic to account for this.
Was this an intended change?  I know the use of nil always tends to be a hot topic.

This is due to Ruby's xmlrpc library. Maybe it changed with newer versions of Ruby, but currently it will parse an empty string node as an empty string.
And an empty string node it gets from the API:
<value><string/></value>
instead of omitting the field.
So this should be either fixed-enabled in the xmlrpc library or the server, but I don't see this as a bug in softlayer-ruby. Please reopen if you disagree.
P.S. There is a blank? method added to Object by the activesupport gem that will check for both nil and empty string values: e.g.is object.notes.blank?, which would be very convenient in this case.


How to visualize the output of the generator

Related code to save the outputs is below:
"
g_objects = sess.run(net_g_test,feed_dict={z_vector:z_sample})
if not os.path.exists(train_sample_directory):
os.makedirs(train_sample_directory)
g_objects.dump(train_sample_directory+'/biasfree_'+str(epoch))
"
so how can I visualize the output 'biasfree_200' ?

I want to know how to see this data ,too.Did you resolve it?can you share with me

In the training or test phase, I change the saved data format to .mat. There is a  python file to visualize the voxel data. Please see my website: https://github.com/tasx0823/voxel-visualization. Hope to help you.

you mean you save the data in .mat rather than dump()???
and you train the result is good?Could you share ?and we can communite in other media?such as QQ?facebook?

Ok. We can communicate in QQ.   My qq is 532474454.

Hi, im stuck with the same problem, could you please share the code you used to save it as a .mat file?

It may not be the best way to solve it, but I did it by using matplotlib 3d scatterplots saving them as images to another folder after n epochs

Hey, could you please share the implementation of it with me? I tried to do that but the whole code broke. I want to see what I am doing wrong.
Thanks!

Below is the function I use for plotting. I didn't bother for a dynamic solution and just hardcoded 4 images as output by range(4).
def plot_arrays_3d(arrs, epoch, img_dir):
    for i in range(4):
        squeezed = np.squeeze(arrs[i], -1)
        x, y, z = squeezed.nonzero()
        fig = plt.figure()
        ax = fig.add_subplot(111, projection='3d')
        ax.scatter(x, y, -z, zdir='z', c='red')
        plt.savefig(img_dir + '/biasfree_{0}_{1}.png'.format(epoch, i))

That's fantastic, thank you so much!
Can I ask you a quick question since you are active on this thread and have used the code. Did you get chairs outputted in the end. I ran my model with the same parameters as the code but in the end, my graphs are cubes and not chairs. I can see chair shapes around the 4000 epoch but after that they start turning into cubes? Did you change the parameters or am I doing something wrong?

I used this model to generate other 3D objects than the given ones. But I ran into the same problem, where objects started to get generated, but started collapsing to cubes after a short time. It was necessary to use lower learning rates for generator and discriminator to generate objects. The downside with those was it took 17000 epochs with  to get near what I was looking for, but in the end the results were looking good. Although the computing time was 20h on a Tesla V100. The learning rates I used on mit_biasfree.py are
g_lr       = 0.0002
d_lr       = 0.000001
z_size     = 100

It took me a while to fit the hyperparameters to get acceptable results and I don't think they're anywhere near an optimum. Trial and Error makes this task pretty tedious.

I used this model to generate other 3D objects than the given ones. But I ran into the same problem, where objects started to get generated, but started collapsing to cubes after a short time. It was necessary to use lower learning rates for generator and discriminator to generate objects. The downside with those was it took 17000 epochs with to get near what I was looking for, but in the end the results were looking good. Although the computing time was 20h on a Tesla V100. The learning rates I used on mit_biasfree.py are
g_lr       = 0.0002
d_lr       = 0.000001
z_size     = 100

It took me a while to fit the hyperparameters to get acceptable results and I don't think they're anywhere near an optimum. Trial and Error makes this task pretty tedious.

If we change the learning rate as mentioned here. Will it work?
Is there any separate inference script to generate the model?
Is testGAN the inference script? which generates the chair?
Please answer my questions.
Thanks in advance.


[Question] Can you make Bounds and Double3 structs not readonly please?

We want to be able to serialize/deserialize a model's bounds to json so we can see the representation of the bounding models without being connected to ARR. At the moment Bounds and Double3 are readonly so it fails to deserialize if we just use the Bound struct directly. For now, we've just removed that keyword so it works, but it's something that must be maintained with every SDK upgrade which is prone to error.
We could obviously just create our own bounds struct and populate it from the ARR bounds struct, but it would be cleaner if you could remove the readonly keywords. Is that something you would consider?
Thanks

Hi,
I think the reasoning was some API requirement. But from a very practical point of view, it indeed does not make too much sense in this context. Let's see if we can change it, I can't promise at this point though.
Cheers,
Florian

good news, we decided to drop the read-only attributes. While it was a recommendation by the Azure guidelines, we think it does not serve any real purpose here, since structs are passed by value anyway.
It will be removed as per next release.

closing this ticket since 1.0.51 with these changes has been released today. Enjoy!


Splitting the download function

Hey Claudiu,
I has wondering if there are any plans on splitting the _download_with_progress method into the different parts it includes (details, purchase, delivery..) to allow for more modular usage of the project (for example, I need to edit the update section, but would still want to easily merge in future changes).
Again, I really love the project.
Thanks

Hi, currently I have no future plans regarding the download method, but I'm open to discussion if you want to propose some enhancements.


fix(cmd) Fix proctype regex for setting limits

This fixes the proctype regex to match the one used by deis/controller.
This fixes an issue reported by user "tylux" on slack where setting limits for a proctype called "worker1" failed with:
Error: worker1=100M/350M doesn’t fit format type=#unit or type=# or type=#/#

I've tested the new regex in this go playground.

I'll add some test cases, this was done quickly in the browser.

Codecov Report

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

@@           Coverage Diff           @@
##           master     #308   +/-   ##
=======================================
  Coverage   72.71%   72.71%
=======================================
  Files          59       59
  Lines        4109     4109
=======================================
  Hits         2988     2988
  Misses        793      793
  Partials      328      328

Impacted Files
Coverage Δ

cmd/limits.go
82.92% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

OK, I've added a few relevang test cases in 1f5e242. Should be good to go from my side.

Could you possibly fix the regex used here as well?

Fixed in f82cf8373b2742ac4a354220dd25a458c9bf160d.


About the training time

Hello, thank you so much for contributing this project.
I am training this model recently. I also use one 3090 and the same setting as you. But i need spend about 20 hours for each epoch. Do you know what's the reason?
Thank you so much for your answering in advance.

Did you put your data in SSD?

My data in /media/user/sda1

sda1 is the name of your disk. You need to check the type of your disk. If it is HDD, the speed for loading the data is very slow. Most of time is using for dataloader (by CPU), so your GPU is empty, which means your GPU device is not training your model.
So you need to put your data into the SSD(Solid-state drive), so CPU can load data very fast. GPU can run 100% util.

Thank you so much! I will try it.

Thank you so much! I will try it.
Hi, I want to ask, have you fixed this problem? I moved the data to SSD, but the training time is still very long.


Cannot invoke error.

I am trying to configure fabric exporter for 1.16.5
using, Windows with all of fabric 3 mod pack.
Not sure if I can ignore the error as I still haven't gotten the panel connected yet.
I can upload the entire log if necessary.
added note: visiting the 25585/metrics seems to work so I feel that this is not of concern

I've tried FabricExporter 1.0.1 and 1.0.3, but was unable to reproduce this with this modpack. Please upload the entire log and config/exporter.properties

I am experiencing the same thing on my server.
I think that I might have found the cause in MillisPerTick.java#L16 because for the value for the label "type" is undefined.
It only happens when Spark is still initializing.

It seems to me that race condition of some kind takes place here, because I still can't reproduce this. I suppose that registering metrics on mod initialization with running updater on server start also can cause this. And I also don't know why this occurs only with MillisPerTick, but doesn't occur with TicksPerSecond where the similar solution with default gauge values is used.

The TicksPerSecond Gauge doesn't have any labels defined so it doesn't need label values but MillisPerTick has the "type" label and doesn't get a value in that null-check case. Maybe instead of setting the gauge to 0 you could set it for the type "min", "max" and "mean".

Okay, it looks like this is the real cause of this problem. Now it should be fixed. Thanks for help.


Debug Console window cannot accept Console.ReadLine() input during debugging

VSCode Version: 1.8.0
OS Version: Win10 x64

Steps to Reproduce:

Create a new .net core cli app using "dotnet new"
Open the folder using VS code
Add two lines of code in Program.cs
string a = Console.ReadLine();
Console.WriteLine(a);
Switch to VS code debug window and start debugging
Debug Console window shows, and displays the first "Hello, World." output, and stops on the line of Console.ReadLine(), enter anything in the Debug Console and press Enter will be given err message of "Unable to perform this action because the process is running."

The debug console is output only. The input field you see is for inspecting the environment available at a given stack frame. In your launch config you can specify what console your program should use. Set the console property to externalTerminal. internalTerminal should work as well.

@weinand I think we should look for a way to make more explicit that the input field is inspection only.

@kieferrm thank you for your reply, below is my launch.json file and I didn't find a property called console, only externalConsole, when it's set to true the keyboard input can be accepted but a new console opened for the debugging, I cannot find internalTerminal configuration option. I tried to switch to the Integrated Terminal while the app waits for the keyboard input but it's the command line there waiting for a command.
Anyway I still wonder if I can debug the app within the Visual Studio Code UI while making Console.ReadLine() to work correctly.
{     "version": "0.2.0",     "configurations": [         {             "name": ".NET Core Launch (console)",             "type": "coreclr",             "request": "launch",             "preLaunchTask": "build",             "program": "${workspaceRoot}\\bin\\Debug\\netcoreapp1.1\\hwapp.dll",             "args": [],             "cwd": "${workspaceRoot}",             "externalConsole": false,             "stopAtEntry": false,             "internalConsoleOptions": "openOnFirstSessionStart"         },         {             "name": ".NET Core Attach",             "type": "coreclr",             "request": "attach",             "processId": "${command.pickProcess}"         }     ] }
If you can get a modified launch.json to solve my problem that will be great.

@LiangZugeng you are using the coreCLR debugger. I'll move this issue to the corresponding repository.

This issue was moved to OmniSharp/omnisharp-vscode#1053

Properties>Application>Output type  Select into ComboBox "Console Application"


STDOUT/STDERR logs to separate endpoints

Is your feature request related to a problem? Please describe.
According to the WES v1.0.0 specs, stdout and stderr in the run and task logs of the GET /runs/{run_id} response should consist of URLs pointing to these logs, not the logs themselves (as is currently implemented).
Describe the solution you'd like
Add an OpenAPI spec for additional endpoints, e.g., /logs/stdout/{id} and /logs/stderr/{id} where run and task logs can be retrieved from via GET requests. Business logic for the existing GET /runs/{run_id} endpoint needs to be adjusted accordingly.
Describe alternatives you've considered
N/A
Additional context
N/A

Started implementation together with #128


max_tokens_to_sample is negative

I am getting this error continuously. I am using mistral-tiny model. After integrating the api I was able to chat with the bot successfully for 15 mins and the conversations was also short like 7 to 8 words of input max. But after that I am continuously getting this error. Earlier it was positive.
2024-01-27 13:20:38 max_tokens_to_sample: -223
2024-01-27 13:20:38 [2024-01-27T07:50:38Z ERROR assistants_extra::llm] Error calling Open Source LLM through OpenAI API: API Error: API request failed with status 422 Unprocessable Entity: {"object":"error","message":"{"detail":[{"type":"greater_than_equal","loc":["body","max_tokens"],"msg":"Input should be greater than or equal to 0","input":-223,"ctx":{"ge":0},"url":"https://errors.pydantic.dev/2.5/v/greater_than_equal\"}]}","type":"internal_error_proxy","param":null,"code":"1000"}
2024-01-27 13:20:38 [2024-01-27T07:50:38Z ERROR assistants_core::executor] Assistant model error: API Error: API request failed with status 422 Unprocessable Entity: {"object":"error","message":"{"detail":[{"type":"greater_than_equal","loc":["body","max_tokens"],"msg":"Input should be greater than or equal to 0","input":-223,"ctx":{"ge":0},"url":"https://errors.pydantic.dev/2.5/v/greater_than_equal\"}]}","type":"internal_error_proxy","param":null,"code":"1000"}
2024-01-27 13:20:38 [2024-01-27T07:50:38Z ERROR assistants_core::executor] Run error: Assistant model error: API Error: API request failed with status 422 Unprocessable Entity: {"object":"error","message":"{"detail":[{"type":"greater_than_equal","loc":["body","max_tokens"],"msg":"Input should be greater than or equal to 0","input":-223,"ctx":{"ge":0},"url":"https://errors.pydantic.dev/2.5/v/greater_than_equal\"}]}","type":"internal_error_proxy","param":null,"code":"1000"}
2024-01-27 13:20:38 [2024-01-27T07:50:38Z INFO  assistants_core::runs] Updating run for run_id: a081865d-8bea-4a37-adad-410c8dd6726d
2024-01-27 13:20:38 [2024-01-27T07:50:38Z ERROR assistants_core::executor] Error: Assistant model error: API Error: API request failed with status 422 Unprocessable Entity: {"object":"error","message":"{"detail":[{"type":"greater_than_equal","loc":["body","max_tokens"],"msg":"Input should be greater than or equal to 0","input":-223,"ctx":{"ge":0},"url":"https://errors.pydantic.dev/2.5/v/greater_than_equal\"}]}","type":"internal_error_proxy","param":null,"code":"1000"}
2024-01-27 13:20:38 [2024-01-27T07:50:38Z INFO  assistants_core::executor] Consuming queue
2024-01-27 13:20:39 [2024-01-27T07:50:39Z INFO  assistants_core::runs] Getting run from database for thread_id: 6f0acb94-24ae-41f9-b58d-a8bc4bf12d6d and run_id: a081865d-8bea-4a37-adad-410c8dd6726d
2024-01-27 13:20:39 [2024-01-27T07:50:39Z INFO  assistants_core::messages] Listing messages for thread_id: 6f0acb94-24ae-41f9-b58d-a8bc4bf12d6d
2024-01-27 13:20:39 [2024-01-27T07:50:39Z INFO  assistants_core::runs] Listing runs for thread_id: 6f0acb94-24ae-41f9-b58d-a8bc4bf12d6d
2024-01-27 13:20:40 [2024-01-27T07:50:40Z ERROR async_openai::error] failed deserialization of: {"detail":"Not Found"}
2024-01-27 13:20:40 [2024-01-27T07:50:40Z ERROR tower_http::trace::on_failure] response failed classification=Status code: 500 Internal Server Error latency=647 ms
2024-01-27 13:20:41 [2024-01-27T07:50:41Z ERROR async_openai::error] failed deserialization of: {"detail":"Not Found"}
2024-01-27 13:20:41 [2024-01-27T07:50:41Z ERROR tower_http::trace::on_failure] response failed classification=Status code: 500 Internal Server Error latency=548 ms
2024-01-27 13:20:43 [2024-01-27T07:50:43Z ERROR async_openai::error] failed deserialization of: {"detail":"Not Found"}
2024-01-27 13:20:43 [2024-01-27T07:50:43Z ERROR tower_http::trace::on_failure] response failed classification=Status code: 500 Internal Server Error latency=567 ms

Thanks
By default we assume 4096 LLM context size and automatically tweak the max tokens to be at maximum using tiktoken
Can you share the prompt seen in logs? Or is it big/small? If your prompt is >4096 I've never tested this use case but probably should fail
If the LLM has more than 4096 you can run the API with MODEL_CONTEXT_SIZE=yourmodelsize

@RahulVerma989 any update


Remove the fullPage scroll functionality.

In fullPage js there is a configuration variable to disable fullpage scrolling. It is a great idea, but doesn't work great for high single-page websites with a decent amount of content.

In fact, fullPage javascript plugin should be removed all together. We should heavily leverage bootstrap 4.0, rather than fullpage JS.

Closed via #13.


Add documentation into API definition before release

Problem description

Agreement is that CAMARA documentation should be embedded within the OAS definition, and not separate. This reduces the effort required in maintaining documentation consistently.
Expected action

Add documentation to API definition as discussed in https://github.com/camaraproject/WorkingGroups/issues/164
In addition it should be considered to move the (remaining) content of https://github.com/camaraproject/NumberVerification/blob/main/documentation/API_documentation/README.MD either into the YAML file or into the sub project README.md.
Additional context

@ECORMAC I think we can close this one too since the cleanup has been completed in PR(#58)

@fernandopradocabrillo yes, thanks!


Re-run colab examples with cirq v0.6.0

The reason for this is to minimize diff when we replace XXYY and YXXY with ISWAP gates.

There are still XXYY and YXXY since those gates haven't been replaced by their Cirq equivalents.

@vtomole Yes, this is intentional. I wanted to split the cirq version update and the gate replacement into two separate PRs in order to make it clear that the changes to the computed values are due to cirq version update and not due to the new gates (which as demonstrated by #359 should have no effect).


Reliability

The terminals didn't count (actively) the checkins at the last ALT night. We need to make sure that every single time that we plug in the SICKs that it connects to our backend.

More stories made for this


Added a PDB write function. The function accepts a dictionary with at…

…om information and writes out a PDB file. A testing ffunction is included.

@svihuri
Please check the latest push. to write a new test output comment out the os.remove line.


DIH in solrcloud(Apache Solr Operator) mode with Solr 8.11.2

Is there any documentation on DIH in SolrCloud mode for version > 8.11.0
Is data-import-handler-8.10.0.jar the only lib we need to include in solrconfig.xml? I don't see any data-import-handler-extras jar
We are trying to use DIH with SolrCloud(Apache Solr Operator) on EKS.

Hello, @rohitbemax @rmuir @jdyer1 @uschindler @markrmiller - Would you have any pointers on this? thanks in advance

Hello @iampranabroy did you figure this out?

Hey @odiloRugamba - We used the default bundled DIH with solr image and used it like below in the solrconfig.xml file.
<lib dir="${solr.install.dir:../../../..}/dist/" regex="solr-dataimporthandler-.*\.jar" />

But the documentation on DIH use with SolrCloud mode would definitely help.

Hey @ilivss - As mentioned we have used the default DIH provided till version 8.xx
<lib dir="${solr.install.dir:../../../..}/dist/" regex="solr-dataimporthandler-.*\.jar" />

For your problem, it looks more like an issue with the config. Can you check if the config is loaded and when you create the collection, you are using that config to create the collection? When DIH runs for the first time, if all properties/configs are correct, it should create  dataimport.properties file.
Also, can you check if you are able to load your custom sqldriver. jar from the solrconfig.xml properties file?
Example: If you sqldriver.jar is in tmp/solr/lib path by using.
<lib dir="/tmp/solr/lib/" regex="sqldriver.jar" />

I read your comment too late unfortunately. for the time being I just deployed Solr 8.11.2 standalone mode in a normal Azure VM. Anyway thanks for your help! @iampranabroy

can we close this issue?


DASH DRM

Please how to deal with DRM ( PlayReady ) in DASH format

i need help please, @NathanaelA @NathanWalker @rigor789

@senateurritchie - ExoPlayer supports Dash & DRM, however I'm not sure if anything has been wired up for DRM (basically the calls have to be made during setup to support DRM).       This is something you can create a PR and we would merge, as the code is open source.   If you don't feel confident in your skills, you can pay another developer to wire the DRM up for you (please note we at nStudio do contract/consulting work, so you can also hire us to do it).

Finally i did it. i implement DRM and also ADS support .
thanks

@senateurritchie - Awesome, can you submit a PR so that the rest of the community can also get the features?

Finally i did it. i implement DRM and also ADS support . thanks

Can you share how you have made it?


Bump cmake to version 3.23.1

bors try --target x86_64

bors try --target x86_64

bors r+

bors cancel
#695

bors r+


Modularized Resolvers and TypeDefs - Error: typeDefs.reduce is not a function

I am trying to place resolvers and typeDefs in separate files using merge-graphql-schemas. They are successfully merged however, I am getting this error when they reach new GraphQLServer({...}). Any help would be appreciated.
Error
TypeError: typeDefs.reduce is not a function
    at mergeTypeDefs (/[path...]/typeorm-demo/node_modules/graphql-yoga/src/index.ts:313:19)

Files
I have 2  .ts resolvers and 2 .graphql typeDefs formatted like:
#/resolvers/simple.resolver.ts
export default {
  Query: {
    beerMe: (_, { name }) => `Beer ${name || "Served"}`
  }
};

#/typeDefs/simple.typeDef.graphql
type Query {
  beerMe(name: String): String!
}

_#/typeDefs/index.ts
import * as path from "path";
import { fileLoader, mergeTypes } from "merge-graphql-schemas";

const typesArray = fileLoader(path.join(__dirname, "./"));
const typesMerged = mergeTypes(typesArray, { all: false });
console.log("typesMerged", typesMerged);
export default typesMerged;

#/resolvers/index.ts
import { mergeResolvers } from "merge-graphql-schemas";
import userResolver from "./user.resolvers";
import simpleResolver from "./simple.resolvers";

const resolversArray = [userResolver, simpleResolver];
const resolvers = mergeResolvers(resolversArray);
console.log("merged resolvers", resolvers);
export default resolvers;

#scr/index.ts
import "reflect-metadata";
import { createConnection } from "typeorm";
import { IResolvers } from "graphql-yoga/dist/src/types";
import { GraphQLServer } from "graphql-yoga";

const resolvers = require("./resolvers");
const typeDefs = require("./typeDefs");
const server = new GraphQLServer({ typeDefs, resolvers });
createConnection().then(() => {
  server.start(() => console.log("Server is running on localhost:4000"));
});

Directory structure
__src
|____entity
| |____Profile.ts
| |____User.mysql-version.ts.bak
| |____User.ts
|____index.ts
|____resolvers
| |____index.ts
| |____simple.resolvers.ts
| |____user.resolvers.ts
|____typeDefs
| |____index.ts
| |____simple.typedefs.graphql
| |____user.typedefs.graphql

Sure can. https://github.com/jboothe/typeorm-graphql-demo.
Thanks for taking a look.

You should import it differently:
import { default as typeDefs } from './typeDefs'
because when you import it with require its in this shape:
{ default: 'schema {\n  query: Query\n  mutation: Mutation\n}\n\ntype Query {\n  beerMe(name: String): String!\n  user(id: Int!): User!\n  users: [User!]!\n}\n\ntype Mutation {\n  createUser(firstName: String!, lastName: String!, age: Int!, email: String!, profile: ProfileInput): User!\n  updateUser(id: Int!, firstName: String, lastName: String, age: Int, email: String): Boolean\n  deleteUser(id: Int!): Boolean\n  deleteUserConditionally(id: Int!): Boolean\n}\n\ntype User {\n  id: Int!\n  firstName: String!\n  lastName: String!\n  email: String!\n  age: Int!\n  profile: Profile\n}\n\ntype Profile {\n  id: Int!\n  gender: String!\n  photo: String\n}\n\ninput ProfileInput {\n  gender: String!\n  photo: String\n}\n' }

so you need to add .default  or use import how i wrote on top :)

@marktani Wanted to add more insight. Your provided Object to mergeTypeDefs what is not supported. Currently is supported string, array, documentNode. So maybe there should be some better error handling to show proper error. So there is missing check for array and if it's not an array just throw error :) If somebody merge #220 I can do this fix and update documentation.

Thanks @Huvik 🎉 . Using that import syntax on both resolvers and typeDefs solved the issue.
import { default as typeDefs } from './typeDefs'
import { default as resolvers } from './resolvers'

Great, thanks for the confirmation @jboothe! I am hoping this helps you progress with #136. I'd be curious to hear more about this.
@Huvik, it would be great if you can include the improvements you mentioned in a new PR.
Thanks all :raised_hands:

I'm on it. If it helps others remove that barrier, I'm glad to help.

@jboothe Can you please tell how you imported types from 'generated/prisma.graphql'? When I try following this, I get Type "<typeName>" not found in the document.

@Alosies can you create a new issue with a reproduction example? :slightly_smiling_face:

I'm currently trying this with prism using merge resolvers, but my user listings aren't showing.
src/schema.graphql
# import Listing from './generated/prisma.graphql'
# import User from './generated/prisma.graphql'

type Query {
  listings(searchString: String): [Listing!]!
  listing(id: ID!): Listing
  users(searchString: String): [User!]!
  user(id: ID!): User
}

type Mutation {
  createDraft(authorId: ID!, title: String!, content: String!): Listing
  publish(id: ID!): Listing
  deleteListing(id: ID!): Listing
  createUser(username: String!, email: String!, name: String!, firstName: String!, lastName: String!): User!
}

src/resolvers/index.js
import * as path from "path";
import { mergeResolvers, fileLoader } from "merge-graphql-schemas";

const resolversArray = fileLoader(path.join(__dirname, "./**/*.resolvers.*"));

const resolvers = mergeResolvers(resolversArray);

export default resolvers;

src/resolvers/listing.resolvers.js
export default {

  Query: {
    listings: (_, args, context, info) => {
      return context.prisma.query.listings(
        {
          where: {
            OR: [
              { title_contains: args.searchString },
              { content_contains: args.searchString },
            ],
          },
        },
        info,
      )
    }
  },
  Mutation: {
    createDraft: (_, args, context, info) => {
      return context.prisma.mutation.createListing(
        {
          data: {
            title: args.title,
            content: args.title,
            author: {
              connect: {
                id: args.authorId,
              },
            },
          },
        },
        info,
      )
    },
    publish: (_, args, context, info) => {
      return context.prisma.mutation.updateListing(
        {
          where: {
            id: args.id,
          },
          data: {
            published: true,
          },
        },
        info,
      )
    },
    deleteListing: (_, args, context, info) => {
      return context.prisma.mutation.deleteListing(
        {
          where: {
            id: args.id,
          },
        },
        info,
      )
    },

  },
}

src/resolvers/user.resolvers.js

export default {

    Query: {

      users: (_, args, context, info) => {
        return context.prisma.query.users(
          info,
        )
      },
      user: (_, args, context, info) => {
        return context.prisma.query.user(
          {
            where: {
              id: args.id,
            },
          },
          info,
        )
      },

    },

    Mutation: {
    createUser: (_, args, context, info) => {
      return context.prisma.mutation.createUser(
        {
          data: {
            name: args.name,
            username: args.username,
            email: args.email,
            firstName: args.firstName,
            lastName: args.lastName,
          },
        },
        info,
      )
    },
  }

}

src/index.js
import { GraphQLServer } from 'graphql-yoga';
import { Prisma } from 'prisma-binding';
// import { default as typeDefs } from './typeDefs'
import { default as resolvers } from './resolvers';

const options = { port: 1337 };

const server = new GraphQLServer({
  typeDefs: 'src/schema.graphql',
  resolvers,
  context: req => ({
    ...req,
    prisma: new Prisma({
      typeDefs: 'src/generated/prisma.graphql',
      endpoint: 'http://localhost:4466',
    }),
  }),
});
server.start(options, () => console.log(`Server is running ⚡ on localhost:${options.port}`)).catch(err => console.error('connection Error', err));

it works, but my users query returns null for listings
{
  "data": {
    "users": [
      {
        "id": "cjizxnenk000e0719e1bx8jvb",
        "username": "jimmyjamieson",
        "name": "Ian Jamieson",
        "firstName": "Ian",
        "lastName": "Jamieson",
        "email"<EMAIL_ADDRESS>        "rating": 0,
        "listings": null
      }
    ]
  }
}

If i copy the resolvers into resolvers/index.js I get the listings showing fine, so I think it has something do do with merge schemas.

Also, a console.log(resolvers) inside src/resolvers/index.js produces
{ Query:
   { listings: [Function: listings],
     users: [Function: users],
     user: [Function: user] },
  Mutation:
   { createDraft: [Function: createDraft],
     publish: [Function: publish],
     deleteListing: [Function: deleteListing],
     createUser: [Function: createUser] } }


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_35noo56gjf/clone/recipe/meta.yaml:15: pip_install_args: pip install should be run with --no-deps.
ERROR: /tmp/abs_35noo56gjf/clone/recipe/meta.yaml:20: host_section_needs_exact_pinnings: Packages in host must have exact version pinnings, except python build tools.
ERROR: /tmp/abs_35noo56gjf/clone/recipe/meta.yaml:21: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_35noo56gjf/clone/recipe/meta.yaml:42: missing_documentation: The recipe is missing a doc_url or doc_source_url
Errors were found


ui/project_form: Improve file handling in UI

Enhance file input handling in the UI to avoid losing selected files when adding new inputs.
Introduce a selectedFiles array to store and manage selected files.
Display selected files in the UI with additional features, including a delete button.
Update the removeFile function to correctly remove files from both the UI and the selectedFiles array.

Fixes: #991
UI Updates
https://github.com/nexB/scancode.io/assets/64846852/4d615d1a-1128-4633-9728-34153f6bc564

@jayanth-kumar-morem I've noticed an issue while reviewing this PR, to reproduce:

Drag and drop a file into the form, then drag and drop it again. The file is duplicated in the list. Note that this does not happen with the "Click" to select file.


chore(policy): Add new default policy for the Rapid Reset vulns

Description
Cherry-picking into the 4.1 branch
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
Here I tell how I validated my change
TODO(replace-me)
Use this space to explain how you validated that your change functions exactly how you expect it.
Feel free to attach JSON snippets, curl commands, screenshots, etc. Apply a simple benchmark: would the information you
provided convince any reviewer or any external reader that you did enough to validate your change.
It is acceptable to assume trust and keep this section light, e.g. as a bullet-point list.
It is acceptable to skip testing in cases when CI is sufficient, or it's a markdown or code comment change only.
It is also acceptable to skip testing for changes that are too taxing to test before merging. In such case you are
responsible for the change after it gets merged which includes reverting, fixing, etc. Make sure you validate the change
ASAP after it gets merged or explain in PR when the validation will be performed.
Explain here why you skipped testing in case you did so.
Have you created automated tests for your change? Explain here which validation activities you did manually and why so.
Reminder for reviewers
In addition to reviewing code here, reviewers must also review testing and request further testing in case the
performed one does not seem sufficient. As a reviewer, you must not approve the change until you understand the
performed testing and you are satisfied with it.

/retest

/retest

/retest

/test ocp-4-12-core-bpf-qa-e2e-tests

/test ocp-4-12-core-bpf-qa-e2e-tests


[bug]: prophet: Does not work as expected.

Check the bug has not already been reported

[x] I could not find the bug in existing issues

Edit function_name and the short error description in title above

[X] I wrote the correct function name and a short error description in the title above

What happened and what did you expect?
When attempting to invoke the prophet function, I received the following error when using the provided example:
Number of arguments does not match for function bigfunctions.us.prophet. Supported signature: bigfunctions.us.prophet(JSON, FLOAT64, JSON) at [1:8]
After some experimentation, I was able to get a working example:
WITH sample_data AS (
SELECT
TO_JSON(ARRAY<STRUCT<ds STRING, y FLOAT64>>[
('2020-01-01', 1.0),
('2020-01-02', 2.0),
('2020-01-03', 3.0)
]) AS records,
CAST(3 AS FLOAT64) AS periods,
TO_JSON(STRUCT<daily_seasonality BOOL, yearly_seasonality BOOL>(TRUE, TRUE)) AS kwargs
)
SELECT
bigfunctions.us.prophet(
records,
periods,
kwargs
) AS forecasted_records
FROM
sample_data;

Fixed.
Thanks for reporting.


chore(examples/starter): Fix DB migrations and subcommand execution

This is a follow-up to https://github.com/electric-sql/electric/pull/505 and https://github.com/electric-sql/electric/pull/502. I'm addressing a few different concerns in the same PR only because we don't have automated tests for the starter and redoing the same manual testing steps multiple times is error-prone.
Here's a brief description of changes.
Removed shelljs-live
This reverts https://github.com/electric-sql/electric/pull/505/commits/a8764b0181171c9ab4360caf028b1c0b0dcec554.
Turns out shelljs-live is not a drop-in replacement for shelljs. It only uses shelljs's config but implements a different API for executing a subprocess that only returns the status code to the caller. This broke our error handling in startCompose.js and startElectric.js that expects the return value to have the stderr field. I discovered this problem when I executed yarn backend:up instead of yarn backend:start:

Console output
$ yarn backend:up
yarn run v1.22.19
warning package.json: No license field
warning ../../../package.json: No license field
$ yarn backend:start --detach
warning package.json: No license field
warning ../../../package.json: No license field
$ node ./backend/startCompose.js --detach
[+] Running 5/5
 ✔ Network app_default         Created                                                                                0.1s
 ✔ Volume "app_pg_data"        Created                                                                                0.0s
 ✔ Volume "app_electric_data"  Created                                                                                0.0s
 ✔ Container app-postgres-1    Started                                                                                0.1s
 ✔ Container app-electric-1    Started                                                                                0.1s
/home/alco/code/tmp/app/backend/startCompose.js:11
if (res.code !== 0 && res.stderr.includes('port is already allocated')) {
                                 ^

TypeError: Cannot read properties of undefined (reading 'includes')
    at Object.<anonymous> (/home/alco/code/tmp/app/backend/startCompose.js:11:34)
    at Module._compile (node:internal/modules/cjs/loader:1256:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
    at Module.load (node:internal/modules/cjs/loader:1119:32)
    at Module._load (node:internal/modules/cjs/loader:960:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:86:12)
    at node:internal/main/run_main_module:23:47

Node.js v18.18.0
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

It does mean we lose colorized output from yarn backend:start. But I believe it can be restored by getting rid of shelljs completely and using cross-spawn like shelljs-live does.
Replaced ad-hoc migration runner with @databases/pg-migrations
This package does everything we need: it can run multiple migrations and keeps track of already applied migrations. Here's sample output where I run it to apply a migration, then run it again to demonstrate the idempotency, then I add a new migration file and run it one more time:

The way @databases/pg-migrations keeps track of applied migrations is a bit noisy:
[localhost] postgres:app=# \d
                          List of relations
 Schema │                 Name                  │   Type   │  Owner
────────┼───────────────────────────────────────┼──────────┼──────────
 public │ atdatabases_migrations_applied        │ table    │ postgres
 public │ atdatabases_migrations_applied_id_seq │ sequence │ postgres
 public │ atdatabases_migrations_version        │ table    │ postgres
 public │ foo                                   │ table    │ postgres
 public │ items                                 │ table    │ postgres
(5 rows)

But I don't think it's a problem for the starter template. Once we introduce integrations with backend frameworks, we'll replace this migrations runner with framework-specific ones.
NOTE: GitHub shows a very hard-to-read diff for db/migrate.js. I suggest viewing the file instead because it has completely new content compared to what was there before.
Reset terminal color back to default after printing an error message
Our colorized error messages where missing the "reset" ANSI escape which was causing the output following the error message to also be colored, namely, the Done line printed by yarn.

I guess we can close #502 now as this replaces it.


Add NWM zonal averaging workflow

Here's an example of the "small" version running https://cloud.coiled.io/clusters/590277/account/dask-engineering/information. It takes ~18 minutes and costs ~$0.60. Running the "large" version now.


Exposing bandwidth estimate

I would like to expose the bandwidth estimate via the API, and I was wondering if such a change would be accepted.
When encoding video for streaming, it is often possible to set a bandwidth limit. This reduces the quality of the video instead of dropping frames which often a better alternative, depending on the application and the degree to which quality would need to be reduced.
It would be nice (and probably also more accurate) to be able to get the bandwidth estimate from the quic API instead of having to calculate it based on own RTT measurements and sizes of outgoing frames.

Sounds reasonable, but we need to be very careful to expose something that's actually useful.
The bandwidth estimate is very dependent on the congestion controller in use. For example, with loss-based congestion controllers like Reno or Cubic (as we're implementing right now), the estimate will vary greatly around the time of packet loss (since a packet loss causes a reduction of the cwnd by 30%). When using a non-queue-building congestion controller like BBR or Prague (which we currently don't implement, but might at some point in the future), the bandwidth estimate will likely not fluctuate that sharply.
Do you have any concrete suggestions?
We should probably also expose an RTT estimate (latest, smoothed?).

It will be pretty useful for knowing how much data is efficient to push through each stream, like for example a giant file server needs to know how big chunks it can send, based on bandwidth. and if large files, it should do it dynamically for efficiency to reduce overheads.
Really hope you guys expose all the RTT methods so we can calculate the bandwidth :D


How do I change the loading type when I am using ActivityData() ?

I want to call this animation with one lines of code from anywhere of my project. So I have created a Util.swift, and make 2 functions. Like this :
func showLoading(message: String){
    let activityData = ActivityData()

    NVActivityIndicatorPresenter.sharedInstance.startAnimating(activityData)
    NVActivityIndicatorPresenter.sharedInstance.setMessage(message)
}

func hideLoading(){
    NVActivityIndicatorPresenter.sharedInstance.stopAnimating()
}

So I can successfully show the loading by calling
showLoading(message: "Testing loading util...")
But the animation is showing .ballSpinFadeLoader, which is not I want.
How to I change the animation type?

@junweimah: You can do it by changing the global default value NVActivityIndicatorView.DEFAULT_TYPE to another animation type, or pass the type on initializing ActivityData(type: <type>).


fix(RELEASE-1063): linting issues in collect-slack-notification-params

this commit fixes the linting issues present in
the collect-slack-notification-params task
Signed-off-by: Leandro Mendes<EMAIL_ADDRESS>

Changes look fine, but can you bump the z of the version and add a README entry? The other PRs doing the same do that

done!

/retest

/retest


feat: adapt search page

What type of PR is this?
/kind feature
What this PR does / why we need it:
适配搜索页面
Which issue(s) this PR fixes:
Fixes #314
Does this PR introduce a user-facing change?
适配基于路由的搜索页面

等待 PluginSearchWidget 发布新版本


[ISSUE #4771]In HA mode, if you do not truncate consumerOffsetMap, it may cause a bug

BUG REPORT
close #4771

Good point!

@RongtongJin The truncation may also need to be done when the broker role changes.

@RongtongJin The truncation may also need to be done when the broker role changes.

Yes, when the broker role changes, commit log and consume queue have been truncated, but consumer offset has not been corrected. This PR will correct consumer offset.

As I pointed out here, this fix is kind of walkaround. Should we invest more efforts on the design flaw or correct the design issue itself?

Codecov Report

Merging #4797 (48968f3) into develop (64c18fb) will decrease coverage by 0.00%.
The diff coverage is 2.43%.

@@              Coverage Diff              @@
##             develop    #4797      +/-   ##
=============================================
- Coverage      43.29%   43.29%   -0.01%
- Complexity      7688     7703      +15
=============================================
  Files            991      994       +3
  Lines          68781    68979     +198
  Branches        9111     9144      +33
=============================================
+ Hits           29782    29866      +84
- Misses         35253    35365     +112
- Partials        3746     3748       +2

Impacted Files
Coverage Δ

.../rocketmq/broker/offset/ConsumerOffsetManager.java
27.89% <0.00%> (-4.23%)
:arrow_down:

...n/java/org/apache/rocketmq/store/MessageStore.java
0.00% <ø> (ø)

...apache/rocketmq/store/timer/TimerMessageStore.java
53.70% <0.00%> (-0.59%)
:arrow_down:

...org/apache/rocketmq/store/DefaultMessageStore.java
55.23% <14.28%> (-0.23%)
:arrow_down:

...or/validator/DefaultTopicMessageTypeValidator.java
40.00% <0.00%> (-10.00%)
:arrow_down:

...e/rocketmq/controller/impl/manager/BrokerInfo.java
78.94% <0.00%> (-9.29%)
:arrow_down:

...ocketmq/controller/impl/manager/SyncStateInfo.java
83.33% <0.00%> (-7.58%)
:arrow_down:

...he/rocketmq/controller/impl/DLedgerController.java
69.51% <0.00%> (-3.46%)
:arrow_down:

...ketmq/client/impl/consumer/PullMessageService.java
49.23% <0.00%> (-3.08%)
:arrow_down:

...ache/rocketmq/controller/impl/event/EventType.java
73.68% <0.00%> (-2.79%)
:arrow_down:

... and 36 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Images resize on search results page load

Description
When I browse search results on the new site there is a slight flicker as images resize to my screen. Though the images resize relatively quickly and users likely don't notice this, I do wonder if this is affecting CLS (Cumulative Layout Shift) scores. It might be worth seeing if this shifting on pageload could be reduced.
Reproduction

Go to https://search-staging.openverse.engineering/search/image?q=dog&ff_new_header=on
Observe the results are originally a smaller size and grow to a larger size to fit the screen.

Screenshots
Screencast: https://d.pr/v/8IC5jL
Environment

Device: Macbook Pro
OS: OSX 12.5.1
Browser: Chrome
Version: 106.0.5249.119 (Official Build) (arm64)

Resolution

[ ] 🙋 I would be interested in resolving this bug.

Wow, nice find! This is a very peculiar regression I hadn't noticed. CC @WordPress/openverse-frontend

@zackkrida I thought I remembered a PR we worked on to fix this issue and it turns out you actually worked to fix this several months ago: https://github.com/WordPress/openverse-frontend/pull/1381
This is definitely a recent regression. I wonder what caused it? The fix for this issue should include a Playwright test to check this, if possible. The linked PR might be a good place to start to look into what differences have been introduced since then that could have caused this regression.

@sarayourfriend that work I did was actually on the single result pages, not on the search result pages. I think this issue may relate to layout/container changes made to the global layout to accommodate the new header.
Big ➕ to the playwright test suggestion.

Oh! I misunderstood this issue. Thank you for clarifying it.

We are rendering the search page as mobile on the server. Then, in the onMounted hook, we open the filters if the page width is above lg and the localStorage value for areFiltersOpen isn't set to false. This causes the error behavior on the video.
The first solution that came to my mind would be to set the filters open on the first render, and then, in onMounted, close them if the width is below lg or the areFiltersOpen value is set to false in localStorage. This will probably cause a flicker on mobile widths, though.
I'm not sure about the Playwright test: it will be difficult to test something that's happening during rendering and before the page is fully loaded.

I've moved this issue from the new header and footer milestone to UI state cookie milestone because the page load will be fixed there.


Improve ui

fixes #220
fixes #221
fixes #237

@Fanevanjanahary although i can see the issues these fixes are applied to, spotting the differences can be difficult, we could meet before merging this PR.


Run without terminal

Hi there, I'm using scrcpy for along time, but when I run scrcpy, I must open a terminal. May I skip it?

On Windows, run scrcpy-noconsole.vbs (on other platforms, just run with a & and close the terminal).

On Windows, run scrcpy-noconsole.vbs (on other platforms, just run with a & and close the terminal).

Thanks, it worked.
I'm using macos.
I have a command below, how can I auto close opening Terminal - which used for open scrcpy after it ran?
#! /bin/bash
/opt/homebrew/Cellar/scrcpy/1.24/bin/scrcpy & --disable-screensaver --stay-awake --turn-screen-off --always-on-top

# close terminal after scrcpy is closed
scrcpy; exit
# close terminal after scrcpy is closed successfully (stay open on error, to get time to read the messages for example)
scrcpy && exit
# run scrcpy and close the terminal immediately
scrcpy & exit

# close terminal after scrcpy is closed
scrcpy; exit
# close terminal after scrcpy is closed successfully (stay open on error, to get time to read the messages for example)
scrcpy && exit
# run scrcpy and close the terminal immediately
scrcpy & exit

Thanks for reply, but I tried there command, but Terminal screen still there. Are there any wrong?.

#! /bin/bash
/opt/homebrew/Cellar/scrcpy/1.24/bin/scrcpy --disable-screensaver --stay-awake --turn-screen-off --always-on-top & exit

It worked, Im missing config for allow close terminal screen after done. many thank

On zsh, use scrcpy &! exit.
https://stackoverflow.com/questions/19302913/exit-zsh-but-leave-running-jobs-open


Brainhack Vanderbilt dates changed

Hello admins, we moved the dates to January 20-21. Please make the adjustments on the global site. Thank you!

should be fixed now


Vanity identifies separate participants before/after log in

I.e. Vanity will show different alternatives to a user before/after logging in, if current_user returns nil before login and then the user object after login.
To fix this, instead of a use_vanity :current_user, we're using use_vanity :previous_vanity_cookie_or_current_user with
  # Default Vanity check's current_user with a fall back to a cookie. However,
  # with user sign in, it's possible to visit the site not-logged in, get
  # cookied and shown alternative A, then sign in and based on user.id, get
  # shown alternative B.
  # This implementation prefers an initial vanity cookie id over a new user.id
  # to avoid the flash of alternative B (FOAB). Of course, it falls back to default
  # Vanity cookie if all are nil.
  # The returned object must respond to `id` so a struct is used.
  def previous_vanity_cookie_or_current_user
    @vanity_user ||= Struct.new(:id)
    vanity_user = @vanity_user.new(cookies["vanity_id"]) if cookies["vanity_id"]
    vanity_user || current_user
  end

Phil - I'm thinking about this scenario..

logged out user gets vanity id
user goes through some process requiring account registration and logs in
user then goes to another computer and gets new vanity id
user logs in with the account created from before on other computer
we should merge participant records from the two separate vanity_ids into just one of those ids so we can track the behavior of this user across the two machines when they were logged in and logged out.\

Thoughts?

@davidguthu that scenario is approached by https://github.com/assaf/vanity/pull/49, if you wanted to review and see if you could bring it up to date, that'd be amazing!

Sounds good Phil - I'll review and make some suggestions this weekend I hope, latest early next week.


up or other commands could fail from partially completed init

Describe the bug
If you run an azd init and it partially fails, the process is incomplete, creating an app environment but not an azure.yaml file.  Thus subsequent operations fail with:
Error: no project exists; to create a new project, run `azd init`

To Reproduce
Create a new .NET Aspire app
In the app host add PostgresContainer (not yet supported)
azd init
observe that init will fail saying the resource type is not supported
remove the postgrescontainer from the app host
run azd up -- fails
run azd init -- says app env already created
Expected behavior
Some way to 're-init'?

Currently for such failure scenarios/partial state. We have to delete the .azure folder and azure.yaml. Re-run azd init from the root of your solution as a re-init strategy.
@weikanglim can we handle failure scenarios/state better. So subsequent azd init works fine?

azd should either:

write all files at the end of azd init
have a revert-changes routine to clean whatever is created if there is an error.

The current model is a bug, as it lets the project on invalid state.  This could be an easy fix, @weikanglim ?

@vhvb1989 A partial completion is not an invalid state. It is only unhandled in the current model. We've brought up reinitialization as an improvement for a while now. Making it idempotent may be worthwhile.
My initial thought is that an undo model that isn't based on atomic rollback transactions, but rather strict "undo-s" will continue to expand as the scope of the logic expands to "what should be undone?"

Here's my proposal:
The core azd init initialize an environment really means currently:

Create .azure/<env>
Make .azure/config.json point to it as a default environment

We update the code here: on a rerun, if there is a default environment, and the environment is valid, we can proceed.
In the "extended init flow" we have the following additional env modifications:

In template initialization, we allow for template metadata to set environment values/config. We update the code here to perform a diff on what changes would be made, with a confirmation prompt.
In Aspire's initialization, we prompt for exposed services. We update the code here to prompt with default values based on the stored exposed services.

Flags for azd init:
If --environment / -e is passed, --subscription and --location can also be passed to create an environment. It is however invalid to use --subscription and --location to set an existing environment.

@weikanglim , I am not a fan of supporting crashed states as valid and then making azd to check what's the current state for either continue or start from zero.
To me, all single-commands should be atomic-transactions.  Only composed-commands (like azd up) should allow intermediate states.
This is one of the reasons why azd prefers fail fast, over failing on the middle of a process and bringing doubts to customers about what to do next.
My preference would be run any validations we know could fail and fails as soon as possible. Never at the middle or after applying changes locally.

@vhvb1989 I disagree that this is a "crashed state" because there is no corruption. A user can stumble upon the same scenario by manually creating azure.yaml, running azd env new. A user could also choose to reinitialize from a template to obtain files and environment variables. This is a perfectly valid state to be in, azd should handle that. azd should support reinitialization as a concept, here we're starting down that path.

My preference would be run any validations we know could fail and fails as soon as possible. Never at the middle or after applying changes locally.

This sounds nice in theory, but in-practice, running the validation could incur computational costs near the operations being performed. Thus, you are hit with the operational cost twice.


Update header tests to check for termios.h's B0 macro.

Will need to be rebased / tested after NVIDIA/thrust#1548 is merged.

gpuCI: NVIDIA/thrust#1551


chore: adjust SDK integration

The type of this PR is: chore
Description
Integrates Adjust SDK following these docs:
https://help.adjust.com/en/article/get-started-ios-sdk
https://segment.com/docs/connections/destinations/catalog/adjust/
Note: We did not do the Android specific integration steps figuring that the react-native integration would cover but if we end up having problems with the SDK on Android that is probably a good place to start: https://segment.com/docs/connections/destinations/catalog/adjust/#android
PR Checklist (tick all before merging)

[x] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[x] I have tested my changes on iOS and Android.
[x] I have added tests for my changes, or my changes don't require testing, or I have included a link to a separate Jira ticket covering the tests.
[x] I have added a feature flag, or my changes don't require a feature flag. (How do I add one?)
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added an app state migration, or my changes do not require one. (What are migrations?)
[x] I have added a changelog entry below or my changes do not require one.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

Integrates Adjust SDK - Brian, Jon

😅 I guess adjust npm package is not what we are looking for, I will remove

This PR contains the following changes:

Dev changes (Integrates Adjust SDK - Brian, Jon)

  Generated by :no_entry_sign: dangerJS against 225367ced25ef5b1707eb864d741c6c5c9e30ab7


PromQL: Fix params for series expansion

One of the refactorings in #6590 causes the parameters for series expansion in the engine to be set incorrectly.
This might be (part of) the cause for #6771.
Signed-off-by: Tobias Guggenmos<EMAIL_ADDRESS>

@slrtbtfs can you make this PR over the release-1.16 branch ? so we can run prombench

Yes, I can redo it.

@roidelapluie Where is that release branch? I somehow can't find it.


Wrong completion for simple element names in Razor editor

This issue has been moved from a ticket on Developer Community.

[severity:It's more difficult to complete my work]

In the first example, the Component is used as a complex element. Changing its name provides proper completion, because it includes other Components.
However, in the second example, when a Component is used as a simple element, wrong completion is displayed, because it only lists basic HTML tag names, and doesn't include Components

Original Comments
Feedback Bot on 1/3/2023, 05:52 PM:
(private comment, text removed)
Wenwen Fan [MSFT] on 1/9/2023, 11:39 PM:
(private comment, text removed)
Juhász Péter on 1/10/2023, 00:18 AM:
(private comment, text removed)
Juhász Péter on 1/10/2023, 00:25 AM:
(private comment, text removed)
Wenwen Fan [MSFT] on 1/9/2023, 11:40 PM:
(private comment, text removed)
Wenwen Fan [MSFT] on 1/16/2023, 01:35 AM:
(private comment, text removed)

Original Solutions
(no solutions)

Thanks so much for the effort, especially on a Sunday! :)

Thanks so much for the effort, especially on a Sunday! :)

Naa... @davidwengier is in Australia, so it was his Monday! :smile:

It still counts! 🎉 I was really happy when I saw yesterday that finally somebody is working on an issue I reported.
@DustinCampbell I work with large .NET Blazor projects every day (25k lines in 200 .razor files + 50k lines in 1k .cs files, 35k lines in 300 blazor files + 380k lines in 650 .cs files, and some medium ones...), and reported on VS Community at least 10 similar issues (related to the Razor Editor) which makes everyday work sometimes quite difficult, each with an example and even a GIF recorded demonstrating the issue like in this case. Although I could not provide a memory snapshot, or upload the whole source code (because the company policy doesn't allow me to do that), almost all of them were closed immediately with "Not Enough Info", which is very frustrating.
Do you think it worth reposting them here on GitHub, so maybe they get better attention from the devs like @davidwengier directly?
(sorry for the off-topic)

Actually this was done on a Sunday 😛
@Peter-Juhasz apologies for the frustrating experience with VS Feedback. In theory it shouldn't matter whether you log issues here or VS Feedback. In theory VS Feedback can be better, because there are many nuanced technical details that dictate which team is responsible for which issue, which you can not be expected to know, and VS Feedback allows us to move issues between teams more easily. As you've found though, sometimes the triage process on VS Feedback can be a little harsh and issues can be closed. There is no guarantee the same thing wouldn't happen if you log an issue here, but you're welcome to try. The worst thing that will happen is we'll have to say "Sorry, that is a bug owned by a different team, please log a VS Feedback issue for it".
For the record though, this issue was moved from VS Feedback to here by us, as we did our weekly triage of issues, so we saw it before it was on GitHub, I just happened to have a lazy Sunday with nothing else to do.

@Peter-Juhasz I had a quick look through the VS feedback issues you files, and the ones that were marked as "Needs more info" were closed automatically because no more info was supplied. I understand that you can't necessarily provide any, but unfortunately there is no way to stop the bot from closing the issue. Next time it happens, if you just comment "I am unable to provide more info due to company rules" or similar, that will prevent the bot from closing the issue, and put the onus back on the team.


fix: relax dask version requirement and use a better check for Task

@martindurant we got pretty... erm direct... feedback that backwards compatibility would be appreciated.
Also the current check was not working with very recent, but older, dask that has Task but it isn't used in blockwise.

We are accepting more future work by allowing for earlier dask. That must be recognised.

It's less future work w.r.t. people managing clusters and images. There are all sorts of weird regressions from dask version to dask version, their pinning times are much longer than ours.

@martindurant changing things so that we avoid touching the private module _task_spec and grab Task/TaskRef/GraphNode from blockwise. The latter is far less likely to disappear or move, and the naming of the classes is probably pretty stable.

any further commentary on this one?


perf: round encoder buffer size to nearest sizeclasses

Previously on PR #415, we updated encoder's buffer size to 1537, however we found that this size can be rounded into nearest golang's sizeclasses: https://go.dev/src/runtime/sizeclasses.go, which is 1536.

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

Project coverage is 100.00%. Comparing base (fd72df2) to head (bfe47cf).

Additional details and impacted files
@@            Coverage Diff            @@
##            master      #416   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           41        41
  Lines         3695      3695
=========================================
  Hits          3695      3695

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


Fixed potentially confusing variable switch in Vignette

The old vignette had switched variables, so if someone wanted to copy and paste this code to see it work it would have failed. I updated.

The checks are failing due to an unfortunately timed bug with Travis CI R support btw. It's fixed by this
https://github.com/travis-ci/travis-build/pull/1830