[FancyZones] Enable to manually zone child windows

Summary of the Pull Request
What is this about?
Enable manual (using hotkey and shift+drag) zoning of child windows and do not keep them in zone app history.
PR Checklist

[x] Applies to #1445 ~#2834~
[x] CLA signed. If not, go over here and sign the CLA
[x] Tests added/passed
[ ] Requires documentation to be updated
[ ] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

Tested, it works as expected, but I suggest a code refactoring to remove the NewlyCreatedWindow from IsInterestingWindow

Tried with Word's navigation pane and VS's 'Solution Explorer'.
'Solution Explorer' could be snapped to a zone and doesn't change app-zone-history as expected.
'Navigation pane' is not allowed to be snapped to a zone for me.

@SeraphimaZ
"Word's navigation pane" is this one?

@SeraphimaZ
"Word's navigation pane" is this one?

I used the same as in this comment.
https://github.com/microsoft/PowerToys/issues/2834#issuecomment-651222557

OK, I've postponed https://github.com/microsoft/PowerToys/issues/2834 to 0.22, we can merge this.


TINKERPOP-1096 TINKERPOP-1097 Session Aliases, Console Sessions and Remote Console

https://issues.apache.org/jira/browse/TINKERPOP-1096
https://issues.apache.org/jira/browse/TINKERPOP-1097
This PR introduces several things:

SessionedClient.alias() is now implemented so that you can do aliases on a session-based connection
The console's :remote connect now allows you to append "session" to the end of it so that it starts that remote with a session
The console now has :remote console which allows the console to be put into a mode where all scripts are sent to remote and the :> is no longer required

Tested the console manually in an abundance of ways but here's an example:
gremlin> :remote connect tinkerpop.server conf/remote.yaml session
==>Connected - localhost/<IP_ADDRESS>:8182-[98bc7cf9-1c7b-451a-acbd-124a53a811d3]
gremlin> :remote config alias a g
==>a=g
gremlin> :remote console
==>All commands will now be sent to Gremlin Server - [localhost/<IP_ADDRESS>:8182]-[98bc7cf9-1c7b-451a-acbd-124a53a811d3] - type ':remote console' to exit
gremlin> x = 1
==>1
gremlin> y = 2
==>2
gremlin> x + y
==>3
gremlin> a.V()
==>v[0]
==>v[1]
==>v[3]
gremlin> :remote config alias b g
==>b=g
gremlin> b.V()
==>v[0]
==>v[1]
==>v[3]

Note that this is a non-breaking change. It is completely compatible with what we had before and the :> still works as it did before. This might yet be useful for some users as they might want to work with remote data in a local way and mix local/remote evaluations. Also, some plugins won't work well without it - like the gephi plugin.
Builds/tests nicely with: mvn clean install && mvn verify -pl gremlin-server,gremlin-console -DskipIntegrationTests=false -DincludeNeo4j
VOTE +1

VOTE +1. This is baller.

It even supports multi-line scripts! Epic.
VOTE: +1


Highlight the need for lat/lon GeoPandas in Quick Start tutorial

First of all, thanks for your work!
I'm starting using the library, and I spent quite some time to figure out that my GeoPandas data should be in lat/lon coordinates.
I know there's a dedicated jupyter notebook for projection and geospatal data, but I'm expecting this important information to be in the QuickStart tutorial, at least with a link to the related notebook.
Maybe the solution is to embed the notebook in the documentation website (via iframe)? I was a little lost after entering the tutorial, I think this is why it took me longer than usual to find the info I needed.

I'm starting using the library, and I spent quite some time to figure out that my GeoPandas data should be in lat/lon coordinates.
I know there's a dedicated jupyter notebook for projection and geospatal data, but I'm expecting this important information to be in the QuickStart tutorial, at least with a link to the related notebook.

Sure, that's a good idea. I've gone ahead and added a comment on that to QuickStart.ipynb.

Maybe the solution is to embed the notebook in the documentation website (via iframe)? I was a little lost after entering the tutorial, I think this is why it took me longer than usual to find the info I needed.

I'm open to ideas about how the documentation can be improved, but I don't think embedding the notebook in the website is a good idea. It's probably not possible anyway—I'm 80% sure that nbviewer has external iframe embedding turned off (and if it doesn't, it frankly should).


[AutoRelease] t2-rdbms-2024-07-12-09599(can only be merged by SDK owner)

https://github.com/Azure/sdk-release-request/issues/2048
Recording test fail, detailed info is in pipeline log(search keyword FAILED)!!!
https://dev.azure.com/azure-sdk/internal/_build?definitionId=982

issue link:https://github.com/Azure/sdk-release-request/issues/2048


fix: added fix for missing fs error

added fix for missing fs issue in web build
updated version to 1.16.1

done @sunil-lakshman


Control on resize state  while change the screen with and open the fullscreen

Hi  thx again for your support
I m using the solution for keep the zoom : http://codepen.io/iangilman/pen/BWKKxQ
my question is about the resize
how can I control the resize to support responsive or similar to that, because I have 2 problem
1- if I open the full screen  the image is looking bad , i guess cause of the autoResize = false ( but if i split the screen to be with 2 images . and then open the full screen its looks good
2- If i open the chrome debugger for second or change the width of the browser I have to refresh the page to fix it . (which it can not be done for example on the full screen mode)
how can I fix or work with the resize situation
btw . when open the full screen on chrome its looks like it close and then open again very fast, it can be fixed ?
.
thanks

Yes, you'll need to handle resizing yourself. This should do it:
$(window).on('resize', maintainZoom);

I'm not sure if there's anything that can be done about the little flicker on full screen on Chrome. I don't think it's actually closing and opening again, though.

@iangilman  thanks , i will try to play with
do you know how to get rid of unnecessary animations when open the 2 images , and now  the image came from top and "jump" .  I m trying to figure it out but did not mange
what i m trying to achieve is just to show the image maybe only with fadein
thx

You're saying it triggers for both going into fullscreen and leaving fullscreen? It's true, that's what that event does. You can take a look at the event object it passes you and look at its fullscreen property to know if you're entering or exiting.

Yes but how can I fix  the issue with the resize in the full screen .
Cause I get the console.log when I open the full screen
Thx :)

I'm sorry, I can't reproduce the full screen issue with http://codepen.io/iangilman/pen/BWKKxQ ...I go into full screen and then come back out with both one image or two, and they always look fine when I get back. I tested in Mac Firefox and Chrome. Seems like everything works?

yes my mistake , its working! thx a lot

Hi its not working when you on full screen on the browser and then click on full screen button and you will see the error - very strange :)  did not manage to fix it

It may be a legitimate timing issue. Try a setTimeout of 1 rather than 200 and see if it still works. If so, it's just a matter of exiting the current call frame, and is a fine solution.


WearOS: Disable swipe-to-dismiss gesture on a destination.

Hi.
Im using a simple approach of destinations on a wear app. As I have one destination showing a map, the swipe-to-dismiss (in fact to go back) gesture collides with the gestures of the map, and that is why i want to turn of this gesture on one destination. But i cannot figure out how I can achive this.
Simple setup:
val engine = rememberWearNavHostEngine()

WatchTheme {
    Scaffold() {
        DestinationsNavHost(
            engine = engine,
            navGraph = NavGraphs.home,
        )
    }
}

Since 1.3.0 androidx.wear.compose:compose-navigation has a userSwipeEnabled: Boolean which pretty much does what I want (as far as I understood)
https://androidx.tech/artifacts/wear.compose/compose-navigation/1.3.0-source/androidx/wear/compose/navigation/SwipeDismissableNavHost.kt.html
Unfortunately this api is not reflected in the wear engine of compose destination (and I guess the androidx.wear.compose:compose-navigation is set to 1.1.2)
Edit:
Found on https://developer.android.com/jetpack/androidx/releases/wear-compose#1.3.0

Recommendations for implementation
If your app allows users to pan around the screen's content, such as in a map-based app, turn off swipe handling by setting userSwipeEnabled to false in the SwipeDismissableNavHost composable, and include a button that allows users to go to the previous screen.

Are there some recommendations (or hints ;) ) to achieve my goal?
Thanks for your great library to make compose navigation easier!

@raamcosta Any ideas how i could use userSwipeEnabled and still using DestinationsNavHost ?

Hi!
To be honest our wear implementation was contributed by someone else and I haven’t prioritised wear artifact in a long while.
I’m also not up to date in wear navigation 😬
I will try to update wear dependencies soon, but no promises.

Hi @matecode !
I've updated wear dependencies for v2. If this is needed for you, please check v2's migration guide and try it! :)
https://composedestinations.rafaelcosta.xyz/migrating-to-v2

@raamcosta Great, thanks for your fast work!
I will try it asap. 🦜


Can't replicate db from another node

Good morning,
I'm trying to spin up OrbitDb for the first time in Node.js.
First I tried IPFS, installed as npm module in two computers: in one computer I added a file (via a .js file), and in the other one I retrieved it, it worked pretty well and suprisingly fast, gotta admit.
So I assumed that the 2 computers are able to find each other pretty quickly.
Then, I added OrbitDb, created a simple keyvalue, but I can't manage to replicate it on the other side!
This is the code I used in the "write" node:
const IPFS = require('ipfs')
const OrbitDB = require('orbit-db')

async function main() {
	const ipfs = await IPFS.create()
	const orbitdb = await OrbitDB.createInstance(ipfs)

	const db = await orbitdb.keyvalue('first-database');
	console.log(db.address.toString());
	await db.load();

	await db.put('key1', 'test');
}

main()

And this is the code in the other PC:
const IPFS = require('ipfs')
const OrbitDB = require('orbit-db')

async function main() {
	const ipfs = await IPFS.create()
	const orbitdb = await OrbitDB.createInstance(ipfs)

	const db = await orbitdb.keyvalue('/orbitdb/zdpuAoxx2Ag97s2GGq9EocJF6iucXivpeGzKTvFdJB4p6RskH/first-database')
	console.log(db.address.toString())
	await db.load()

	db.events.on('replicate', (address) => {
		console.log('Begin to replicate...')
		console.log(address)
	});

	db.events.on('replicate.progress', (address, hash, entry, progress, have) => {
		console.log('Progress: ' + progress)
	});

	db.events.on('replicated', (address) => {
		console.log('Replicated!')
		console.log(db.get('key1'))
	});
}

main()

The events "replicate", "replicate.progress" and "replicated" are NEVER fired, so it doesn't even try to replicate the other address at all.
What am I doing wrong, what am I missing?
Thank you!

Hi Zorinik,
replicating stores has always been somewhat difficult (at least for me).
It's good that you know the nodes can transfer files/talk to each other.
I think the issue with this is that discovering pubsub peers, in my experience, can be pretty iffy compared to discovering content on the network.
Some things that can help is adding some more discovery methods to your ipfs node. A common one is websocket-star. You can see partly how to do this in this custom libp2p example.
I'd also be interested in any results using pubsub peer discovery or stardust.

I'm struggling with the same problem...I created a quick'n dirty Proof of Concept to try the replication feature of Orbitdb (after I struggled with tools like the control-center).
That PoC has a producer who creates the orbitdb and adding periodically some dummy records. Furthermore, there's a consumer that just wants to listen to the added records. Each of them runs its own IPFS node. Running both on my local machine works like a charm. Then we tried it remotely on different computers in different global regions (no cloud hosting)...and it didn't work. I'm no network expert, and I know that is something about the configuration, but I really don't know what do now. Any help is highly appreciated.

On your consumer, take the Id output here by the producer: https://github.com/ohager/orbitdb-remote-poc/blob/master/producer.js#L34
and run this on the consumer: await ipfs.swarm.connect('/ipfs/<producer id here>')
I see you are using js-ipfs, possibly try using go-ipfs via ipfsd-ctl and go-ipfs-dep
The dht efficiency has improved beyond measure in the latest stable release of go-ipfs (v0.5.1 as of writing).

