[Bug]: Timeout with 403 on bucket creation(python)

Affected sdk: Python(didn't test other)
Version: latest(v0.99.1)
Not yandex problems tested with yc cli on same credentials currently cant test with terraform but will assume it works fine because i cant find any issues about something similar from same release in official repo.
Erroring regardless bucket name.

sa = yandex.IamServiceAccount('sa')

role = yandex.IamServiceAccountIamMember(
    "sa-editor",
    role="storage.editor",
    service_account_id=sa.id,
    member=sa.id.apply(lambda x: f"serviceAccount:{x}")
)

key = yandex.IamServiceAccountStaticAccessKey(
    "sa-editor-key",
    service_account_id=sa.id,
    opts=pulumi.ResourceOptions(
        depends_on=[role]
    )
)

b = yandex.StorageBucket(
    "s3.energostalin.ru",
    acl="public-read",
    bucket="s3.energostalin.ru",
    website=yandex.StorageBucketWebsiteArgs(
        index_document="idnex.html",
        error_document="idnex.html",
    ),
    access_key=key.access_key,
    secret_key=key.secret_key,
    max_size=1e6,
    opts=pulumi.ResourceOptions(
        custom_timeouts=pulumi.CustomTimeouts(create="1m", update="1m", delete="1m")
    )
)

Just to let people know about issue.

Like always documentation reading problem here's working config.
folder_id = yandex.get_client_config().folder_id

sa = yandex.IamServiceAccount(
    'sa',
    folder_id=folder_id
)

role = yandex.ResourcemanagerFolderIamMember(
    "sa-editor",
    role="storage.editor",
    sleep_after=10,
    folder_id=folder_id,
    member=sa.id.apply(lambda x: f"serviceAccount:{x}")
)

key = yandex.IamServiceAccountStaticAccessKey(
    "sa-editor-key",
    service_account_id=sa.id,
    opts=pulumi.ResourceOptions(
        depends_on=[role],
    )
)

b = yandex.StorageBucket(
    "s3.energostalin.ru",
    bucket="s3.energostalin.ru",
    acl="public-read",
    website=yandex.StorageBucketWebsiteArgs(
        index_document="index.html",
        error_document="index.html",
    ),
    access_key=key.access_key,
    secret_key=key.secret_key,
    max_size=1e6
)

Explicit folder_id config required also double check permission issuing right next time.

Anyway thanks for up to date provider. If you ever need help with maintaining reach me out. I'm interested in rewriting my infrastructure on pulumi from terraform. Because yep it's declarative but hardly reusable and excessively large when it comes to configuration size. Also putting questionable restrictions and absolutely cant do anything really useful out of the box. Not mentioning their new license which making it unusable in my case. I'd better have problems with pulumi and use more convenient configuration language than would write on HCL ever again.


Cleanup tests

Codecov Report

Merging #14 (01672d9) into main (d72135e) will increase coverage by 0.11%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main      #14      +/-   ##
==========================================
+ Coverage   92.15%   92.26%   +0.11%
==========================================
  Files          81       81
  Lines        3823     3762      -61
==========================================
- Hits         3523     3471      -52
+ Misses        300      291       -9

Impacted Files
Coverage Δ

src/orientation/quaternion.jl
82.92% <0.00%> (-5.41%)
:arrow_down:

src/orientation/mapping.jl
36.36% <0.00%> (-5.31%)
:arrow_down:

src/joints/rotational/input.jl
42.10% <0.00%> (-1.49%)
:arrow_down:

src/joints/joint.jl
88.88% <0.00%> (-0.51%)
:arrow_down:

src/contacts/impact.jl
86.20% <0.00%> (-0.46%)
:arrow_down:

src/bodies/set.jl
94.54% <0.00%> (-0.37%)
:arrow_down:

src/joints/rotational/springs.jl
97.29% <0.00%> (-0.14%)
:arrow_down:

src/utilities/methods.jl
96.66% <0.00%> (-0.11%)
:arrow_down:

src/joints/prototypes.jl
96.15% <0.00%> (-0.08%)
:arrow_down:

src/bodies/state.jl
100.00% <0.00%> (ø)

... and 15 more

Continue to review full report at Codecov.

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


Add test for binder/apt.txt detection

Add a test that makes sure #140 keeps working in the future.
The Beyonce strategy: 'Cause if you liked it, then you should have put a test on it  ;)

Done: #145

Thank you and closing :)


Quickly group multiple files into a new folder

Description of the new feature / enhancement

The user selects one or more files
Right click for the context menu
A select "New folder" option would appear
Rename folder
Files are moved into newly created folder

Scenario when this would be used?
More efficient file management. Instead of having to create the folder first, then select the files, cut, and paste into the folder, the user can select the files and create and move the files quicker.
Supporting information
macOS has this feature built into Finder.

/dup #3569


copyTextFrom

Hello!
Tell me how the command copyTextFrom works correctly.
I call the command by passing the element ID into it, but when inserting it into a field, it inserts not the text, but the name of the element ID.
The problem is either in the correct ID for the elements or I’m doing something wrong. Help me figure it out
Example:
copyTextFrom:
id: MainFromEditorialText

This issue belongs to the Maestro repo, not here.


Feature/test write box

Add test code for all leaves in box tree
Remove entry_count that is duplicated with entries.len()

Thank you! 👍


Added example of how to create prefabs.

Objective

Creating prefabs in Bevy using scenes is largely undocumented, with the biggest issue being the inability to capture the spawned scene.
This inability makes it difficult to modify the prefab after spawn, in order to do things such as parent to other entities, adjust values, or add components.
The use of Dynamic Scenes is thus greatly limited, and until the involved systems are updated, Bevy needs an easier and more stable method of creating prefabs.

Solution

Using code from  bevy/crates/bevy_scene/src/dynamic_scene.rs, I have created a prefab factory that takes a new Entity and a Handle and inserts components from the loaded scene into the entity.
This PrefabFactory is simply a HashMap<Entity, Handle> that is placed into a Resource.
An exclusive system then checks to see if the handle is loaded, then applies the components directly to entity.
Components can be assigned to the Entity upon spawn, and will remain after the scene components are applied, assuming that the DynamicScene did not already have the component.

Limitations

Component data from the prefab won't be available immediately; the PrefabFactory systems run in the CoreStage::Last stage, and the actual scene must load before the scene is applied.
Sub-entities are not supported currently, as the factory only applies the first entity listed in the scene. It may be possible to spawn multiple new entities at a time, but it would be difficult to capture them. It is likely that nested scene support is necessary before prefab sub-entities are ergonomic.

Component data from the prefab won't be available immediately; the PrefabFactory systems run in the CoreStage::Last stage, and the actual scene must load before the scene is applied.
Sub-entities are not supported currently, as the factory only applies the first entity listed in the scene. It may be possible to spawn multiple new entities at a time, but it would be difficult to capture them. It is likely that nested scene support is necessary before prefab sub-entities are ergonomic.

Thanks for listing out these limitations; they're very useful to have documented.
Can you add them to the example? The PR description will not be very discoverable for future users.

Thank you for raising this issue :-)

Creating prefabs in Bevy using scenes is largely undocumented, with the biggest issue being the inability to capture the spawned scene.
This inability makes it difficult to modify the prefab after spawn, in order to do things such as parent to other entities, adjust values, or add components.

I agree with the need for better documentation, but there are ways to do what you described. They are shown in the update_gltf_scene example.
Here is how to spawn a scene as a child of another entity: https://github.com/bevyengine/bevy/blob/94db0176fecfac7e7e9763f2dc7458a54c105886/examples/3d/update_gltf_scene.rs#L38-L47
Here is how to modify the spawned entities: https://github.com/bevyengine/bevy/blob/94db0176fecfac7e7e9763f2dc7458a54c105886/examples/3d/update_gltf_scene.rs#L55-L74
Not shown in any example to my knowledge. but you can also modify the scene's inner world after it's loaded, before spawning it (possibly by listening to the asset creation event).
I do think we should improve the documentation, and make an example of a higher abstraction to easily work with scenes (fixing the limitations of the one proposed). I'm happy to answer any questions on the subject!

The issue with Scenes (versus DynamicScenes) is that there is no way to serialize them. This is not for 3d models, but more for data entities. I've been using this to generate items and stat entities for my RPG.

The issue with Scenes (versus DynamicScenes) is that there is no way to serialize them.

You should be able to use DynamicScene::from_scene to convert scenes into dynamic scenes and then serialize.

Can you convert it back though? There's nothing in DynamicScene to convert it back in order to spawn it as a child or instance. I've tried spawning the DynamicScene into a new world to make a Scene but it panics due to there being no TypeRegistry in the new world.

You're right, we should probably improve the API for DynamicScene to have parity with Scene, including commands.

I've tried spawning the DynamicScene into a new world to make a Scene but it panics due to there being no TypeRegistry in the new world.

I think you can clone the app's type registry and insert it in the scene's world, then use DynamicScene::write_to_world() (with an empty entity map).

Updated to add some features. I still think this method has some merit, since it returns an entity that can be used and/or stored immediately.

@Semihazah This looking good :) Can you click "Resolve" on the comments that you've addressed so reviewers can see what's outstanding?

I feel that if you fleshed out of few parts, this could be a useful third party plugin rather than an example:

using another custom file extension for prefab, with a custom loader that would still call the scene loader
adding checks on the fact that there is only one entity when writing the scene
adding a prefab writer system that would use the IOTaskPool to write files

* adding checks on the fact that there is only one entity when writing the scene

That's no longer necessary, you can have multiple entities in the scene and they'll all be loaded and mapped.

That's no longer necessary, you can have multiple entities in the scene and they'll all be loaded and mapped.

oh right I was confused with this limitation:
 Only components from the FIRST entity listed in the file will be inserted into the provided entity.
but on re-read it's clearer
Then I agree that we should first bring parity to DynamicScene from Scene which would make this example a lot simpler

This PR adds a new example. Adding module and item level doc comments, as described in:

#3951 and
#4438,

would be really useful to those who will browse examples.

The example description should go to the top, with //! comments. Documenting components where appropriate is also good.

Q: What's a prefab?
This PR adds the concept of a "prefab" but never defines what it means or why you would want to use it. I know the term is used in Unity, but I've never used Unity.

this looks too complex to be an example, and too limited to be merged in engine


Update naming conventions

Bit of an overstuffed PR. This PR introduces some luau code support so that I can publish this to wally in the future.


cast_assoc won't persist updated sort order as specified in the docs

Elixir version
1.14.4
Database and Version
PostgreSQL 15.2 with PostGIS 3.3.2
Ecto Versions
3.10.0
Database Adapter and Versions (postgrex, myxql, etc)
postgrex
Current behavior

call Changeset.cast_asoc with sort_param and drop_param.
call a custom function to update the sort, ending with a Changeset.put_change

