geofence plugin no longer compiles on ios

Hi, with the recent update of the core apple system that happened last night, it appears to me this plugin is no longer compatible.  I'm getting build compile errors in Swift.  Would love to help out but at present have no time so I'm passing this along.  Please fix as soon as possible! :)
What I did to test this:

downloaded fresh ionic-geofence example app from github
have correct cli when running npm install
ran npm install
added ios platform (all plugins carried over from the output)
ran in emulate: 5 swift compile errors
ran in xcode: 19 swift compile errors

These errors are found in:
Plugins/json.swift
Plugins/SwiftData.swift
And your plugin, I replaced "as" to "as!" which fixes your issues  apparently but it appears you are using libraries that are no longer compatible.
Thanks!

+1 to this. We've having the same problem getting projects using this plugin to compile in XCode 6.3.

I actually fixed this, it looks like there were some mild changes to swift that broke this.  One issue is the NSString optional assigned to a String variable, just changing NSString to String fixes it and there's some "as" to "as!" changes.  I forked the repo, I'll make changes and push and see if he can help test and make sure that everything still works as expected.
Thanks!

Great :+1: . I haven't upgrade to XCode 6.3 yet. Waiting for PR

Hey tsubik!  I just pushed this to the forked repo, let me know when you have a chance to look it over.  It has formatting changes on top of the code changes so the diffs are a little muddy.

Hey @DataHerder I'm getting the following errors after installing your fork of the plugin:
2015-04-17 09:26:28.044 notificationTesterApp[1520:376116] CDVPlugin class HWPGeofencePlugin (pluginName: GeofencePlugin) does not exist.
2015-04-17 09:26:28.045 notificationTesterApp[1520:376116] ERROR: Plugin 'GeofencePlugin' not found, or is not a CDVPlugin. Check your plugin mapping in config.xml.
2015-04-17 09:26:28.045 notificationTesterApp[1520:376116] -[CDVCommandQueue executePending] [Line 159] FAILED pluginJSON = ["GeofencePlugin534443115","GeofencePlugin","initialize",[]]
2015-04-17 09:26:28.045 notificationTesterApp[1520:376116] CDVPlugin class HWPGeofencePlugin (pluginName: GeofencePlugin) does not exist.
2015-04-17 09:26:28.046 notificationTesterApp[1520:376116] ERROR: Plugin 'GeofencePlugin' not found, or is not a CDVPlugin. Check your plugin mapping in config.xml.

This is after removing the generated XCode project and creating it again using cordova platform add ios and cordova build ios.

I was able to successfully compile the application using my repo with a new starter project.  Here are the steps:
Step 1:
ionic start test-geo
Step 2:
sudo chmod 777 test-geo
I need to do that on my machine or I get a node error, may not be the same for you
Step 3:
sudo npm install
Step 4:
cordova plugin add https://github.com/DataHerder/cordova-plugin-geofence.git
Step 5:
ionic platform add ios
Step 6:
Open up xcode project in Xcode and compile

What kind of build settings are you using in Xcode? I'm getting the following errors now: when targeting iOS 7.0 or higher as my deployment target: screenshot

Turns out that creating a new ionic project over the top of the existing project isn't a good idea. It's running as expected now without compile errors. :-P

:+1: cool!

@DataHerder
I can confirm that too (the String an as!) I made the change on my project and it worked great.
Are you doing a pull request? If not, I will

I am unable to create a branch on this project and I am unable to push to a branch on this project at this time unless tsubik gives me access apparently.  I get Forbidden access pushing a branch "swift-change" to the repo.

https://github.com/cowbell/cordova-plugin-geofence/pull/39


need to strip the path seprator at the end of the path string

On windows, to install a local pacakge through python setup.py develop, i was prompted:
("Can't get a consistent path to setup script from installation directory", 'd:\devroot\src\gitee.com\kadeem\freeway\', 'd:\devroot\src\gitee.com\kadeem\freeway')
The difference is the trailing slashes, because os.path.normcase don't remove the trailing seprators
Summary of changes

Closes
Pull Request Checklist

[ ] Changes have tests
[ ] News fragment added in changelog.d. See documentation for details

@shenqisoft Thank you for your report and PR!
This issue was reported as #1519, and there is an open but approved PR for it in #1521. Since that one is basically ready to merge and this one is not (it would need tests, and it supports fewer edge cases than the version in #1521), I am going to close it, but as a general policy, we do welcome PRs if you have future issues!


Compatibility with Beta 8

Waiting to see compatibility with Beta 8 for manage registered users.

user-list ? is another plugin?

Yes this one wasn't listed yet, thanks.

Umh there is a github page where i can activate notification for new release? I am subscrived to this plugin user-directoy, if this will be updated to Beta 8 ok, if not i need find the plugin that will be compatible with Beta 8. The most important things is be able to have a list of users. Thanks again :)

Yes feel free to subscribe to releases. Or follow https://twitter.com/flagrowio ;)

Yes but with link? Where is the plugin link? Is this one on GitHub or is another?

This is the one for the public user list, the users-list extensions is for the one that shows the list in the admin and allows for mass mailing (or something like it).


Documentation is lacking

Readme goes directly to code, without explaining what concepts the library operates with; what is a Link, an Element, Events, animateScroll and so on and how it all fits together.
I think this is an issue. At least what is what and the basic mechanics / use cases should be explained in plain English.

Update documentation please, i can't understand how work with scrollSpy and other objects from library.

It would also be great to know in the documentation which props for example will all be accepted.
When this is done it will be way easier to update the corresponding typescript typings.


not able to do keyboard navigation within ADS because of the callout dialog

once we have the callout dialog opened once, the keyboard navigation within ADS is broken, unless the notebook is closed.

also, keyboard navigation is not possible within this dialog

@halerankin please take a look. We need to fix this for March. Please let me know if you have any concerns.


Feature request: Add "X-Forwarded-For" to keys

No auto tip for XFF now.

@AKXF2020
Dear @AKXF2020
Thank you so much for creating the feature request.
The upcoming version(1.0.61) includes the header.


Add interfaces to allow using custom modules to inject in worker

What changes are proposed in this pull request?
Add interfaces to allow using custom modules to inject in worker
Why are the changes needed?
The LocalAlluxioCluster can be reused outside the repo with custom worker implemenetation.
Does this PR introduce any user facing changes?
no

alluxio-bot, merge this please

@ssyssy FYI


Twitter not working

Are you using ... https://github.com/jublonet/codebird-cors-proxy ?
I had to use that proxy to make Twitter work again.
e.g. twitter:{ proxy: "/assets/js/codebird-proxy/"

so must change in codebird.js ? Could you give me exactly?

Download https://github.com/jublonet/codebird-cors-proxy  into a directory on your website .... and then in your jquery running socialfeed add proxy: "<path to codebird-cors-proxy-directory" to the twitter bit.
e.g.
$('#socialfeed').socialfeed({
twitter:{
proxy: "/assets/js/codebird-proxy/",
accounts: ['@x'],
limit: 6,
consumer_key: 'x',
consumer_secret: 'x'
},
show_media: true,
length:240
});

thank u! It works now

Glad to hear :)


sensu-client is 'stopped' after machine reboot

Using v0.19 sensu-client running on some machine, once the machine is rebooted the service is 'stopped'

https://sensuapp.org/docs/latest/install-sensu-client#enable-sensu-on-boot


Release/cf220

Removed "Performance-sizing guidance for rendering with a small configuration" content from CF220 release

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: biancaluna:x: sunilkn002-hclYou have signed the CLA already but the status is still pending? Let us recheck it.


Refcounting fix for bug exposed by qps_test

This still needs some refinement, but the idea is to take a ref on the stream when it becomes writable... otherwise we risk resurrecting a reference after the write loop, which leads to disaster.