thanks for fast and concise response. I'll try ASAP. :pray:

Try this version of the demo. I think it's slightly more up to date: https://ipfs.io/ipfs/Qma4jzYSZkzUt4Tz4Pxr7KGupHCViaFNZh13bsEhovPkZp/

Hi @phillmac. I just tried what you suggested...running on my local machine works fine, but we got the following error:
(node:6620) UnhandledPromiseRejectionWarning: AggregateError:
    Error: No transport available for address /p2p/QmdkhnnKfGD9dWteVP9so1Bfi36FZXLbueDwduMHNiquNy```

WARNING
I'm no longer recomending upgrading to > 0.4.23 because of broken p2p-circuit relay functionality
In fact I recommend sticking with 0.4.23 as the last working version. see https://github.com/ipfs/go-ipfs/issues/7433

I'm still unable to solve the issue; I tried the last provided solution (ipfs.swarm.connect), but I get the same error as of @ohager :
(node:11344) UnhandledPromiseRejectionWarning: AggregateError:      Error: No transport available for address /p2p/QmRzzfyk9Ckwg6pwTTiyywa7fFx2icU9QtHNXDYpCutadg         at TransportManager.dial (C:/Users/zorin/Desktop/Siti/healthcare-app/node_modules/libp2p/src/transport-manager.js:83:21)         at DialRequest.dialAction (C:/Users/zorin/Desktop/Siti/healthcare-app/node_modules/libp2p/src/dialer/index.js:140:36)         at C:/Users/zorin/Desktop/Siti/healthcare-app/node_modules/libp2p/src/dialer/dial-request.js:58:29         at async C:/Users/zorin/Desktop/Siti/healthcare-app/node_modules/p-some/index.js:53:19     at maybeSettle (C:\Users\zorin\Desktop\Siti\healthcare-app\node_modules\p-some\index.js:31:11)     at C:\Users\zorin\Desktop\Siti\healthcare-app\node_modules\p-some\index.js:69:23

@Zorinik For nodejs, you need to enable listening on TCP ports in your config. e.g.
"Addresses": {
"Swarm": [
"/ip4/<IP_ADDRESS>/tcp/4001"
]
}
This will enable the TCP transport and fix the no transports error

Still no luck, same error; this is the code I use; what am I getting wrong?
const ipfs = await IPFS.create({
   "config": {
   	"Addresses": {
   		"Swarm": [
   			"/ip4/<IP_ADDRESS>/tcp/4001"
   		]
   	}
   },
   relay: {enabled: true, hop: {enabled: true, active: true}},
   pubsub: {enabled: true},
   EXPERIMENTAL: {pubsub: true, ipnsPubsub: true}
})
await ipfs.swarm.connect('/ipfs/QmRzzfyk9Ckwg6pwTTiyywa7fFx2icU9QtHNXDYpCutadg')
const orbitdb = await OrbitDB.createInstance(ipfs)

Both IPFS and Orbit are updated to their last version.

@phillmac I saw your discussion in https://github.com/ipfs/go-ipfs/issues/7433 - I still had no luck to make it work. I understood that go-ipfs nodes take advantage of DHT, but it was mentioned that DHT does not work in Browsers...does it mean it might work using nodejs, or is it not implemented in js-ipfs at all?
Is there some way to get in contact with you like discord? Such, you could help out directly. It's all pretty confusing to me. And we are building a product which relies on that feature, otherwise I need to look out for working alternatives.

@ohager please join us on ]Gitter](https://gitter.im/orbitdb/Lobby), which is bridged to Discord. It would be great if we could both solve the problem and come to come sort of consensus on the proper updated solution

@phillmac @Zorinik @tabcat
I had some time today for further stuff and made it work, such that I can go on using it in my project.
For me it's sufficient to set the Bootstrap addresses accordingly. Even the issue with connection loss on each side was solved.... it's all a question of correct configuration. For non-local communication port forwarding may be necessary.
I created a demo repo (https://github.com/ohager/orbitdb-remote-poc) to demonstrate the replication and pubsub stuff. Works fine now!
From my perspective this issue can be closed, but the final decision remains to @Zorinik .  Thanks for your attention and help.

@ohager Hello,
I tried your git and it worked but is it possible to do that in the browser version? Since I tried and it seems in browser we cannot make socket server.

@am2222 tbh, I don't know. :shrug:

Please try with latest version of OrbitDB. If problem persists, please re-open this issue.


ISSUE: bq_load_timestamp corrupted

Hi Sam,
Description:
Latest release 0.18 which fixed event time watermarking may have corrupted the BQ load timestamp.
The error below is returned by BQ indicating an invalid timestamp in bq_load_timestamp (note: the streaming queries that populate this DO NOT use watermarking BTW).
I now need to add EXCEPT(bq_load_timestamp) on my queries to stop them erroring (will need to patch these in the future).  Refer below:

For some tests on streams that DO use the new watermarking feature, the timestmap on the sink tables is the beginning of epoc rather then the clock time.

Let me know if you need anymore info
Kurt

@kurtmaile should be all good now on v 0.1.9

Thanks heaps - I tried testing patching the old BQ timestamps and go this error - seems I cant do update statements on partiton tables yet? Ekk.....


Dragging Across Multiple Lists

Is it currently possible to drag & drop between different levels of nested lists? That is; if I have a list within another list, is it possible to drag an item from the parent list into the child list and vice versa? If not, how much work would it take to achieve this?
Taking this concept even more abstract, would it be possible to drag and drop between completely separate lists?

No. Dragging between lists is not possible. But instead of nesting lists, why not just make the nested items smaller to create the look of a nested list?


Unable to lock car, 'NoneType' object has no attribute 'completed'

Region and Brand of car
2024 NA Kia Niro EV
Describe the bug
Unable to lock car, "Failed to call service lock/lock. 'NoneType' object has no attribute 'completed'"
Debug logs if an error occurred
During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 238, in handle_call_service
    response = await hass.services.async_call(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2067, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2104, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 272, in handle_service
    return await service.entity_service_call(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 878, in entity_service_call
    single_response = await _handle_entity_call(
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 948, in _handle_entity_call
    result = await task
             ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/lock/__init__.py", line 107, in _async_lock
    await entity.async_lock(**_add_default_code(entity, service_call))
  File "/config/custom_components/ha_kia_hyundai/lock.py", line 47, in async_lock
    await self.hass.async_create_task(
  File "/config/custom_components/ha_kia_hyundai/vehicle.py", line 33, in mark_used_wrapper
    await func(*args, **kwargs)
  File "/config/custom_components/ha_kia_hyundai/vehicle.py", line 218, in lock_action
    await self.api_cloud.lock(vehicle=self, action=action)
  File "/config/custom_components/ha_kia_hyundai/api_cloud_us_kia.py", line 33, in request_with_active_session_wrapper
    return await func(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/ha_kia_hyundai/api_cloud_us_kia.py", line 324, in lock
    await self._lock(vehicle)
  File "/config/custom_components/ha_kia_hyundai/api_cloud_us_kia.py", line 64, in current_action_wrapper
    if not self._current_action.completed():
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'NoneType' object has no attribute 'completed'

To Reproduce
Steps to reproduce the behavior:

Go to default dashboard
Click on lock

Expected behavior
Car locks
Screenshots

Additional context
Add any other context about the problem here.

thanks so much for writing this up, I missed a typo introduced in #103's quick fix; this is fixed in https://github.com/dahlb/ha_kia_hyundai/commit/0508c38c6bd689f33bdf9d653722da8184b836a1 release 1.8.6

Thanks! I can confirm it’s fixed after upgrading.


Added LaSalle College Institute Vancouver

Added "LaSalle College Institute - Vancouver" for<EMAIL_ADDRESS>

@jon-bogert Please provide us with:

an URL of a page on the official website where the school offers an IT-related long-term (>1 year) course
a proof, which shows that the school recognizes the domain you are submitting as an official email domain for the students.

You can provide us with any of the following as the proof:

A copy of instruction (a hard-copy or electronic one) given to you by the school that tells you to use an email address in this email domain
An URL of a page at the official school website that says that students use this email domain
A reference to a recognized journal where an article was published by someone from the school, with explicit affiliation to the school, and e-mail address from the email domain
A WHOIS data that link the email domain to the school somehow
A copy of official letter from the school representative saying that the school provides e-mail addresses in this domain to the students
Anything else that can prove this fact in similar way, i.e. can be verified independently.

Hello,
Here is the link to my school’s info for the 3 year Bachelor of Science in
Game Programming Degree I am enrolled in:
https://www.lasallecollegevancouver.com/vfx-game-design/game-programming-bachelor
I have also attached a screenshot of the email I received from the
University when my school email was created.
Thanks,

Jon Bogert

On Thu, Feb 16, 2023 at 12:43 PM Philip Torchinsky @.***>
wrote:

@jon-bogert https://github.com/jon-bogert Please provide us with:

an URL of a page on the official website where the school offers an
IT-related long-term (>1 year) course
a proof, which shows that the school recognizes the domain you are
submitting as an official email domain for the students.

You can provide us with any of the following as the proof:

A copy of instruction (a hard-copy or electronic one) given to you
by the school that tells you to use an email address in this email domain
An URL of a page at the official school website that says that
students use this email domain
A reference to a recognized journal where an article was published
by someone from the school, with explicit affiliation to the school, and
e-mail address from the email domain
A WHOIS data that link the email domain to the school somehow
A copy of official letter from the school representative saying that
the school provides e-mail addresses in this domain to the students
Anything else that can prove this fact in similar way, i.e. can be
verified independently.

—
Reply to this email directly, view it on GitHub
https://github.com/JetBrains/swot/pull/16583#issuecomment-1433689797,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARSDIARNXAEZINWJ4BX5YILWX2GN3ANCNFSM6AAAAAAU4DBEZI
.
You are receiving this because you were mentioned.Message ID:
@.***>

@jon-bogert Thank you for your patience while waiting for a review and processing your request. Pull request merged.


camel-jbang - Upgrade to Camel 3.20.0

Yes when the 3.20 is GA and in maven central then we can merge


MIPv6 Support

Hello,
To run nodes with IPv6 Mobility inside Docker, is necessary that the host kernel have some kernel flags enabled.
With this modules, we can run mipv6d inside containers without problems.
The list of modules activated is documented here: http://git.umip.org/umip/umip.git/plain/INSTALL.kernel
I tested and works great.
PD: I don't know if CONFIG_EXPERIMENTAL=y is deprecated or not, because it not appeared in the built kernel.
Salu2

Hello.
I rebuild the config more clean. I downloaded the proper version and use menuconfig instead of direct changes.
Tested and still working the MIPv6.
Salu2

Looks good, thanks! :+1:


bash test.sh

Bash test How should I write the parameters after sh-- exp_ dir ./ experiments_$ {degradation}/${model}/${exp_id}
--mode test
--model ${model}
--opt test. yml
--gpu_ id ${gpu_id}
Can you give me an example? There is no problem with my path. It keeps reminding me that I can't find the file

Hello, I met the same problem and I just modified the code as below:
python ./codes/main.py
--exp_dir ./experiments_BD/FRVSR/001/
--mode test
--model FRVSR
--opt test.yml
--gpu_id ${gpu_id}


💡[Feature]: Code for optimizer

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
The work I propose involves:
Implementing key optimizers such as Stochastic Gradient Descent (SGD), Adam, RMSprop, and others from scratch. This would allow for comparison between different optimization algorithms in your models
Documenting each optimizer and explaining their strengths, weaknesses, and use cases, making it easier for users to choose the right one.
Use Case
1.model performance tuning
2.Better understanding on choosing optimizer
Benefits
No response
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

@sanjay-kv please do check my idea and if you find this satisfactory please assign this to me.


install as service

hi,
can you provide this as a windows service.
the idea. we are running tests in teamcity, it would be super cool to enalbed disable fuslog and be able to export the data and make it availabel during build. So users can quickly investigate whats going on
thanks

Hi,
what an idea - but I think this does not fit well. You see, Fusion++ is an UI-centered app. There's no headless mode or anything like that. Running this as a Windows Service seems wrong to me (especially with all those megabytes of DevExpress UI controls, etc.).
However, I want to encourage you to build an own service. You can use the classes I wrote to control the .NET Assembly Log registry keys and parse the logs if you want.
To record a session, simply use this code:
var session = new FusionSession(new RegistryFusionService());
session.Start()
...
session.Stop();

This handles everything you need in the Windows Registry.
To parse the logs afterwards, use:
var logStore = new TransparentLogStore("PATH-GOES-HERE");
var parser = new LogFileParser(new LogItemParser(), new FileReader(), new LogFileService(logStore));
parser.Progress = (current, total) => ... // do anything here if you want progress reporting
var logs = await parser.ParseAsync();

Hope this helps.

Ok thanks. Yes what i had in mind was stripping the all thing and get only
the needs parts in. But could u at least provide a nuget dev package api
for third partys to consume. This is not  only usefull in windows service
but pretty much any app.
Like record and stop and export
Thanks
On Tue, 21 May 2019, 23:14 Andreas Wäscher<EMAIL_ADDRESS>wrote:

Closed #7 https://github.com/awaescher/Fusion/issues/7.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/awaescher/Fusion/issues/7?email_source=notifications&email_token=AAH6HSEWMVFEWBQRQ7SL6LLPWRJZZA5CNFSM4HOJKZL2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGORSA73IQ#event-2357329314,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAH6HSFZV5WTTJUPSUTW3XDPWRJZZANCNFSM4HOJKZLQ
.

For an upcoming experiment, I extracted all the reusable Fusion++ logic to an .NET Standard library here.
I do not plan to make a package or anything. However you can use that lib from now on if you want.


Make join not ignore delimiter when working with ObjectLikeSequences

This fixes #184.

So this is succeeding in Travis against Node.js:0.10 and Node.js:0.11 (and on my local machine running Node v6.2.0), but failing against iojs with the following message:

2.3.4: If x is not an object or function, fulfill promise with x The value is true eventually-rejected:
Error: timeout of 200ms exceeded
at done (/home/travis/build/dtao/lazy.js/node_modules/mocha/lib/runnable.js:205:67)
at /home/travis/build/dtao/lazy.js/node_modules/mocha/lib/runnable.js:226:9
at onPromise2Fulfilled (/home/travis/build/dtao/lazy.js/node_modules/promises-aplus-tests/lib/tests/2.3.4.js:36:21)
at /home/travis/build/dtao/lazy.js/lazy.js:5193:26
at Immediate._onImmediate (/home/travis/build/dtao/lazy.js/lazy.js:5356:26)
at processImmediate [as _immediateCallback] (timers.js:371:17)

Odd.

Thanks!  As explained in 9d234a1, I've pulled in your commits anyway (just reverted the alternate implementation) because the tests seemed worth adding :)


VisibilityNotifier2D doesn't notifies as soon as it's out of viewport

Godot version: Built from master
VisibilityNotifier2D doesn't notifies as soon as it's out of viewport, there seem to be son kind of internal offset. It's the same for "exit_viewport" and "exit_screen" signal.
EDIT:
Here is a demo:
QuickTest.zip (Arrow keys to move the sprite/visibilitynotifier out the view)

I don't understand the issue correctly. Could you specify a bit more? It would be also helpful to provide an example project, if possible.

Sorry for the delay, I uploaded a demo. :)

I could reproduce it with the example project. It's weird because I had a similar demo I did around a month ago and there was no such issue. It may be a recent regression.

I've confirmed this behavior.  Oddly enough, if you are in windowed mode and resize the screen using your mouse, I am able to see correct behavior on some window dimensions.

This is intended behavior, VisibilityNotifier uses a hashed grid to quickly determine when something is near the screen, so it's really really fast even if you have thousands of objects moving. The downside is that it's approximate but not exact.
It is warranted that the notifier will always be visible when on the screen though. Maybe this should be documented..

Well, I wanted to remove bullets using this node, but I ran in the same problem. I wouldn't have an issue with the VisibilityNotifier2D being triggered AFTER it leaves the screen/viewport, but exit_screen, exit_viewport signals are emitted BEFORE leaving the screen/viewport in some cases.
I have a 1920x1080 px resolution project with stretch_mode set to 2d in the Project Settings. The bullets have VisibilityNotifier2D set to queue_free when signals are emitted. See the result in the attached gif.

I've hit the same issue when I've set my stretch mode to 2d with keep aspect: the VisibilityNotifier2D seemed to be offset as much as the viewport in relation to the window.
I've tried a quick fix (https://github.com/RandomShaper/godot/commit/13451dabf69cc94e19198168e0c586a698208a73). What this does is passing the viewport rect to the VisibilityNotifier2D positioned at (0, 0) before applying the transform.
Please test. I'm not sending a PR unless we are sure this works for every stretch mode and keep aspect setting. I'm pretty tired right now and I'm not very confident about this.

@RandomShaper I've tried your fix for 2.1 but it is not making any difference.
I don't think is an offset because it affects all sides on my tests (like if the notifier area is 3x bigger than it should).

In this topic there are two issues:

The notifiers being considered visible although they are not
actually inside the viewport, just when they get close.
This one is expected behaviour and can't be fixed. The engine only
guarantees the notifier is out-of-view when it's notified as being
so, but for the case of becoming visible it can notify before the
viewport is actually entered because of the optimizations used by
the implementation.
The other one is nodes being notified as no-longer-visible before
they actually leave the viewport, but this one only happens on one
edge because of the offset.
If you were able to see it, at the opposite edge they would need to
be even further than usual to be notified as no-longer-visible.
This is the one I'm trying to fix.

Which one are you talking about?
What we aim to fix here is not the size
El 06/03/2017 a las 15:13, eon-s escribió:

@RandomShaper https://github.com/RandomShaper I've tried your fix
for 2.1 but it is not making any difference.
I don't think is an offset because it affects all sides on my tests
(like if the notifier area is 3x bigger than it should).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/4803#issuecomment-284406489,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALQCttjZ7Z0_DWxb4pX9gmw-4NFAJFphks5rjBSMgaJpZM4ImF-V.

@RandomShaper ah, ok, I think that only got the first but for both, visible and not visible, on 2.1.2 and the fixed version.
Is weird because in one project I have noticed the offset and got almost perfect edge notifications but on another got the on/off screen notifications far from the edges (outside of the screen), no offset.
I will continue trying to see if I can trigger the offset and test the fix properly.

If you do this, you should probably create a more exact notifier class (or
a parameter to enable), with this change, and leave the old one alone.  The
less granular checks are proposed to be faster given large amounts of
objects (see above) at the expense of accuracy.
Perfect notifications probably fit a narrow use case and should be treated
as such.
On Mon, Mar 6, 2017 at 8:10 AM, eon-s<EMAIL_ADDRESS>wrote:

@RandomShaper https://github.com/RandomShaper ah, ok, I think that only
got the first but for both, visible and not visible, on 2.1.2 and the fixed
version.
Is weird because in one project I have noticed the offset and got almost
perfect edge notifications but on another got the on/off screen
notifications far from the edges (outside of the screen), no offset.
I will continue trying to see if I can trigger the offset and test the fix
properly.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/4803#issuecomment-284422674,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIWVfxR0MocKTGLl9f0j_M-OlH2ucqXFks5rjCHOgaJpZM4ImF-V
.

I was going to open my own issue, but it fits very well with the discussion here.
From a design standpoint, it seems like VisibilityEnabler2D should be very well suited for keeping track of a countably limited number of nodes that you want to keep in the hierarchy but not have running.
However, when I tried to implement it in a project (making enemies deactivate when off screen, I'm finding that they often can walk out of the scene without disabling, and that I sometimes have to not be one but two screens over (with a jumping camera that works in cells) before they deactivate. In short, it doesn't work as predicted out of the box, and I don't know that mine really qualifies as an "edge" case for the node.
The current workaround involves adding an Area2D to the camera and using that to manually disable the various properties, but it strikes me as hacky, and not ideal when there's a core class designed for that exact purpose
After investigating, it seems that it's possible that this is due to the above comment by @reduz about how VisibilityNotifier works, which is definitely a reasonable implementation for less countable use cases (like destroying offscreen projectiles in a bullet hell for instance).
I think a parameter for adding more precision is something that VisibilityNotifier2D needs. That kind of precision is not going to be needed with the kind of scalability that the current implementation offers, so I don't think a trade-off in that department is prohibitive.
Thoughts?

Configurable precision would be nice, but that may need to be applied project wide on VisualServer settings, depending on how this is working.

In that case, I'd think the grid hash for everything would have to either be less/more granular or replaced with a different less performant method? That definitely seems like a potentially big effect for this.

2x screens or more away is not how Visibility Notification should work!
I'm on 3.2 and I'm forced to do some hacky calculation that is not even near as performant.
If I do checks against camera positions, that is not always the correct way to tell a drawn rect position.
If I do against a player, then it's a hustle to make it null instance safe.

@nezvers It's OK for most use cases, is the thought, since it's performant (more of a heuristic).

If you do this, you should probably create a more exact notifier class (or
a parameter to enable)

think a parameter for adding more precision is something that VisibilityNotifier2D needs

2x screens or more away is not how Visibility Notification should work!

The cell size (i,e., the granularity of the detection) is 100 pixels. If you could provide a minimal reproduction project that does it as close as possible to your actual project, that'd help.

Ok, here it is. My game is 160x90 resolution and this imprecision is really problematic.
VisualNotificationBug.zip


[BUG] ImageSurface::create_for_data() should take a smaller lifetime than 'static for data

Bug description
use cairo::{ImageSurface, Format};

fn main() {
    let mut data = vec![255, 0, 0, 255];
    {
        let surface = ImageSurface::create_for_data(&mut data, Format::ARgb32, 1, 1, 4).unwrap();
        do_stuff_with(surface);
    }
    // surface is now dropped, data still lives, but create_for_data() doesn’t allow this.
}

Error
error[E0597]: `data` does not live long enough
  --> src/main.rs:6:53
   |
6  |         let surface = ImageSurface::create_for_data(&mut data, Format::ARgb32, 1, 1, 4).unwrap();
   |                       ------------------------------^^^^^^^^^--------------------------
   |                       |                             |
   |                       |                             borrowed value does not live long enough
   |                       argument requires that `data` is borrowed for `'static`