has_many(:addresses, Address,
  on_replace: :delete
)

changeset
|> cast_assoc(changeset, :addresses,
  sort_param: :addresses_sort,
  drop_param: :addresses_drop)
|> copy_children_positions()

defp copy_children_positions(changeset) do
  if children = Ecto.Changeset.get_change(changeset, :children) do
    children
    |> Enum.with_index(fn child, index ->
      Ecto.Changeset.put_change(child, :position, index)
    end)
    |> then(&Ecto.Changeset.put_change(changeset, :children, &1))
  else
    changeset
  end
end

Expected behavior
The changeset should successfully change with the updated addresses. However it fails with:
** (RuntimeError) cannot replace related %Address{__meta__: #Ecto.Schema.Metadata<:loaded, "address">,
...
This typically happens when you are calling put_assoc/put_embed with the results of a previous
put_assoc/put_embed/cast_assoc/cast_embed operation, which is not supported. You must call
such operations only once per embed/assoc, in order for Ecto to track changes efficiently
    (ecto 3.10.0) lib/ecto/changeset/relation.ex:430: Ecto.Changeset.Relation.check_action!/2
    (ecto 3.10.0) lib/ecto/changeset/relation.ex:180: Ecto.Changeset.Relation.do_change/4
    (ecto 3.10.0) lib/ecto/changeset/relation.ex:347: Ecto.Changeset.Relation.map_changes/9
    (ecto 3.10.0) lib/ecto/changeset/relation.ex:156: Ecto.Changeset.Relation.change/3
    (ecto 3.10.0) lib/ecto/changeset.ex:1729: Ecto.Changeset.put_change/7
    (ecto 3.10.0) lib/ecto/changeset.ex:1720: Ecto.Changeset.put_change/3

Thank you. We definitely need to fix the docs to not mention this. I also think we should support :with to receive 3 arguments. In such cases, the third argument is going to be the index in the collection, so we can store it in the database without an additional pass.

Streamlining the update into the single cast_assoc call would be a great enhancement.

@josevalim Is there any more detail around of why this limitation is in place? It would be nice if this specific usecase can be solved, but on the other hand that means only this specific usecase is covered.

@LostKobrakai because it can be complex, because we had the original data, the modified data (cast_assoc), and now new data (put_assoc) and it can be complex and ambiguous to what the new data applies to. For example, what happens if the new data is missing some changesets, how can we even generate the proper "patch" to delete it from the database.
The only case it is easy is if we assume the new data are all changesets which precisely match the changesets we had before. So I would prefer to allow the index to be given to :with and avoid another pass. :)

+1 for adding the index on :with, but how, exactly? Do we decide the implementation based on the arity? I can write a PR.