Ok, there's definitely a memory leak introduced by this.
I have some clues... will try to get back to this tonight.

But a nice thing is that the perf smoke test actually completed!

Made some progress. One leak left it seems.

Awesome!

I'm almost certainly going to regret this, but based on https://grpc-testing.appspot.com/view/Pull requests/job/gRPC_pull_requests/6648/, green enough?
This is certainly ready for review.

Let me push it hard with some perf scripts. Let's go above and beyond the
call of duty here....
On Wed, Mar 2, 2016, 11:31 PM Craig Tiller<EMAIL_ADDRESS>wrote:

I'm almost certainly going to regret this, but based on
https://grpc-testing.appspot.com/view/Pull requests/job/gRPC_pull_requests/6648/,
green enough?
This is certainly ready for review.
—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/5535#issuecomment-191629536.

Well, actually, Jenkins answered that for me. Any idea why the performance smoke test is still failing? Is this related to the bug that was trying to be fixed here?

Is this portion passable from the sanity log?
PASSED: make [time=2.7sec; retries=0:0; cpu_cost=0.8; estimated=1.0]
failed to detect port server: <class 'urllib2.URLError'>
None

I'm happy with the code review; I've asked the questions I wanted.

I think the perf tests are pointing to another thing. The crash this is fixing left a very clear 'stream xxx still in list 4' trace in the log whenever it happened.

Ok, yes, I recall seeing those traces. Less frequent, though. The code
looks good, so let's live dangerously!
On Wed, Mar 2, 2016 at 11:46 PM Craig Tiller<EMAIL_ADDRESS>wrote:

I think the perf tests are pointing to another thing. The crash this is
fixing left a very clear 'stream xxx still in list 4' trace in the log
whenever it happened.
—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/5535#issuecomment-191635881.


Package proposal: autopsy.vm

Package Name
autopsy
Tool Name
Autopsy
Package type
SINGLE_EXE
Tool's version number
4.19.3
Category
Forensic
Tool's authors
Brian Carrier
Tool's description
Autopsy® is a digital forensics platform and graphical interface to The Sleuth Kit® and other digital forensics tools. It is used by law enforcement, military, and corporate examiners to investigate what happened on a computer. You can even use it to recover photos from your camera's memory card.
Download URL
https://github.com/sleuthkit/autopsy/releases/download/autopsy-4.19.3/autopsy-4.19.3-64bit.msi
Download SHA256 Hash
c61beb6ad0ccb6182c9af376fd74b12387f6bfac515bada249f8c9ca96f9cb72
Why is this tool a good addition?
Autopsy is an easy to use, Digital Forensics GUI-based program that allows you to efficiently analyze hard drives and smart phones. It has a plug-in architecture that allows you to find add-on modules or develop custom modules in Java or Python.

Completed: https://github.com/mandiant/VM-Packages/pull/782


New status overlay

add a background and improve visibility
disable zooming when the overlay is shown
rewrite ErrorContactDevRectangle inline, remove old component
simplify the code a little

(I didn't rewrite the whole file; Github just doesn't realize the file was renamed.)

Look good. Thank you


[Sema] Warn on @_implementationOnly imports from a module without library-evolution

Add a warning on uses of @_implementationOnly from an importer module without library-evolution. @_implementationOnly was designed for use from resilient modules only, using it from non-resilient modules is unsupported and can lead to run time crashes.
If anyone hits this warning, they should either enable library-evolution or consider adopting the new internal import when it is available as it handles this scenario properly.
More about what actually leads to a crash: an @_implementationOnly import fully hides the dependency from indirect clients. This can lead to the compiler being unaware of some internal details (mostly incomplete memory layouts) of a non-resilient module when building a client against it. In turn, this may lead to run time crashes caused by miscompilation. We don't see this problem with resilient modules as the required information is queried at run time.
In general, one could still use @_implementationOnly in a non-resilient modules as long as it's referenced only from function bodies. However, using imported types for even non-public properties does lead to important memory layout information being hidden from clients of the module.
rdar://78129903

@swift-ci Please smoke test

Fixing more tests and adding more -swift-version 5.
@swift-ci Please smoke test

@swift-ci Please smoke test

In general, one could still use @_implementationOnly in a non-resilient modules as long as it's referenced only from function bodies. However, using imported types for even non-public properties does lead to important memory layout information being hidden from clients of the module.

@xymus Are there other problems due to using implementationOnly in non-resilient modules? Could we produce a warning when a type is used incorrectly instead of this warning?
We are using @_implementationOnly extensively in a bunch of non-resilient modules and have warnings-as-errors. The update to Xcode 15.3 brought us this warning and it seems like there's no good workaround.


No license?

Hi
This is a very interesting project but there is no license specified.
Could you please add one or perhaps let me know what you allow?
The most developer friendly license is MIT (see https://github.com/opennars/OpenNARS-for-Applications for a similar project with this license)
Thanks!
Seamus

Hello, good idea. After doing some reading, this MIT license seems the most reasonable choice for open-source software.
Anyone can use this code without restriction. It is based directly on the description of NARS in the book Non-Axiomatic Logic - A Model of Intelligent Reasoning by Dr. Pei Wang.


For vue-apollo@3 and apollo-client@3, an old apollo-client@2 is still required.

Describe the bug
After upgrading from apollo-v2 to apollo-v3 and vue-apollo from v2.* to v3.* vue-apollo still requires old dependencies from the apollo-client package.
Old closed issue that wasn't fully fixed - https://github.com/vuejs/vue-apollo/issues/1059
Related discussion https://github.com/vuejs/vue-apollo/discussions/1079
To Reproduce
Upgrade project following an official tutorial: https://www.apollographql.com/docs/react/migrating/apollo-client-3-migration/#updating-imports
Delete unneeded apollo-client library.
Run project.
Get err..
node_modules/vue-apollo/types/vue-apollo.d.ts
13:28 Cannot find module 'apollo-client/util/Observable' or its corresponding type declarations.
11 | } from 'apollo-client'
12 | import { FetchResult } from 'apollo-link'