...
10 | }
   | - `data` dropped here while still borrowed

For more information about this error, try `rustc --explain E0597`.

Due to surfaces being reference counted, the data has to be 'static and must be owned by the surface. Everything else would be unsound.
There are unsafe constructors with less strict requirements if your code can ensure that the surface can't outlive the data, and you can also build abstractions with safe code that return you the data via a channel from Drop. There is an example for the latter in the gtk3-rs repo. The former should be relatively self explanatory.


Failed to check app setting propagation for SCM_DO_BUILD_DURING_DEPLOYMENT and ENABLE_ORYX_BUILD.

First observed yesterday, our deployment action is having some issues. We're using node.js, our action is based on this template.
After Client.updateAppSettingViaKudu is called and returns 204, we get stuck in a timeout / retry cycle for about 3 minutes. See Github job log below.
Run Azure/functions-action@v1
  with:
    app-name: REDACTED
    package: .
    publish-profile: ***
    slot-name: REDACTED
    respect-pom-xml: false
    respect-funcignore: false
    scm-do-build-during-deployment: false
    enable-oryx-build: false
  env:
    AZURE_FUNCTIONAPP_NAME: REDACTED
    AZURE_FUNCTIONAPP_PACKAGE_PATH: .
    NODE_VERSION: 10.x