Exactly. Just check the arity. I already deprecated the MFA version in main. :)

  if children = Ecto.Changeset.get_change(changeset, :children) do
    children
    |> Enum.with_index(fn child, index ->

One issue I see with this is that children will include replaced rows (with action: :replace) so there may be gaps in the resulting index sequence. Those rows are also what makes put_change complain:
https://github.com/elixir-ecto/ecto/blob/f3311eeb1d49b7dad129fe5a84d290b196403b76/lib/ecto/changeset/relation.ex#L429-L434
Would something like skip_replaced from phoenix-ecto help with this?

Yeah, I noticed that gap too while troubleshooting this. Ideally the indexes passed to a new :with would exclude the items that are queued for delete.


Ensure SoftBody3D does not use compressed mesh format.

Fixes: https://github.com/godotengine/godot/issues/84094
When using the compressed mesh format (default for imported meshes when possible) the SoftBody3D ended up still updating its vertex attributes as if the attributes were uncompressed leading to the mesh containing bogus data.
The solution is to force it to use an uncompressed format since we are creating a new ArrayMesh internally anyway. There is no need to copy the compression flag.

Thanks!


TF GRID DEMO - WIKI DEPLOY ISSUES

[x]   wiki is failed to deploy, and but it is listed at ‘my workload’ ....? sashaastiadi-wiki-sasha.tfgw-testnet-01.3x0.me

[x] On my workload, when wiki domain is clicked, it should open a new tab instead of in the same tab.

[x] users get reminded on unsafe connection, can we resolve / remove this?

Domain doesn’t work/ wiki is not displayed successfully

Where can I access my wiki repo?

wiki is failed to deploy, and but it is listed at ‘my workload’ ....? sashaastiadi-wiki-sasha.tfgw-testnet-01.3x0.me

fixed already (TODO: link where)

On my workload, when wiki domain is clicked, it should open a new tab instead of in the same tab.

@abom please link ur commit id

users get reminded on unsafe connection, can we resolve / remove this?
No, staging env used will use self signed certs, and we won't consume llet's encrypt certs for staging envs.

Domain doesn’t work/ wiki is not displayed successfully
validation been done on the urls to be in the form of the https/git URLs

Where can I access my wiki repo?
Don't understand what you mean here.

removed the first item to be able to verify that issue alone

verified

URL is opened on a new tab
the token amount, message is shown on scan QR


Named arguments not extraction from array

Slicing out of an array is super hard to read, and less efficient than just having named arguments and choosing how to use them based on the type. I'd rather we kept the arguments named.
As an aside, an optional anonymous boolean third argument is a bad move for extensibility later on. Much better to take an options object imo, or just have a stopProp function that composes into the proxy.

Yeah, I struggled with parsing args myself when first looking at Flight code. I've no idea why I thought it was a good idea to copy that style. Will fix.
Will add options arg for stopProp and preventDefault.

When I went back to this, I think I see better what I was thinking. I don't want to parse all possible and optional event args (node, type, callback), because I can use base.on in flight core for that. I only need to check if the callback (last arg) is a string, and if so make the proxy function.

I think 74ba71c clarifies the intent here, and the comment speaks to exactly what the purpose is.


Configuration parsing sometimes attempts parsing a value of the wrong type

[X] Defect (LOW)
[ ] Feature Request or Change Proposal

Defects
If you have a simple cluster config like this:
# This file was generated 2017-05-17 17:03:40.501690691 -0500 CDT
listen: xxx.local:10571
http: xxx.local:15571

tls {
	cert_file: "/Users/xxx/test_certs/xxx.cert"
	key_file: "/Users/xxx/test_certs/xxx.key"
	verify: false
	timeout: 2.0
}

cluster {
	listen: xxx.local:13071

	authorization {
	 	user: cluster_1
	 	password: 5ADISY_bfhkprstuvv
	 	timeout: 2.0
	}

	routes = [

		nats-route://cluster_1:5ADISY_bfhkprstuvv@xxx.local:12628

		nats-route://cluster_1:5ADISY_bfhkprstuvv@xxx.local:12885

	]
}
max_connections: 10
max_payload: 65536

include ./auth.conf
include ./messagerate.conf

The cluster config for the password will fail because the lexer attempts to parse as an integer. Gnatsd will report: Parse error on line 20: 'Expected a map value terminator "," or a map terminator "}", but got 'A' instead.'.
The workaround is to enclose the password value in quotes. Since the password field likely should be interpreted as a string this shouldn't be necessary. Alternatively for safety we should be indicating that string values should be quoted (specially if the configuration is machine generated).
Versions of gnatsd and affected client libraries used:
found on 0.9.6
OS/Container environment:
OS X
Steps or code to reproduce the issue:
Use config above
Expected result:
Parse value as string or provide a better error message indicating that the value was expected as a number.

You can always put a string in single or double quotes to force string parsing.

Yes this is the workaround.

In Windows, I had the same error. I escaped all double quotes with . And then it worked. The only problem for me was to transfer the file via SSH and ECHOing it into a conf file. WHich I had to map using --volume option.

@mmanna-sapfgl this is fixed in master already and part of the next release


iOS PCL project using AdvancedTimer will not run on iPhone unless Debugging is enabled

I have an app which uses a PCL and 2 platform specific projects for iOS and Android and makes use of the AdvancedTimers.
The android app works fine, but the iOS app will only work on a device with debugging enabled in the iOS Build options. If I comment out all the code associated with the AdvancedTimers then the app will work again.

You are right. It is fine with emulator, but it crashes on a device on release mode.
I will try to get crash logs from the device and symbolicate to what's wrong with it.
I'll let you know.

I am facing the same issue. I released the app for client testing & they were not even able to go to the second screen where timer was used. The instance of the timer is always null in release mode.

I'm sorry I couldn't find time to fix that.
There is something wrong with nuget package.
You can fork and directly use code from github to fix that. Imported code just works fine on release mode.

No Sorry. I don't think this is nuget issue here. I forked your code, build locally in release mode & hooked the DLL thus generated in my code. All works fine as long as you are running the app in debug mode, it crashes the app in release mode. Same results.

Try by directly adding code to your project instead of compiling and adding DLL.
I tried by copying code into a sample project and it worked fine with release mode.

I implemented your code in my app (copied the interface & its implementation for IOS) & so far it seems like its working fine. Thanks

Ran into same issue, implementing code directly seems to be working.

Is this still an issue? Or has it been fixed?

It was fixed on the project but I am not sure if the fix is pushed here.

I am using NuGet version <IP_ADDRESS>. Is it fix in there?

This issue is still happening for me.  Integrating the code into my project didn't help. However, setting the IoS Build to Debugging Enabled didn't help. The downside is that it doubled the size of my IPA file.

For some reason, advanced timer is not working for me on either iOS or Android. It works in one PCL class but not in another. Seems odd.

@adrianknight89 you maybe experiencing the same problem as me, each time you call DependencyService.Get(); you get the same object back, so the first time it works great, however if you want to use it again elsewhere its already bound to the callback when you used it the first time you called it, so appears to not work.
Looking into DependencyService it looks like its suited to more singleton model, where there is only a single instance returned, however timers you would expect to be able to create multiple objects.

Actually don't have to use DependencyService at all can use any IOC container
e.g. using Autofac which xamarin.forms uses,
So on iOS/Android side call following to register :-
builder.RegisterType ().As ();
then on PCL side, can you following code which will create a new object each time
timer = ServiceLocator.Current.GetInstance();

I'm not sure my issue is the same as that above.  I'm not even able to
call the timer once before some kind of exception occurs (which
unfortunately I can't trap). All I see is that when stepping through
code and starting the timer, it is as if the current thread is
terminated and execution appears elsewhere in my app.  The timer
doesn't appear to start either.
Although setting the iOS build with the debug option does work for me,
my IPA size has pretty much doubled in size.
On 23/02/2016, mannyvw<EMAIL_ADDRESS>wrote:

Actually don't have to use DependencyService at all can use any IOC
container
e.g. using Autofac which xamarin.forms uses,
So on iOS/Android side call following to register :-
builder.RegisterType ().As ();
then on PCL side, can you following code which will create a new object each
time
timer = ServiceLocator.Current.GetInstance();

Reply to this email directly or view it on GitHub:
https://github.com/ufuf/AdvancedTimer/issues/5#issuecomment-187753052

@mannyvw You're correct that DependencyService always returns the same instance. However, I figured there is a way to return a new instance each time. Try:
timer = DependencyService.Get<IAdvancedTimer>(DependencyFetchTarget.NewInstance);

I've been having the same issue with release mode, and a different issue where the timer would re-init, so it only worked the first time.
@rlingineni suggestion of integrating the code directly, fixed my issue with release mode.
@adrianknight89 suggest with the new instance, fixed the issue of the timer not re-initializing.
Thanks guys!

Can confirm this is still an issue. Works fine until you try and use it in release mode on a device. Will try integrating the code directly. Thanks for the implementation!

We ran in to this exact issue and have no resolution.
Will have to move away from AdvancedTimer if it can't be resolved.
Tested on several iOS devices, running >= 8.1

Xamarin.Forms <IP_ADDRESS>29
AdvancedTimer <IP_ADDRESS>

Only way i got it to work was include the code directly in project rather than use nuget package.
N

Also running into this. Took me forever to figure out the problem but thank you all for letting me know of a workaround.

@TravyDale what did you do to fix the problem? I tried building from source, but now I am getting this error....

MTOUCH: Error MT2002: Failed to resolve "System.Void AdvancedTimer.Forms.Plugin.Abstractions.IAdvancedTimer::initTimer(System.Int32,System.EventHandler,System.Boolean)" reference from "AdvancedTimer.Forms.Plugin.Abstractions, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null" (MT2002)

Is there another timer available for Xamarin.Forms that allows of cancelling the timer before it's Elapsed event? That's the only reason I'm using this library.

@eclipsed4utoo  lol sorry for the delay in response. I see your EDIT and that is what I did and it works for me now too.

Thanks all for posting the solution here, removing the nuget package and including the code directly into my project solved my issue. App successfully submitted to the app store :)

Never thought that such a popular nuget package can have issue like this. I wasted my whole day on this issue. But thanks everyone for posting the solution. It worked for me after integrating the source code directly.

Adding the untouched projects to the solution didn't worked either, You have to include the files directly in your current app. Sadly I wasted 2 hours with this looking at clueless ios logs =( anyway, it is what it is ... thanks guys

An alternative solution to including the code directly into the iOS project is to simply include a dummy use of the AdvancedTimerImplementation class, so the linker does not blow away this class.  For example, include the following class in the iOS project.
public class AdvancedTimerBootstrap
{
	public AdvancedTimerBootstrap()
	{
		new AdvancedTimerImplementation();
	}
}

If anyone still maintains this project, adding the preserve attribute on the platform implementations should fix DLL issue.
[Preserve(AllMembers = true)]
public class AdvancedTimerImplementation : IAdvancedTimer {

Is this issue still persist with nuget package ?
still need to add the files into the project ?

@shrimantNikate Yes issue still remains with the nuget package.

@ufuf I have implemented nuget package in my ongoing project, but seems working correctly. Can you pls let me know how can i reproduce this issue ?

@shrimantNikate I don't use this library anymore but others state that the app is working fine on debug mode but not working on release mode with the nuget package.

@ErnieScott Your solution worked for me. I just added the
new AdvancedTimerImplementation();
right after I registered the dependency.
Thanks for the suggestion!

I just uploaded https://www.nuget.org/packages/info.dmwilson.AdvancedTimer.Forms.Plugin/1.0.2-alpha5 which appears to resolve this issue. I just used TestFlight to test a Release build of my iOS app, and the crash did not happen anymore.
Instead of using attributes to register the implementations with the Xamarin.Forms DependencyService, I just call DependencyService.Register() from the AdvancedTimerImplementation.Init() static method. If you try the updated NuGet package, please let me know how it goes.
FYI, my fork is not updated with these code changes yet. I'll try to get that done tomorrow.


The badge does not work on latest Samsung

Plugin version:

isSupported() method returns false. When digging into it more, I have found the shortcutBadger this plugin uses is not maintained anymore. And there is still this open issue https://github.com/leolin310148/ShortcutBadger/issues/266. It seems Android has come up with its own supported badge/notification since android 8. I wonder how everyone else is using this plugin?
Platform(s):

latest samsung
latest pixel
Current behavior:

isSupported return false
Expected behavior:

isSupported return true
Steps to reproduce:

Related code:

insert short code snippets here

Other information:

Capacitor doctor:

insert the output from `npx cap doctor` here

Hi @happymago,
thank you for your request.
I'll look at using Android's own badge setting interface to replace or extend ShortcutBadger once I have a little more time.
I will get back to you.

Hi @robingenz,
I use your plugin on IOS, where it works excellently! However, I am also migrating to Android and unfortunately here it doesn't work. I have tried to run both my app as well as the Capacitor plugin demo on an upgraded Samsung Galaxy S4 running LineageOS and a Samsung Galaxy S10e running Android 11. It seems that the badge settings are picked up properly inside the plugin, the problem is that the actual badge never appears on the screen. As happymago commented above, the problem seems to be inside ShortcutBadger. I can add more info if needed but if you plan to replace ShortcutBadger with Android's own interface maybe that isn't necessary. Anyway, your efforts are appreciated :)

So I've been looking into this.
First of all: I have two Android devices to test here: A Samsung Galaxy S4 (Android 5) and a OnePlus 7T (Android 11).
On the Samsung Galaxy S4 this plugin works, because this Samsung OS version is supported by ShortcutBadger. On the OnePlus 7T, the plugin does not work.
Android supports so-called "Notification Badges" since Android 8.0 (see here). These appear when an app has an active notification. I could not find any other way to display badges. If I have missed a possibility and someone has experience with it, I would be very grateful for any advice.
Since these badges are thus dependent on the notifications of an app and Capacitor already offers a very good official plugin for this, I recommend using the Local Notification plugin if ShortcutBadger does not support the device.
Here is some sample code:
import { LocalNotifications } from '@capacitor/local-notifications';
import { Badge } from '@robingenz/capacitor-badge';

const set = async (count: number) => {
  const { isSupported } = await Badge.isSupported();
    if (isSupported) {
      await Badge.set({ count });
    } else {
      await LocalNotifications.schedule({
        notifications: [
          {
            id: 1,
            title: 'My Title',
            body: 'My Body',
          },
        ],
      });
    }
};

From my point of view, it is outside the scope of this plugin to support local notifications on Android. App icon badges are simply not a standalone feature on Android but a side effect of notifications.
I hope you can understand my point of view. I will turn this issue into a discussion so that we can gather other opinions and suggestions there as well.


Increasing number of go routines when postgresql cannot be accessed

What's wrong?
I have noticed that at one of our production servers there way too many go routines reported in comparison to other instances.

When I checked the logs I found that there are issues with connectin to the PostgreSQL database using prometheus.exporter.postgres.
I have reproduced the issue with an Alloy instance that has configured a postgres exporter to a database that it cannot connect to (pg_hba rejected or simply the db doesn't exist).

Steps to reproduce
Create a prometheus.exporter.postgres component and configure the URL to a non-existing postgresql URL.
System information
No response
Software version
Grafana Alloy v.1.4.2
Configuration
logging {
    level  = "info"
    format = "logfmt"
}

prometheus.exporter.postgres "POSTGRESQL_METRICS" {
    data_source_names = ["postgresql://postgres:postgres@postgres:5432/postgres?sslmode=disable"]
    autodiscovery {
        enabled = true
    }
}

prometheus.scrape "SCRAPE_POSTGRESQL_METRICS" {
    targets    = prometheus.exporter.postgres.POSTGRESQL_METRICS.targets
    forward_to = [prometheus.remote_write.PROMETHEUS_REMOTE_WRITE.receiver]
    // increased the number of intervals to reproduce the issue faster.
    scrape_interval = "5s"
    scrape_timeout="4s"
}

prometheus.exporter.self "SELF_REPORT" {}

prometheus.scrape "SELF_SCRAPER" {
    targets    = prometheus.exporter.self.SELF_REPORT.targets
    forward_to = [prometheus.remote_write.PROMETHEUS_REMOTE_WRITE.receiver]
    scrape_interval = "15s"
}

prometheus.remote_write "PROMETHEUS_REMOTE_WRITE" {
    endpoint {
        url = format("http://%s:%s/api/v1/push", env("MIMIR_URL"), env("MIMIR_PORT"))
    }
}

Logs
ts=2024-10-18T15:36:51.273854616Z level=info msg="Established new database connection" component_path=/ component_id=prometheus.exporter.postgres.POSTGRESQL_METRICS fingerprint=postgres:5432
ts=2024-10-18T15:36:51.348885966Z level=error msg="Error opening connection to database" component_path=/ component_id=prometheus.exporter.postgres.POSTGRESQL_METRICS err="error querying postgresql version: dial tcp: lookup postgres on <IP_ADDRESS>:53: server misbehaving"
ts=2024-10-18T15:36:52.34972657Z level=error msg="Error opening connection to database" component_path=/ component_id=prometheus.exporter.postgres.POSTGRESQL_METRICS dsn="postgresql://postgres:PASSWORD_REMOVED@postgres:5432/postgres?sslmode=disable" err="dial tcp: lookup postgres on <IP_ADDRESS>:53: server misbehaving"

This appears to be an issue that was resolved in newer releases of the postgres prometheus exporter. Will take a look at updating the exporter version that is bundled with Alloy. Thanks for the detailed bug report!

After some testing, it appears that while other connection leaks have been fixed, this is still an issue in v0.15.0 of the prometheus exporter. Looking into fixing the issue upstream.

@KaczDev this should be resolved -- however as we've cut the release candidate for the current release, this will likely not hit until v1.6 in December.

Thanks a lot, @dehaansa!


Added tighter dependency on Highline as their later release broke things

rake db:bootstrap would fail using e.g. highline 1.6.5 with the error:
undefined method parse' for String:Class /Library/Ruby/Gems/1.8/gems/highline-1.6.5/lib/highline/question.rb:329:in convert'
/Library/Ruby/Gems/1.8/gems/highline-1.6.5/lib/highline.rb:253:in ask' …/radiant/lib/radiant/setup.rb:92:in prompt_for_admin_name'
…/radiant/lib/radiant/setup.rb:29:in create_admin_user' …/radiant/lib/radiant/setup.rb:19:in bootstrap'
…/radiant/lib/radiant/setup.rb:10:in `bootstrap'
…/radiant/lib/tasks/database.rake:43
[…]

thanks. i was just this minute hitting the same issue.


Corrupt display of TIFF file

I have an example TIFF file which displays perfectly, except at the very bottom of the image where VLIV has inserted a black stripe. The same image displayed in IrfanView is how I expect, without the black stripe.

(VLIV on the left, IrfanView underneath on the right)

Do you have a link to the TIFF image ?
Is it the only one with a bad display ?
And what is the VLIV version ?

VLIV is 2.5.4 (latest).
TIFF is here: https://we.tl/t-LdDBgvXtYK
I haven't tried any others yet.

I reproduce the issue, working on it...

Vliv 2.5.5 fixes the issue, please test

v2.5.5 does display the image properly, thank you for the quick fix :-)
(I don't see any source code changes in the repo though, apart from the version number!).
I also like the zoom through pyramids feature, very useful. I will have to try it on a cloud-optimised GeoTIFF next.

The fix is in the plugins repo : https://github.com/delhoume/vlivplugins.
I might have to make different versions and releases for Vliv and its plugins


Create justfile

Repo could use a justfile to automate some of the non-CI/CD bits.
Have a decent example that covers the bulk of Docker functionality here.
Could be extended to do other things that would be useful (cf. Django migrations, Terraform scaffolding, start Jupyter server, etc.)

For Hacktoberfest participants, PR can be done any time before October. I'll hold off on approval/merging until October 1st so you get credit.


feat(alternativeto): init

🎉 Theme for AlternativeTo 🎉

AlternativeTo is a crowdsourced software recommendation website that lists alternatives to software. it allows users to vote on alternatives and leave text reviews. it also lists key features and allows filtering alternatives (e.g. alternatives to photoshop that support linux and are open source)

💬 Additional Comments 💬

🗒 Checklist 🗒

[x] I have read and followed Catppuccin's submission guidelines.
[x] I have made a new directory underneath /styles/<name-of-website> containing the contents of the /template directory.

[x] I have ensured that the new directory is in lower-kebab-case.
[x] I have followed the template and kept the preprocessor as LESS.

[x] I have made sure to update the
userstyles.yml
file with information about the new userstyle.
[x] I have included the following files:

[x] catppuccin.user.css - all the CSS for the userstyle, based on the
template.
[x] preview.webp - composite image of all four individual flavor screenshots (taken with the default accent color of mauve) stitched together, generated via Catwalk.

Header text is pretty much unreadable.

Just make the header accent colored and the footer mantle + text.

(the github icon is monochrome so it doesn't need special theming)

The text and close button of this modal is unthemed. Small but if you have a chance would be great :)

Log out, go to https://alternativeto.net/software/yaak/about/, click the heart/like/upvote button, and this modal will pop up prompting you to register.

Theming https://auth.alternativeto.net/ would also be appreciated.

These account related settings buttons are unthemed:

i themed the warning button (send password reset e-mail) by looking at the original css as i do not have an account on the website. you'll have to confirm if that themes it correctly.
i also themed the auth page based on what i can see as a no-account user.


Removed unsupported scenario.

Remove the following comment as iPad is NOT supported for Centralized Deployment
o	  On iOS (iPad only), Version 2.9.18010804 or later.

@Sirkkuw - PR is ready for final review.
Thank you.
cc: @kenwith

This has already been fixed in the live topic.


Unified user feedback (UUF) triage for August 2024

Create UUF issues for the next quarter (October--December) when this issue is completed.

Create UUF issues for the next quarter (October--December) when this issue is completed.

cc @wadepickett,  the following quarter you'll be in charge of creating the quarterly issues and assign creating the next quarter issues to @tdykstra

OK thanks, put it on my calendar as a reminder for 2025 April to create and assign to tdykstra and on my calendar for 2025 Jan-March to do UUF myself.

Finished, only a dozen left.


Epson TM81 could not print text in right side

Hi everyone,
I'm using CUPS as print server and i have 1 Epson TM81 but when printing the receipt some of text/number in the right side were missed (look like oversize the paper size). I've tried to change another paper size but not worked.
Anyone here had faced same problem or can help me to fix it so please leave your comment here.
Thanks everyone!

@TungLe93 It would be useful to know:

What version of CUPS you are using
What driver you are using for this printer
What kind of data/file you are sending to CUPS when printing the receipt

@TungLe93 It would be useful to know:

What version of CUPS you are using
What driver you are using for this printer
What kind of data/file you are sending to CUPS when printing the receipt

Hi bro, I would like to reply as below, sorry for late:

What version of CUPS you are using
CUPS 1.7.2

What driver you are using for this printer
TM/BA Series Printer Driver for Linux Ver.<IP_ADDRESS>
Download link: https://download.epson-biz.com/modules/pos/index.php?page=single_soft&cid=5012&pcat=3&pid=3260

What kind of data/file you are sending to CUPS when printing the receipt
I dont know what you means, the receipt was printed via POS app (our vendor give this app to us)

@TungLe93 For my third question, I wondered whether the POS app was sending printer-ready data or was generating PostScript or PDF for the CUPS filters to convert? If it sends printer-ready data then there is nothing we can do to help you here... :/
As the linked driver does not include source code, I'm afraid there isn't much I can suggest... Have you tried getting help from your POS vendor?


@payloadcms/plugin-search - "Search Results" collection does not show up when using Next.js 14

Link to reproduction
No response
Describe the Bug
Problem is on Next.js 14 with Payload 2.11.0.
I used the website template and I have two branches - one with Next 13.5, and another with Next 14.
The search plugin creates the "search results" collection on the admin panel, when on Next 13.5. It does not create it when on Next 14.
However all other plugins continue working as expected. I would like for search plugin to work on Next.js 14 if possible.
To Reproduce

Clone and Use the website template
upgrade payload to 2.11.0
upgrade to Next.js 14
Validate it loads with existing plugins / libraries
Install the search plugin
Check if the admin panel displays the "Search Results" collection

Package.json dependencies:

Payload Version
2.11.0
Adapters and Plugins
db-postgres, bundler-webpack, plugin-cloud-storage, plugin-nested-docs,plugin-redirects, plugin-search, plugin-seo, richtext-slate

I managed to get this working on the latest versions of the plugins with v2 of payload website template.
Will close this issue for now but we can re-open if there's a reproduction


update README with info about deploy contexts

Fixes https://github.com/netlify/netlify-plugin-nextjs/issues/97
would love your feedback as well @amuttsch!

Sounds good to me :+1:


Add remove from collection patch

Equality on complex child collections compares all fields, could possibly inspect for identity field as an optimisation.

@jimgolfgti You might just be the new gold standard for PR's. Thanks for doing this.


Remove Splash Art

Currently after Splash Art is set, there is no way to remove picture. You can only replace with another.

I created a patch for this, hopefully the pull request will be accepted and merged

This is now included in Release 0.5.7, thank you @Dilomos!


[OTHER] Picamera2 & Cronjob

Hello everyone!
I am trying to start Picamera2 with crontab -e. Unfortunately, I can't seem to get it working.
The preview is working and my scripts are also working and capturing the video storing the data to a file.
But whenever my script is invoked from cron I got the error: Camera __init__ sequence did not complete.
Does anybody has a clue?

Hi, thanks for the question. I'm afraid I don't know the answer, but it feels like it might be related to permissions in some way. I expect others have faced this too, so if anyone does have a fix or workaround I'd be very pleased to know so that I can add it to the official manual.

Could you say a bit more about how you're using crontab? Are you running the job as root or as a regular user? Are you trying to get something to run at startup, or once the system has been up for a while? These are all likely to affect what you can and can't do. Another factor may be environment variables - are there any that you're setting up that might not be picked up by a cron job?

I will come back to you in a few days! Sorry, I am not able to have a closer look at this project atm.

I have seen this error when there was still another process using the camera running on another terminal, i,e, by not calling picamera2.stop()

@tvoverbeek That is true, normally. But the job doesn't even start after a fresh reboot while no instance of picamera2 has been used. In my scripts I also switch between different instances which does work, but only after starting it manually.
I did not find any solution myself nor in the web search, that's why I opened this ticket.

My suspicion is that the error message is a bit generic, libcamera is saying "I couldn't open it so someone else must be using it". I think it may be more likely that there's some other reason, such as not having the right permissions, but I'm rather guessing here.

@Maddy1206  Why are you running the cron job as root?
I just tried to run a video capture as a cron job and it works fine.
My default user is tvo, not pi.
Here is my crontab entry generated as user tvo with crontab -e
# m h  dom mon dow   command
10 22 * * * /home/tvo/mp4output.py >> /home/tvo/cron.log 2>&1

Note: stdout and stderr are redirected to /home/tvo/cronlog otherwise cron tries to mail the output which in my case fails because there is no MTA (Mail Transfer Agent) installed.
Here is the mp4output.py script:
#! /usr/bin/python3

#import libraries
import time
import os
import cv2
from picamera2 import MappedArray, Picamera2
from picamera2.encoders import H264Encoder
from picamera2.outputs import FfmpegOutput

#set variables
hour = int(time.strftime('%H'))
now = time.strftime("%y_%m_%d_%H_%M")
h264_output = "test"+now+".h264"
mp4_output = "test"+now+".mp4"

#set timestamp
colour = (255, 255, 255)
origin = (0, 30)
font = cv2.FONT_HERSHEY_SIMPLEX
scale = 1
thickness = 2

def apply_timestamp(request):
    timestamp = time.strftime("%Y-%m-%d %X")
    with MappedArray(request, "main") as m:
        cv2.putText(m.array, timestamp, origin, font, scale, colour, thickness)

#set video configuration
picam2 = Picamera2()
picam2.pre_callback = apply_timestamp
picam2.video_configuration.controls.FrameRate = 25.0
picam2.video_configuration.size = (1280, 720)
encoder = H264Encoder(bitrate=10000000)
output = FfmpegOutput(mp4_output)

#set length of footage
picam2.start_recording(encoder, output)
time.sleep(10)
picam2.stop_recording()

The log file for the run at 22;10:
[6:41:41.393397975] [1713]  INFO Camera camera_manager.cpp:299 libcamera v0.0.3+40-9b860a66
[6:41:41.416827658] [1714]  WARN CameraSensorProperties camera_sensor_properties.cpp:205 No static properties available for 'imx708_wide_noir'
[6:41:41.416940210] [1714]  WARN CameraSensorProperties camera_sensor_properties.cpp:207 Please consider updating the camera sensor properties database
[6:41:41.529705792] [1714]  INFO RPI raspberrypi.cpp:1425 Registered camera /base/soc/i2c0mux/i2c@1/imx708@1a to Unicam device /dev/media3 and ISP device /dev/media0
[6:41:41.538514846] [1713]  INFO Camera camera.cpp:1028 configuring streams: (0) 1280x720-XBGR8888
[6:41:41.539169998] [1714]  INFO RPI raspberrypi.cpp:805 Sensor: /base/soc/i2c0mux/i2c@1/imx708@1a - Selected sensor format: 1536x864-SBGGR10_1X10 - Selected unicam format: 1536x864-pBAA

and the entry in /var/log/syslog:
Feb 24 22:10:01 picam2-32 CRON[1712]: (tvo) CMD (/home/tvo/mp4output.py >> /home/tvo/cron.log 2>&1)

@tvoverbeek I was running it on root because of the assumption that permissions for the Picamera were denied.
Anyway, I found out that my script file was showing unusal behavior because I created new files and with them the cronjob worked.
And just to make sure I did a full reset and installed a new OS. After that everything worked fine.
Thanks a lot! I am closing this issue.


Salt the Salt master

Use Salt to install the Salt master.
The Salt master will get restart on configuration changes,
but will need to be manually restarted on package changes to
allow for proper ordering of updating.
(Salt masters must be updated before Salt minions.)
Use Jinja to generate the config file YAML directly, preventing
typos in the master config file and providing access to master
configuration options in the SLS file (e.g. the file_roots locations).
Incorporates and thus fixes #298.
TODO:

[x] Add gitfs support. Fixes #264.
[x] Add _modules/ dir and backport launchctl.py module

TODO after landing:

[ ] Add master install instructions to the wiki
[ ] Update Salt-inside-Vagrant usage instructions on the wiki

After I finish the WIP tasks, landing this will unblock a bunch of other things that need the launchctl.py module (upgraded ssh, salt-minion salting, upgrading salt, etc.)

This change is

OK, this is ready for review. See the commit messages for details; also, a few notes:

The Vagrantfile needed to be updated, so I cherry-picked #298 as well.
I tested out the new launchctl.py module and updates to the Buildbot slave state on servo-macpro1 and in Vagrant.

Rebased since #298 landed.

:umbrella: The latest upstream changes (presumably #374) made this pull request unmergeable. Please resolve the merge conflicts.

Reviewed 1 of 11 files at r6, 4 of 4 files at r7, 3 of 3 files at r8, 3 of 3 files at r9.
Review status: all files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.

_modules/launchctl.py, line 3 [r9] (raw file):

# -*- coding: utf-8 -*-
'''
Module for the management of MacOS systems that use launchd/launchctl

It looks like we're vendoring this in from the Salt builtin module (https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.launchctl.html). Do we need to worry about keeping this up to date with changes that Salt makes upstream, or will it be obsoleted relatively soon once we upgrade our Salt version?

Comments from Reviewable

@edunham I backported that module temporarily; we shouldn't need to update it unless it breaks, and we can simply remove it once we've updated Salt.
I rebased the branch and made some tweaks, but haven't tested them in Vagrant yet because my home Internet connection is slower than at school. Do you know why Travis doesn't seem to be triggering?

Not sure what's up with Travis; I've manually restarted https://travis-ci.org/servo/saltfs/builds/128187498 .

Rebased, but I want to tweak this a little more before merging.

Rebased with tweaks and lightly tested in Vagrant. Ready for review.

:umbrella: The latest upstream changes (presumably #394) made this pull request unmergeable. Please resolve the merge conflicts.

Reviewed 3 of 4 files at r11, 4 of 4 files at r12, 3 of 3 files at r13.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

Comments from Reviewable

@bors-servo r+

:pushpin: Commit 037d31b has been approved by edunham

:hourglass: Testing commit 037d31b with merge d7f388d...

:broken_heart: Test failed - status-travis

I think I'll need to backport the pip_state.py state module as well for this to pass Travis - I'll try to do that this evening.

OK, I backported the pip execution and state modules. Something important I discovered is that custom modules with the same name don't work properly, so I prefixed the files with backported_.
Should be good to go now.

It turns out the file naming wasn't the issue, and that giving the files the same name is the right thing to do for overriding. However, our version of Salt is so old that the backported pip modules weren't working properly (looking for Salt utilities that don't exist in our version), so I've backported only the needed changes to pip_state.py.
Also, I added some headers to (try to) comply with the Apache 2.0 license of the backported modules.

All of the test failures are happening on the builders where we test the PR as an upgrade; they fail when applying the initial highstate (of the old code). All of the builders that test the PR from scratch are passing, though, so I think this is OK.

@edunham Is there anything else left to review here? We're having to do all manual merges to saltfs until this lands.

Reviewed 2 of 2 files at r14, 1 of 1 files at r15.
Review status: all files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.

Comments from Reviewable

I think that the problems we're encountering from outdated Salt version are greater than any problems likely to remain in this PR. The Travis failures look like the standard Salt version issues we've been seeing.

Just a clarification, this PR doesn't update the whole Salt version, only backports a few modules.


JSON-Config HideExpression with custom functions

I'm submitting a ...  (check one with "x")
[ ] bug report => search github for a similar issue or PR before submitting
[ x ] feature request
[ ] support request

Current behavior
Based on the example config found here https://formly.dev/examples/other/json-powered.
You can use hideExpressions within the JSON-powered configuration. However; custom functions are not supported as JSON does not allow this. I would like to have a custom hideExpression function provided like the custom validations. Thus hide expressions are limited to simple equal comparisons.
Current example JSON-hideExpression implementation:
{
    "key": "reason",
    "type": "textarea",
    "templateOptions": {
      "label": "Why?"
    },
    "expressionProperties": {
      "templateOptions.label": "'Why did you choose ' + model.color + '?'"
    },
    "hideExpression": "!model.color" //<--- Limited usecases
}

Expected behavior
My suggestion would be to add a hideExpressions key to the ConfigOption interface.
export function myCustomHideExpression(value: any) : boolean {
    return Number(value) === 1;
}

@NgModule({
  imports: [
    CommonModule,
    ReactiveFormsModule,
    FormlyBootstrapModule,
    FormlyModule.forRoot({
      hideExpressions: [
        { name: 'myExpression', validation: myCustomHideExpression },
      ],
    }),
  ],
  declarations: [
    AppComponent,
  ],
})
export class AppModule { }

What is the motivation / use case for changing the behavior?
This allows for (JSON) configurations with more advanced validations. Or default (complex) hide expression for non-JSON variants
{
    "key": "reason",
    "type": "textarea",
    "templateOptions": {
      "label": "Why?"
    },
    "expressionProperties": {
      "templateOptions.label": "'Why did you choose ' + model.color + '?'"
    },
    "hideExpression": "myExpression" <-- Endless custom implementations.
  }

Please tell us about your environment:
Currently using ngx-formly 3.1.0

Angular version: 2.0.X
Not relevant; but this would be in the latest/greatest version of ngx-formly.

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]
All

Language: [all | TypeScript X.X | ES6/7 | ES5]
All

Node (for AoT issues): node --version =

you can use a custom extension for that, see https://github.com/formly-js/ngx-formly/issues/1109#issuecomment-412295111

Hi
i followed the extension way to use hideExpression as shown on stackblitz url
https://stackblitz.com/edit/angular-n3vyut?file=src/assets/json-powered/user-form.json
it's running absolutely fine in local or on stackblitz.
when i deploy it to other environment it's giving below error. can someone help me to resolve this.

see https://github.com/ngx-formly/ngx-formly/issues/1624#issuecomment-502771903

Hello,
I am new to using formly, I have tried to use the above example for hideExpression in my project, but I have come to the issue that in Extension, the value of the model is relative to the field and its children on which hide expression is used.
in my case, the element which has to hide is dependent on element present in its parents' form field. and as an element is in parents' scope I am not able to use its value to hide an element.
is there any workaround for this situation.

@siddheshpdy you can have access to the parent field using field.parent.


Not update.

If there is a VIP Ad, script send last VIP Ad and don't send other Ad, because ViP Ad on Top Ads.

If 2 Ads and more send update every start, rotations Ads.

Issue fix in update v1.1


Bug 1720033: Jun112019 jenkins security advisory

@openshift/sig-developer-experience fyi
/assign @akram
/assign @waveywaves

/lgtm

master branch PR https://github.com/openshift/jenkins/pull/872 merged 5 days ago

Opened https://jira.coreos.com/browse/ART-681 to get jenkins plugin rpm updated ... combination of 4 recent plugin updates for 4.1

plugin list https://github.com/openshift/jenkins/pull/860#issuecomment-503658743

osbs brew distgit http://pkgs.devel.redhat.com/cgit/rpms/jenkins-2-plugins/commit/?h=rhaos-4.1-rhel-7&id=495d2aabfadfe7c6ecdd16dd151ed741b76052d1


How to Display banner in test mode?

There's currently now way to set a test device ID for banner ads. I will push a big update soon which will enable this feature.

On 31.05.2016, at 16:17, Uysim<EMAIL_ADDRESS>wrote:
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hey @Uysim, I just published a new version of react-native-admob!
Now you can enable test mode by setting a prop like this:
<AdMobBanner
  testDeviceID="..."
  adUnitID="..."
/>

Setting testDeviceID to "EMULATOR" will set it to Simulator mode on iOS and Emulator mode on Android.
Hope it works, please give me feedback if it doesn't!


Add set_default_context to mx.util namespace for better usability

Description
...previously under test_utils, hard to find and use.
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at https://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[ ] To the best of my knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

Should
https://github.com/apache/incubator-mxnet/blob/440a44a084f46aeead51937067aadcda082c1dc0/python/mxnet/context.py#L139
be improved instead?


Unwanted newlines being added

Each time the formatter runs on this sample document, more blank lines get added.
I would expect that once a document has been formatted, the results would not change if it is formatted again.
  <title>test formatting</title>

    The Pythagorean Theorem states
    <me>r = \sqrt{{x^2}+{y^2}}</me>.

    <md>
      <mrow>(a+b)^2</mrow>
    </md>
    .   For some reason they keep getting extra newlines. Let's see, should be an easy fix.

@whaynes The latest commit should address this, please let me know and close the issue if it does.

Haris,
I ran the new version across my books, and it all looks good.
Thanks for making this tool, and for your quick response.    ptx-formatter  is really very helpful to me.
Will Haynes


Automated cherry pick of #5344

Cherry pick of #5344 on release-5.23.

#5344: MM-23605 Reload team memberships when team scheme is

/cc  @fmunshi

Will try to auto merge this PR once all tests and checks are passing. This might take up to an hour.


Post-mount with componentDidMount

#In 8.1.0, componentDidMount/componentDidUpdate can not promise to be called after dom mount/update.
related resource: https://developmentarc.gitbooks.io/react-indepth/content/life_cycle/birth/post_mount_with_component_did_mount.html
related PR:
https://github.com/developit/preact/pull/506#issuecomment-293879820

@ustccjw would you be able to put together a jsfiddle that shows the ordering issue?  I'm not sure I understand the problem.

demo: https://jsfiddle.net/ustccjw/uzyh4r01/1/
when you click update button，child componentDidUpdate will execute before parent DOM update.

I'll describe the issue as I understand it. Given this component tree:
Parent
   |
   Child

In Preact 8.1.0, triggering an update on Parent which re-renders both Parent and Child will result in the child's componentDidUpdate callback being triggered after the Child's DOM has updated but before the Parent's DOM has been updated.
React on the other hand queues both componentDidMount and componentDidUpdate callbacks and executes them all once the entire tree has been updated (in the Fiber renderer, in the stack Renderer).
The componentDidUpdate docs don't specify this behaviour, but if the child runs code in componentDidUpdate which might be invalidated by the parent's update in any way (eg. accessing the parent directly, measuring the child's own size) then the result will be wrong unless the child's componentDidUpdate is deferred until the whole tree is updated.
I suggest that in Preact we queue componentDidUpdate callbacks in the same queue that handles mount callbacks and flush them all once the entire tree is updated. I think we deferred doing this last time because it increased the size slightly, but I don't see an easy way around this. Thoughts @developit ?

I agree. We can work some magic to keep the size down. Maybe this ties into the idea of a more general queue (though we can't really use it as a general callback queue due to size/perf).

@developit @robertknight Are there any solutions ?

I haven't had time to dig into this properly yet.  We need a generic "end of work" queue to replace the three specific queues we do now.

Hi, I've just commited a PR trying to solve this issue, along with a test case same as this issue's example. The bundle size slightly increased from 3444->3503 according to 'yarn build'.
Please kindly check and give more thoughts on this, thanks

So somehow today we also hit this case where componentDidMount() from a Child Component is triggered later and componentDidUpdate() from  triggered before.
A colleague created a jsfiddle (with console output):
react: https://jsfiddle.net/69z2wepo/213165/
preact: https://jsfiddle.net/3hvru6ex/619/
We hit this when we wanted to start measuring render and call performance.mark API.


Userscripts compatibility issues

https://www.baiduyun.wiki/install.html
https://greasyfork.org/zh-CN/scripts/329484-豆瓣资源下载大师-1秒搞定豆瓣电影-音乐-图书下载

@JohnnyWoong
Hello, seems like it's working fine on my side (see details). Can you share more details about the version of AdGuard and installed AV on your device?

@JohnnyWoong
Hello, seems like it's working fine on my side (see details). Can you share more details about the version of AdGuard and installed AV on your device?

ADG7.6.1, how about first one? this two dont work in my computer

@JohnnyWoong
Unfortunately, I cannot register in that network to check if we can do something with it. But I've checked with another extension from the link you've provided and seems like it's ok too:

Maybe you should check with only AdGuard & browser? I mean without any other extensions that can prevent the script's work.

@JohnnyWoong
Unfortunately, I cannot register in that network to check if we can do something with it. But I've checked with another extension from the link you've provided and seems like it's ok too:
Maybe you should check with only AdGuard & browser? I mean without any other extensions that can prevent the script's work.

The problem still same, by the way, if i use second user script by Tmonkey,

this part of it will disapper,but its not advertising

Or maybe a test account we could use?

Its no need for account, open https://movie.douban.com/subject/34913671/?tag=热门&from=gaia and you will see this part of it will disapper if you install https://greasyfork.org/zh-CN/scripts/329484-豆瓣资源下载大师-1秒搞定豆瓣电影-音乐-图书下载 by Tmonkey

Another compatibility issue with YouTube: Age Verification Bypass ( https://greasyfork.org/ru/scripts/375525-youtube-age-verification-bypass ) which is not working correctly (e.g here https://www.youtube.com/watch?v=NV-cnKFH8vU)
https://github.com/AdguardTeam/AdguardForWindows/issues/3835

One more: https://github.com/AlekPet/Rutor-Preview-Ajax/blob/master/RutorPreviewAjax.user.js

The issue with the douban download userscript should be fixed along with https://github.com/AdguardTeam/CoreLibs/issues/1400
The verification bypass userscript is not available by https://greasyfork.org/ru/scripts/375525-youtube-age-verification-bypass, but https://greasyfork.org/en/scripts/423851-simple-youtube-age-restriction-bypass works fine
The rutor preview script uses GM_addValueChangeListener which is not implemented by our userscript wrapper. We already have a feature request for that (jira/AG-87)

Yep, its working right now, thx :)


NEXT-9611 - Cross Selling Preview Modal won't close when opening a product

When using the preview function of a cross selling you can navigate to previewed products but the preview modal won't close itself.
The Modal should be closed before the product is opened

Cannot reproduce. Is it possible that this has been fixed?
https://user-images.githubusercontent.com/3930922/104611190-25d09d80-5685-11eb-8bd0-35bbb9fa298f.mov

Cannot reproduce. Is it possible that this has been fixed?
https://user-images.githubusercontent.com/3930922/104611190-25d09d80-5685-11eb-8bd0-35bbb9fa298f.mov

@shopwareBoostDay/shopware-qa

@shopwareBoostDay/shopware-qa


w-full

Hello, I can't find where to modify the global class to put the site in w-full and not with big white borders on the sides.
I'm starting to develop it and I don't have all the notions yet.

Hi @lmbow, I use the max-width-wrapper.tsx component to add container and max-width classes. There is the large parameter the full width but you can add some others parameters to manage it.
In tailwind.config.ts, you can update the padding to change the padding of the container class :
theme: {
    container: {
      center: true,
      padding: ".8rem", // change this value if you want
    },
   //...
}


How to generate topK predictions using Levenstein Transformer?

❓ Questions and Help
Before asking:

search the issues.
search the docs.

What is your question?
I want to generate topK translated sentences. I found in the documents that I could set --nbest to achieve this goal. However, I've tried and it still generated only one sentence when translating.
Code
fairseq-generate
data-bin/Dataset
--gen-subset test
--task translation_lev
--path checkpoints/checkpoint_best.pt
--iter-decode-max-iter 9
--iter-decode-eos-penalty 0
--beam 1 --remove-bpe
--print-step
--batch-size 400
--results-path data-test
--nbest 10
What have you tried?
I set --nbest to 10 but it didn't work.
What's your environment?

fairseq Version (e.g., 1.0 or main):
PyTorch Version (e.g., 1.0)
OS (e.g., Linux):
How you installed fairseq (pip, source):
Build command you used (if compiling from source):
Python version:
CUDA/cuDNN version:
GPU models and configuration:
Any other relevant information:

I spent several days on this and only found out that this modal could not generate multiple predictions so as all the iterative-refine generators, which made me very upset. Why not state more clearly in the documentation? I think it's too general considering all the models and functions of fairseq, isn't it?


[HOLD for payment 2024-03-25] [HOLD for payment 2024-03-22] [$500] App crashes when navigating to another report while playing a video

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number:
Reproducible in staging?:
Reproducible in production?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by:
Slack conversation:
Action Performed:

Play a video
Navigate to another report

Expected Result:
App doesn't crash
Actual Result:
App crashes
Workaround:
Reload app
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
https://github.com/Expensify/App/assets/22219519/f87a6aee-ecd8-4125-b7c1-cf1a5103da35
Add any screenshot/video evidence

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~013fb810bafe68c299
Upwork Job ID:<PHONE_NUMBER>646979584
Last Price Increase: 2024-03-14
Automatic offers:

situchan | Contributor | 0

I can take this, thanks.

Proposal
Please re-state the problem that we are trying to solve in this issue.
When we play a video and navigate to a different report we crash!
What is the root cause of that problem?
It's a regression from https://github.com/Expensify/App/commit/6f92384ba7d8b3fe2af1486a0b6b7ff2d8c75201
Where we are no longer typesafe.
As we unload the video the ref becomes undefined, and calling stop on the video now crashes.
There's a cleanup that happends on reportId change https://github.com/Expensify/App/blob/6f92384ba7d8b3fe2af1486a0b6b7ff2d8c75201/src/components/VideoPlayerContexts/PlaybackContext.tsx#L80
But by the time we are here it seems the ref is destroyed.
What changes do you think we should make in order to solve the problem?
We should make it typesafe again to unblock the deployment by adding the optional chaining back
What alternative solutions did you explore? (Optional)

[x] The PR that introduced the bug has been identified. Link to the PR: https://github.com/Expensify/App/pull/37134
[x] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: https://github.com/Expensify/App/pull/37134#issuecomment-1998603352
[x] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: N/A
[x] Determine if we should create a regression test for this bug.
[x] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.

Regression Test Proposal

Send any video on any chat
Play a video
While playing, navigate to another report
Verify that app doesn't crash

Payment Summary:

Contributor: @jeremy-croff $500
Reviewer: @situchan $500 paid via Upwork

Upwork job: https://www.upwork.com/ab/applicants/1768419024646979584/hired

@jeremy-croff request payment whenever you're ready.

Ah, my mistake! It just looks like you need a manual offer in Upwork, not that you're on our NewDot payments process. Just sent you an offer from Upwork.

Ah, my mistake! It just looks like you need a manual offer in Upwork, not that you're on our NewDot payments process. Just sent you an offer from Upwork.

Thanks! Accepted it.
Is there any benefits or process to look into getting on NewDot payments process? (Mainly because UpWork takes a large fee )

Paid! We're working on enabling more contributors to use our NewDot payment process, but it's a bit of work to do right now so it's not a super high priority.


Automatic PR from RestAPI-PR1900

Generated from RestAPI PR: https://github.com/Azure/azure-rest-api-specs/pull/1900

Codecov Report

Merging #1559 into master will increase coverage by 0.2%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master    #1559     +/-   ##
=========================================
+ Coverage   54.18%   54.39%   +0.2%
=========================================
  Files        3595     3594      -1
  Lines       88698    88328    -370
=========================================
- Hits        48065    48046     -19
+ Misses      40633    40282    -351

Impacted Files
Coverage Δ

...09_01/operations/public_ip_addresses_operations.py
65.1% <ø> (+7.83%)
:arrow_up:

.../v2017_09_01/operations/route_tables_operations.py
95.93% <ø> (+16.6%)
:arrow_up:

...etwork/v2017_09_01/operations/usages_operations.py
93.75% <ø> (ø)
:arrow_up:

...01/operations/express_route_circuits_operations.py
67.24% <ø> (+6.62%)
:arrow_up:

...2017_09_01/operations/load_balancers_operations.py
95.93% <ø> (+16.6%)
:arrow_up:

...9_01/operations/application_gateways_operations.py
9.05% <ø> (+0.49%)
:arrow_up:

...1/operations/network_security_groups_operations.py
95.93% <ø> (+16.6%)
:arrow_up:

...01/operations/local_network_gateways_operations.py
16% <ø> (+2.61%)
:arrow_up:

...17_09_01/operations/virtual_networks_operations.py
84.75% <ø> (+11.45%)
:arrow_up:

...17_09_01/operations/network_watchers_operations.py
6.69% <ø> (+0.07%)
:arrow_up:

... and 4 more

Continue to review full report at Codecov.

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

Wrong branch


Azure SDK Review - [Azure SDK - Azure.Core & Event Grid System Events]

New SDK Review meeting has been requested.
Service Name: Azure SDK - Azure.Core & Event Grid System Events
Review Created By: Ronnie Geraghty
Review Date: 07/03/2023 02:05 PM PT
Hero Scenarios Link: Not Provided
Architecture Diagram Link: Not Provided
Core Concepts Doc Link: Not Provided
APIView Links: .NET,
Description: Combine session for Azure.Core and Event Grid System Events
Detailed meeting information and documents provided can be accessed here

Cancelled by: Ronnie Geraghty


poorly documented mixin case

dart 1.16, problem where both mixins need to access same parent variable.
Case 1 works, but throws error in strong mode.
Case 2 fixes this but is case that could use better documentation.
Case 1
abstract class A2 {
  int  a;

  p2() {
        print("A2 - $a");
  }
}

abstract class A3 {
  int  a;

  p3() {
    print("a3 - $a");
  }
}

class A extends Object with A2, A3 {
  int a;

  A() {
     a = 11;
  }

  void p() {
    print("A - $a");
  }
}

main() {
  A a = new A();
  a.p();
  a.p2();
  a.p3();
}

Case 2
abstract class A2 {
  int get a;

  p2() {
        print("A2 - $a");
  }
}

abstract class A3 {
  int get a;

  p3() {
    print("a3 - $a");
  }
}

class A extends Object with A2, A3 {
  int a;

  A() {
     a = 11;
  }

  void p() {
    print("A - $a");
  }
}

main() {
  A a = new A();
  a.p();
  a.p2();
  a.p3();
}

Mixins can be tricky, but they are not different from other classes. You just get to write the class body somewhere else than at the declaration.
In case 1 you have the class A with super-classes Object-with-A2-with-A3, Object-with-A2, and Object.
Three of these classes declare an "a" field, so you have three "a" fields on the resulting class with the one in A overriding and shadowing the other two, and those two are just a waste of memory.
This is no different from what happens if you declare:
class A2 extends Object {
  int  a;
  p2() {
    print("A2 - $a");
  }
}
class A3 extends A2 {
  int a;
  p3() {
    print("A3 - $a");
  }
}
class A extends A3 {
  int a;
  p() {
    print("A - $a");
  }
}
main() {
  A a = new A();
  a.p();
  a.p2();
  a.p3();
}

It is basically the exact same program, just without complicating it with mixins. Here it's more clear that you declare three a fields, and why that's probably not what you intended.
So, all in all, I don't think it's a problem with mixins as such, mixins just makes it easier to not see the actual class inheritance structure because they allow you to put the class body further away.

I'm going to close this because it looks like the language is working as intended. I totally agree that this is a footgun. It is too easy to override a field, which is almost never what you want.
See also: #26461


[FeatureRequest] Azure SQL binding

Support for azure sql in/out binding
I've already seen people raise similar issue before: #365
At this time, looks like the only db binding supported is cosmos, the doc is here
Considering

programming model 1 already supported sql in/out biding, doc, can we expect same feature to exist for model 2
RDBMS like azure sql has a huge user base, Having these bindings would really benefit the sql users

Sample v1 binding for sql
{
    "name": "todoItems",
    "type": "sql",
    "direction": "out",
    "commandText": "dbo.ToDo",
    "connectionStringSetting": "SqlConnectionString"
}

Thanks for Feedback will confirm for the same.

Similar topic, I see in the v2 doc below is ss for supported triggers. Is there a timeline/roadmap where we can see the progress of supporting each of these?


clippy::redundant_closure warning on cxx::bridge macro in cxx 1.0.43+

Hi! Starting with cxx 1.0.43, I'm getting this Clippy warning for my project (Rust 1.48 and Rust 1.51):
error: redundant closure found
 --> rust/libnewsboat-ffi/src/logger.rs:3:1
  |
3 | #[cxx::bridge(namespace = "newsboat::Logger")]
  | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  |

I couldn't narrow this down to anything in particular; the only way to make the warning go away is to make the bridge mod empty. It's also not related to the (namespace = …) thing, because removing it doesn't make the warning go away.
The warning advises to "run with -Z macro-backtrace for more info", but doing so makes the warning go away (I tried both cargo +nightly … and rustup override set nightly).
The result of macro expansion:
$ cargo +nightly rustc --package libnewsboat-ffi --profile=check -- -Zunstable-options --pretty=expanded
#![feature(prelude_import)]
// Each function in this crate is used in a single place: a corresponding C++ wrapper. It doesn't
// make sense to document these functions because they are basically an internal detail and don't
// stand on their own.
#![allow(clippy :: missing_safety_doc)]
// This lint is nitpicky, I don't think it's really important how the literals are written.
#![allow(clippy :: unreadable_literal)]
#[prelude_import]
use std::prelude::rust_2018::*;
#[macro_use]
extern crate std;

use libc::c_char;
use std::ffi::CString;
use std::panic::{catch_unwind, UnwindSafe};
use std::process::abort;

// SNIP: some unrelated modules

pub mod logger {
    use libnewsboat::logger;
    #[deny(improper_ctypes, improper_ctypes_definitions)]
    #[allow(non_camel_case_types, non_snake_case, clippy ::
            upper_case_acronyms)]
    mod ffi {
        #[repr(transparent)]
        pub struct Level {
            #[allow(missing_docs)]
            pub repr: u8,
        }
        impl ::core::marker::StructuralEq for Level { }
        #[automatically_derived]
        #[allow(unused_qualifications)]
        impl ::core::cmp::Eq for Level {
            #[inline]
            #[doc(hidden)]
            fn assert_receiver_is_total_eq(&self) -> () {
                { let _: ::core::cmp::AssertParamIsEq<u8>; }
            }
        }
        impl ::core::marker::StructuralPartialEq for Level { }
        #[automatically_derived]
        #[allow(unused_qualifications)]
        impl ::core::cmp::PartialEq for Level {
            #[inline]
            fn eq(&self, other: &Level) -> bool {
                match *other {
                    Level { repr: ref __self_1_0 } =>
                    match *self {
                        Level { repr: ref __self_0_0 } =>
                        (*__self_0_0) == (*__self_1_0),
                    },
                }
            }
            #[inline]
            fn ne(&self, other: &Level) -> bool {
                match *other {
                    Level { repr: ref __self_1_0 } =>
                    match *self {
                        Level { repr: ref __self_0_0 } =>
                        (*__self_0_0) != (*__self_1_0),
                    },
                }
            }
        }
        #[allow(non_upper_case_globals)]
        impl Level {
            pub const USERERROR: Self = Level{repr: 1,};
            pub const CRITICAL: Self = Level{repr: 2,};
            pub const ERROR: Self = Level{repr: 3,};
            pub const WARN: Self = Level{repr: 4,};
            pub const INFO: Self = Level{repr: 5,};
            pub const DEBUG: Self = Level{repr: 6,};
        }
        unsafe impl ::cxx::ExternType for Level {
            #[doc(hidden)]
            type Id =
             (::cxx::n, ::cxx::e, ::cxx::w, ::cxx::s, ::cxx::b, ::cxx::o,
              ::cxx::a, ::cxx::t, (), ::cxx::L, ::cxx::o, ::cxx::g, ::cxx::g,
              ::cxx::e, ::cxx::r, (), ::cxx::L, ::cxx::e, ::cxx::v, ::cxx::e,
              ::cxx::l);
            type Kind = ::cxx::kind::Trivial;
        }
        impl ::std::marker::Copy for Level { }
        impl ::std::clone::Clone for Level {
            fn clone(&self) -> Self { *self }
        }
        #[doc(hidden)]
        const _: () =
            {
                #[doc(hidden)]
                #[export_name = "newsboat$Logger$cxxbridge1$unset_loglevel"]
                unsafe extern "C" fn __unset_loglevel() {
                    let __fn = "newsboat::logger::ffi::unset_loglevel";
                    fn __unset_loglevel() { super::unset_loglevel() }
                    ::cxx::private::catch_unwind(__fn,
                                                 move || __unset_loglevel())
                }
                #[doc(hidden)]
                #[export_name = "newsboat$Logger$cxxbridge1$set_logfile"]
                unsafe extern "C" fn __set_logfile(logfile:
                                                       ::cxx::private::RustStr) {
                    let __fn = "newsboat::logger::ffi::set_logfile";
                    fn __set_logfile(logfile: &str) {
                        super::set_logfile(logfile)
                    }
                    ::cxx::private::catch_unwind(__fn,
                                                 move ||
                                                     __set_logfile(logfile.as_str()))
                }
                #[doc(hidden)]
                #[export_name = "newsboat$Logger$cxxbridge1$get_loglevel"]
                unsafe extern "C" fn __get_loglevel() -> i64 {
                    let __fn = "newsboat::logger::ffi::get_loglevel";
                    fn __get_loglevel() -> i64 { super::get_loglevel() }
                    ::cxx::private::catch_unwind(__fn,
                                                 move || __get_loglevel())
                }
                #[doc(hidden)]
                #[export_name = "newsboat$Logger$cxxbridge1$set_loglevel"]
                unsafe extern "C" fn __set_loglevel(level: Level) {
                    let __fn = "newsboat::logger::ffi::set_loglevel";
                    fn __set_loglevel(level: Level) {
                        super::set_loglevel(level)
                    }
                    ::cxx::private::catch_unwind(__fn,
                                                 move ||
                                                     __set_loglevel(level))
                }
                #[doc(hidden)]
                #[export_name = "newsboat$Logger$cxxbridge1$log_internal"]
                unsafe extern "C" fn __log_internal(level: Level,
                                                    message:
                                                        ::cxx::private::RustStr) {
                    let __fn = "newsboat::logger::ffi::log_internal";
                    fn __log_internal(level: Level, message: &str) {
                        super::log_internal(level, message)
                    }
                    ::cxx::private::catch_unwind(__fn,
                                                 move ||
                                                     __log_internal(level,
                                                                    message.as_str()))
                }
                #[doc(hidden)]
                #[export_name =
                  "newsboat$Logger$cxxbridge1$set_user_error_logfile"]
                unsafe extern "C" fn __set_user_error_logfile(user_error_logfile:
                                                                  ::cxx::private::RustStr) {
                    let __fn =
                        "newsboat::logger::ffi::set_user_error_logfile";
                    fn __set_user_error_logfile(user_error_logfile: &str) {
                        super::set_user_error_logfile(user_error_logfile)
                    }
                    ::cxx::private::catch_unwind(__fn,
                                                 move ||
                                                     __set_user_error_logfile(user_error_logfile.as_str()))
                }
            };
    }
    fn ffi_level_to_log_level(level: ffi::Level) -> logger::Level {
        match level {
            ffi::Level::USERERROR => logger::Level::UserError,
            ffi::Level::CRITICAL => logger::Level::Critical,
            ffi::Level::ERROR => logger::Level::Error,
            ffi::Level::WARN => logger::Level::Warn,
            ffi::Level::INFO => logger::Level::Info,
            ffi::Level::DEBUG => logger::Level::Debug,
            _ => { ::std::rt::begin_panic("Unknown log level") }
        }
    }
    fn unset_loglevel() { logger::get_instance().unset_loglevel(); }
    fn set_logfile(logfile: &str) {
        logger::get_instance().set_logfile(logfile);
    }
    fn get_loglevel() -> i64 { logger::get_instance().get_loglevel() as i64 }
    fn set_loglevel(level: ffi::Level) {
        let level = ffi_level_to_log_level(level);
        logger::get_instance().set_loglevel(level);
    }
    fn log_internal(level: ffi::Level, message: &str) {
        let level = ffi_level_to_log_level(level);
        logger::get_instance().log(level, message);
    }
    fn set_user_error_logfile(user_error_logfile: &str) {
        logger::get_instance().set_user_error_logfile(user_error_logfile);
    }
}

// SNIP: a few more modules

The only closures that I can see are the ones passed to ::cxx::private::catch_unwind, but these were present even in 1.0.41 (which didn't produce the warning).
I'm okay with suppressing this warning on my end, but I thought I'd let you know about this and see if you have some insights.
If you'd like to experiment locally:

the repo is https://github.com/newsboat/newsboat.git
the crate in question resides under rust/libnewsboat-ffi
the command to run is cargo clippy (my CI adds -D warnings and more flags, but none of it is required to get the warning)

This looks like a Clippy bug in the 1.51.0 toolchain clippy. If you build with a newer clippy (cargo +beta clippy) then there is no warning.

I published cxx 1.0.46 with a workaround.

Thank you!


Streaming Category Organized A Little

Basically just re-organized the streaming section a bit so it looks cleaner/in order.
Changes:

Put Reddit Links at the top of each category then specifically for HD Streaming Section, Ordered description from Unique Design to Basic Streaming

Thanks :) you might want to rebase as I've removed a lot of capitalisation that wasn't needed. Can you make sure you only capitalise proper nouns, acronyms, and the first letter of each description?


[PE-D][Tester B] UG does not mention how to unpin a project, issue and clients

e.g. Didn't mentioned about how to unpin the project while it actually using the same command to unpin

Labels: type.DocumentationBug severity.Medium
original: eesung00/ped#9

Duplicate with #187


Add pysoundfile to requirements

Closes: #76
Topic: pip_pysoundfile

Reviews in this chain:
└https://github.com/riffusion/riffusion/pull/87 Add pysoundfile to requirements

#
head
base
diff
date
summary

0
d4838e14
75c67e1e
diff
Jan 14 22:16 PM
1 file changed, 1 insertion(+)


Adding Linked Accounts with the same first and last names but totally different domains does not work.

Azure Data Studio Version: 1.41.2
OS Version: Windows 11

Steps to Reproduce:

Have an account already linked to Azure Data Studio
Try to link an account with the same name but different domain ex<EMAIL_ADDRESS>vs<EMAIL_ADDRESS>Azure Data Studio will think you are adding an already added user and will therefore do nothing.
Cry

Does this issue occur when all extensions are disabled?: Yes/No

Hi @roryteas
Could you please validate the behavior with latest insiders and let us know if it continues to exist?
https://github.com/microsoft/azuredatastudio#try-out-the-latest-insiders-build-from-main-branch
Thanks!

Works perfect.
Thank you,
Cheers
Rory
On Tue, 21 Mar 2023, 3:41 pm Cheena Malhotra, @.***>
wrote:

Hi @roryteas https://github.com/roryteas
Could you please validate the behavior with latest insiders and let us
know if it continues to exist?
https://github.com/microsoft/azuredatastudio#try-out-the-latest-insiders-build-from-main-branch
Thanks!
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/azuredatastudio/issues/22154#issuecomment-1477203070,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AYUP2OYFNK4W2Y3RWWHM7JLW5EINXANCNFSM6AAAAAAVQP5NOY
.
You are receiving this because you were mentioned.Message ID:
@.***>

Thanks for confirming, it will be available in the April release (1.43)
Closing the issue as resolved.


Dawn/Dusk Hooks?

I need to run a script (actually hit a REST WWW site) to start and stop my dew heater. Is there a preferred method to trigger this hit using the allsky software or should I investigate another script that calculates sunrise/sunset times?

Nevermind, I found the sunwait documentation.


Bug: Bud HMR not working as expected outside of front page

Terms

[X] I have read the guidelines for Contributing to Roots Projects
[X] This request is not a duplicate of an existing issue
[X] I have read the docs and followed them (if applicable)
[X] I have seached the Roots Discourse for answers and followed them (if applicable)
[X] This is not a personal support request that should be posted on the Roots Discourse community

Description
What's wrong?
From a yarn dev session, updates made to assets (at least stylesheets) aren't applied to the proxy session correctly unless you're on the home page
Steps To Reproduce

yarn dev
Visit http://localhost:3000/sample-page/
404 on the hot update json file

Expected Behavior

Hot update json file shouldn't 404 outside of the front page
Updates to assets should be applied in the Bud proxy session

Actual Behavior
Failed to load resource: the server responded with a status of 404 (Not Found)

:3000/sample-page/app.34c442a9dc0b3adc14e3.hot-update.json:1

Relevant Log Output
No response
Versions
10.0.0-beta.2

fixed as of bud v5.1.0 (#2952) with the latest acorn (#2953)

@retlehs I'm having this issue in a new Sage project v10.1.3

@zchlm prob need to bump to bud 5.7.2


modify adUnit infomation

Type of change

[ ] Bugfix

[ ] Feature

[ ] New bidder adapter

[ ] Updated bidder adapter

[ ] Code style update (formatting, local variables)

[ ] Refactoring (no functional changes, no api changes)

[ ] Build related changes

[ ] CI related changes

[ ] Does this change affect user-facing APIs or examples documented on http://prebid.org?

[x] Other: Documentation (about Test Parameters) is updated.

Description of change

In ssp_genieeBidAdapter.md , we modify Test Parameters content.

Other information

Displaying test is executed in https://another.geniee.jp/test/murano/Reproducts/PrebidTest.html?pbjs_debug=true .


receiving numerious warnings on install

npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to<EMAIL_ADDRESS>as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
npm WARN deprecated<EMAIL_ADDRESS>graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to<EMAIL_ADDRESS>as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR
gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR
code-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance
xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance
gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR
SOLINK_MODULE(target) Release/.node
CXX(target) Release/obj.target/fse/fsevents.o
SOLINK_MODULE(target) Release/fse.node

Could you please post the specs of your system? I'm running a OSX and Ubuntu 16.04 LTS both running node v5.5.0 and seem working fine

max osx 10.11.4 node 6.1

The issue was in set version for chimp in package.json.
I just publish version 1.1.0 who get the lasted version from chimp.js thanks to *


Fix LoadableByAddress to handle convert_functions.

Handle function_ref -> convert_function -> thin_to_thick.
Fixes rdar://problem/35059942 Failed - Lark, 3.0, Swift Package - Source Compatibility Suite (master)

@swift-ci smoke test and merge.


Static sparsity

It should be self-explanatory mostly apart from the change of torch.view to torch.reshape in MagnitudePruner due to error RuntimeError: view size is not compatible with input tensor's size and stride (at least one dimension spans across two contiguous subspaces). Use .reshape(...) instead. Functionality should be the same but for efficiency maybe we could try with view and then use reshape exceptionally?

oh and can rebase on main too now


Wait until location permission is granted

I need a way to poll when I call bluetooth.requestCoarseLocationPermission() to know when the user has allowed or rejected the request.

I recommend looking at https://github.com/NathanaelA/nativescript-permissions

There's this


bug(syntax): fypp highlighting breaks with derived types

Is there an existing issue for this?

[X] I have searched the existing issues

Description
I noticed fypp support has recently been added, thanks a lot!! I understand it's still new, but I've noticed a little bug:

First (I suspect this is something to do with my configuration?) if my file extension is .fpp then it looks like nothing is recognised, there are red squiggles everywhere (I have it configured for Fortran). If I rename it to have .fypp extension and don't change anything else, suddenly it's fine.
If I have a derived type that uses the preprocessor, then any code that comes after that derived type loses all syntax highlighting.

In the attached screenshot, all the highlighting goes back the way I expect it to be if I:

rename to .fypp
remove the derived type

Screenshots

Code Example
program highlighting_eg
    use iso_fortran_env, only: sp => real32, dp => real64
    implicit none
    #:for dtype in ['real', 'complex']
    #:for prec in ['sp', 'dp']
    ${dtype}$(${prec}$) :: a_${dtype}$_${prec}$
    #:endfor
    #:endfor

    #:for dtype in ['real', 'complex']
    type literally_anything_${dtype}$_t
    endtype literally_anything_${dtype}$_t
    #:endfor

    contains

    subroutine print(arg)
        real, intent(in) :: arg
        print*, arg
    end subroutine print
end program highlighting_eg

Fortran Version (Free/Fixed Form)
Free Form e.g. F90+
Version of Modern Fortran
v3.2.0
Version of Visual Studio Code
v1.72.2
Platform and Architecture
Linux (OpenSUSE)
Additional Information
I noticed my other issue got sent into discussion. Should this also be there?

So the main thing you noticed is a Duplicate issue of https://github.com/fortran-lang/vscode-fortran-support/issues/617. I will not close this just yet as a duplicate because I want to check what you mentioned about the extensions. That is strange indeed.

I am not able to reproduce the behaviour you pointed out. I was able to get fypp diagnostics for the .fpp file. Is there something else I should be doing to recreate your issue?


documentation: csv.Reader missing default field values

https://golang.org/pkg/encoding/csv/#Reader
Only the Comma field's default value is documented. Why not document the rest as well?

An undocumented default is always assumed to be the zero value.  Nothing special about this case.


test_cfmodel.py cause segmentation fault on MacOS

Hi there,
I've been following the contributor's guide and started off by running tests locally before modifying the code in any way. I'm getting the following error:
(env) (base)  ~/Documents/code/CARLA/ [main] make test
env/bin/python -m pytest test/*
========================================================================================== test session starts ===========================================================================================
platform darwin -- Python 3.7.10, pytest-6.1.2, py-1.11.0, pluggy-0.13.1
rootdir: /Users/FA31DU/Documents/code/CARLA
collected 117 items

test/test_api.py ....                                                                                [  3%]
test/test_autoencoder.py .....                                                                                [  7%]
test/test_benchmark.py .......                                                                                [ 13%]
test/test_causal_recourse.py .                                                                                [ 14%]
test/test_cfmodel.py Fatal Python error: Segmentation fault

Thread 0xFatal Python error: make: *** [test] Segmentation fault: 11

I'm using MacOS and see you're running CI on Ubuntu so it might just be OS-related. But thought I'd flag anyway and check if you've come across this in the past?

I have never seen that before.
Did you try to isolate the error? Maybe if it's one particular method I can get an idea where the problem might be coming from.
If it is OS-related, I can't reproduce it and that would make it difficult to fix myself.