13 | import { Observable } from 'apollo-client/util/Observable'
|                            ^
14 | import { ApolloProvider, VueApolloComponent } from './apollo-provider'
15 | import {
16 |   VueApolloQueryDefinition,

Expected behavior
Replace imports an old dependencies from apollo-client with new imports from@apollo/client.
Versions
"vue-apollo": "^3.0.7",
"@apollo/client": "^3.3.20",
"vue": "^2.6.14",

Another example is in apollo-provider.d.ts:
import { ApolloClient } from 'apollo-client'

I had to manually change that to @apollo/client in order not to get the following error when giving VueApollo a defaultClient created with the ApolloClient from @apollo/client:
Type 'ApolloClient<NormalizedCacheObject>' is missing the following properties from type 'ApolloClient<any>': store, writeData, initQueryManager

@EM-Benji Note that all Vue Apollo documentation still instructs to install apollo-client 2 as a peer dependency instead of @apollo/client 3.
Confusingly it seems this will change only starting Vue Apollo 4.

@HansCronau I know the docs say install apollo-client but then why does the package depend on @apollo/client as shown in the package.json https://github.com/vuejs/vue-apollo/blob/92a4a11e2627d39981f2c9ec1e46e1fc9e6dcb09/packages/vue-apollo/package.json#L47 and the commit https://github.com/vuejs/vue-apollo/issues/1059#issuecomment-709331356 that adds it so you end up needing both apollo-client and @apollo/client.
either be fully updated to use only @apollo/client and update docs for v3 or revert the dependency changes on v3 and make @apollo/client a v4 only change.

@EM-Benji The line you are pointing to is a dev dependency of vue-apollo 3. It is not a peer dependency and AFAIK you are not required to install it alongside apollo-client 2.
I believe issue #1059 was closed, because @mstys incorrectly assumed that vue-apollo 3 was supposed to support @apollo/client 3. In his defense: I made the same mistake and it took me a day to realise why stuff didn't work as I had expected.
That does leave your question: why does vue-apollo 3.0.7 have a (dev) dependency on @apollo/client 3? I'm not entirely sure. Going by the message of commit 6dc7c8e, which introduced the change, it appears the goal was to fix TypeScript typing.
The help the Vue Apollo devs manage issues: could I suggest closing this issue, or updating the title?


Semester selection and admin page course list broken.

The semester selection and course list on the admin page are currently broken. This might be due to a course scheduled in 1970.

Scheduling a course < 1970 works for me and does not lead to any issues. 🤔


Change in behaviour with files from workspace folder

We're working on upgrading josh from a one year old version (https://github.com/josh-project/josh/commit/effe6290559136faba5591a115e56c2b30210329) to the latest one, and have run into an unexpected behaviour.
We have some workspaces that are defined in our monorepo, and "exported" to various other places. For example, there is a //views/tvix workspace which constructs the exported view of our tvix project on Github: https://github.com/tvlfyi/tvix
When we upgrade to the latest josh, the resulting commit hashes from this workspace change. I poked around a bit and noticed that the files that were previously "pulled in" from the folder in which the workspace is located (e.g. this buildkite.yml file) are now missing in the exported tree.
I read through many of the commits between then and now, but am not sure which one introduced this. Haven't had the time to bisect yet. Does this sound familiar, and is there a way to get the old behaviour back, so that we can continue the same commit history without force-pushing?
I've pushed a workspace filter with a new version of josh to the hash-debug branch, where it's visible that the contents of default.nix differ between it and the canon branch and the buildkite.yml file is missing.

Sorry you are running into this...
We are quite careful to avoid this kind of behavior changes, but we needed to fix the behavior in cases where filters can "overlap", that is the same input path getting mapped to the same output path, to be able to have consistent behavior when reversing the filters.
What you did here is a bit strange because the last line in workspace.josh is :/tvix: A filter without any prefix, completely overlapping the actual workspace root. I have never seen that before ;)
But it is valid, so we have to deal with it...
That explains the difference in content of default.nix.
I can't explain the missing buildkite.yml yet so I will need to take a closer look at what is happening here.
The easy way out would be force push of course, but I'll check if we can do something else: In a similar (but certainly more complicated) way as the :unsign filter it might be possible the get to the same sha as before by somehow pre-filtering before applying the workspace.

What you did here is a bit strange because the last line in workspace.josh is :/tvix: A filter without any prefix, completely overlapping the actual workspace root. I have never seen that before ;)

Basically the idea of this is that the //views folder in our repository contains workspace definitions that "cherry-pick" other parts of the repository together, and enhance them with things like external-facing READMEs or CI definitions. This looks much more "lively" in the example of //views/kit (i.e. in the sibling folder to this one), as //tvix only needed some minor internal dependencies from the repo.

In a similar (but certainly more complicated) way as the :unsign filter it might be possible the get to the same sha as before by somehow pre-filtering before applying the workspace.

If this arose because of a bugfix, then this is probably not worth it and we should just eat a force push (especially as we have no guarantees about the external copy of the repo right now). If it's doable with existing filters, that'd be nice, but if it needs new filters to be implemented then I'd vote for skipping it.

Basically the idea of this is that the //views folder in our repository contains workspace definitions that "cherry-pick" other parts of the repository together, and enhance them with things like external-facing READMEs or CI definitions. This looks much more "lively" in the example of //views/kit (i.e. in the sibling folder to this one), as //tvix only needed some minor internal dependencies from the repo.
Yes, that is what workspaces are meant to be used for. The problem here is just that workspaces always contain an implicit :/<workspace root> and with :/tvix now two canon folders are mapped to the same ws folders. That means even if you do get the right result for read access this will lead to ambiguity as soon as you try to push (it will work, but the result is probably not what you expect/want)
This problem is not present in the "kit" workspace. (It's sha should not have changed)

If this arose because of a bugfix, then this is probably not worth it and we should just eat a force push (especially as we have no guarantees about the external copy of the repo right now). If it's doable with existing filters, that'd be nice, but if it needs new filters to be implemented then I'd vote for skipping it.

The default.nix overlap should be fixable by filtering the not wanted one out first:
::exclude[::tvix/default.nix]:workspace=views/tvix
There might also be a solution for buildkite.yml.
If practical I would still go for the force push. But wait until thebuildkite.yml absence is understood. In case there is another bug there.

So I did some digging and it turned out this is actually a bug. The fix is in #1159
With the fix applied the tvix workspace yields the same sha as before. So no force push will be necessary.
I would still recommend to change the workspace to not have an overlapping mapping for the root, for the reasons already described: It will not (cannot) work well if the backwards direction ever becomes important.
But I'm certainly glad you did it this way to expose this quite subtle bug. :)

Great, confirmed that in combination with :unsign the latest commit yields the same hashes as before :)
Thanks so much!


[7|Resource Page (Item) and Note Taking Feature] The Questionnaire/Poll Section

 🍰 Appetite 🍰

Property
Value

Points
?? points

Difficulty rating
★★★★☆

Maximum Assignees
5 person

🤔 Problem Statement

This Piece has three parts:

Create a custom field in Payload CMS to allow the creation of a multiple-choice questionnaire with a chosen correct answer or a poll. (The poll has no chosen correct answer)

Create a multiple-choice questionnaire or poll section on the Resource Page to serve the newly created custom field in Payload CMS (in case the questionnaire or poll exists for that Resource Page). This section should be below the Content Space and above the Comment Section as shown in the sketch above. Make sure that with the questionnaire, when the user makes a selection, the component will react and tell the user if the answer is correct or incorrect.

After the user makes his/her selection, the result will be sent to Supabase. Then, this component will fetch down all of the answers from all users for that questionnaire (or poll). Next to each questionnaire or poll selection, display the selected ratio between them.

🧪 Required Tests
Mainly screenshot tests, some integration tests for Payload CMS and Supabase.
Review the Code & Testing Guidelines for more info.
⚠ Careful about:
No major rabbit holes identified. But always be careful with scope creep!
🤖 Technologies focused on in this feature

React
Tailwind
Shadcn
Payload CMS
NextJS
Supabase/PostGresQL

Can I work on this @vo-d

@thejasveer It's yours if you still want it!


egui 0.16

Basically copied egui_glium's Painter for the new 0.16 API, as TextureAllocator no longer provides a mutable self.
Right now it doesn't nicely extract epi::backend::TexAllocationData from an epi::Frame nor does it handle it, which could be something to add.