Successfully parsed SCM credential from old publish-profile format.
Using SCM credential for authentication, GitHub Action will not perform resource validation.
Sucessfully acquired app settings from function app (with SCM credential)!
Will archive . into /home/runner/work/_temp/temp_web_package_47007169786336567.zip as function app content
Will use Kudu https://<scmsite>/api/zipdeploy to deploy since publish-profile is detected.
Setting SCM_DO_BUILD_DURING_DEPLOYMENT in Kudu container to false
Update using Client.updateAppSettingViaKudu
Response with status code 204
Warning: Failed to check app setting propagation for SCM_DO_BUILD_DURING_DEPLOYMENT, remaining retry 19
App setting SCM_DO_BUILD_DURING_DEPLOYMENT has not been propagated to Kudu container yet, remaining retry 19
Warning: Failed to check app setting propagation for SCM_DO_BUILD_DURING_DEPLOYMENT, remaining retry 18
...truncated...
Warning: Failed to check app setting propagation for SCM_DO_BUILD_DURING_DEPLOYMENT, remaining retry 1
App setting SCM_DO_BUILD_DURING_DEPLOYMENT has not been propagated to Kudu container yet, remaining retry 1
Warning: Failed to check app setting propagation for SCM_DO_BUILD_DURING_DEPLOYMENT, remaining retry 0
App setting SCM_DO_BUILD_DURING_DEPLOYMENT has not been propagated to Kudu container yet, remaining retry 0
Warning: App setting SCM_DO_BUILD_DURING_DEPLOYMENT fails to propagate to Kudu container
Setting ENABLE_ORYX_BUILD in Kudu container to false
Update using Client.updateAppSettingViaKudu
Response with status code 204
Warning: Failed to check app setting propagation for ENABLE_ORYX_BUILD, remaining retry 19
App setting ENABLE_ORYX_BUILD has not been propagated to Kudu container yet, remaining retry 19
Warning: Failed to check app setting propagation for ENABLE_ORYX_BUILD, remaining retry 18
App setting ENABLE_ORYX_BUILD has not been propagated to Kudu container yet, remaining retry 18
...truncated...
Warning: Failed to check app setting propagation for ENABLE_ORYX_BUILD, remaining retry 1
App setting ENABLE_ORYX_BUILD has not been propagated to Kudu container yet, remaining retry 1
Warning: Failed to check app setting propagation for ENABLE_ORYX_BUILD, remaining retry 0
App setting ENABLE_ORYX_BUILD has not been propagated to Kudu container yet, remaining retry 0
Warning: App setting ENABLE_ORYX_BUILD fails to propagate to Kudu container
Package deployment using ZIP Deploy initiated.
Deploy logs can be viewed at REDACTED
Successfully deployed web package to App Service.
Successfully updated deployment History at REDACTED
Response with status code 204
Response with status code 204
Response with status code 204

Here's some additional information.

The deploy itself seems to go as expected. But the retry cycle is significantly slowing down our releases.
We've observed this happening on both production & staging deploy slots.
We've observed this with both Windows & Linux Function Apps.
No similar issues are observed when deploying to the function app via VS Code (running in a dev docker container).
No changes were made to our workflow files since the last time it was working properly.

Here's a few things I've tried, to no effect.

Explicitly setting the scm-do-build-during-deployment and enable-oryx-build in the workfile (both true & false).
Knew it was probably unrelated, but tried tweaking the NODE_VERSION from 12.x to 10.x

I'd be happy to provide more information on request. Thanks for your help!

Seeing the same issue with a .NET Core 3.1 Function deployment. Wasn't seeing this a couple of weeks ago.

Also seeing the same issues on .NET 5.0 Function deploy.  I attempted most of the changes you did, I even changed those settings in Azure to see if it would read them from the function and skip setting them but no luck. It's adding a ton of time to our deploys.

Same here with a Python using this template and a brand new Azure Functions with Python runtime 3.8 (although other versions behave similar)

+1 - I can repro if I create the pipeline from the Azure Portal directly

+1 - Also experiencing the same issue.  Function deployment duration has slowed from 1 minute to 8 - 10 minutes.

+1 - We are also experiencing this issue, switching back to v1.3.2 fixes it.

This seems like a backend issue where the Kudu lite container is not able to pick up the app settings change in time.
I will reduce the retry count to 3 in the next release. Thanks for reporting the bug.

Not to sound negative bc I appreciate the issue getting attention but that doesn't sounds like it's fixing the actual problem. And all of us who are having the issue will still see increased build times (just not quite as bad, bc of 3 vs 10 retries).
Speaking only for myself, I would like to see the core issue get resolved or to have these attempts to apply settings removed altogether if they're not actually needed.

This seems like a backend issue where the Kudu lite container is not able to pick up the app settings change in time.
I will reduce the retry count to 3 in the next release. Thanks for reporting the bug.

Reducing the retry count will treat the symptom (delay in function app deployment) but not the root cause (settings not syncing with kudu container).
It is never successfully syncing these settings with the Kudu container, unless I revert to v1.3.2 as suggested above.
Thank you for looking into this!

I opened #90 as a bandage solution to limit the retries while a proper solution is figured out.

Can confirm that I am experiencing this issue as well. Azure Functions 3.1 new GitHub workflow.

Warning: Failed to check app setting propagation for SCM_DO_BUILD_DURING_DEPLOYMENT, remaining retry 10
App setting SCM_DO_BUILD_DURING_DEPLOYMENT has not been propagated to Kudu container yet, remaining retry 10
Warning: Failed to check app setting propagation for SCM_DO_BUILD_DURING_DEPLOYMENT, remaining retry 9
App setting SCM_DO_BUILD_DURING_DEPLOYMENT has not been propagated to Kudu container yet, remaining retry 9
Warning: Failed to check app setting propagation for SCM_DO_BUILD_DURING_DEPLOYMENT, remaining retry 8
App setting SCM_DO_BUILD_DURING_DEPLOYMENT has not been propagated to Kudu container yet, remaining retry 8
Warning: Failed to check app setting propagation for SCM_DO_BUILD_DURING_DEPLOYMENT, remaining retry 7
App setting SCM_DO_BUILD_DURING_DEPLOYMENT has not been propagated to Kudu container yet, remaining retry 7
Warning: Failed to check app setting propagation for SCM_DO_BUILD_DURING_DEPLOYMENT, remaining retry 6
App setting SCM_DO_BUILD_DURING_DEPLOYMENT has not been propagated to Kudu container yet, remaining retry 6
Warning: Failed to check app setting propagation for SCM_DO_BUILD_DURING_DEPLOYMENT, remaining retry 5
App setting SCM_DO_BUILD_DURING_DEPLOYMENT has not been propagated to Kudu container yet, remaining retry 5
Warning: Failed to check app setting propagation for SCM_DO_BUILD_DURING_DEPLOYMENT, remaining retry 4
App setting SCM_DO_BUILD_DURING_DEPLOYMENT has not been propagated to Kudu container yet, remaining retry 4
Warning: Failed to check app setting propagation for SCM_DO_BUILD_DURING_DEPLOYMENT, remaining retry 3
App setting SCM_DO_BUILD_DURING_DEPLOYMENT has not been propagated to Kudu container yet, remaining retry 3
Warning: Failed to check app setting propagation for SCM_DO_BUILD_DURING_DEPLOYMENT, remaining retry 2
App setting SCM_DO_BUILD_DURING_DEPLOYMENT has not been propagated to Kudu container yet, remaining retry 2
Warning: Failed to check app setting propagation for SCM_DO_BUILD_DURING_DEPLOYMENT, remaining retry 1
App setting SCM_DO_BUILD_DURING_DEPLOYMENT has not been propagated to Kudu container yet, remaining retry 1
Warning: Failed to check app setting propagation for SCM_DO_BUILD_DURING_DEPLOYMENT, remaining retry 0
App setting SCM_DO_BUILD_DURING_DEPLOYMENT has not been propagated to Kudu container yet, remaining retry 0
Warning: App setting SCM_DO_BUILD_DURING_DEPLOYMENT fails to propagate to Kudu container
Setting ENABLE_ORYX_BUILD in Kudu container to false
Update using Client.updateAppSettingViaKudu
Response with status code 204
Warning: Failed to check app setting propagation for ENABLE_ORYX_BUILD, remaining retry 19
App setting ENABLE_ORYX_BUILD has not been propagated to Kudu container yet, remaining retry 19
Warning: Failed to check app setting propagation for ENABLE_ORYX_BUILD, remaining retry 18
App setting ENABLE_ORYX_BUILD has not been propagated to Kudu container yet, remaining retry 18

This is what I get as of today. It looks like a complete failure of the deployment process.

Reverting to v1.3.2 fixed it for me.

Reverting to v1.3.2 fixed it for me as well.
Was using v1.0.0 and v1.4.0.

Reverting to v1.3.2 of the action fixed the error for me also.
Failed to check app setting propagation for SCM_DO_BUILD_DURING_DEPLOYMENT and ENABLE_ORYX_BUILD

Seeing the same issue for ENABLE_ORYX_BUILD and SCM_DO_BUILD_DURING_DEPLOYMENT -
Warning: Failed to check app setting propagation for SCM_DO_BUILD_DURING_DEPLOYMENT, remaining retry 0
App setting SCM_DO_BUILD_DURING_DEPLOYMENT has not been propagated to Kudu container yet, remaining retry 0
Warning: App setting SCM_DO_BUILD_DURING_DEPLOYMENT fails to propagate to Kudu container

Should this issue be "idle"? I think we're just waiting around to see it get fixed.

Yes, a lot of time and no response whatsoever and it is even properly identified by the repo maintainers. This is a bug that considerably slows downs release times on our Prod/Dev instances for each Azure Function that we have, and it is a lot of time to be wasting on a CI/CD pipeline.

Just discovered this today too. Deploying Azure Functions. 19 retries and then succeeds. Slows down deploy time dramatically.

Also getting the same - action completes successfully, however spends ages retrying over the two variables.

Same here:
Warning: Failed to check app setting propagation for SCM_DO_BUILD_DURING_DEPLOYMENT, remaining retry 19
App setting SCM_DO_BUILD_DURING_DEPLOYMENT has not been propagated to Kudu container yet, remaining retry 19

after that:
Warning: Failed to check app setting propagation for ENABLE_ORYX_BUILD, remaining retry 19
App setting ENABLE_ORYX_BUILD has not been propagated to Kudu container yet, remaining retry 19

and finally:
Package deployment using ZIP Deploy initiated.

On my case, I do the builds using ubuntu-latest.
jobs:
  build-and-deploy:
    runs-on: ubuntu-latest

3 days ago my deployments stopped working. The github actions logs were saying that the deployment was succesful, but my functions were not really deployed.
App setting ENABLE_ORYX_BUILD has not been propagated to Kudu container yet, remaining retry 1
Warning: Failed to check app setting propagation for ENABLE_ORYX_BUILD, remaining retry 0
App setting ENABLE_ORYX_BUILD has not been propagated to Kudu container yet, remaining retry 0
Warning: App setting ENABLE_ORYX_BUILD fails to propagate to Kudu container
Package deployment using ZIP Deploy initiated.
Deploy logs can be viewed at <redacted>
Successfully deployed web package to App Service.
Successfully updated deployment History at <redacted>
Response with status code 204
Response with status code 204
Response with status code 204

Rolling back to v1.3.2 fixed the issue to me.
I assume that my case was actually being a failure because I need these 2 settings to be true since I'm building on ubuntu instead of windows.
    - name: 'Run Azure Functions Action'
      uses<EMAIL_ADDRESS>      id: fa
      with:
        app-name: <redacted>
        package: ${{ env.AZURE_FUNCTIONAPP_PACKAGE_PATH }}
        publish-profile: <redacted>
        scm-do-build-during-deployment: true
        enable-oryx-build: true

Hello folks - thanks for reporting it. we are looking into this.

FYI for apps with flex consumption see https://github.com/Azure/functions-action/issues/245#issuecomment-2362727235


Audio group permission missing

Without this, the pine64 user will not have audio access!
This is the root of the audio missing issue from a clean install of at least version 0.7.1 onwards of the ubuntu mate pinebook image ;)

This won't fix existing installs, but I can't see a clean way to essentially do the 'usermod -aG audio pine64' that is needed, bar add a --after-upgrade script, which seems overkill for what seems be a fairly recently introduced glitch, and is easily fixed with a one-line command and reboot. Is it worth adding it to  pine64_fix_whatever.sh?

@pfeerick Yes, fix_whatever seems like a good place.


Fix current apparition variable name in docstring

Changed cal -> cap in docstring.

Thanks, Miguel, for your contributions!


parser doesnt cope with urls in proxy requests

im playing with replacing a proxy at work with node, but cannot get some requests through to the http servers request handler because http-parser inappropriately rejects them.
the tests below reproduce the issues. the second one fails because the parser thinks its looking at a port rather than a password in the uri. i cant explain why the first one fails.
please excuse the weird paths in the diff.
diff --git a/deps/http_parser/test.c b/deps/http_parser/test.c
index 7d95b0e..c42e756 100644
--- a/deps/http_parser/test.c
+++ b/deps/http_parser/test.c
@@ -70,8 +70,46 @@ static int num_messages;
/* * R E Q U E S T S * */
const struct message requests[] =
+{ {.name= "env https_proxy=node curl -i https://secure.google.com/"

,.type= HTTP_REQUEST
,.raw= "CONNECT secure.google.com:443 HTTP/1.1\r\n"

    "User-Agent: curl/7.21.4 OpenSSL/1.0.0a zlib/1.2.3 libidn/1.19\r\n"

    "Proxy-Connection: Keep-Alive\r\n"

    "\r\n"

,.should_keep_alive= TRUE
,.message_complete_on_eof= FALSE
,.http_major= 1
,.http_minor= 1
,.method= HTTP_CONNECT
,.request_url= "secure.google.com:443"
,.num_headers= 2
,.headers=
{ { "User-Agent", "curl/7.21.4 OpenSSL/1.0.0a zlib/1.2.3 libidn/1.19" }
, { "Proxy-Connection", "Keep-Alive" }
}
,.body= ""
}

+, {.name= "env ftp_proxy=node ftp ftp://user:pass@host/test"

,.type= HTTP_REQUEST
,.raw= "GET ftp://user:pass@host/test HTTP/1.0\r\n"

    "User-Agent: OpenBSD ftp\r\n"

    "\r\n"

,.should_keep_alive= FALSE
,.message_complete_on_eof= FALSE
,.http_major= 1
,.http_minor= 0
,.method= HTTP_GET
,.request_url= "ftp://user:pass@host/test"
,.num_headers= 1
,.headers=
{ { "User-Agent", "OpenBSD ftp" }
}
,.body= ""
}

#define CURL_GET 0
-{ {.name= "curl get"
+, {.name= "curl get"
,.type= HTTP_REQUEST
,.raw= "GET /test HTTP/1.1\r\n"
"User-Agent: curl/7.18.0 (i486-pc-linux-gnu) libcurl/7.18.0 OpenSSL/0.9.8g zlib/<IP_ADDRESS> libidn/1.1\r\n"

The first case fails because the test definition needs to indicate that an upgrade was expected. You can set
,upgrade= ""

in your definition to fix this.
The second case is a real bug -- we just don't handle user:password@host:port syntax. I'll rename this issue appropriately.


TMF CoAP messages checking for Confirmable/Non-confirmable is too strict

Describe the bug A clear and concise description of what the bug is.
In many places in the Openthread code, checks like below are performed on a received TMF message:
VerifyOrExit(aMessage.IsConfirmablePostRequest());

But in CoAP, the messaging layer (CON/NON) is separated from the request/response processing layer, and therefore the CON or NON transport does not impact the semantics of the request or response.  Forcing a particular transport (CON/NON) at the receiver side seems to serve no purpose and also limits the full use of CoAP features in the future.
Please feel free to provide some comments here -- I won't make a PR for this if the basic assumptions are not agreed on, of course.
To Reproduce Information to reproduce the behavior, including:
N/A
Expected behavior A clear and concise description of what you expected to happen.
Only check for required CoAP message elements at the req/resp layer, such as request method (e.g. verify it is POST).
VerifyOrExit(aMessage.IsPostRequest());

Additional context
See RFC 7252

@EskoDijk, I agree, makes sense to me to relax the condition if it's permissible for specific commands.

Relaxing the constraint makes sense to me.

I checked the code for feasibility for this, and it turns out that due to the current design philosophy and current definition of transaction patterns in the Thread spec, this change is not easy to do.
Examples:

handlers of a CON POST will unconditionally send an empty Ack, if there's no response to be sent back. It doesn't depend on CON/NON of the request.
handlers that do send a response with content back, will always use the 'Ack' Type and this makes it hard to introduce the 'Non-confirmable' type which would be required in response to a NON request.

So allowing both NON/CON type requests could lead to new issues such as a device Ack'ing a NON.
All of this could be optimized by cleanly separating the CoAP reliability layer from handling the request/responses, but this is not the present design. It would in fact save quite a bit of code, because code for 'Acking' is now custom in every handling and this could be just a single CON-layer handler doing this.
Note that the present design also gives rise to behaviors that are not in line with the CoAP semantics: for example, if a CON request application-level handling fails somewhere, the ACK may not be sent, leading to repeated processing of the same CON request due to retransmissions!  Formally, the recipient needs to ACK the request even if the payload/app-layer processing of it failed - it was received, after all.  The sender ought not to resend the same request again per CoAP semantics.
Anyhow, this is a bit too much of a change - instead I have a PR with some bugs caught in the doc/naming: see #10615


is there a plan to support kubernetes 1.22+

Hi!
I am going to use cubefs but the version of my kubernetes cluster is 1.22.5.
Could I ask is there a plan to support kubernetes 1.22+?

Hi, kubernetes 1.22 + was supported.

You can have a try.

Thanks. Let me try.


Use PublicKeyBytes as keys in maps to avoid deserialization

Description
Use PublicKeyBytes instead of PublicKeys as keys in various maps in Narwhal. There could be more places (eg. Commitee or WorkerCache) where this switch may also be done, but I've done the minimal amount of change in order to fix #9222.
Closing #9222
Closing (at least partly) #8930
Test Plan
All tests in CI passes.

do we plan to keep around struct AuthorityPublicKeyBytes?

@akichidis are you planning to take it to the next step, getting rid of pubKeyBytes as identifiers and use indexes or we believe this is low priority and insignificant for mainnet?

@akichidis are you planning to take it to the next step, getting rid of pubKeyBytes as identifiers and use indexes or we believe this is low priority and insignificant for mainnet?

@kchalkias I was actually planning to start working on it immediately so we could have this ready by mainnet to minimise as much as possible the impact of deserialisation - as we still keep doing this for Headers etc. It will require more extensive refactoring so I'll also confirm the other priorities in the team.

@akichidis Do you have any idea why the format_test fails? Running cargo -q run --example generate-format -- print, I get an error:
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: UnknownFormatInContainer("StructTag")', crates/sui-core/src/generate_format.rs:121:35


Enable github issues labeling

We need to be able to label our github issues.

it looks like only contributors can label things, let me know if you want to label stuff and I can add you as a contributor


feat(getter): Allow define a noDefault tag

Thank your for your work for the opensource project.
Here is a proposal of my contribution:

To ensure not have a pointer to manipulate and no use the ZeroValue. (sometimes we just don't want to transform a value to this zero value, example with *bool == nil and not false)
It should be nice to not have a pointer for getters since we do not modify instance in getters (Maybe I could report the modification for other cases)
Some refactoring about templates loaded to get it more structured
Adds lock using go-templating system.

Don't hesitate to comment me, I could rework the PR ;)

Thank you for the merge. \o/


Feature/webhook

Pull Request type

[ ] Bugfix
[x] Feature
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes (Please run ./gradlew generateLock saveLock to refresh dependencies)
[ ] WHOSUSING.md
[ ] Other (please describe):

Changes in this PR
Note: Work In Progress, will notify when it is ready for review.
Webhooks for workflow and task status
Problem:
We have a requirement to publish status of workflow and task to a Webhook.
Solution:
WorkflowStatusListener and TaskStatusListener interfaces can be implemented to call webhooks when there is a change in status of workflow and task. We can add new module called 'webhook'.
Issue #
https://github.com/Netflix/conductor-community/discussions/212
Alternatives considered
Describe alternative implementation you have considered

This looks great. Any progress here?

Hi, when will it be merged?

Closing this PR, as these changes are already in another related PR - https://github.com/Netflix/conductor-community/pull/228


Update tootip customize to iTwin brand

Logo image
Thumbnails

I'm not happy with the quality of the thumbnails. Going to regenerate.


Raduom/pab resume

Adds a command-line option (--resume-from) and a configuration section which allows for the PAB to resume from a given block and slot id.
Notes:

The resume will happen from the block immediately after the one specified on the command line (or the configuration).
This will be rolled back when we will implement persistence for our internal state, but provides a way to "synchronise" very fast in cases where the history of the blockchain is not needed for contract operation.

Pre-submit checklist:

Branch

[ ] Tests are provided (if possible)
[x] Commit sequence broadly makes sense
[x] Key commits have useful messages
[x] Relevant tickets are mentioned in commit messages
[ ] Formatting, materialized Nix files, PNG optimization, etc. are updated

PR

[x] Self-reviewed the diff
[x] Useful pull request description
[ ] Reviewer requested

Nice; maybe could do with a hint about how to get the block information when you want to start from a certain point?


ESP32 AT not responsed until reset

Environment
<6>May 30 19:15:56 at.dev.esp32: esp0 device initialize retry...
<6>May 30 19:15:56 at.dev.esp32: esp0 device wifi is disconnect.
<6>May 30 19:15:57 at.dev.esp32: AT version:<IP_ADDRESS>(883f7f2 - Jul 24 2020 11:50:07)
<6>May 30 19:15:57 at.dev.esp32: SDK version:v4.0.1-193-ge7ac221
<6>May 30 19:15:57 at.dev.esp32: compile time(0ad6331):Jul 28 2020 02:47:21
<6>May 30 19:15:57 at.dev.esp32: Bin version:2.1.0(WROOM-32)

Power supply 3.3V.
Problem Description
After a few hours of pressure MQTT test (keep publish different MQTT message to a broker without delay), it stops responding to any AT command. I am not using ESP32's MQTT commands, but socket commands.
It also fails to send a message which leads to closing and reopening the socket. Every a few minutes (from 5 to 20min).
Until finally it stops responding to any AT command. (also tested by handwriting AT)
Expected Behavior
It should reply error/busy/OK no matter the state of the module.
Actual Behavior
No response.
Steps to repropduce
Code to reproduce this issue
Debug Logs
<3>May 30 18:03:34 at.skt.esp32: esp0 device socket(0) wait connect result timeout.
<7>May 30 18:03:54 at.dev.esp32: system is processing a commands...
<3>May 30 18:04:54 mqtt: [536968768] can't recv Ping Response
<7>May 30 18:04:54 mqtt: MQTT offline
<3>May 30 18:04:54 mqtt: publish fail, wait for reconnect
<7>May 30 18:04:59 mqtt: restart!
<7>May 30 18:04:59 mqtt: MQTT connecting
<7>May 30 18:04:59 mqtt: ipv4 address port: 1883
<7>May 30 18:04:59 mqtt: HOST = '<IP_ADDRESS>'
<6>May 30 18:04:59 mqtt: MQTT server connect success.
<6>May 30 18:04:59 mqtt: Subscribe #0 state OK!
<6>May 30 18:04:59 mqtt: Subscribe #1 ota_downstream OK!
<7>May 30 18:04:59 mqtt: MQTT online

msh />
msh /><7>May 30 18:14:01 at.dev.esp32: system is processing a commands...
<3>May 30 18:14:11 at.skt.esp32: esp0 device socket(0) wait connect result timeout.
<3>May 30 18:14:31 mqtt: publish fail, wait for reconnect
<7>May 30 18:14:36 at.clnt: execute command (AT+CIPSEND=0,2) timeout (5000 ticks)!
<3>May 30 18:14:36 mqtt: [11636394] send ping rc: -1
<7>May 30 18:14:36 at.dev.esp32: system is processing a commands...
<7>May 30 18:14:36 mqtt: MQTT offline
<7>May 30 18:14:41 mqtt: restart!
<7>May 30 18:14:41 mqtt: MQTT connecting
<7>May 30 18:14:41 mqtt: ipv4 address port: 1883
<7>May 30 18:14:41 mqtt: HOST = '<IP_ADDRESS>'
<6>May 30 18:14:41 mqtt: MQTT server connect success.
<6>May 30 18:14:42 mqtt: Subscribe #0 state OK!
<6>May 30 18:14:42 mqtt: Subscribe #1 ota_downstream OK!
<7>May 30 18:14:42 mqtt: MQTT online
<7>May 30 18:19:12 at.dev.esp32: system is processing a commands...
<3>May 30 18:19:22 at.skt.esp32: esp0 device socket(0) wait connect result timeout.
<7>May 30 18:19:42 at.dev.esp32: system is processing a commands...
<3>May 30 18:20:42 mqtt: [536968768] can't recv Ping Response
<7>May 30 18:20:42 mqtt: MQTT offline
<3>May 30 18:20:43 mqtt: publish fail, wait for reconnect
<7>May 30 18:20:47 mqtt: restart!
<7>May 30 18:20:47 mqtt: MQTT connecting
<7>May 30 18:20:47 mqtt: ipv4 address port: 1883
<7>May 30 18:20:47 mqtt: HOST = '<IP_ADDRESS>'
<6>May 30 18:20:48 mqtt: MQTT server connect success.
<6>May 30 18:20:48 mqtt: Subscribe #0 state OK!
<6>May 30 18:20:48 mqtt: Subscribe #1 ota_downstream OK!
<7>May 30 18:20:48 mqtt: MQTT online
<3>May 30 18:23:44 at.skt.esp32: esp0 device socket(0) wait connect result timeout.
<3>May 30 18:23:48 mqtt: publish fail, wait for reconnect
<7>May 30 18:23:53 at.clnt: execute command (AT+CIPSEND=0,2) timeout (5000 ticks)!
<3>May 30 18:23:53 mqtt: [12193202] send ping rc: -1
<7>May 30 18:23:58 at.clnt: execute command (AT+CIPSEND=0,2) timeout (5000 ticks)!
<7>May 30 18:23:58 mqtt: MQTT offline
<7>May 30 18:23:58 at.clnt: execute command (AT+CIPCLOSE=0) timeout (300 ticks)!
<7>May 30 18:24:04 mqtt: restart!
<7>May 30 18:24:04 mqtt: MQTT connecting
<7>May 30 18:24:04 mqtt: ipv4 address port: 1883
<7>May 30 18:24:04 mqtt: HOST = '<IP_ADDRESS>'
<7>May 30 18:24:09 at.clnt: execute command (AT+CIPSTART=0,"TCP","<IP_ADDRESS>",1883,60) timeout (5000 ticks)!
<7>May 30 18:24:09 at.skt.esp32: esp0 device socket (0) connect failed, the socket was not be closed and now will connect retry.
<7>May 30 18:24:09 at.clnt: execute command (AT+CIPCLOSE=0) timeout (300 ticks)!
<3>May 30 18:24:09 mqtt: connect err!
<7>May 30 18:24:09 at.clnt: execute command (AT+CIPCLOSE=0) timeout (300 ticks)!
<3>May 30 18:24:09 mqtt: Net connect error(-2).
<7>May 30 18:24:09 mqtt: MQTT offline
<7>May 30 18:24:14 mqtt: restart!
<7>May 30 18:24:14 mqtt: MQTT connecting
<7>May 30 18:24:14 mqtt: ipv4 address port: 1883
<7>May 30 18:24:14 mqtt: HOST = '<IP_ADDRESS>'
<7>May 30 18:24:19 at.clnt: execute command (AT+CIPSTART=0,"TCP","<IP_ADDRESS>",1883,60) timeout (5000 ticks)!
<7>May 30 18:24:19 at.skt.esp32: esp0 device socket (0) connect failed, the socket was not be closed and now will connect retry.
<7>May 30 18:24:20 at.clnt: execute command (AT+CIPCLOSE=0) timeout (300 ticks)!
<3>May 30 18:24:20 mqtt: connect err!
<7>May 30 18:24:20 at.clnt: execute command (AT+CIPCLOSE=0) timeout (300 ticks)!
<3>May 30 18:24:20 mqtt: Net connect error(-2).
<7>May 30 18:24:20 mqtt: MQTT offline
<7>May 30 18:24:25 mqtt: restart!
<7>May 30 18:24:25 mqtt: MQTT connecting
<7>May 30 18:24:25 mqtt: ipv4 address port: 1883
<7>May 30 18:24:25 mqtt: HOST = '<IP_ADDRESS>'
<7>May 30 18:24:30 at.clnt: execute command (AT+CIPSTART=0,"TCP","<IP_ADDRESS>",1883,60) timeout (5000 ticks)!
<7>May 30 18:24:30 at.skt.esp32: esp0 device socket (0) connect failed, the socket was not be closed and now will connect retry.
<7>May 30 18:24:30 at.clnt: execute command (AT+CIPCLOSE=0) timeout (300 ticks)!
<3>May 30 18:24:30 mqtt: connect err!
<7>May 30 18:24:31 at.clnt: execute command (AT+CIPCLOSE=0) timeout (300 ticks)!
<3>May 30 18:24:31 mqtt: Net connect error(-2).
<7>May 30 18:24:31 mqtt: MQTT offline

@majianjia It looks like self-defined MQTT code broke the ESP-AT interval workflow.
Could you please share the project to us, and provide the steps for us to reproduce.
If possible, i would like to recommend the latest esp-at version, it got greatly improved at stability and compatibility.

@ustccw
Thanks for your reply. I might locate the issue. It was the power.
The PCB power supply was throught a 0.5mm FPC wire, which cannot provide enough current.
I tested for a few hours now with a USB power supply. The issue was not replicated.

@majianjia Glad to hear that :smile:


Bug 1880359: [release-4.5] Bump 1.18.9

Description of the change:
Cherry pick of #1775
Motivation for the change:
Reviewer Checklist

[ ] Implementation matches the proposed design, or proposal is updated to match implementation
[ ] Sufficient unit test coverage
[ ] Sufficient end-to-end test coverage
[ ] Docs updated or added to /docs
[ ] Commit messages sensible and descriptive

/bugzilla refresh

/lgtm

/refresh


Dbeaver is unable to retain the original datatype

System information:

Operating system (distribution) and version WIN - 10
DBeaver version 6.1.2

Connection specification:

Database name and version - SQL Server 16
Do you use tunnels or proxies (SSH, SOCKS, etc)? No

Describe the problem you're observing:
Datatypes of columns in the select list are smalldatetime but the results are reformatted to date in Dbeaver.
I have attached a snapshot of this issue to this ticket,
The one in the left is from Dbeaver(dark theme) and the one in the right is from SSMS.

cannot reproduce it for now.
If issue is still actual for you - feel free to reopen the ticket


fix(next): add support for Next.js 13.5.4

This PR introduces support for the latest release of Next.js where they changed the file structure, see "misc: refactor node utils".

[x] I have read CONTRIBUTING.md
[x] This PR is not security related (see SECURITY.md)

Most importantly: thank you so much for all your work! 🙏

Wow, I got pinged for the failing test and just pulled up my workspace and fixed it without checking GitHub for PRs... sorry about that 😅 Thank you for this regardless! And for the kind words!

Amazing, thank you!


Publish snapshots for pinot-java-client to maven snapshots repo

I was unable to find snapshots for the pinot-java-client module in maven central snapshots repository. For now, I have been building the project locally for testing my changes to pinot-java-client in a downstream project but it would be nice if regular snapshots and releases could be published (possibly in a semi-automated way) by the Pinot team.

cc @xiangfu0


[Bug]: Zombies may throw air if the item of custom throw behavior doesn't exist

What happened?
If the item added in "custom throw behaviors" doesn't exist, and with "zombie can throw items" on, all zombies will try to throw air.
I checked the data of it, there's nothing in its hand.
Screenshots

Logs
No response
Mod Version
1.9.0
Minecraft Version
1.19.2

Could you please check this build? https://github.com/constellation-mc/andromeda/actions/runs/9329162781

Yeah, it's fixed.
But seems that somehow the smooth tooltips ignore the config value.

This is fixed in 1.20 & 1.20.4. 1.19.2 will come when I'm brave enough to fix all the git conflicts.


failure parsing yaml file with block scalar without indented block

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
I am targeting an helm values file which contains:
# -- Pod affinity, passed thru tpl function
affinity: |-

serviceAccount:
  create: true

Updatecli pipeline fails with:
ERROR: something went wrong in target "searchValuessearch_23n" : "updating yaml file: parsing yaml file: [144:15] unexpected token. required string token\n      141 | # -- Pod affinity, passed thru tpl function\n      142 | affinity: |-\n      143 | \n    > 144 | serviceAccount:\n                          ^\n      145 |   # -- Specifies whether a service account should be created\n      146 |   create: true\n      147 |   # -- Automatically mount a ServiceAccount's API credentials?\n      148 | "

Expected Behavior
affinity field should be parsed as empty string (tried with a bunch of online parser)
Steps To Reproduce
No response
Environment
- OS: Ubuntu 22.04
- updatecli: 0.71.0

Anything else?
I know it's quite an edge case but we were using it the make the life easier for helm charts users who want to provide a custom values file.

Are you facing the problem with the yaml plugin or the helm plugin?
There are two main YAML libraries.
One is goccy/go-yaml and the other one is yaml.v3
As explained on updatecli.io The yaml plugin allows to choose either go-yaml or yamlpath where yamlpath is based on yaml.v3 and it comes with its own set of limitation
But I don't think the helm plugin expose this setting. It just relies on the defined engine which is go-yaml

Goccy/go-yaml has a few issues around scalar
https://github.com/goccy/go-yaml/issues?q=is%3Aissue+is%3Aopen+scalar

Are you facing the problem with the yaml plugin or the helm plugin?

sorry, it's the plain yaml plugin
I guess it's https://github.com/goccy/go-yaml/issues/168
to workaround the issue I have simply removed the scalar, not a big deal
affinity: ""

@gionn Could you give it another look?
I see the goccy/go-yaml library introduced a few fixes around scalar recently
https://github.com/goccy/go-yaml/issues?q=is%3Aissue+scalar+is%3Aclosed


The performance of my pretraining model is very bad.

CUDA_VISIBLE_DEVICES=0,1,2,3 accelerate launch pretrain_e4t.py
--pretrained_model_name_or_path="runwayml/stable-diffusion-v1-5"
--clip_model_name_or_path="openai/clip-vit-large-patch14"
--domain_class_token="face"
--placeholder_token="*s"
--prompt_template="a photo of {placeholder_token}"
--reg_lambda=0.01
--output_dir="pretrained-face-2"
--train_image_dataset="FFHQ"
--iterable_dataset
--resolution=512
--train_batch_size=4
--learning_rate=1.6e-5
--max_train_steps=30000
--mixed_precision="no"
--enable_xformers_memory_efficient_attention

The sampled images of monet style almost have no human face.
10k steps:

and sampled results become weird after 13k steps like this:

If I use 10k pretrained model for finetuning, I get totally unrelated faces by inference. (*s on the beach)

If I use 20k or 30k pretrained model for finetuning, I get totally weird images without any face. (*s on the beach)

So do I have to train the model with a mixed dataset of FFHQ and CelebA-HQ instead of using only FFHQ dataset? What can I do to get better results?

Does loss_reg equal 0?

Does loss_reg equal 0?

The loss seems reasonable.

https://github.com/mkshing/e4t-diffusion/blob/main/pretrain_e4t.py
427, 429, 445
you have loss_reg=args.reg_lambda(=0.01) * domain_embed.pow(2).sum() = 1e-4 => domain_embed.pow(2).sum() = 0.01. I think its very low to make sense. And its main information about the input image.
I have same problems. Changed reg_lambda from 1e-2 to 1e-4 few hours ago

https://github.com/mkshing/e4t-diffusion/blob/main/pretrain_e4t.py 427, 429, 445
you have loss_reg=args.reg_lambda(=0.01) * domain_embed.pow(2).sum() = 1e-4 => domain_embed.pow(2).sum() = 0.01. I think its very low to make sense. And its main information about the input image.
I have same problems. Changed reg_lambda from 1e-2 to 1e-4 few hours ago

Thank you, I will try this.

@dong-y21 any results?)

@dong-y21 any results?)

Still very few faces appear in monet style

I changed a lot of parts to get better results and released the pre-trained model for face. You should check the latest code and reopen this issue if you have still problems.


IE11 version thumbnail image slowly viewed.

Hi. I use nk visual portfolio plugin in wordpress.
When I use by IE 11 version browser,I find thumbnail some of images blank image.
so I asked this issue nk development person.
He said "this plugin image script this lazysizes.
so, I ask this issue.
(If use device PC Version Microsoft Internet Explorer 11, can check this issue.)
chrome browser no issue.
my url : http://bold-b.co.kr
can I solve this issue?
Please help.
Thanks.

@seoungilchoi
I can not replicate your issue. But I see that you are using another image related script there, which is only running if IE11 is used so it is much more likley that this script is causing your IE11 only issue.
It's the following script: https://github.com/bfred-it/object-fit-images
On the other hand:
lazySizes comes with its own very simple solution of object-fit images. If the author of your page would instead use the following plugin it should be fixed:
https://github.com/aFarkas/lazysizes/tree/gh-pages/plugins/object-fit
Due to the fact, that the CSS syntax is the same to the other object-fit polyfill he has to simply remove the other polyfill and switch it with the lazySizes plugin.


L5.4 getJoinKeys breaking changes

In Relations/Joiner.php https://github.com/jarektkaczyk/eloquence/blob/5.3/src/Relations/Joiner.php#L177
the method getJoinerKeys
calls the following methods that do not exist in Laravel 5.4

instanceof HasOneOrMany calls getForeignKey
instanceof BelongsTo calls getQualifiedOtherKeyName
instanceof BelongsToMany calls getOtherKey

In Mappable.php
https://github.com/jarektkaczyk/eloquence/blob/5.3/src/Mappable.php#L306
the method getJoinerKeys
calls the following methods that do not exist in Laravel 5.4

instanceof HasOne calls getForeignKey
instanceof BelongsTo calls getQualifiedOtherKeyName

@bdanchilla this should fix it:
https://github.com/ortic/eloquence/pull/1

https://github.com/jarektkaczyk/eloquence/tree/5.4


Unable to build on MacOS

I'm using MacOS 13.3, attempting to build this module.  I've tried building with both Clang and GCC (10 and 13) but get the same error no matter what.  I'm able to build on Linux without issue.  I've exhausted my troubleshooting abilities as I'm not really familiar with CMake.  Any ideas how this can be successfully built on MacOS?
[ 96%] Linking C static library libcanokey-core.a
[ 96%] Built target canokey-core
[ 97%] Building C object CMakeFiles/canokey-qemu.dir/canokey-core/virt-card/fabrication.c.o
[ 98%] Building C object CMakeFiles/canokey-qemu.dir/Src/qemu.c.o
[ 98%] Building C object CMakeFiles/canokey-qemu.dir/canokey-core/virt-card/device-sim.c.o
[ 98%] Building C object CMakeFiles/canokey-qemu.dir/canokey-core/littlefs/bd/lfs_filebd.c.o
[100%] Linking C shared library libcanokey-qemu.dylib
Undefined symbols for architecture x86_64:
  "_canokey_emu_get_rx_data_size", referenced from:
      _USBD_LL_GetRxDataSize in qemu.c.o
  "_canokey_emu_prepare_receive", referenced from:
      _USBD_LL_PrepareReceive in qemu.c.o
  "_canokey_emu_set_address", referenced from:
      _USBD_LL_SetUSBAddress in qemu.c.o
  "_canokey_emu_stall_ep", referenced from:
      _USBD_LL_StallEP in qemu.c.o
  "_canokey_emu_transmit", referenced from:
      _USBD_LL_Transmit in qemu.c.o
ld: symbol(s) not found for architecture x86_64
collect2: error: ld returned 1 exit status
make[2]: *** [libcanokey-qemu.0.dylib] Error 1
make[1]: *** [CMakeFiles/canokey-qemu.dir/all] Error 2
make: *** [all] Error 2

canokey_emu_get_rx_data_size

libcanokey-qemu expects these symbols from qemu. But it seems that MacOS compiler treat them like internal symbol. I do not use MacOS so I do not know how to handle it.
https://github.com/pgRouting/pgrouting/issues/5
Maybe we need to change SHARED into MODULE and add QEMU as the bundle_loader?
One thing that can make trouble is that now this is circular dependencies: qemu use symbols from libcanokey-qemu and libcanokey-qemu use symbols from qemu. I have no idea on this.

Other materials I found

https://github.com/ziglang/zig/issues/8180
https://blog.tim-smith.us/2015/09/python-extension-modules-os-x/

A friend suggested using static lib. I am not against it. Seems like changing the SHARED flag and corresponding pkg-config should work.

Thanks for the feedback.  Besides changing the SHARED flag to STATIC, how does pkg-config need to be modified?  I was able to build the dylib for SHARED using the "-undefined dynamic_lookup" flag, but now I'm running into the circular reference I think you were alluding to (qemu.c from canokey-qemu is referencing a symbol from qemu itself).

Removing
https://github.com/canokeys/canokey-qemu/blob/b70af31229f1858089c3366f71b8d771de4a1e84/canokey-qemu.pc.in#L7
should work?

Finally figured it out.  Thanks for the help; I had to make a few tweaks but eventually this is what made it work:

Change from SHARED to STATIC https://github.com/canokeys/canokey-qemu/blob/b70af31229f1858089c3366f71b8d771de4a1e84/CMakeLists.txt#L26

Copy ALL static libraries compiled by canokey-qemu (should be 4: libcanokey-qemu.a, libcanokey-crypto.a, ibmbedcrypto.a, libcanokey-core.a) to a central directory.  I made my own include folder, but you could just copy them to /usr/local/lib.  Let's assume it's /usr/local/lib.  I found the files by running (from the root of the canokey-qemu repo folder) 'find ./ -name "*.a"'.

Run the QEMU configure script with a few extra flags: ./configure --enable-canokey --enable-cocoa --extra-cflags='-Wno-unused-but-set-variable' --extra-ldflags='-L/usr/local/lib -lcanokey-qemu  -lcanokey-core -lmbedcrypto -lcanokey-crypto'

"--enable-cocoa" makes the QEMU gui work on Mac, "--extra-ldflags" is what's needed to include the static libraries that we copied to /usr/local/lib in step 2, "--extra-cflags" is to ignore an error that's thrown during compilation; this might not be necessary if using gcc <=12 (which I did, after giving up on clang).
Doing this I was able to build QEMU 8.0.0 from trunk and launch a VM successfully with a virtual Canokey attached!
Thanks so much for your help @ZenithalHourlyRate!

If you get the time, could you make such changes to the repo so that other users could benefit from it? Seems that the /usr/local/lib trick is not disired by most people, I think that could be resolved by pkg-config, as qemu finds where libcanokey-qemu is by pkg-config, and these cflags like -L/usr/local/lib are not needed.

If you get the time, could you make such changes to the repo so that other users could benefit from it? Seems that the /usr/local/lib trick is not disired by most people, I think that could be resolved by pkg-config, as qemu finds where libcanokey-qemu is by pkg-config, and these cflags like -L/usr/local/lib are not needed.

PR submitted.


Mineshafts above ground

This happened with version v2.8.2-SNAPSHOT. All I did was generate a Mesa/Desert/Savanna-only world.

Post your worldconfig.ini

https://pastebin.com/VjqFdXbL

But I do want mineshafts, just not on the surface.

I don't know, sorry.

I've seen these before and just looked it up.  They are normal.  http://minecraft.gamepedia.com/Abandoned_mineshaft

This is normal as MadCat64 stated.


Add possibility to generate intermediary types in documents generating plugins ( typescript-operations)

Is your feature request related to a problem? Please describe.
When trying to migrate away from the apollo cli and its codegen feature there is one feature which seems to be missing and is described here: https://github.com/apollographql/apollo-tooling/issues/2053#issuecomment-767293917
Basically it generated intermediary core types which could then be reused.
For example it would generate code such as below:
export type UserFieldsFragment_profile = { __typename?: 'Profile', age?: number | null };

export type UserFieldsFragment = { __typename?: 'User', id: string, username: string, profile?: UserFieldsFragment_profile | null };

In our codeline we use those intermediary types a lot and it would really helps us minimizing the cost of migration.
It would also seem pretty useful to me but then I could be biased.
Describe the solution you'd like
Have the possibility, when using the typescript-operations to explicitely generate intermediary types.
Describe alternatives you've considered
I've tried playing with the option exportFragmentSpreadSubTypes even though the description weren't really giving much hopes about it but it seemed like the closest option.
Is your feature request related to a problem? Please describe.
No response

This is not a feature we want codegen to support. This encourages an anti-pattern. Fragments is how intermediary types should works. Fragments are built in language feature to support things like this we do not need to create some types wrapper because this just gets messier to manage.


docs: adding link to wiki

PR checklist:

[ ] Github Issue associated with branch.
[ ] Code passes linting through autopep8.
[ ] PR branch is up-to-date with latest master branch.

Codecov Report

Merging #8 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master       #8   +/-   ##
=======================================
  Coverage   59.51%   59.51%
=======================================
  Files          10       10
  Lines         788      788
=======================================
  Hits          469      469
  Misses        319      319

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 5831df4...80b827d. Read the comment docs.


WARN: Error opening URL blocks error methods.

Bug description:
When passing an invalid uri/url the webView sends back a WARN: Error opening URL:  [Error: Unable to open URL ...
This seams to block the rest of the webView methods such as:

onError
onHttpError
onRenderError

To Reproduce:
pass an invalid url/uri or an empty string. ''
Expected behavior:
Expecting the webView to run one of the following error methods:

onError
onHttpError
onRenderError

Environment:

OS: Ios / Android
OS version: ios 16, Android 12/13
react-native version:
react-native-webview version: ^11.22.7

Not opening an URL cannot lead to one of these errors. This is an expected behaviour.
You could check validity before passing it to the web view by using a regex for example.

originWhitelist={['blob:']}


find_related_tags scope fails whenever Rails 3 calls COUNT

In a Rails 3 application, if you call .count .present? or .empty? on the find_related_tags scope or matching_contexts_for scope you will get a SQL error. Rails changes the :select option to use a COUNT(*) as count_all but does not account for existing COUNT calls in the scope. I'm not exactly sure of the fix--maybe you can specify the sql for calling count on the scope...
This occurs in MySql, Postgres, and SQLlite.
> m.find_related_tags.present?
ActiveRecord::StatementInvalid: Mysql2::Error: Unknown column 'count' in 'order clause': SELECT COUNT(*) AS count_all, messages.id, messages.created_at, messages.updated_at AS messages_id_messages_created_at_messages_updated_at FROM messages, tags, taggings WHERE (messages.id != 1 AND messages.id = taggings.taggable_id AND taggings.taggable_type = 'Message' AND taggings.tag_id = tags.id AND tags.name IN (NULL)) GROUP BY messages.id, messages.created_at, messages.updated_at ORDER BY count DESC

Stacktrace:
from /Users/pivotal/.rvm/gems/ruby-1.8.7-p174/gems/activerecord-3.0.4/lib/active_record/connection_adapters/abstract_adapter.rb:207:in log' 	from /Users/pivotal/.rvm/gems/ruby-1.8.7-p174/gems/mysql2-0.2.7/lib/active_record/connection_adapters/mysql2_adapter.rb:314:in execute'
from /Users/pivotal/.rvm/gems/ruby-1.8.7-p174/gems/mysql2-0.2.7/lib/active_record/connection_adapters/mysql2_adapter.rb:635:in select' 	from /Users/pivotal/.rvm/gems/ruby-1.8.7-p174/gems/activerecord-3.0.4/lib/active_record/connection_adapters/abstract/database_statements.rb:7:in select_all'
from /Users/pivotal/.rvm/gems/ruby-1.8.7-p174/gems/activerecord-3.0.4/lib/active_record/connection_adapters/abstract/query_cache.rb:56:in select_all' 	from /Users/pivotal/.rvm/gems/ruby-1.8.7-p174/gems/activerecord-3.0.4/lib/active_record/relation/calculations.rb:235:in execute_grouped_calculation'
from /Users/pivotal/.rvm/gems/ruby-1.8.7-p174/gems/activerecord-3.0.4/lib/active_record/relation/calculations.rb:180:in perform_calculation' 	from /Users/pivotal/.rvm/gems/ruby-1.8.7-p174/gems/activerecord-3.0.4/lib/active_record/relation/calculations.rb:152:in calculate'
from /Users/pivotal/.rvm/gems/ruby-1.8.7-p174/gems/activerecord-3.0.4/lib/active_record/relation/calculations.rb:58:in `count'

@rheaton you can pass options to find_related_tags. For example
find_related_tags(order: 'count_all desc').


Destructuring props in constructor (IE10+IE11)

class EmbedModal extends React.Component {
  constructor(props) {
    super(props);
    let { one, two } = this.props
    one.callSomething() // one is undefined

    // Operations usually carried out in componentWillMount go here
  }
}

This works fine in Chrome and Firefox, was only having problems in IE10 and IE11.

You probably want to push your code through Babel to transform it into a format the browsers in question can understand. See https://www.npmjs.com/package/babel-loader .


Version not found: latest

I have correctly deployed nuts on heroku and connected it to github repository.

/download/0.10.0 works correctly (it's my only released version). it returns zip to download
/download route should give me latest version (0.10.0), instead it says "Version not found: latest"

What should I do to make "latest" work? Github release is marked "latest", so that should not be a problem, right?

Hello!
I have this error also. What should I do to make "latest" work?

I found out that dropping the /latest part of the URL works:
http://download.myapp.com/download/latest/osx -> http://download.myapp.com/download/osx
Documentation should be fixed accordingly


Why the specific dependency on Go 1.21.9?

Checklist

[X] I have looked into the README and have not found a suitable solution or answer.
[X] I have looked into the documentation and have not found a suitable solution or answer.
[X] I have searched the issues and have not found a suitable solution or answer.
[X] I have upgraded to the latest version of OpenFGA and the issue still persists.
[X] I have searched the Slack community and have not found a suitable solution or answer.
[X] I agree to the terms within the OpenFGA Code of Conduct.

Description
Hello,
I see that a recent change which then made it into 0.3.6 has caused a bump of Go from 1.21 to 1.21.9 but I can't figure out why.
This bump is preventing us from consuming 0.3.6 from within Incus as our base is still 1.21.
Expectation
Be able to build with Go 1.21.x
Reproduction
Build or consume go-sdk from a project using Go 1.21.x < 1.21.9.
OpenFGA SDK version
0.3.6
OpenFGA version
irrelevant
SDK Configuration
irrelevant
Logs
No response
References
No response

Hi @stgraber - Will have chat with the team before reverting around this. We can bump it up in CI, but that means that folks running earlier builds of Go may be vulnerable.
If we agree on this path, we'll revert to 1.21 next week - sorry for this.
Main reason for the bump is Go's vulnerability reporting. It was raising errors on the CI.
If I am not mistaken, this issue is what triggered govulncheck for us, https://github.com/golang/go/issues/65065. Fixed in Go 1.21.8.
On one hand we can say the choice of the runtime should be up to the user, but we're usually erring a lot on the side of caution.
Apologies if it takes us a bit of time to get back on this, I'd rather not revert without a team consensus.

Hi @stgraber - just an update, we agreed to revert to 1.21 - sorry for the delay and the noise. A release with this fix should go out tomorrow.

Thanks!

v0.3.7 is now out - thanks @stgraber!

thanks!


chore: remove or lower maxHeartbeats to match the current state

A hand-ful further maxHeartbeats change related to field_simp are also obsolete; I will file a separate PR for these.

Thanks!
bors merge


[dev] [wip] accept https connections

http://<IP_ADDRESS>:8787 should preview http://myzone.com and https://<IP_ADDRESS>:8787 should preview https://myzone.com

for posterity - was encountering this issue:
when compiling i get this error:
$ cargo check
error: future cannot be sent between threads safely
   --> src/commands/dev/gcs/mod.rs:75:22
    |
75  |         let server = tokio::spawn(serve(server_config, Arc::clone(&preview_id)));
    |                      ^^^^^^^^^^^^ future returned by `serve` is not `Send`
    |
   ::: /Users/averyharnish/.cargo/registry/src/github.com-1ecc6299db9ec823/tokio-0.2.21/src/task/spawn.rs:127:21
    |
127 |         T: Future + Send + 'static,
    |                     ---- required by this bound in `tokio::task::spawn::spawn`
    |
    = help: the trait `std::marker::Send` is not implemented for `dyn futures_core::stream::Stream<Item = std::result::Result<tokio_rustls::server::TlsStream<tokio::net::tcp::stream::TcpStream>, std::io::Error>>`
note: future is not `Send` as it awaits another future which is not `Send`
   --> src/commands/dev/gcs/server.rs:123:21
    |
123 |     if let Err(e) = server.await {
    |                     ^^^^^^ await occurs here on type `hyper::server::Server<commands::dev::tls::HyperAcceptor<'_>, hyper::service::make::MakeServiceFn<[closure@src/commands/dev/gcs/server.rs:59:35: 112:6 client:hyper::client::Client<hyper_rustls::connector::HttpsConnector<hyper::client::connect::http::HttpConnector>>, server_config:commands::dev::server_config::ServerConfig, preview_id:std::sync::Arc<std::sync::Mutex<std::string::String>>]>>`, which is not `Send`

error: aborting due to previous error

error: could not compile `wrangler`.

To learn more, run the command again with --verbose.

this is a bit strange since it seems to me like the server.await should still be the same type. I wonder if I need to do something with HyperAcceptor to make it Send...

currently running into some more issues:
when curling https:
$ curl https://<IP_ADDRESS>:8787 --insecure
curl: (92) HTTP/2 stream 1 was not closed cleanly: INTERNAL_ERROR (err 2)

when curling http
$ curl http://<IP_ADDRESS>:8787
curl: (52) Empty reply from server

$ wrangler dev
server error: error accepting connection: TLS Error: Custom { kind: InvalidData, error: CorruptMessage }

so - i need to figure out why https isn't working properly, and i need to also modify my code to allow http requests in addition to https requests

ok - i have it accepting curl https://<IP_ADDRESS>:8787 just fine now! big problem is that it no longer accepts http connections, AND if it happens to receive an http connection, it then seems to corrupt the parser. To reproduce:
$ wrangler dev
💁  JavaScript project found. Skipping unnecessary build!
💁  watching "./"
👂  Listening on http://<IP_ADDRESS>:8787
executing worker
[2020-07-14 11:51:03] GET example.com/ HTTP/1.1 200 OK
server error: error accepting connection: TLS Error: Custom { kind: InvalidData, error: CorruptMessage }

$ curl --insecure https://<IP_ADDRESS>:8787
Hello, World!

$ curl http://<IP_ADDRESS>:8787
curl: (52) Empty reply from server

$ curl --insecure https://<IP_ADDRESS>:8787
curl: (7) Failed to connect to <IP_ADDRESS> port 8787: Connection refused

i found these two examples: https://github.com/izderadicka/tokio-tls/blob/new-tokio/examples/hyper-server.rs and https://users.rust-lang.org/t/use-hyper-server-with-tls/18535, but they seem to use a lower level Http API that I'm not currently using, and I'm not quite sure how to fit this in with the way things are currently set up.


Procedures/Investigations- list all planned items in form, disallow duplicate entry

Is your feature request related to a problem? Please describe.
When a user adds procedure/investigation suggestion in Consultation form/ progess note (log update), the user has no way to see the already planned procedure/investigation. without this the user may end up duplicating entries.
Describe the solution you'd like
Show list all upcoming planned procedures/investigations for the patient along with details (like time/repetative etc).
And if the user recommends a  procedures/investigation in the list, show a message saying "this procedures/investigation is already scheduled for the patient. Please edit the existing entry".
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

I would like to work on this issue. Before that i have few things to clear, when i try to add some random procedures and investigations in the consulation form of a patient with no exisiting consultation, i could see the procedures and investigations (values that i added previously) when i open edit consultation form. Is this the issue that you mentioned above
OR
When i fill a procedure with some random value and try to add one more procedure with same values, it is allowing users to add. Is the issue that was mentioned.
@rithviknishad

@rithviknishad @aparnacoronasafe can u assign this to me..?

@gigincg can you look into the relevance of this issue, since we are moving towards FHIR and refactoring of investigation modules

@nihal467 Blocked the issue, this is better done post Questionnaires and Lab Management is shipped out.
cc: @noufalrahim

not a invalid issue based on the current develop


fatal: unable to access 'https://github.com/meta-toolkit/meta-cmake.git/': OpenSSL SSL_read: Connection reset by peer, errno 104

when i use this command  git submodule update --init --recursive for set up submodules in installing meta,i received this error,and i checked my connention and it's ok,do somebody knows how to solve this problem? thanks a lot. here is the details.
$ git submodule update --init --recursive Cloning into '/home/Chris/meta/deps/cpptoml/deps/meta-cmake'... fatal: unable to access 'https://github.com/meta-toolkit/meta-cmake.git/': OpenSSL SSL_read: Connection reset by peer, errno 104 fatal: clone of 'https://github.com/meta-toolkit/meta-cmake.git' into submodule path '/home/Chris/meta/deps/cpptoml/deps/meta-cmake' failed Failed to clone 'deps/meta-cmake'. Retry scheduled Cloning into '/home/Chris/meta/deps/cpptoml/deps/meta-cmake'... fatal: unable to access 'https://github.com/meta-toolkit/meta-cmake.git/': Failed to connect to github.com port 443: Connection timed out fatal: clone of 'https://github.com/meta-toolkit/meta-cmake.git' into submodule path '/home/Chris/meta/deps/cpptoml/deps/meta-cmake' failed Failed to clone 'deps/meta-cmake' a second time, aborting Failed to recurse into submodule path 'deps/cpptoml'

problem solved.i am in China ,so i need to add some settings in host and flush the dns