Def not the best way to do this (it's really easy to step on your own feet). Anyone have any ideas?

Thank you for your PR.
This PR seem to implement more than just adding support for egui 0.16. Please rebase you changes and only add only the changes that are needed for the current feature set. For example: I'm not sure why you arced the BindGroup.  "set_texture()" seems to be a new feature?
I also fell that the trait for egui_texture_to_wgpu() is overkill and we could simply use parameters.
The cleanup suggestions by parasyte also seem valid.

My understanding is that the set_texture thing is trying to follow https://github.com/emilk/egui/pull/999
I don't know if changing texture allocation is necessary, here. But if I read that PR right, the high-level API appears to be in epi:

https://github.com/emilk/egui/blob/0960f385523e4206a23c92f1dbb06330cb9ce02a/epi/src/lib.rs#L333-L341
https://github.com/emilk/egui/blob/0960f385523e4206a23c92f1dbb06330cb9ce02a/epi/src/lib.rs#L344-L352

This is what I would suggest looking to for inspiration.

I also have a discussion here, but my big problem is that TextureAllocator is now by shared reference, which makes it impractical for the TextureAllocator to be the Renderpass. (I'm probably wrong, but the only way I can think of off the top of my head is to make Renderpass send messages to itself? Might work idk.)

I also fell that the trait for egui_texture_to_wgpu() is overkill and we could simply use parameters.

Yeah, it is... I did it so that epi::FontImage and a custom image data type can both work with the method without duplication

For example: I'm not sure why you arced the BindGroup. "set_texture()" seems to be a new feature?

I was basically following https://github.com/emilk/egui/pull/999/files#diff-23f23e44bac11e24b5797a2fa0734dbcd65b21830492cde1ad030e2314e76e7f and here the Texture points to an Rc, which hints that the type should be clonable because of how epi::NativeTexture works: it takes the texture by move, so if users want to also display the texture outside of egui, they still need a copy, which explains the Arc. Honestly, it should be Arc<wgpu::Texture>.
So action items:

[ ] Remove Arc<BindGroup>, and replace with Arc<Texture> in NativeTexture
[ ] Remove Arc from user_textures
[ ] Remove free_texture and rename free_texture_id -> free_texture (or completely remove it and set_texture)
[ ] Use message passing to pass stuff from uses as TextureAllocator into a pending queue
[ ] Clean up

but my big problem is that TextureAllocator is now by shared reference

If that's the only problem, you can use a type that offers interior mutability. RefCell or Mutex, for instance. It looks like you started to do that with the commented code, but abandoned it for some reason?
It should also be mentioned that this crate doesn't use epi at all, except to implement the TextureAllocator trait.

If that's the only problem, you can use a type that offers interior mutability. RefCell or Mutex, for instance. It looks like you started to do that with the commented code, but abandoned it for some reason?

I tried that, but it got real nasty, as this crate returns a reference to the bind groups it holds internally, but you reasonably can't send a reference through a lock, the lock doesn't live long enough... (and bind groups aren't Clone, so no go there).

It should also be mentioned that this crate doesn't use epi at all, except to implement the TextureAllocator trait.

That's a pretty important use (to me), as it was what made egui_example work at all!

I also fell that the trait for egui_texture_to_wgpu() is overkill and we could simply use parameters.

Does this mean handling UserTexture and epi::FontImage separately? Wouldn't that duplicate work? I might be misunderstanding what you are saying...

I tried that, but it got real nasty, as this crate returns a reference to the bind groups it holds internally, but you reasonably can't send a reference through a lock, the lock doesn't live long enough... (and bind groups aren't Clone, so no go there).

Got it. I'll be honest, I haven't really dug into the issue or tried to work through it in practice. But then again #52 proposes to remove the TextureAllocator implementation entirely.

That's a pretty important use (to me), as it was what made egui_example work at all!

Yes, but I'm not sure you need to use epi for anything other than the egui_demo_app, or another app that is already built on it. If starting from scratch, you don't need it. The whole thing is kind of confusing, which is why I opened https://github.com/emilk/egui/issues/212 Emil's first response is spot on.
In light of that, I don't think there is a need for epi or its TextureAllocator trait at all.

I just pushed a version that support egui 0.16 to crates.io. If something is missing, please open another issue / PR.

Closing as #52 was merged


DOC: Distinct warnings for benchmark and treasury fetchers

The core of data/loader.py is the function load_market_data which
in turns calls functions ensure_benchmark_data and
ensure_treasury_data. These two functions are similar. Their
logger.info and logger.exception messages are slightly different
but their logger.warn messages are the same.
Having two different functions outputing the same warning can
be needlessly confusing when debugging.
This commit makes these two warnings explicitely different.

No idea what failed, my changes were extremely minimal.

Hi @JoaoAparicio it looks like there was some style warnings coming from flake8:

You'll probably want to just make that log string into a multi-line string, which you can do with parentheses. I'd also probably add in the dates there. An example can be found here: https://github.com/JoaoAparicio/zipline/blob/b7bd52fdcdf1bf0c4bd7522b976324fa77a0103b/zipline/data/loader.py#L218

@FreddieV4 You were right, I had forgotten to run flake8.
Made the fixes to mentioned. In addition added dates to yet another treasury fetcher logger.info message.

LGTM 👍 Thanks!


Hosted pipeline agent

Hello, the documentation mentioned the initial run could be run on the Hosted Pipeline, and then switched to the custom image, but this isn't the case, as the Hosted Pipelines have a 6 hour maximum run time.
https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/hosted?view=azure-devops&tabs=yaml

I never noticed that limitation, and I ran my first image on a paid Microsoft hosted agent with success.
Have you tried it and did it fail?

Hi @YannickRe, yes, I tried it twice using the MS Hosted Agent, both times failed at 6 hours 15minutes.

I got the scripts to work by creating a self hosted agent with a temporary VM, and then manually installing chocolaty, packer and the latest Powershell.
It took a number of failed attempts before I found the required packages needed to run the scripts fully.
Thank you for your time in putting this together, but I thought it would be useful to update your readme to mention the Hosted Agent has timeout of 6hours and would not be able to create a windows image using it.

Thank you for informing me! Feel free to submit the PR, but otherwise I'll keep this open until I get to adjusting the readme myself.
Probably this would work too: Hosted Agent to build a Linux Agent, and then use the Linux Agent to build your Windows Agent. Not sure what would be quicker: this extra step with the Linux agent or you trying to create a minimal image to create the full image 😀
Glad you made it work, and again: thank you!

yes this is a bummer, im trying to create a vmss with Linux first then will run the CICD scripts using the vmss agent to create windows image

yes this is a bummer, im trying to create a vmss with Linux first then will run the CICD scripts using the vmss agent to create windows image

Microsoft is looking to change their scripts to only install the LATEST of each .NET runtime, which should drop the end to end runtime a huge amount, this change is going to take place September 6 I believe.
The crazy thing is running the same scripts on our own hosted agent only took 5 hours, but depending on when you try to run it in the public pipelines you might run into "noisy neighbors" where all the other people using public pipelines slow down the build due to I/O or network contention.

Have you got the URL that explains what MS are going to change in
September.  That would be really helpful.
On Mon, 9 Aug 2021, 19:37 spoelstraethan, @.***> wrote:

Microsoft is looking to change their scripts to only install the LATEST of
each .NET runtime, which should drop the end to end runtime a huge amount,
this change is going to take place September 6 I believe.
The crazy thing is running the same scripts on our own hosted agent only
took 5 hours, but depending on when you try to run it in the public
pipelines you might run into "noisy neighbors" where all the other people
using public pipelines slow down the build due to I/O or network contention.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/YannickRe/azuredevops-buildagents/issues/8#issuecomment-895448497,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AH7GYFYEJ5O4VIYJCE6MAS3T4AN6TANCNFSM5AKDZCSQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

@CurlyBytes thank you for the PR, I merged it and made some other README updates too
@spoelstraethan thank you for the heads up, that would help a lot for sure
@Marcus-James-Adams they mention the change here: https://github.com/actions/virtual-environments/issues/3809
Given that the README is updated regarding the original issue, I will now close this issue.


The uglify 'warning' output is missing filename

The uglify 'warning' option throws useful messages to console.error. Unfortunately, it does so without filename information. If you're uglifying a bunch of files, that's a real drag.

We should probably ask the UglifyJS project to hand us the warnings so that we can do something with them.

Good point. In the mean time, as you might've seen, I've put in a PR (#164) for your consideration.

Opened mishoo/UglifyJS2#958.

In version 3, UglifyJS now passes the warnings back to the caller of the API, so I'll now be able to handle it in a better fashion. I haven't decided how I'll do so yet, but tagging this ticket for the next major release.

@erwinw On the "three" branch, I'm logging the warnings (along with the filename) to the gulp logger. I think this preserves the behavior expected, without requiring a separate gulp plugin to print them (like the eslint gulp plugins).
Please give it a shot and let me know what you think. In the meantime, I'm closing this ticket, as I think the work is done and awaiting release.


Issue Winhost "hanging" after transition #1835

What changed?
I found a StackOverflow post (https://stackoverflow.com/questions/12465357/force-redraw-after-storyboard-with-windowsformshost-wpf/12748181#12748181) with the same problem and implemented a fix using de solution provided (calling InvalidateVisual() when the transition is completed to force a redraw of the Winform Host).
I believe a more elegant solution would be to have events for when the transition animation is starting or completing so that the developer can decide if it is better to hide the Winform host until the transition is completed, avoiding that the user seeing the winform control abrupty moving to another position when the transition is completed.
These new events would have to be created in MetroContentControl and MetroWindow controls.
I can do this, but  I´d like to ask if this is something the project maintainers think is a good idea.
#1835

@petvetbr Thx for this. I changed it a little bit, I added a TransitionCompleted event to MetroContentControl and WindowTransitionCompleted event to MetroWindow which will be fired after the loaded Storyboard is completed.


Expose AWS role and user mappings

Allow additional role and user mappings to be added to the aws-auth
config map.

cc @eshamay


CLI: deploy,scale,? commands to show event log with the spinner

maybe with --events ?
Currently I'm hacking it like this:
kontena service events --since $(date -u +"%Y-%m-%dT%T.0Z") -t myservice &
kontena service scale myservice 10

related PR: #2195 which has been on the shelf/hold for a while because it started to get a bit too fancy (multiple simultaneous progress bars etc).


Separate type imports only if necessary.

Is your feature request related to a problem?
I like to have my imports on a single line, but importing types quickly makes it span in multiple lines.
So I would like to have a way, to separate out the type imports on a separate line below when the import statements exceed the prettier printWidth limit.
Describe the solution you'd like
For example,
// before
import {
  applyPatches,
  enablePatches,
  produce,
  produceWithPatches,
  type Draft,
  type Objectish,
  type Patch,
} from 'immer'

// after
import { applyPatches, produce, produceWithPatches, enablePatches } from 'immer'
import type { Draft, Objectish, Patch } from 'immer'

Additional context
But if possible, the imports and type imports should be kept together if it could fit in a single line.
For example, the following should be unchanged.
import { applyPatches, produce, type Draft, type Patch } from 'immer'

If you want to always split your type imports into a different import expression, you can do that with the <TYPES> magic word: https://github.com/IanVS/prettier-plugin-sort-imports?tab=readme-ov-file#4-group-type-imports-separately-from-values
We do not have the ability to dynamically make that decision if-and-only-if the line would otherwise wrap, sorry!

Yes, I was aware of the <TYPES> thing.
But how could I make it so that the type imports automatically always appear at the bottom of import expressions?
Thanks!

I’ve never seen a codebase organized like that! In this situation, especially if you’re just curious (😉) about it, I would recommend forking this package to implement that feature.
The goal of this package is to implement a mostly opinionated set of additions on top of prettier, and there’s no reason you can’t layer your own style on top of this. Good luck!

I think this request is similar to https://github.com/IanVS/prettier-plugin-sort-imports/issues/147#issuecomment-2378281985.
I think it would be difficult to build this in a way that considers line-length limits (due to the way that prettier works), and while we could add an option to break apart type and value imports while keeping them next to each other, one of our goals is to keep our number of options to a minimum.  If you would like to always split apart type and value imports, while keeping those lines next to each other, please open a new feature request and we can use that to gauge interest on whether the behavior should perhaps be changed in a future major version.  Though I have to admit I think it will be a tough sell.


Making parser consistent with #542

Follow-up steps for #542 should be taken but I have no idea how to do.

Motivating example(I’m guessing there would be  a few more, I’ve not checked though):
#

Above simple code crashes the parser because parseIdent calls Parser.next with Eof, eventually violates an assertion of res_parser.ml added by #542. I thought it could be fixed easily by adding another pattern matching for Eof or substitute Parser.next with Parser.nextUnsafe(as far as it does not results another infinite loop), but neither pass the static analyzer. Any solution?
https://github.com/rescript-lang/syntax/blob/08029afafeef01cda2366c580b0b06d376b31d54/src/res_core.ml#L564-L586

@cristianoc

How about checking for Eof before calling parseIndent.

Please check #596.
Seems to work, though a few code repeat was needed.

Looks good.
Will take a closer look later.

Thank you.
Please let me know after taking a look later, as there are other similar cases to be treated.


when adding host in Kubernetes environment we should stay on Kubernetes page

Version - master UI 3/3
Steps to Reproduce:

Create a Kubernetes environment
Switch to that environment
Click on add host and add one

Results: Takes me to the Rancher Host page
Expected: Stay on Kubernetes page where you can see setting up status

Version - master 3/9
Verified fixed


ResponsePropertyBecameOptionalCheck panics on property removal

Describe the bug
ResponsePropertyBecameOptionalCheck throws a panic error on property removal
To Reproduce
Steps to reproduce the behavior:

Run -base {source_path}/breaking-changes-test-spec-base.yaml -revision {source_path}/breaking-changes-test-spec-revision.yaml -deprecation-days=365 -check-breaking"
With base
And revision
Recieve

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x2 addr=0x0 pc=0x104753ad0]

goroutine 1 [running]:
github.com/tufin/oasdiff/checker.ResponsePropertyBecameOptionalCheck(0x14000306870, 0x140000109a8, {{0x140001648c0, 0x38, 0x38}, 0x1f, 0xb4, {{0x10491566e, 0x2}, {0x10491566e, ...}, ...}})
	/<redactedpath>/workplace/oasdiff/checker/check-response-property-became-optional.go:39 +0x5c0
github.com/tufin/oasdiff/checker.CheckBackwardCompatibility({{0x140001648c0, 0x38, 0x38}, 0x1f, 0xb4, {{0x10491566e, 0x2}, {0x10491566e, 0x2}, 0x1400007f5c0}}, ...)
	/<redactedpath>/workplace/oasdiff/checker/checker.go:118 +0x14c
main.main()
	/<redactedpath>/workplace/oasdiff/main.go:172 +0xdcc

Expected behavior

Backward compatibility errors (1):
error at /<redactedpath>/workplace/mms/server/openapi/atlas/breaking-changes-test-spec-revision.yaml, in API GET /api/atlas/v2/removeOutputFieldTest removed the required property 'name' from the response with the '200' status [response-required-property-removed].

Desktop (please complete the following information):

OS: macOS Monterey
Browserchrome
Version oasdiff version: 1.3.4

Additional comments
Opening a PR to fix it now

fixed by https://github.com/Tufin/oasdiff/pull/189


♻Use my task to get task list

This change was also made in gradle-test-collector: https://github.com/unaguna/gradle-test-collector/pull/39

Wrong branch to merge into.


WARN is logged on Mapper creation if javax.el (optional module) is not on classpath

Are you in the right place?

For issues or feature requests related to the code in this repository file a Github issue.
For general technical questions, post a question on Google Groups.

Whats your runtime?

Dozer version: 6.5.0
OS version: Mac, Mojave
JDK version: 1.8

Whats the problem?
com.github.dozermapper.core.el.ELExpressionFactory#isSupported(java.lang.ClassLoader) logs a warning if javax.el is not on the classpath.
Observed Results:
A warning is logged.
Expected Results:
Warnings should indicate a potential problem.  Not having what is documented as an optional module should not be considered a potential problem.

i can easily submit a fix if there is agreement that this is an issue.  i have a work-around but it seems like this will be a problem for any organization that pays attention to warnings in their logs.

i see this as a nitpick as most alerting systems can dampen / ignore matching alerts but if you want to raise the PR, go for it.

I consider this an issue as well. If this is nitpicking really depends how your organization is reacting to log warnings. Our average Java stack has 100 - 200 libraries. Thankfully they tend not to spit out warnings when optional requirements are missing and they work fully functional. Therefor we get an alarm immediately when there is a warning.
Filtering out warnings is a workaround but there is a fair chance that you hide other warnings with similar text.

like I said, last year. If someone wants to raise a PR, go for it.


Added Swift 4 Support

This seems to be kind of stuck, shouldnt we merge the changes...

Moving this into #32


Comma problem for operator "FOR"

In according to our discussion https://github.com/elliotchance/c2go/issues/154.
Now, Just solved COMMA problem for operator "FOR".
Tests are added.
Integration tests - will be OK )).
One pull request for one task.
Also, that patch solve issue in https://github.com/elliotchance/c2go/issues/133.

This change is

Reviewed 1 of 4 files at r4, 4 of 4 files at r5.
Review status: all files reviewed at latest revision, 4 unresolved discussions.

a discussion (no related file):
Great work @konstantin8105 !

tests/for.c, line 48 at r5 (raw file):

    }

	diag("big ininitialization");

Did you mean "initialization"?

tests/for.c, line 53 at r5 (raw file):

	}

	diag("big ininitialization");

Please give this a different heading so it's easier to identify if the tests fails, like "big initialization 2"

transpiler/branch.go, line 138 at r5 (raw file):

	case *ast.BinaryOperator:
		c := children[0].(*ast.BinaryOperator)
		if c.Operator == "," {

There is a trick with Go when using type switching so that you don't have to use a temporary variable. You can assign a variable in the switch and it will always have the correct type from the case:
switch c := children[0].(type) {
case *ast.BinaryOperator:
    if c.Operator == "," {

Comments from Reviewable

Review status: all files reviewed at latest revision, 3 unresolved discussions.

tests/for.c, line 48 at r5 (raw file):
Previously, elliotchance (Elliot Chance) wrote…
Did you mean "initialization"?

done.

tests/for.c, line 53 at r5 (raw file):
Previously, elliotchance (Elliot Chance) wrote…
Please give this a different heading so it's easier to identify if the tests fails, like "big initialization 2"

done

transpiler/branch.go, line 138 at r5 (raw file):
Previously, elliotchance (Elliot Chance) wrote…
There is a trick with Go when using type switching so that you don't have to use a temporary variable. You can assign a variable in the switch and it will always have the correct type from the case:
switch c := children[0].(type) {
case *ast.BinaryOperator:
    if c.Operator == "," {

Done

Comments from Reviewable

Thank you for review.
Just for information.
One source more is Ok, in according to my rating.
https://github.com/Konstantin8105/c2go-rating
Also, I will try to solve the COMMA problem for While, Do...While, IF, Function, but after that review.
Please don`t reject, that pull request - just because - it is not Absolute full solving.
Also, for your information - present test inside integration test is not full check. So, I test by hand on preliminary that code:
#include <stdio.h>

int foo(int i)
{
	return i+i;
}

int main(void){
	int i,j,k = 8;
	for (i =0,j=1,printf("init\n"),k= 2;k+=5,printf("cond\n"),j++,j = foo(f),i<2000;i++,j+=2,printf("increment"),k+=3)
	{
		printf("%d %d %d\n",i,j,k);
	}
	return 0;
}

, but more more bigger.

Reviewed 2 of 2 files at r6.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Hello!
If all is Ok, then could you merge pull request.

Thanks @Konstantin8105 - https://github.com/elliotchance/c2go/releases/tag/v0.13.5


Error when several times switching between Home and "DDA Quant"

I observed that when switching between Home and "DDA Qaunt ... " several times
e.g. Home -> DDA Quant -> Home -> DDA Quant -> Home -> DDA Quant this leads to:

Reproduced on my local installation as well as on the server.
https://proteobench.cubimed.rub.de

Was this issue resolved? I tried to reproduce it both locally and on the server, as it appeared somewhat similar to https://github.com/Proteobench/ProteoBench/issues/286, however, I couldn't reproduce it even after switching 15+ times.


Update README with the instructions for editing/compiling a single lecture

i.e. https://github.com/QuantEcon/lecture-source-jl/blob/master/README.md
Explain how to edit a single lecture, what settings should be required (e.g. LF and 4 spaces for tabs?)
For windows: https://docs.microsoft.com/en-us/windows/wsl/wsl2-install

The docker on windows WSL may require waiting for the next release of windows.


relocate /var/lib/containers dir via mount --bind prevents container from start

I've relocated the the containers data dir via linux fs command mount --bind in order to change the real location where container data - especially volume data - are stored.
> mount --bind /srv/containers /var/lib/containers
This prevents the container from starting with the following error:
root@unhaim ~# podman run -it fedora  bash
bash: error while loading shared libraries: libc.so.6: cannot change memory protections

The mounted source dir /srv/containers is a local dir owned by root.

podman version 1.0.0
as root
on
Operating System: Fedora 29 (Server Edition)
CPE OS Name: cpe:/o:fedoraproject:fedora:29
Kernel: Linux 4.20.5-200.fc29.x86_64
Architecture: x86-64

Can you run podman --log-level=debug run -it fedora bash and pastebin the result? That would give us a good idea as to where in the init process we're failing.

Could this be SELinux?
What is the permissions on /srv?
ls -lad /srv

root@unhaim ~# mount --bind /srv/containers/ /var/lib/containers

root@unhaim ~# ls -lad /srv
drwxr-xr-x. 7 root root 111 22. Feb 08:03 /srv/

root@unhaim ~# ls -lad /srv/containers
drwxr-xr-x. 4 root root 34 22. Feb 08:05 /srv/containers/

root@unhaim ~# podman --log-level=debug run -it fedora bash
DEBU[0000] Initializing boltdb state at /var/lib/containers/storage/libpod/bolt_state.db
DEBU[0000] Using graph driver overlay
DEBU[0000] Using graph root /var/lib/containers/storage
DEBU[0000] Using run root /var/lib/containers/storage
DEBU[0000] Using static dir /var/lib/containers/storage/libpod
DEBU[0000] Using tmp dir /var/run/libpod
DEBU[0000] Set libpod namespace to ""
DEBU[0000] [graphdriver] trying provided driver "overlay"
DEBU[0000] overlay test mount with multiple lowers succeeded
DEBU[0000] backingFs=xfs, projectQuotaSupported=false, useNativeDiff=true
INFO[0000] Found CNI network podman (type=bridge) at /etc/cni/net.d/87-podman-bridge.conflist
DEBU[0000] parsed reference into "[overlay@/var/lib/containers/storage+/var/lib/containers/storage]docker.io/library/fedora:latest"
DEBU[0000] parsed reference into "[overlay@/var/lib/containers/storage+/var/lib/containers/storage]@d7372e6c93c6c7b925600981b655c94829515a37cf876ff9e6d0287ff2b739d9"
DEBU[0000] exporting opaque data as blob "sha256:d7372e6c93c6c7b925600981b655c94829515a37cf876ff9e6d0287ff2b739d9"
DEBU[0000] parsed reference into "[overlay@/var/lib/containers/storage+/var/lib/containers/storage]@d7372e6c93c6c7b925600981b655c94829515a37cf876ff9e6d0287ff2b739d9"
DEBU[0000] exporting opaque data as blob "sha256:d7372e6c93c6c7b925600981b655c94829515a37cf876ff9e6d0287ff2b739d9"
DEBU[0000] parsed reference into "[overlay@/var/lib/containers/storage+/var/lib/containers/storage]@d7372e6c93c6c7b925600981b655c94829515a37cf876ff9e6d0287ff2b739d9"
DEBU[0000] Using bridge netmode
DEBU[0000] parsed reference into "[overlay@/var/lib/containers/storage+/var/lib/containers/storage]@d7372e6c93c6c7b925600981b655c94829515a37cf876ff9e6d0287ff2b739d9"
DEBU[0000] exporting opaque data as blob "sha256:d7372e6c93c6c7b925600981b655c94829515a37cf876ff9e6d0287ff2b739d9"
DEBU[0000] created container "06e64eb5a0900b38fdc9e91f856562fd0515ed3e051fc641acdc438fb1f44590"
DEBU[0000] container "06e64eb5a0900b38fdc9e91f856562fd0515ed3e051fc641acdc438fb1f44590" has work directory "/var/lib/containers/storage/overlay-containers/06e64eb5a0900b38fdc9e91f856562fd0515ed3e051fc641acdc438fb1f44590/userdata"
DEBU[0000] container "06e64eb5a0900b38fdc9e91f856562fd0515ed3e051fc641acdc438fb1f44590" has run directory "/var/lib/containers/storage/overlay-containers/06e64eb5a0900b38fdc9e91f856562fd0515ed3e051fc641acdc438fb1f44590/userdata"
DEBU[0000] New container created "06e64eb5a0900b38fdc9e91f856562fd0515ed3e051fc641acdc438fb1f44590"
DEBU[0000] container "06e64eb5a0900b38fdc9e91f856562fd0515ed3e051fc641acdc438fb1f44590" has CgroupParent "machine.slice/libpod-06e64eb5a0900b38fdc9e91f856562fd0515ed3e051fc641acdc438fb1f44590.scope"
DEBU[0000] Handling terminal attach
DEBU[0000] Made network namespace at /var/run/netns/cni-5ffdb2a0-864b-3944-5789-85703a114c0c for container 06e64eb5a0900b38fdc9e91f856562fd0515ed3e051fc641acdc438fb1f44590
INFO[0000] Got pod network &{Name:happy_brahmagupta Namespace:happy_brahmagupta ID:06e64eb5a0900b38fdc9e91f856562fd0515ed3e051fc641acdc438fb1f44590 NetNS:/var/run/netns/cni-5ffdb2a0-864b-3944-5789-85703a114c0c PortMappings:[] Networks:[] NetworkConfig:map[]}
INFO[0000] About to add CNI network cni-loopback (type=loopback)
DEBU[0000] mounted container "06e64eb5a0900b38fdc9e91f856562fd0515ed3e051fc641acdc438fb1f44590" at "/var/lib/containers/storage/overlay/998148c769d992afb03fc83599a4d9425f2f1df0f5d914462833b7502dd047b9/merged"
DEBU[0000] Created root filesystem for container 06e64eb5a0900b38fdc9e91f856562fd0515ed3e051fc641acdc438fb1f44590 at /var/lib/containers/storage/overlay/998148c769d992afb03fc83599a4d9425f2f1df0f5d914462833b7502dd047b9/merged
INFO[0000] Got pod network &{Name:happy_brahmagupta Namespace:happy_brahmagupta ID:06e64eb5a0900b38fdc9e91f856562fd0515ed3e051fc641acdc438fb1f44590 NetNS:/var/run/netns/cni-5ffdb2a0-864b-3944-5789-85703a114c0c PortMappings:[] Networks:[] NetworkConfig:map[]}
INFO[0000] About to add CNI network podman (type=bridge)
DEBU[0000] [0] CNI result: Interfaces:[{Name:cni0 Mac:76:d1:7a:1a:8e:31 Sandbox:} {Name:vethb8a93945 Mac:2e:31:94:f7:94:9e Sandbox:} {Name:eth0 Mac:e2:08:28:ef:ce:6d Sandbox:/var/run/netns/cni-5ffdb2a0-864b-3944-5789-85703a114c0c}], IP:[{Version:4 Interface:0xc0000366e8 Address:{IP:<IP_ADDRESS> Mask:ffff0000} Gateway:<IP_ADDRESS>}], Routes:[{Dst:{IP:<IP_ADDRESS> Mask:00000000} GW:<nil>}], DNS:{Nameservers:[] Domain: Search:[] Options:[]}
DEBU[0000] /etc/system-fips does not exist on host, not mounting FIPS mode secret
DEBU[0000] parsed reference into "[overlay@/var/lib/containers/storage+/var/lib/containers/storage]@d7372e6c93c6c7b925600981b655c94829515a37cf876ff9e6d0287ff2b739d9"
DEBU[0000] parsed reference into "[overlay@/var/lib/containers/storage+/var/lib/containers/storage]@d7372e6c93c6c7b925600981b655c94829515a37cf876ff9e6d0287ff2b739d9"
DEBU[0000] exporting opaque data as blob "sha256:d7372e6c93c6c7b925600981b655c94829515a37cf876ff9e6d0287ff2b739d9"
DEBU[0000] parsed reference into "[overlay@/var/lib/containers/storage+/var/lib/containers/storage]@d7372e6c93c6c7b925600981b655c94829515a37cf876ff9e6d0287ff2b739d9"
DEBU[0000] exporting opaque data as blob "sha256:d7372e6c93c6c7b925600981b655c94829515a37cf876ff9e6d0287ff2b739d9"
DEBU[0000] parsed reference into "[overlay@/var/lib/containers/storage+/var/lib/containers/storage]@d7372e6c93c6c7b925600981b655c94829515a37cf876ff9e6d0287ff2b739d9"
DEBU[0000] Setting CGroups for container 06e64eb5a0900b38fdc9e91f856562fd0515ed3e051fc641acdc438fb1f44590 to machine.slice:libpod:06e64eb5a0900b38fdc9e91f856562fd0515ed3e051fc641acdc438fb1f44590
WARN[0000] failed to parse language "en_US.UTF-8": language: tag is not well-formed
DEBU[0000] reading hooks from /usr/share/containers/oci/hooks.d
DEBU[0000] reading hooks from /etc/containers/oci/hooks.d
DEBU[0000] Created OCI spec for container 06e64eb5a0900b38fdc9e91f856562fd0515ed3e051fc641acdc438fb1f44590 at /var/lib/containers/storage/overlay-containers/06e64eb5a0900b38fdc9e91f856562fd0515ed3e051fc641acdc438fb1f44590/userdata/config.json
DEBU[0000] /usr/libexec/podman/conmon messages will be logged to syslog
DEBU[0000] running conmon: /usr/libexec/podman/conmon    args=[-s -c 06e64eb5a0900b38fdc9e91f856562fd0515ed3e051fc641acdc438fb1f44590 -u 06e64eb5a0900b38fdc9e91f856562fd0515ed3e051fc641acdc438fb1f44590 -r /usr/bin/runc -b /var/lib/containers/storage/overlay-containers/06e64eb5a0900b38fdc9e91f856562fd0515ed3e051fc641acdc438fb1f44590/userdata -p /var/lib/containers/storage/overlay-containers/06e64eb5a0900b38fdc9e91f856562fd0515ed3e051fc641acdc438fb1f44590/userdata/pidfile -l /var/lib/containers/storage/overlay-containers/06e64eb5a0900b38fdc9e91f856562fd0515ed3e051fc641acdc438fb1f44590/userdata/ctr.log --exit-dir /var/run/libpod/exits --socket-dir-path /var/run/libpod/socket -t --log-level debug --syslog]
INFO[0000] Running conmon under slice machine.slice and unitName libpod-conmon-06e64eb5a0900b38fdc9e91f856562fd0515ed3e051fc641acdc438fb1f44590.scope
DEBU[0000] Received container pid: 33988
DEBU[0000] Created container 06e64eb5a0900b38fdc9e91f856562fd0515ed3e051fc641acdc438fb1f44590 in OCI runtime
DEBU[0000] Attaching to container 06e64eb5a0900b38fdc9e91f856562fd0515ed3e051fc641acdc438fb1f44590
DEBU[0000] connecting to socket /var/run/libpod/socket/06e64eb5a0900b38fdc9e91f856562fd0515ed3e051fc641acdc438fb1f44590/attach
DEBU[0000] Received a resize event: {Width:213 Height:29}
DEBU[0000] Enabling signal proxying
DEBU[0000] Starting container 06e64eb5a0900b38fdc9e91f856562fd0515ed3e051fc641acdc438fb1f44590 with command [bash]
DEBU[0000] Started container 06e64eb5a0900b38fdc9e91f856562fd0515ed3e051fc641acdc438fb1f44590
bash: error while loading shared libraries: libc.so.6: cannot change memory protections
DEBU[0000] Checking container 06e64eb5a0900b38fdc9e91f856562fd0515ed3e051fc641acdc438fb1f44590 status...
DEBU[0000] Cleaning up container 06e64eb5a0900b38fdc9e91f856562fd0515ed3e051fc641acdc438fb1f44590
DEBU[0000] Tearing down network namespace at /var/run/netns/cni-5ffdb2a0-864b-3944-5789-85703a114c0c for container 06e64eb5a0900b38fdc9e91f856562fd0515ed3e051fc641acdc438fb1f44590
INFO[0000] Got pod network &{Name:happy_brahmagupta Namespace:happy_brahmagupta ID:06e64eb5a0900b38fdc9e91f856562fd0515ed3e051fc641acdc438fb1f44590 NetNS:/var/run/netns/cni-5ffdb2a0-864b-3944-5789-85703a114c0c PortMappings:[] Networks:[] NetworkConfig:map[]}
INFO[0000] About to del CNI network podman (type=bridge)
DEBU[0000] unmounted container "06e64eb5a0900b38fdc9e91f856562fd0515ed3e051fc641acdc438fb1f44590"
DEBU[0000] Successfully cleaned up container 06e64eb5a0900b38fdc9e91f856562fd0515ed3e051fc641acdc438fb1f44590

restorecon -R -v /var/lib/containers

This worked for me:
sh-4.4# mkdir -p /srv/containers
sh-4.4# mount -o bind /srv/containers /var/lib/containers
sh-4.4# restorecon -v /var/lib/containers/
Relabeled /var/lib/containers from unconfined_u:object_r:var_t:s0 to unconfined_u:object_r:container_var_lib_t:s0
sh-4.4# podman run -ti fedora ls
Trying to pull docker.io/fedora:latest...Getting image source signatures
Copying blob 2ec1fbfd44b7: 85.73 MiB / 85.73 MiB [=========================] 15s
Copying config d7372e6c93c6: 1.99 KiB / 1.99 KiB [==========================] 0s
Writing manifest to image destination
Storing signatures
bin  boot  dev	etc  home  lib	lib64  lost+found  media  mnt  opt  proc  root	run  sbin  srv	sys  tmp  usr  var

Hi, is there any convention on remapping dirs for overlay?
Here is what I did:

do the mounts

mount /dev/vdb1 /root/mnt
mkdir -p /root/mnt
mount -o bind /root/mnt /var/lib/containers/storage/overlay
restorecon  -R -v   /var/lib/containers/storage/overlay

check the mounts
after executed the commands above,
there are two mount points for /dev/vdb1 in /proc/mounts

do a normal status check

podman ps
podman images

recheck the mount points

cat /proc/mounts

In step 4 I cannot see the vdb1 mount on /var/lib/containers/storage/overlay
Since libpod does not have a daemon to restart to reload the change, is there any conventional way to do this?

@zhuguoliang I got stuck with that also. I did this:
systemctl restart io.podman.service

which seemed to have the desired effect.


Caching breaks application

The ServiceWorker caching strategy "Network falling back to cache" is not set up correctly. It seems to break the application, due to the fact, that API calls seems to be cached as well, which is not what we want.

The caching not caused the problem. Instead the ngx-scrollbar library had some incompatability issues, wherefore I removed it from the project.


PoC of localForage replacement

What is the motivation for adding / enhancing this feature?

We do encouter some problems with indexedDB (for example when few instances of vue storefront are open in different tabs). Would be awesome to test some other library (like https://github.com/gruns/irondb/blob/master/README.md)?
We're just needing set, get and iterate (easy to simulate using set and get) to port the storage.ts to other library: https://github.com/DivanteLtd/vue-storefront/blob/master/core/store/lib/storage.ts

With localForage you can select the database engine you want to use (localStorage, Indexed DB...) Take a look at the setDriver API in the docs https://localforage.github.io/localForage/

Of course. The problem is that for caching we must use indexedDb because no other storage driver offers such quotas

So the problem will be the same with another solution since they use the same technologies!

Aparat from this. We should have dedicated mechsnism only for caching catalog no matter what lib it Will use and use local storage (native one) for everything else. Right now we have too much unncesessary abstraction on top of it

The localStorage API is quite nice but it has a lot of restrictions too


IDTA Asset Adminstration Shell v3.1 API

Implementation of IDTA AAS v3.1 API

https://app.swaggerhub.com/apis/Plattform_i40/DiscoveryServiceSpecification/V3.1.0_SSP-002
https://app.swaggerhub.com/apis/Plattform_i40/AssetAdministrationShellRegistryServiceSpecification/V3.1.0_SSP-003

Implementation of IDTA AAS v3.1 API

Hello @thomas-henn
Since the feature is a 24.08 feature and the development phase is coming to an end, we need a status on the feature.

[ ] Currently you are assigned (Responsible) → Is this correct? If not, please assign the correct contact person
[ ] Please check whether the status (backlog, work in progress ...) is set correctly
[ ] Please check whether there is an assignment to a committee or expert group (supported-by) to be found on the board
[ ] Please comment on the current status of the feature
[ ] Are all SubTasks (issues from other repositories that deal with the feature) linked? → The easiest way is to mention the feature here in the issue (via the ID) so we can see which teams/repositories are involved.

If you need any clarification, please get in touch, thank you very much.
Stephan


About taking movable holograms

I have deployed the case and can also see and record color-changing holographic objects on the iPhone.But when I tried to make a movable object, it failed. Objects are movable in hololens, but static in the iPhone. Is there any solution?

文档详细信息
⚠ 请勿编辑此部分。 docs.microsoft.com ➟ GitHub 问题链接必须具有此部分。

ID: d7c80c33-09c9-2f47-7486-d6c406a9a1a4
Version Independent ID: f8ae5662-23e0-141b-efcc-8e5fb3361193
Content: Spectator View - Mixed Reality
Content Source: mixed-reality-docs/spectator-view.md
Product: mixed-reality
GitHub Login: @chrisfromwork
Microsoft Alias: chriba

Hello,
When you say movable object, what is driving the transform applied to the object? Is it being moved by user input? Spectator View is able to set up a shared coordinate space across devices. It doesn't however perform full scene synchronization. We are working on adding components to the MRTK that enable scene synchronization to help make this process easier, but don't have anything to point at as an example in this point of time.
In terms of unity scene synchronization, most of the spectator view preview (not the current refactor) uses UNet. UNet is in the process of being deprecated by Unity, but it does provide workflows for synchronizing scenes across devices. https://docs.unity3d.com/Manual/UNet.html


haproxy configuration is incomplete

hello,
while following the chapters I noticed that the haproxy configuration in chapters rekor and dex are incomplete, however in the fulcio chapter it looks good, could you please check?

sure!

I think I understand why haproxy configuration is left like that, there are two approaches to that:

bootstrap certificates manually using certbot CLI, and then in haproxy configuration pass acme request through to certbot, this would require changes to letsencrypt configuration file for automatic renewal, also a post hook script to concatenate certificates and reload haproxy service
a certbot hooks to stop haproxy before renewal, and run it afterward

the first approach is reflected in https://github.com/lukehinds/sigstore-the-hard-way/pull/6