Update imports for Angular v2 B2C sample

This PR addresses a comment made on this commit about imports in the Angular v2 B2C sample, and updates the imports accordingly. It also changes a type-casting warning in the same file.

Coverage increased (+10.2%) to 92.667% when pulling 336ac8dfadbfc5682f3ae47c842d2d54fd4f99b3 on update-angular-b2c-sample into 6dbc8b39cb8c3d6769c81ee6cf81a299289d28c7 on dev.

Coverage increased (+10.2%) to 92.667% when pulling 336ac8dfadbfc5682f3ae47c842d2d54fd4f99b3 on update-angular-b2c-sample into 6dbc8b39cb8c3d6769c81ee6cf81a299289d28c7 on dev.


Geometry that should be clipped sometimes appears at certain camera angles/distances

https://community.cesium.com/t/shadows-from-geometry-hidden-by-cesiumcartographicpolygon-effecting-our-own-meshes/33039
Also noted here:
https://community.cesium.com/t/geographic-polygon-collision-clipping-works-in-5-1-but-not-in-5-4/32661/7?u=kevin_ring
And here:
https://community.cesium.com/t/cartographicpolygon-clipping-not-precise/33227

I can reproduce this problem, and I have a working theory about what is happening.
First of all, tiles that are entirely inside the clipping polygon seem to no longer get excluded. This was probably broken in v2.4.1, which means it was probably broken by a cesium-native change in this set of changes:
https://github.com/CesiumGS/cesium-native/compare/c9cf5430d5a1d5a2bbdf667169e2c47316f7a8b0...e868c5c85b2de61ded38ff21a88e49f3c6617a95
But that doesn't explain why the phantom geometry appears, because the clipping material layer should discard it regardless.
The immediate reason that that geometry appears is because when we sample the polygon raster overlay, we once-in-awhile end up erroneously see an alpha 0.0 (or less than the mask cutoff value of 0.5, anyway). This is very surprising because this texture doesn't even have an alpha channel! So why in the world would we sometimes see an alpha of 1.0 (as we should), and sometimes see other values. It doesn't make a lot of sense.
My working theory is that this only happens in a tile that is entirely inside the clipping polygon (that's the only time I've seen it happen, at least). And in that scenario, we create a 1x1 texture for the clipping mask. That seems like it should be fine, but we have previously seen cases where Unreal materials just straight up don't work with 1x1 textures. Switching to 2x2 textures has fixed those previous problems. I wonder if it will help here, too.

Switching to 2x2 or even 4x4 textures didn't help.
The actual problem is that the polygon raster overlay isn't being mapped to these problematic tiles at all. This is strange because a polygon raster overlay covers the entire globe. The immediate problem is that getTileBoundingRegionForUpsampling in TilesetContentManager.cpp is returning a region with a north coordinate that is less than its south coordinate. This commit fixes it, and I believe it's a good change - I did the same thing previously for the Clips feature in ion. But I can't entirely explain why it fixes it, so I don't trust it as a complete fix yet.

First of all, tiles that are entirely inside the clipping polygon seem to no longer get excluded.

The reason for this is described in CesiumGS/cesium-native#914.

This may be related too: https://community.cesium.com/t/in-v2-6-0-exclude-selected-tiles-in-cesiumpolygonrasteroverlay-does-not-work/33124/

I think I finally understand what's going on here. In Google Photorealistic 3D Tiles, we often have tiles that look like this:

Where the border shows the tile boundary and the blue blobs are some geometry within it. So there's a lot of blank space, but also some geometry. The bounding volume is tight-fitting. For example, this tile might be at elevation and the geometry is treetops.
Now in order to do polygon clipping, we have to map a raster overlay to this tile. We assign UV (0,0) to the bottom left, and UV (1,1) to the top right, and UV coordinates for vertices in between are calculated based on the position of the vertex in the raster overlay's projection. So far, so good.
Now let's say this is a leaf tile. If we want to hang a more detailed raster overlay on it, we need to "upsample" it, which means divide its geometry into four new, smaller tiles. It looks like this:

Notice that the new tile in the lower left only has geometry on the right side. The box around it is not tight-fitting. Now we need to generate raster overlay texture coordinates for this new tile. As an optimization, we don't go compute the bounding rectangle for it first. Instead, we assume that while the tile has a bounding volume which is a region, we can trust it. It may not be optimal, but it should be good enough. We generate the texture coordinates based on the full box, even though the geometry only occupies part of it. We do this in order to avoid making two passes over the geometry: one to compute the rectangle, and a second to compute the texture coordinates using the rectangle.
The texture coordinate generation process has two outputs: the rectangle that was used to compute the texture coordinates (which may not be tight fitting and that's ok), and the actual tight-fitting bounding rectangle. The tight-fitting bounding rectangle is computed nearly for free while computing the texture coordinates (but by then it's too late to use this tight-fitting rectangle for the coordinates themselves without another pass).
So far, there's a bit of wasted UV and texture space in this tile, but nothing catastrophic has happened. But what happens when we need to upsample that tile for further raster overlay detail.
Here's where we run into problems. We have to decide on the bounding regions for the four upsampled children. And currently, it does this: it divides the parent's tight-fitting bounding rectangle at the point where the texture coordinates would be exactly (0.5,0.5). It looks like this:

See the problem? The center split point is not inside the bounding rectangle at all. A bounding rectangle for the southwest tile that is created like this ends up being total rubbish:
CesiumGeospatial::GlobeRectangle(
  parentRectangle.getWest(), // west
  parentRectangle.getSouth(), // south
  center.longitude, // east
  center.latitude) // north

The bounding rectangle doesn't properly have west less than east and south less than north. Depending on some details, it might be considered empty, or wrapping the wrong way around the entire Earth past the anti-meridian.

What do we do about this? Well, there are basically two choices:

Choose a center point for subdivision that is at the center of the tight-fitting bounding volume instead of in the center of the previously-computed texture coordinates, or
Continue to subdivide at the center point of the texture coordinates, but use the rectangle that was used to compute the texture coordinates instead of the tight-fitting rectangle.
Bonus third option! Do two passes over the geometry in order to determine the tight-fitting bounding box before computing texture coordinates, so there is never a disagreement between them.

I don't like (3) very much. It's expensive (every vertex has to be transformed to ECEF and converted to longitude/latitude/height) and usually unnecessary.
(2) is much easier than (1), because the upsampling algorithm currently always assumes it is splitting at (0.5,0.5) (though this wouldn't be too hard to change). This is what I did previously for Cesium Clips, and it is what the commit I mentioned above does (the one that fixed the problem but I couldn't explain why at the time).
Is it the best solution, though? Well, it'll lead to three out of the four upsampled tiles being blank in the example shown above. That's not a huge problem, though.
I think (2) will have better LOD behavior than (1). With (1), we end up with a very small tile with a large-ish geometric error - half the LOD of its parent. Which means that if you zoom in close to that tile so that it fills the screen, and the tile is further upsampled, you can end up with a giant grid of tiles on the screen. This might point to shortcomings in our geometric error selection for upsampled tiles, but it's not obvious what would be better. Anyway, it's not great, and (2) doesn't have that problem.
So that's a point against (1). I can't think of much downside to (2). So (2) it is!

This is what I did previously for Cesium Clips, and it is what the commit I https://github.com/CesiumGS/cesium-unreal/issues/1461#issuecomment-2188354252 does (the one that fixed the problem but I couldn't explain why at the time).

Oops the fix in Clips was actually closer to (1), and kind of broken because it cuts the geometry at a different place from where it divides the bounding volume.


Icons are not displayed when injected dynamically

Version
@nuxthq/ui: v2.7.0
nuxt: v3.6.5
Reproduction Link
https://stackblitz.com/edit/nuxt-starter-urybxe?file=app.vue
What is Expected? / What is actually happening?
When injecting icon components with a dynamic prop (not a string), icon is not displayed. Or to be more accurate, it is only displayed if the icon is used somewhere else with a plain string (see the reproduction link).
EDIT: it seems to happen when the file containing the data (in my example: filters.ts) lives outside a Nuxt folder. For example, if the file is put into utils/filters.ts, the problem does not occur anymore).

This is the normal behaviour, we use egoist/tailwindcss-icons to bundle the icons. Like for Tailwind CSS classes, you cannot write dynamic icon names.
You can read more here: https://ui.nuxtlabs.com/getting-started/theming#icons

Sorry I was talking about dynamic classes such as text-${color}-500.
For Tailwind CSS to parse classes (works the same for icons), you have to specify the content entry in the tailwind.config.ts: https://tailwindcss.com/docs/content-configuration
The @nuxtjs/tailwindcss module does that for you automatically, it specifies all the places where you could have Tailwind CSS classes which does not include the rootDir except for the app.vue, error.vue and app.config.*.
This is why it works when in the utils/ dir.
Take a look at all the paths included: https://github.com/nuxt-modules/tailwindcss/blob/main/src/resolvers.ts#L25

Oh thanks it's much clearer to me now!


Detect new object and Keep tracking of old obejcts

Hi,
Thanks for this very wonderful and useful project. I wondered if it would be possible to accept streaming video as input, constantly detect new objects and track them, while keeping track of old ones (even if they disappear for a while due to occlusion).
Thanks in advance!

For SAM2, it depends on the length of the FIFO queue. For Grounded-SAM2, you can preserve the text of the old object as the input for GroundingDINO. Unfortunately, this code hasn't been tested with multiple reference objects.

For SAM2, it depends on the length of the FIFO queue. For Grounded-SAM2, you can preserve the text of the old object as the input for GroundingDINO. Unfortunately, this code hasn't been tested with multiple reference objects.

Thanks for your reply. But when data is streamed in and new objects need to be constantly detected, I'm still not sure can SAM2 get a consistent instance id for the same object, even if it disappears for a while and reappears.

Apologies for the late reply. I believe it is possible as long as the object remains within the FIFO queue.


size issue with AnimateLCM I2V model

when inference AnimateLCM I2V, the recommended size is (768,512)
However, it is not possible to inference on A100 GPU.
In the paper, you trained on A800 GPU..
is there any way of reducing the size and preserving the quality?
(I cannot use once..)

Do you mean you face GPU memory overflow? This is not a normal case. In my testing, you won't need over 20 GB for inference. If you use pytorch<2.0, please make sure that xformers is properly installed, which greatly reduce the GPU memory need. Additionally, you can set up enable_vae_slicing to reduce the GPU memory needed for decoding.

Thanks so much!
I success inference 768 resolution image to video.
Thanks so much!!
2024년 9월 3일 (화) 오전 11:52, Fu-Yun Wang @.***>님이 작성:

Do you mean you face GPU memory overflow? This is not a normal case. In my
testing, you won't need over 20 GB for inference. If you use pytorch<2.0,
please make sure that xformers is properly installed, which greatly reduces
the GPU memory need. Additionally, you can set up enable_vae_slicing to
reduce the GPU memory needed for decoding.
—
Reply to this email directly, view it on GitHub
https://github.com/G-U-N/AnimateLCM/issues/35#issuecomment-2325515132,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQKBRW5HOS26HENXQEE4NHLZUUP7NAVCNFSM6AAAAABNRF4K62VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRVGUYTKMJTGI
.
You are receiving this because you authored the thread.Message ID:
@.***>


Idea: make pre-release nuget packages from your dev branch

It would be nice to release your dev branch as pre-release nuget versions so that people can try new features quicker

I will not implement this idea at this point of time.
I aim to not have stuff on dev for longer periods of time and try to keep my changes smaller.
The refactoring to support another platform was bigger than I expected. Also the main reason why it's not merged to master is that the nuget packaging needs to be updated

I aim to not have stuff on dev for longer periods of time
Good goal :+1:

Which platforms do you want to support?
I tried upgrading the SharpCaster target framework to dotnet-standard-1.x (as an experiment) but I got compilation trouble (like the Generic.xaml not being able to build, etc)

I currently have .NET 4.5.x, Windows 8.1 and Windows Phone 8.1.
Will look into adding dotnet-standard but not sure what's the status of socket APIs there.
Mainly did the .net 4.5.x support to practice building library that targets multiple platforms.

Ok.
Is there anything specific for which you want to keep the win8.1 (phone) support?

It's to support UWP development. Mainly targeting Win10 but you can get win8.1 (phone) for free.

Aah, I thought that for UWP you had to create an UWP library or target windows 10

Done. When pushing stuff into dev and wanting to publish just add -pre tag into it and it will be released ot nuget with the tag.


Fix test command error reporting

Closes #772
We have a uniform mechanism for reporting errors (along with exit codes) for
failed executions, but the test subcommand wasn't using it, so it was exiting
with a 0 and without reporting on stderr.
This change makes it so that test produces a non-zero exit code on failures.
Note that this has also uncovered a failing test.

[x] Tests added for any new code
[x] Ran npm run format (or had formatting run automatically on all files edited)
[x] Documentation added for any new functionality
[x] Entries added to the respective CHANGELOG.md for any new functionality
[x] Feature table on README.md updated for any listed functionality

I don't see anything in the lottery spec that could set the lastTx.status to "drawing". I think this is a specification error?
@konnov Is it OK with you if i ignore this test for now, and open an issue to track need to fix it? I don't want to get side tracked into bebugging this demos spec given the other stuff on my plate, and this fix is blocking correct quint CI for the cosmosbft repo.

I've tracked the need for followup on the spec test in #775

Nice! I will check the broken test!


test(consensus): PBTS should be enabled by default in test units

Addresses #2324.

PR checklist

[ ] Tests written/updated
[ ] Changelog entry added in .changelog (we use unclog to manage our changelog)
[ ] Updated relevant documentation (docs/ or spec/) and code comments
[ ] Title follows the Conventional Commits spec

@cason check out #2284. There, you can control when you enable PBTS via the manifest, rather than hard-coding it

I have probably to revert all changes here, with a force-push. This should not be a problem, as it is in draft mode.


Create atlanticcollege.txt

@ac16lbal Pull request merged. Please notice that free educational license for JetBrains tools is for high and higher schools students, i.e. those who are over 13 of age. Thank you!


unmanged-cluster: Add details about using provider configuration

Let's add details on provider configuration to the unmanaged-cluster reference docs:
https://tanzucommunityedition.io/docs/latest/ref-unmanaged-cluster/
Let's use the kind provider as an example

@jpmcb assigned this to you for sometime before the v0.11.0 release.
lmk if you have any questions or concerns!


create_file(..., contents=None) unintentionally crates a "large file"

Seems it's a lack in the API:
    # pytest
    def test_thinks_is_a_large_file(fs):
        fs.create_file("/tmp/file.txt", contents=None)

        with open("/tmp/file.txt", 'rt') as ff:
            ff.read()

If the contents is None there is no chance to later read the file.
In my opinion None in this API should be equivalent to "" - giving an empty file. However at read attempt it raises:
    self = <pyfakefs.fake_filesystem.FakeFileWrapper object at 0x7f5a8c6dd310>
    name = 'read'

        def __getattr__(self, name):
            if self.file_object.is_large_file():
    >           raise FakeLargeFileIoException(self._file_path)
    E           FakeLargeFileIoException: Read and write operations not supported for fake large file: /tmp/file.txt

Of course setting contents='' works OK.

Well, given that the default value for contents is an empty string, you have to explicitely pass None to contents in create_file(), so this has to be a conscious decision. But I agree that handling None contents as empty contents as long as st_size is also None makes sense.


Instrument: Fix bindless checking for BufferDeviceAddress

Avoid using OpConstantNull with types that do not allow it.
Update existing tests for slight changes in code generation.
Add new tests based on the Vulkan Validation layer test case that exposed this problem.
This is a fix for https://github.com/KhronosGroup/Vulkan-ValidationLayers/issues/4983

Would like @greg-lunarg or @s-perron to formally approve

@dneto0  I will review..

@s-perron & @dneto0 Is there anything else needed to get this merged? Thanks!

Not all of the CIs ran. If they all pass, we can merge it.

Not all of the CIs ran. If they all pass, we can merge it.

Is that the purpose of the kokoro:run label you added 4 days ago? Or is there something I need to do to trigger CI?

The label should be good enough, but the bots do not seem to be responding. I'm looking into it now.

The bots where still looking for PRs to the master branch instead of main. I've fixed that up. I'll give it a little time, so see if it worked.


Split Makefile to be self-contained per directory - resubmit

Re-submit for accidentally closed PR #545
I think this addresses all the comments and concerns from that earlier PR.  Please let me know if you find anything else that needs attention.
Split the src/Makefile out to each directory where installation actions are needed:

config_repo
notification_images
scripts
src
Top-level

The Makefile in each sub-directory can be called individually and it'll perform the proper actions, independent of other directories.
The top-level Makefile calls all sub-dir's functions as needed.
Tweaked install.sh to use the top-level Makefile.

Michael, in Makefile, you added
...
That code seems to be at odds with the title of the commit (Relocated allsky.sh back to top level, removed .repo version). The code puts allsky.sh in libexecdir and uses the .repo version. Are we keeping allsky.sh.repo or not? Where will allsky.sh exist?

@EricClaeys  The .repo is a typo, I've fixed that in the next commit.  The 'libexec' stuff is only triggered when using the PKGBUILD environment variable -- not the default action.  It's for future package building convenience.

config.sh.repo:  Since config.sh is sourced after variables.sh, the following lines in config.sh.repo can use $ALLSKY_CONFIG instead of $ALLSKY_HOME/config:
CAMERA_SETTINGS_DIR="${ALLSKY_HOME}/config"
source "$ALLSKY_HOME/config/autocam.sh"

config_repo/Makefile: line 60: @sed -e "s|User=pi|User=allsky|g" -e "s|/home/pi/allsky|$(bindir)|g" allsky.service.repo > allsky.service Will changing the User to "allsky" break anything?
config_repo/Makefile: line 63: @echo -e "export ALLSKY_TMP=/tmp\nexport ALLSKY_CONFIG=$(DESTDIR)$(sysconfdir)/allsky\nexport ALLSKY_SCRIPTS=$(DESTDIR)$(libexecdir)\nexport ALLSKY_NOTIFICATION_IMAGES=$(DESTDIR)$(sharedir)\nexport ALLSKY_IMAGES=/home/allsky/Pictures/" > $(DESTDIR)$(sysconfdir)/profile.d/allsky.sh
Is that for possible future use?  The locations aren't what we're currently using.
notification_images/Makefile:  line 37:  install -m 0644 *.jpg *.png $(DESTDIR)$(sharedir)/; \  I created PR 565 to add AllskyNotifications.psd which I used to create all the .jpg and .png files, so it should probably be copied as well.
@linuxkidd, @ckuethe,
since this PR has lots of changes to almost every file, can we test it on a Pi prior to merging it, both as a clean install and as an upgrade (whatever that means)?  I suspect we missed a variable name change or location change or something...
Also, how do you put @ names in yellow?  When I do an @name it doesn't have a yellow background.

The yellow / brown or on the name is to highlight your own name so it's easier for you to spot.
Yes, I agree.. I'd much prefer you compile / test it.  It runs great for me with a fresh install on Buster.

I won't have access to my Pi for another week.
@ckuethe, are you able to install Michael's PR on your Pi and test it?  I think if it works for 2 people it should be good to go.

Yeah, I'm reading through it now and will set up a test machine tomorrow.

Ok, I moved the variables.sh script back to $ALLSKY_HOME per Eric's request.
I also took the time to make an Uninstall function, including uninstall.sh


Fix "Rubocop/Metrics/MethodLength" issue in app/controllers/donations_controller.rb

Method has too many lines. [32/10]
https://codeclimate.com/github/OperationCode/operationcode/app/controllers/donations_controller.rb#issue_57a14669e3d8a20001000167

This page is no longer used and won't be carried over in the redesign


claim option

Does not work for me command  /co min-claim-size-basic-z 2
In the wasteland it is reported that I have no rights to install options. The claims say that you need to change the administrator options.
no error in log
forge-1.12.2-<IP_ADDRESS>03-universal.jar
spongeforge-1.12.2-2703-7.1.0-BETA-3119.jar
LuckPerms-Sponge-4.2.14.jar
griefprevention-1.12.2-<IP_ADDRESS>7.jar

Hey I was wondering the progress on the fix for this? My current shop plots at spawn are 7x7, if there's no progress on this within a couple weeks, I'm going to have to re-build my entire spawn shop area to accommodate larger plots. Rather not do that, as you can imagine.

This will be fixed after GP 5.0.0 is released which should be soon. You can work around it by manually applying the option to sponge's default user in luckperms. For example, if you want to set the minimum claim size to 2 for basic then the default user must have an option set for 2 or lower.

That is what I did and that didn't work...


VTK folder and Vx sign for OLAF

Ready to merge
Feature or improvement description

Vx sign was wrong for aero outputs per node with OLAF
Folder fvw_vtk was not in the right location when openfast called from a different folder, no vtk files were produced

Impacted areas of the software
OLAF

Note for our future selves:
For the Vx sign, this change now aligns the equation for the FVW output with that for the BEMT (code block above it).  The signs used for Vx in the standard outputs match between FVW and BEMT, so this is expected here.


Hostname resolution works only in one container in pod

Only one container in pod can access shared /etc/hosts and /etc/resolv.conf
Both containers in one pod and:
[root@minion-2 ~]# docker exec d5165f999bdb cat /etc/hosts
<IP_ADDRESS>     coolpodname
<IP_ADDRESS>       localhost
::1     localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

[root@minion-2 ~]# docker exec 9d60e556774c cat /etc/hosts
cat: /etc/hosts: Permission denied
[root@minion-2 ~]# docker exec 9d60e556774c cat /etc/resolv.conf
cat: /etc/resolv.conf: Permission denied

So result:
[root@minion-2 ~]# docker exec d5165f999bdb ping coolpodname
PING coolpodname (<IP_ADDRESS>) 56(84) bytes of data.
64 bytes from coolpodname (<IP_ADDRESS>): icmp_seq=1 ttl=64 time=0.053 ms
64 bytes from coolpodname (<IP_ADDRESS>): icmp_seq=2 ttl=64 time=0.048 ms
64 bytes from coolpodname (<IP_ADDRESS>): icmp_seq=3 ttl=64 time=0.035 ms

[root@194-44-0-77-kube-minion-2 ~]# docker exec 9d60e556774 ping coolpodname
ping: unknown host

Is this normal behavior?)

/cc @thockin

I am not sure what would cause permission denied.  This is not the expected
behavior.    I
am on 1.5.0.
On Thu, Mar 26, 2015 at 10:42 AM, Robert Bailey<EMAIL_ADDRESS>wrote:

/cc @thockin https://github.com/thockin
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/5991#issuecomment-86639697
.

We use Docker version 1.4.1, build 5bc2ff8/1.4.1 and Kubernetes v0.12.0
I do exactly what you do:
[root@minion-1 ~]# docker exec $ID cat /etc/hosts | head -2
cat: can't open '/etc/hosts': Permission denied
[root@minion-1 ~]# docker exec $ID2 cat /etc/hosts | head -2
<IP_ADDRESS>     47ce89556fb7
<IP_ADDRESS>       localhost

try docker exec $ID ls -l /etc and paste here?
On Thu, Mar 26, 2015 at 11:28 AM, pythonpowerd<EMAIL_ADDRESS>wrote:

We use Docker version 1.4.1, build 5bc2ff8/1.4.1 and Kubernetes v0.12.0
I do exactly what you do:
[root@minion-1 ~]# docker exec $ID cat /etc/hosts | head -2
cat: can't open '/etc/hosts': Permission denied[root@minion-1 ~]# docker exec $ID2 cat /etc/hosts | head -<IP_ADDRESS>     47ce89556fb7<IP_ADDRESS>       localhost
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/5991#issuecomment-86657792
.

[root@minion-1 ~]# docker exec $ID ls -l /etc
total 92
-rw-rw-r--    1 root     root           466 Feb 27  2014 fstab
-rw-rw-r--    1 root     root           344 Feb 27  2014 group
-rw-r--r--    1 root     root            13 Mar 26 18:24 hostname
-rw-r--r--    1 root     root           175 Mar 26 18:24 hosts
drwxrwxr-x    2 root     root          4096 May 22  2014 init.d
-rw-rw-r--    1 root     root          1086 May 22  2014 inittab
-rw-rw-r--    1 root     root          1180 Feb 27  2014 inputrc
drwxr-xr-x    2 root     root          4096 May 22  2014 iproute2
-rw-rw-r--    1 root     root            21 May 22  2014 issue
-rw-r--r--    1 root     root             0 May 22  2014 ld.so.conf
drwxrwxr-x    2 root     root          4096 Feb 27  2014 ld.so.conf.d
lrwxrwxrwx    1 root     root            12 Mar 26 18:24 mtab -> /proc/mounts
drwxrwxr-x    8 root     root          4096 May 22  2014 network
-rw-rw-r--    1 root     root           439 Feb 27  2014 nsswitch.conf
-rw-r--r--    1 root     root            95 May 22  2014 os-release
-rw-r--r--    1 root     root           596 Feb 27  2014 passwd
-rw-rw-r--    1 root     root          1836 Feb 27  2014 profile
-rw-rw-r--    1 root     root          2744 Feb 27  2014 protocols
-rw-rw-r--    1 root     root           512 Feb 27  2014 random-seed
-rw-r--r--    1 root     root            45 Mar 26 18:24 resolv.conf
-rw-rw-r--    1 root     root           386 Feb 27  2014 securetty
-rw-rw-r--    1 root     root         10873 Feb 27  2014 services
-rw-------    1 root     root           346 May 22  2014 shadow

I can not fathom how you would get a permission error.  It's world
readable.  Can you try updating Docker?  Docker is the one who sets up
those bind mounts, maybe there's something funky there?
On Thu, Mar 26, 2015 at 11:32 AM, pythonpowerd<EMAIL_ADDRESS>wrote:

[root@minion-1 ~]# docker exec $ID ls -l /etc
total 92
-rw-rw-r--    1 root     root           466 Feb 27  2014 fstab
-rw-rw-r--    1 root     root           344 Feb 27  2014 group
-rw-r--r--    1 root     root            13 Mar 26 18:24 hostname
-rw-r--r--    1 root     root           175 Mar 26 18:24 hosts
drwxrwxr-x    2 root     root          4096 May 22  2014 init.d
-rw-rw-r--    1 root     root          1086 May 22  2014 inittab
-rw-rw-r--    1 root     root          1180 Feb 27  2014 inputrc
drwxr-xr-x    2 root     root          4096 May 22  2014 iproute2
-rw-rw-r--    1 root     root            21 May 22  2014 issue
-rw-r--r--    1 root     root             0 May 22  2014 ld.so.conf
drwxrwxr-x    2 root     root          4096 Feb 27  2014 ld.so.conf.d
lrwxrwxrwx    1 root     root            12 Mar 26 18:24 mtab -> /proc/mounts
drwxrwxr-x    8 root     root          4096 May 22  2014 network
-rw-rw-r--    1 root     root           439 Feb 27  2014 nsswitch.conf
-rw-r--r--    1 root     root            95 May 22  2014 os-release
-rw-r--r--    1 root     root           596 Feb 27  2014 passwd
-rw-rw-r--    1 root     root          1836 Feb 27  2014 profile
-rw-rw-r--    1 root     root          2744 Feb 27  2014 protocols
-rw-rw-r--    1 root     root           512 Feb 27  2014 random-seed
-rw-r--r--    1 root     root            45 Mar 26 18:24 resolv.conf
-rw-rw-r--    1 root     root           386 Feb 27  2014 securetty
-rw-rw-r--    1 root     root         10873 Feb 27  2014 services
-rw-------    1 root     root           346 May 22  2014 shadow
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/5991#issuecomment-86659804
.

And since we can repro it without kubernetes at all, maybe we can ask
Docker people for help?
On Thu, Mar 26, 2015 at 11:51 AM, Tim Hockin<EMAIL_ADDRESS>wrote:

I can not fathom how you would get a permission error.  It's world
readable.  Can you try updating Docker?  Docker is the one who sets up
those bind mounts, maybe there's something funky there?
On Thu, Mar 26, 2015 at 11:32 AM, pythonpowerd<EMAIL_ADDRESS>wrote:

[root@minion-1 ~]# docker exec $ID ls -l /etc
total 92
-rw-rw-r--    1 root     root           466 Feb 27  2014 fstab
-rw-rw-r--    1 root     root           344 Feb 27  2014 group
-rw-r--r--    1 root     root            13 Mar 26 18:24 hostname
-rw-r--r--    1 root     root           175 Mar 26 18:24 hosts
drwxrwxr-x    2 root     root          4096 May 22  2014 init.d
-rw-rw-r--    1 root     root          1086 May 22  2014 inittab
-rw-rw-r--    1 root     root          1180 Feb 27  2014 inputrc
drwxr-xr-x    2 root     root          4096 May 22  2014 iproute2
-rw-rw-r--    1 root     root            21 May 22  2014 issue
-rw-r--r--    1 root     root             0 May 22  2014 ld.so.conf
drwxrwxr-x    2 root     root          4096 Feb 27  2014 ld.so.conf.d
lrwxrwxrwx    1 root     root            12 Mar 26 18:24 mtab -> /proc/mounts
drwxrwxr-x    8 root     root          4096 May 22  2014 network
-rw-rw-r--    1 root     root           439 Feb 27  2014 nsswitch.conf
-rw-r--r--    1 root     root            95 May 22  2014 os-release
-rw-r--r--    1 root     root           596 Feb 27  2014 passwd
-rw-rw-r--    1 root     root          1836 Feb 27  2014 profile
-rw-rw-r--    1 root     root          2744 Feb 27  2014 protocols
-rw-rw-r--    1 root     root           512 Feb 27  2014 random-seed
-rw-r--r--    1 root     root            45 Mar 26 18:24 resolv.conf
-rw-rw-r--    1 root     root           386 Feb 27  2014 securetty
-rw-rw-r--    1 root     root         10873 Feb 27  2014 services
-rw-------    1 root     root           346 May 22  2014 shadow
—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/issues/5991#issuecomment-86659804
.

I just tried docker 1.5 on my home machine (ArchLinux) and all works fine!
Found repo for CentOS 7 (we use it at our cluster) with docker 1.5 and try on fresh VM and...
[root@minion-3 ~]# docker exec $ID cat /etc/hosts | head -2
cat: can't open '/etc/hosts': Permission denied
[root@minion-3 ~]# docker exec $ID2 cat /etc/hosts | head -2
<IP_ADDRESS>      5bef0ac2caac
<IP_ADDRESS>       localhost

Obviously, it's a docker + CentOS bug ((
Thanks for help!

@pythonpowerd: Glad you found the issue! Since you seem to have resolved this, I'm closing this. If you have any more trouble, feel free to reopen.

This looks like and SELinux issue.  Since the first containers resolv.conf would have a private label on it.


Backups to Google Cloud Storage are accessible over the Internet

Having the Google Cloud integration enabled and doing backup on ControlPanel tries to put objects in the bucket with allUsers object level permission.
Tried different setups, didn't work.

Cloud Storage Bucket with Public Access Prevention enabled - Failed with the following error.

Google.Apis.Requests.RequestError The member bindings allUsers and allAuthenticatedUsers are not allowed since public access prevention is enforced. [412] Errors [ Message[The member bindings allUsers and allAuthenticatedUsers are not allowed since public access prevention is enforced.] Location[If-Match - header] Reason[conditionNotMet] Domain[global] ]

Cloud Storage Bucket with Uniform Access Control and Public Access Prevention enabled - Failed with the following error.

Google.Apis.Requests.RequestError Cannot insert legacy ACL for an object when uniform bucket-level access is enabled. Read more at https://cloud.google.com/storage/docs/uniform-bucket-level-access [400] Errors [ Message[Cannot insert legacy ACL for an object when uniform bucket-level access is enabled. Read more at https://cloud.google.com/storage/docs/uniform-bucket-level-access] Location[ - ] Reason[invalid] Domain[global] ]

The only way it works is to disable the Public Access prevention on the bucket and have Fine Grained Access Control enabled, but this results in objects being accessible over the Internet, which is not secure.
Suggesting to remove the allUsers and allAuthenticatedUsers object level permissions if there is one in the object ACL when OnlyOffice tries to upload the image to the bucket.
My Setup

OnlyOffice Community Server - v<IP_ADDRESS>8
Control panel - v<IP_ADDRESS>6
Document Server - v<IP_ADDRESS>

Hello @EdgarHarutyunyan02 Yes, we have this problem. At this point, I cannot provide you with any other option other than to disable Prevent Public Access. We will try to fix this in future versions.


It is stucked after "occlum run"

after "occlum run /bin/hello_world"，It is ok. But another example is stucekd . I use "ps aux" to check the problem，it shows that CPU is full.

ps aux shows as follows:

Hi @Ariel08081214 ,

Can you successfully run the SGX SDK Samples, by following the instructions?

Have you successfully enabled the wr/rdfsbase instructions for unprivileged part by following the instructions?

Hi @Bonjourz

Yes，I can run the SGX SDK Samples successfully
Yes，wr/rdfsbase is enabled

Maybe the pre-allocated memory is not enough？

@Bonjourz I modify the memmap value to 32G，then it work。Now，here is anther question，if the mysql-server run in occlum，how does the outside client connect to it？Waiting for your help

Hi @Ariel08081214

I modify the memmap value to 32G，then it works

Cool!

if the mysql-server run in occlum，how does the outside client connect to it，how does the outside client connect to it？

HyperEnclave is only responsible for providing TEE environment for applications. How to program applications inside is another topic.
To my understanding, Occlum provides OS's functionality for unmodified applications running inside enclave. In your provided case, Occlum is responsible transfer messages between unmodified applications(MYSQL-server) and components outside(MYSQL-client) via syscall ABIs(read, write, epoll etc.) and POSIX abstraction (socket).
You may dive deeply into Occlum's source code or discuss it in Occlum's community: https://github.com/occlum/occlum.

Hi @Bonjourz I appreciate it for your reply. I‘ll try to find answer form Occlum official site


[BUG] Longhorn v.1.7.0-rc1 on ARM, the v2-data-engine failed to enable the instance-manager pod

Describe the bug
Longhorn v.1.7.0-rc1 on ARM, the v2-data-engine failed to enables the instance-manager pod
instance-manager-8306dc3c074955035261ab2b042af6f6                 0/1     Terminating         0          17s   <none>         ryao-arm64-w3-56e0d12e-g8rvs   <none>           <none>
instance-manager-8306dc3c074955035261ab2b042af6f6                 0/1     Terminating         0          17s   <none>         ryao-arm64-w3-56e0d12e-g8rvs   <none>           <none>
instance-manager-8306dc3c074955035261ab2b042af6f6                 0/1     Pending             0          0s    <none>         ryao-arm64-w3-56e0d12e-g8rvs   <none>           <none>
instance-manager-8306dc3c074955035261ab2b042af6f6                 0/1     ContainerCreating   0          0s    <none>         ryao-arm64-w3-56e0d12e-g8rvs   <none>           <none>
instance-manager-3221697e54c160c846ffd80e1bd1c933                 0/1     Error               0          17s   <none>         ryao-arm64-w2-1f3f32e8-27ktm   <none>           <none>
instance-manager-3221697e54c160c846ffd80e1bd1c933                 0/1     Terminating         0          17s   <none>         ryao-arm64-w2-1f3f32e8-27ktm   <none>           <none>
instance-manager-3221697e54c160c846ffd80e1bd1c933                 0/1     Terminating         0          17s   <none>         ryao-arm64-w2-1f3f32e8-27ktm   <none>           <none>
instance-manager-3221697e54c160c846ffd80e1bd1c933                 0/1     Pending             0          0s    <none>         ryao-arm64-w2-1f3f32e8-27ktm   <none>           <none>
instance-manager-3221697e54c160c846ffd80e1bd1c933                 0/1     ContainerCreating   0          0s    <none>         ryao-arm64-w2-1f3f32e8-27ktm   <none>           <none>
instance-manager-8306dc3c074955035261ab2b042af6f6                 1/1     Running             0          1s    <IP_ADDRESS>    ryao-arm64-w3-56e0d12e-g8rvs   <none>           <none>
instance-manager-3221697e54c160c846ffd80e1bd1c933                 1/1     Running             0          1s    <IP_ADDRESS>    ryao-arm64-w2-1f3f32e8-27ktm   <none>           <none>

To Reproduce

Prepare ARM64 cluster
Enable v2 data engine
Check the V2 instance-manager pod

Expected behavior
the v2-data-engine enables the instance-manager pod without error on ARM cluster.
Support bundle for troubleshooting
supportbundle_d6fad975-6c73-4ca0-9ce8-1c42e1704adf_2024-07-15T11-36-44Z.zip
armsupportbundle_6e0e928a-28a9-4300-87fe-446e4e2f2cf5_2024-07-15T10-54-47Z.zip
Environment

Longhorn version: v1.7.0-rc1
Impacted volume (PV):
Installation method (e.g. Rancher Catalog App/Helm/Kubectl):Kubectl
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version:k3s

Number of control plane nodes in the cluster: 1
Number of worker nodes in the cluster: 3

Node config

OS type and version: ubuntu 24.04
Kernel version:
CPU per node: 4
Memory per node: 16
Disk type (e.g. SSD/NVMe/HDD): SSD
Network bandwidth between the nodes (Gbps):

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal): AWS
Number of Longhorn volumes in the cluster:

Additional context
https://longhorn.github.io/longhorn-tests/manual/pre-release/v2-volume/sanity-check/

@roger-ryao
The instance-manager pods are still starting. Can you check it again?
I also tried to deploy v2 data engine in my arm64 env, and no issue is found.

Verified on master-head/v1.7.x 20230722

longhorn-instance-manager master-head https://github.com/longhorn/longhorn-instance-manager/commit/49de3ef60d4b946337ae220d9a9c07688356b752
longhorn-instance-manager v1.7.x https://github.com/longhorn/longhorn-instance-manager/commit/c62fa08c11fc96f5cd3bcff8bf31ac0dccf67f73

The test steps
https://github.com/longhorn/longhorn/issues/9004#issue-2408523042
Result passed


Issue 783: NullPointerExceptions after calling closeSessions on ServiceMXBean

This PR fixes [JMX management service: closeSessions (by principal) service bean method causes NPEs #783](JMX management service: closeSessions (by principal) service bean method causes NPEs #783).
It also contains the changes from PR https://github.com/kaazing/gateway/pull/784 so better to wait for that to be merged before reviewing this one.
The fix is to remove the ManagementContext.removeSessionManagementBean method (which was previously called from FullManagementFilterStrategy.doSessionClosed and called managementServiceHandler.removeSessionManagementBean) and instead call a new method JmxManagementServiceHandler.removeSessionMXBean from JmxSessionManagementListener

LGTM, waiting for travis


Revert "(BKR-871) Don't test packages on Windows"

This reverts commit 480cbad5f8b75c9cb96d104e2537bc8771ed4f8c.

Refer to this link for build results (access rights to CI server needed):
http://jenkins-beaker.delivery.puppetlabs.net//job/qe_beaker_btc-intn/2711/

@tvpartytonight Could you like to the windows image fix please?


Add hint to microcuke

Adding information from @smortex (https://gitter.im/cucumber/chat?at=56445b7efb98af9976c0bfd9) to the official cucumber website.
@aslakhellesoy Ping.

@mattwynne Ping as well...

What about this PR? Should I merge it?

Sure please do!

Done.


complete the integration of memberships view and the

complete the integration of memberships view and the
API also refer to admin app
https://github.com/freelancing-solutions/gcp-database-as-a-service-stock-markets/blob/cf171fa2d415e1ae119f38d0cb6bc9a2678e9228/data_service/api/memberships/routes.py#L113

    member_ship_instance_view: MembershipPlansView = MembershipPlansView()
    return member_ship_instance_view.add_plan(membership_plan_data=membership_plan_data)

@memberships_bp.route('/api/v1/membership-plans', methods=["GET"])
def get_membership_plans() -> tuple:
    member_ship_instance_view: MembershipPlansView = MembershipPlansView()
    return member_ship_instance_view.return_all_plans()

# TODO complete the integration of memberships view and the
#  API also refer to admin app

b87025c4d02cc9adebe0e1468a2f2d7b5fb9a27d

Closed in 7950f7a32295fce783fb9e46a239661671f8a1e8


ConcurrentObjectUseError with grpc + gevent

What version of gRPC and what language are you using?
grpcio 1.12.1 python
What operating system (Linux, Windows, …) and version?
Centos 7.5, kernel 4.7.11
What runtime / compiler are you using (e.g. python version or version of gcc)
python 2.7.10
What did you do?
I have a gunicorn+gevent+grpc setup. I have gcloud libraries imported but not actually using them yet. I have also checked that gevent is using 'libev' and not 'libuv' event loop.
I am patching grpc in a custom gunicorn worker:
gevent_grpc_worker.py:
import gunicorn.workers.ggevent

class GeventGrpcWorker(gunicorn.workers.ggevent.GeventWorker):

  def patch(self):
    super(GeventGrpcWorker, self).patch()

    # Patch grpc library to support gevent.
    import grpc._cython.cygrpc
    grpc._cython.cygrpc.init_grpc_gevent()
    self.log.info('GeventGrpcWorker: patched grpc.')

gunicorn.conf:
bind = "unix:/tmp/gunicorn.sock"
workers = 129
worker_class = "gevent_grpc_worker.GeventGrpcWorker"
logerror = "/mnt/log/gunicorn-error.log"
max_requests = 100000
backlog = 2048
user = "dropcam"
group = "dropcam"
pidfile = "/var/run/gunicorn.pid"
timeout = 90
worker_connections = 25

I am using:
gunicorn==19.8.1
grpcio==1.12.1
gevent==1.3.5
greenlet==0.4.14
google-cloud-core==0.28.1
google-cloud-pubsub==0.35.4
google-cloud-storage==1.10.0
google-cloud-bigquery==1.4.0
google-api-core==1.3.0
google-api-python-client==1.7.4
google-apitools==0.5.23
grpc-google-iam-v1==0.11.4
I am getting the following stack trace in my logs. There is no request_id meaning that it's not tied to a specific operation/web-request, so it's not causing any issues yet, and I am not aware of what's triggering it. Regardless, it doesn't seem like the right thing is happening, seems like some kind of incompatibility with the google auth library and gevent.
2018-08-01 08:24:08,146 ERROR [root] request_id=None AuthMetadataPluginCallback "<google.auth.transport.grpc.AuthMetadataPlugin object at 0x152a040fe610>" raised exception!
Traceback (most recent call last):
  File "/usr/lib64/python2.7/site-packages/grpc/_plugin_wrapping.py", line 77, in __call__
    callback_state, callback))
  File "/usr/lib/python2.7/site-packages/google/auth/transport/grpc.py", line 77, in __call__
    callback(self._get_authorization_headers(context), None)
  File "/usr/lib/python2.7/site-packages/google/auth/transport/grpc.py", line 65, in _get_authorization_headers
    headers)
  File "/usr/lib/python2.7/site-packages/google/auth/credentials.py", line 122, in before_request
    self.refresh(request)
  File "/usr/lib/python2.7/site-packages/google/oauth2/service_account.py", line 322, in refresh
    request, self._token_uri, assertion)
  File "/usr/lib/python2.7/site-packages/google/oauth2/_client.py", line 145, in jwt_grant
    response_data = _token_endpoint_request(request, token_uri, body)
  File "/usr/lib/python2.7/site-packages/google/oauth2/_client.py", line 106, in _token_endpoint_request
    method='POST', url=token_uri, headers=headers, body=body)
  File "/usr/lib/python2.7/site-packages/google_auth_httplib2.py", line 116, in __call__
    url, method=method, body=body, headers=headers, **kwargs)
  File "/usr/lib64/python2.7/site-packages/newrelic-<IP_ADDRESS>/newrelic/api/external_trace.py", line 103, in dynamic_wrapper
    return wrapped(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/httplib2/__init__.py", line 1609, in request
    (response, content) = self._request(conn, authority, uri, request_uri, method, body, headers, redirections, cachekey)
  File "/usr/lib/python2.7/site-packages/httplib2/__init__.py", line 1351, in _request
    (response, content) = self._conn_request(conn, request_uri, method, body, headers)
  File "/usr/lib/python2.7/site-packages/httplib2/__init__.py", line 1307, in _conn_request
    response = conn.getresponse()
  File "/usr/lib64/python2.7/site-packages/newrelic-<IP_ADDRESS>/newrelic/hooks/external_httplib.py", line 65, in httplib_getresponse_wrapper
    return wrapped(*args, **kwargs)
  File "/usr/lib64/python2.7/httplib.py", line 1132, in getresponse
    response.begin()
  File "/usr/lib64/python2.7/httplib.py", line 453, in begin
    version, status, reason = self._read_status()
  File "/usr/lib64/python2.7/httplib.py", line 409, in _read_status
    line = self.fp.readline(_MAXLINE + 1)
  File "/usr/lib64/python2.7/socket.py", line 480, in readline
    data = self._sock.recv(self._rbufsize)
  File "/usr/lib64/python2.7/site-packages/gevent/_sslgte279.py", line 457, in recv
    return self.read(buflen)
  File "/usr/lib64/python2.7/site-packages/gevent/_sslgte279.py", line 318, in read
    self._wait(self._read_event, timeout_exc=_SSLErrorReadTimeout)
  File "src/gevent/_hub_primitives.py", line 265, in gevent.__hub_primitives.wait_on_socket
  File "src/gevent/_hub_primitives.py", line 266, in gevent.__hub_primitives.wait_on_socket
  File "src/gevent/_hub_primitives.py", line 245, in gevent.__hub_primitives._primitive_wait
ConcurrentObjectUseError: This socket is already used by another greenlet: <bound method Waiter.switch of <gevent.__waiter.Waiter object at 0x152a03bfe9f0>>

What did you expect to see?
No errors around grpc + gevent
What did you see instead?
ConcurrentObjectUseError: This socket is already used by another greenlet: <bound method Waiter.switch of <gevent.__waiter.Waiter object at 0x152a03bfe9f0>>
Anything else we should know about your project / environment?

Can you try the latest gRPC and see if it still happens? There have been a number of gevent fixes since I think.

Don't see issues after update, closing.

Cool, thanks for the update.


Github workflows

Github Workflows
Adds automated testing and builds to this project via Github Workflows.
Workflow descriptions
Testing.yml

Runs cargo check to ensure that the binaries compile
Runs cargo fmt --all --check to ensure that the project has been formatted
Runs cargo clippy to ensure that the project has been linted (ignores warnings)
Runs cargo/cross test --release --target ${{ matrix.target }} --verbose to ensure that all tests pass for various targets:

x86_64-unknown-linux-gnu
x86_64-unknown-linux-musl
x86_64-apple-darwin
x86_64-pc-windows-msvc

Release.yml

Builds release binaries for various targets:

x86_64-unknown-linux-gnu
x86_64-apple-darwin
x86_64-pc-windows-msvc

Builds berkshire_hog_lambda release binary for x86_64-unknown-linux-musl
Builds Docker images for each hog
Publishes release binaries for each target
Publishes berkshire_hog_lambda release binary for x86_64-unknown-linux-musl
Publishes scripts directory
Pushes Docker images to each respective Docker hub repository

Other changes
Added files for builds:

Dockerfile.build
Dockerfile.hog
Makefile (contains build_docker.sh logic)

Removed unused files:

.travis.yml
build_docker.sh (moved logic to Makefile)
build_ghrelease.sh (moved logic to release.yml)
build_lambda.sh (moved logic to release.yml; will update manual lambda build instructions in next commit)
entrypoint.sh (entrypoint is defined in Dockerfile.hog

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


cmd/compile: "unknown field" error for unexported field in struct literal is misleading

What version of Go are you using (go version)?

$ go version
go version go1.12beta2 linux/amd64

Does this issue reproduce with the latest release?
yes, same on Playground
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/bpaskinc/.cache/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/bpaskinc/go"
GOPROXY=""
GORACE=""
GOROOT="/usr/lib/golang"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/golang/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build091900586=/tmp/go-build -gno-record-gcc-switches"

What did you do?
package main
import "net/http"
var _ = http.Server{doneChan: nil}  // this field does exist but isn't public

For a full matrix of (outside/inside package X exists/unknown X Public/private X struct literal/object.field) see: https://play.golang.org/p/cWl3JV8pSNL
What did you expect to see?
An error message indicated the problem is I'm trying to set an unexported field (from outside the package).  Something like:
cannot set unexported field 'doneChan' in struct literal of type http.Server
If the field really doesn't exist, the current message is OK.
This is only about struct literals. When simply reading (or assigning) object.field, the messages already make the distinction between can't access vs really doesn't exist:
s.doneChan undefined (cannot refer to unexported field or method doneChan)
s.noSuchPrivate undefined (type http.Server has no field or method noSuchPrivate)
What did you see instead?
error message: unknown field 'doneChan' in struct literal of type http.Server
which IMHO is misleading because the field does exist, I just can't see it from this place.

This is a followup to #25727, the necessary change is probably similar.  cc @odeke-em who's improved these messages before (thanks!).
I can submit a PR if nobody gets to it first.

Strawman defense: A purist could argue it's none of my business which private fields exist and which don't.  But as a human I do care!  I may be the author of both packages and just forgot where I am.  I may be in position to make the field public.  I may need to use an exported factory function instead of a literal...
Anyway the wording "unknown" when the field clearly was there left me derailed me for several minutes and only figured it with StackOverflow...
Plus the messages for regular access already make the "unexported field" / "has no field" distinction.

I'm sympathetic to making the error message more helpful.
One distinction I'll point out about the s.doneChan case is that the error is primarily "s.doneChan undefined" (which is the real error), and then parenthetically mentions that doneChan is a non-exported field (which is additional detail that may or may not help the user).
In the case of the struct literal element, "unknown field" is the primary error. We could add more details about the similarly-named non-exported field, though the message as-is is already kinda wordy.
Maybe we can change the error message to something like:
invalid key doneChan: cannot refer to unexported field or method doneChan
invalid key noSuchPrivate: type http.Server has no field or method noSuchPrivate

Are there any security implications of leaking the fact that there is a private field with such a name ? I guess it doesn't matter anyways since we are doing away with binary-packages.

Are there any security implications of leaking the fact that there is a private field with such a name ?

No, it's outside of Go's security model to keep non-exported fields confidential. There are numerous ways to enumerate them anyway; e.g., go/types or reflect.

Thank you for the ping @cben and my apologies for the late reply, I was drowning in a bunch of work but I am finally catching up :) Good stuff advocating for better user experience in compiler error messages and sorry that it consumed your time.
Thank you @agnivade for the question about revealing what's exported or unexported: I've always wondered about that question too, and I think that in most contexts it is a valid security issue e.g. when doing an RPC, one can start to phish for fields, for example if am trying to guess the size of a struct that's remote and I want to examine what fields it has e.g. with Go Cloud Functions, but that might be too contrived and also the ease of use is what comes first so I agree with @mdempsky here that we shouldn't be sweating about the security model, but also in deed, one can use go/types or reflect.
@mdempsky thank you for the error message suggestions

invalid key doneChan: cannot refer to unexported field or method doneChan
invalid key noSuchPrivate: type http.Server has no field or method noSuchPrivate

However, I am not too fond of using "invalid key". "key" is valid for a struct field but for a method, that becomes awkward. I can whip up a CL shortly, that'll be simple and we can discuss on there what the messages should look like.

However, I am not too fond of using "invalid key". "key" is valid for a struct field but for a method, that becomes awkward.

"Key" is what the spec calls the syntax before the colon in a composite literal element: https://golang.org/ref/spec#Composite_literals

Thanks Matthew! Yes, I am aware :) Perhaps I should have said that using "Key" in a message about a "method" seemed awkward to me, but on re-evaluating SGTM.


[CONTROLLER/TAGRECORDER] support cluster redis

This PR is for:

Server

Fixes cluster redis connection error
Steps to reproduce the bug

try to fit cluster redis

Changes to fix the bug

create universal redis client based on host info

Affected branches

main

Checklist

[ ] Added unit test to verify the fix.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.zhengya seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Rename symlink command to link in README.

The symlink command was previously renamed to link (in 59f6239), but references in the README
were not updated.  Running homesick help doesn't reveal a symlink command.
This patch updates homesick symlink ...  examples in the README.  The word symlink is still used in general descriptions in the paragraph text (i.e wherever it is not actually a code example).

Coverage increased (+0.03%) to 88.276% when pulling 4cb2006f41702b7010e49201caaa8c3c267555c8 on fuzzbomb:update-README-symlink-command into 66347d307ff062434a6e2674b69e172e3d809bab on technicalpickles:master.

Coverage increased (+0.03%) to 88.276% when pulling 4cb2006f41702b7010e49201caaa8c3c267555c8 on fuzzbomb:update-README-symlink-command into 66347d307ff062434a6e2674b69e172e3d809bab on technicalpickles:master.

Coverage increased (+0.03%) to 88.276% when pulling 4cb2006f41702b7010e49201caaa8c3c267555c8 on fuzzbomb:update-README-symlink-command into 66347d307ff062434a6e2674b69e172e3d809bab on technicalpickles:master.


X-CSRF-TOKEN

When I attempt to rank someone, I get an error.
An error occured when running the promote command: Error: Did not receive X-CSRF-TOKEN

Update noblox

How do I do that?

npm i noblox.js

Please could you close this issue if you've solved it now.


pytest run is failing

py-evm Version: master (with https://github.com/ethereum/py-evm/pull/1538)
OS: osx
Python Version 3.6.7, 3.7.1
Environment (output of pip freeze):

(venv36) javi@franciscos-mbp ~/e/py-evm> pip freeze
alabaster==0.7.12
apipkg==1.5
appnope==0.1.0
argh==0.26.2
asn1crypto==0.24.0
async-generator==1.10
async-lru==0.1.0
asyncio-cancel-token==0.1.0a2
atomicwrites==1.2.1
attrdict==2.0.0
attrs==18.2.0
Babel==2.6.0
backcall==0.1.0
bleach==3.0.2
bloom-filter==1.3
bumpversion==0.5.3
cachetools==2.1.0
certifi==2018.11.29
cffi==1.11.5
chardet==3.0.4
coincurve==8.0.2
colorama==0.4.1
coverage==4.5.2
cryptography==2.4.2
cytoolz==<IP_ADDRESS>
decorator==4.3.0
docopt==0.6.2
docutils==0.14
eth-abi==1.2.2
eth-account==0.2.3
eth-bloom==1.0.1
eth-hash==0.2.0
eth-keyfile==0.5.1
eth-keys==0.2.0b3
eth-rlp==0.1.2
eth-typing==2.0.0
eth-utils==1.3.0
execnet==1.5.0
flake8==3.5.0
hexbytes==0.1.0
hypothesis==3.69.5
idna==2.7
ifaddr==0.1.5
imagesize==1.1.0
ipython==6.5.0
ipython-genutils==0.2.0
jedi==0.13.1
Jinja2==2.10
jsonschema==2.6.0
lahja==0.9.0
lru-dict==1.1.6
lxml==4.2.5
MarkupSafe==1.1.0
mccabe==0.6.1
more-itertools==4.3.0
mypy==0.641
mypy-extensions==0.4.1
netdisco==2.2.0
netifaces==0.10.7
packaging==18.0
parsimonious==0.8.1
parso==0.3.1
pathtools==0.1.2
pexpect==4.6.0
pickleshare==0.7.5
pkginfo==1.4.2
pluggy==0.7.1
plyvel==1.0.5
prompt-toolkit==1.0.15
ptyprocess==0.6.0
py==1.7.0
py-ecc==1.4.3
-e git+git@github.com:javimaravillas/py-evm.git@387496a5fb289e3a5f7881cb3bc86ca38847d9cc#egg=py_evm
pycodestyle==2.3.1
pycparser==2.19
pycryptodome==3.7.2
pyethash==0.1.27
pyflakes==1.6.0
Pygments==2.3.0
pyparsing==2.3.0
pysha3==1.0.2
pytest==3.6.4
pytest-asyncio==0.9.0
pytest-asyncio-network-simulator==0.1.0a2
pytest-cov==2.5.1
pytest-watch==4.2.0
pytest-xdist==1.18.1
python-dateutil==2.7.5
pytz==2018.7
PyYAML==3.13
readme-renderer==24.0
requests==2.20.1
requests-toolbelt==0.8.0
rlp==1.0.3
simplegeneric==0.8.1
six==1.11.0
snowballstemmer==1.2.1
Sphinx==1.7.9
sphinx-rtd-theme==0.4.2
sphinxcontrib-asyncio==0.2.0
sphinxcontrib-websupport==1.1.0
termcolor==1.1.0
toolz==0.9.0
tox==2.7.0
tqdm==4.28.1
traitlets==4.3.2
trie==1.3.8
twine==1.12.1
typed-ast==1.1.0
uPnPClient==0.0.8
urllib3==1.24.1
uvloop==0.11.2
virtualenv==16.1.0
watchdog==0.9.0
wcwidth==0.1.7
web3==4.4.1
webencodings==0.5.1
websockets==5.0.1
zeroconf==0.21.3

What is wrong?
pytest run is failling
Please include information like:

full output of the error you received

(venv36) javi@franciscos-mbp ~/e/py-evm> pytest
================================================================== test session starts ==================================================================
platform darwin -- Python 3.6.7, pytest-3.6.4, py-1.7.0, pluggy-0.7.1
rootdir: /Users/javi/ethereum/py-evm, inifile: pytest.ini
plugins: xdist-1.18.1, cov-2.5.1, asyncio-0.9.0, asyncio-network-simulator-0.1.0a2, hypothesis-3.69.5
collected 55381 items / 3 errors / 1 skipped

======================================================================== ERRORS =========================================================================
_______________________________________________ ERROR collecting tests/core/validation/test_validation.py _______________________________________________
import file mismatch:
imported module 'test_validation' has this __file__ attribute:
  /Users/javi/ethereum/py-evm/tests/beacon/test_validation.py
which is not the same as the test file we want to collect:
  /Users/javi/ethereum/py-evm/tests/core/validation/test_validation.py
HINT: remove __pycache__ / .pyc files and/or use a unique basename for your test file modules
____________________________________________________ ERROR collecting tests/database/test_chaindb.py ____________________________________________________
import file mismatch:
imported module 'test_chaindb' has this __file__ attribute:
  /Users/javi/ethereum/py-evm/tests/beacon/db/test_chaindb.py
which is not the same as the test file we want to collect:
  /Users/javi/ethereum/py-evm/tests/database/test_chaindb.py
HINT: remove __pycache__ / .pyc files and/or use a unique basename for your test file modules
__________________________________________ ERROR collecting tests/trinity/integration/test_plugin_discovery.py __________________________________________
ImportError while importing test module '/Users/javi/ethereum/py-evm/tests/trinity/integration/test_plugin_discovery.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
tests/trinity/integration/test_plugin_discovery.py:7: in <module>
    from peer_count_reporter_plugin import PeerCountReporterPlugin
E   ModuleNotFoundError: No module named 'peer_count_reporter_plugin'
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Interrupted: 3 errors during collection !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
========================================================== 1 skipped, 3 error in 13.88 seconds ==========================================================

what command you ran

pytest

How can it be fixed
Still debugging the issue
Fill this in if you know how to fix it.
Still debugging the issue

Hi @javimaravillas
This doesn't happen if you run these tests through tox though (e.g tox -e py36-trinity-integration)
The failing test basically test that external plugins can be installed. We install the plugin through tox though.
https://github.com/ethereum/py-evm/blob/f2d0d5d187400ba46a6b8f5b1f1c9997dc7fbb5a/tox.ini#L73
So, if you run these test locally through pytest directly you'll run into this because the plugin was simply not install. Of course you can just manually install it and then running pytest will work as expected.
I'd say it is slightly annoying but it's something that could probably be improved through better docs or maybe even a raised warning that hints about this.
That said, I'm open to other solutions (e.g. doing the plugin installation from within the test) if they achieve what we want.

Thanks for the fast reply @cburgdorf, I will update the docs, I think is good enough

Alright! I'll close this issue. Feel free to re-open if you think it needs further discussion.

This is mighty annoying when trying to run a single test by node ID, e.g.
pytest -vvvvv --capture=no -k "test_rpc_against_fixtures[/home/veox/src/py-evm/fixtures/BlockchainTests/GeneralStateTests/stRevertTest/RevertInCreateInInit_d0g0v0.json:RevertInCreateInInit_d0g0v0_Byzantium-Chain]"

I either have to also specify the file:
pytest -vvvvv --capture=no tests/trinity/json-fixtures-over-rpc/test_rpc_fixtures.py -k "test_rpc_against_fixtures[/home/veox/src/py-evm/fixtures/BlockchainTests/GeneralStateTests/stRevertTest/RevertInCreateInInit_d0g0v0.json:RevertInCreateInInit_d0g0v0_Byzantium-Chain]"

... or remove the offending test files, so they don't get collected.

For the first two errors, the solution could be simple, following the suggestion in error message:
use a unique basename for your test file modules

For the peer_count_reporter_plugin error, perhaps it can be added as a dependency to [dev], or something?.. (No good ideas yet.)

I think we should double check if we can move the installation into the test (instead of having it installed through tox).

Actually, always specifying the file turned out to be not so bad, since now pytest doesn't have to collect the tests on every invocation, to find which file that test_state_fixtures is described in.
Still, it can be very confusing, as this issue highlights. I'm sure we'll be seeing duplicates.


Able to learn, Unable to send.

When I use Example 3 I am able to learn, I see the light come on on the RM4 mini and I am able to get a long string when I press my remote.
When I try to send it, nothing happens. Added the code I am using below.
Then I tried adding "520c" to Constant.js to see if that would help, but no luck. Discover node outputs this.
12/9/2024, 5:25:00 PM[node: debug 110](https://<IP_ADDRESS>:1881/#) msg.payload : array[1] array[1] 0: object mac: "e870723f41c6" ip: "<IP_ADDRESS>" typeid: "520c" type: "Broadlink: Unconfigured Device Type: Log an issue with the device details and typeid returned as this may be a new device type." name: "智能遥控" cloud: false msgdata: buffer[128]
[     {         "id": "f43b5608.668fb8",         "type": "inject",         "z": "e708aa63.cfe5a8",         "name": "",         "repeat": "",         "crontab": "",         "once": false,         "topic": "",         "payload": "",         "payloadType": "str",         "x": 250,         "y": 1020,         "wires": [             [                 "4ed7416f.e4605"             ]         ]     },     {         "id": "7e782238.85366c",         "type": "debug",         "z": "e708aa63.cfe5a8",         "name": "",         "active": true,         "console": "false",         "complete": "payload",         "x": 670,         "y": 1020,         "wires": []     },     {         "id": "8736841b.643398",         "type": "RM",         "z": "e708aa63.cfe5a8",         "name": "",         "device": "876c8eb5.648ce8",         "action": "_msg_",         "remote": "",         "button": "",         "fix": "",         "x": 530,         "y": 1020,         "wires": [             [                 "7e782238.85366c"             ]         ]     },     {         "id": "4ed7416f.e4605",         "type": "function",         "z": "e708aa63.cfe5a8",         "name": "Set IR Data",         "func": "//Insert learning code here\nvar data = [38,0,150,0,243,92,20,46,18,47,17,93,19,92,18,92,20,91,17,49,18,92,20,91,17,48,19,47,19,46,19,47,19,45,19,47,20,91,19,47,18,47,18,47,20,46,17,47,21,45,20,91,19,47,19,46,19,91,20,46,19,46,17,94,19,47,19,46,19,46,20,46,20,45,17,48,20,46,19,47,18,47,19,47,18,48,18,47,18,46,21,45,20,45,20,46,19,47,17,49,18,47,18,47,19,47,19,46,19,47,19,45,18,48,20,46,17,49,18,47,17,94,19,46,17,48,20,46,20,45,20,91,18,48,19,91,19,46,19,47,17,48,19,91,20,46,20,91,19,91,20,0,13,5,13,5];\n\nmsg.payload={\n    //\"mac\":\"E870723F41C6\",\n    //\"host\":\"<IP_ADDRESS>\",\n    \"action\":\"send\",\n    \"data\":data,\n    \"repeat\":2\n};\n\nreturn msg;",         "outputs": 1,         "timeout": "",         "noerr": 0,         "initialize": "",         "finalize": "",         "libs": [],         "x": 390,         "y": 1020,         "wires": [             [                 "8736841b.643398",                 "a7e33051ef28dd0b"             ]         ]     },     {         "id": "ac0302cc.1943b",         "type": "RM",         "z": "e708aa63.cfe5a8",         "name": "",         "device": "876c8eb5.648ce8",         "action": "learn",         "remote": "",         "button": "",         "fix": "",         "x": 370,         "y": 920,         "wires": [             [                 "db4a927d.dba42"             ]         ]     },     {         "id": "4a665352.1a5d0c",         "type": "inject",         "z": "e708aa63.cfe5a8",         "name": "",         "repeat": "",         "crontab": "",         "once": false,         "topic": "",         "payload": "",         "payloadType": "str",         "x": 250,         "y": 920,         "wires": [             [                 "ac0302cc.1943b"             ]         ]     },     {         "id": "aff7c493.75d488",         "type": "debug",         "z": "e708aa63.cfe5a8",         "name": "",         "active": true,         "tosidebar": true,         "console": false,         "complete": "payload",         "x": 630,         "y": 920,         "wires": []     },     {         "id": "db4a927d.dba42",         "type": "json",         "z": "e708aa63.cfe5a8",         "name": "",         "pretty": false,         "x": 490,         "y": 920,         "wires": [             [                 "aff7c493.75d488"             ]         ]     },     {         "id": "745f4e02.4fe5b",         "type": "comment",         "z": "e708aa63.cfe5a8",         "name": "Learn",         "info": "1. Inject\n2. Tap the remote button\n3. Copy learned code from debug tab",         "x": 250,         "y": 880,         "wires": []     },     {         "id": "232d8d19.4ce052",         "type": "comment",         "z": "e708aa63.cfe5a8",         "name": "Send learned code",         "info": "1. Insert learned code in the function node\n2. Deploy\n3. Inject",         "x": 290,         "y": 980,         "wires": []     },     {         "id": "a7e33051ef28dd0b",         "type": "debug",         "z": "e708aa63.cfe5a8",         "name": "debug 111",         "active": true,         "tosidebar": true,         "console": false,         "tostatus": false,         "complete": "false",         "statusVal": "",         "statusType": "auto",         "x": 570,         "y": 980,         "wires": []     },     {         "id": "876c8eb5.648ce8",         "type": "rmdevice",         "folder": "/data/node_modules/node-red/public/broadlink",         "mac": "E870723F41C6",         "host": "<IP_ADDRESS>",         "devType": "520c"     } ]

https://github.com/mlfunston/node-red-contrib-broadlink-control/issues/90#issuecomment-1180639971
this was the fix.


Enable communication with rabbitmq using rabbitmq_stomp plugin

TODO:

[ ] Make pass with ActiveMQ broker: AMQ and RMQ handle temporary queues differently. May not be able to get away with one handling for both.
[ ] Run tests with RMQ and AMQ?
[ ] RMQ timeouts test_subscribe_before_connect.

Logical flow of subscribe_before_connect:

Submit request to subscribe
As not connected, subscribe operation is cached
enter connect()
Connect to broker
All cached subscription operations occur
return from connect()
Any further operations

Working with RMQ container with stomp locally (https://github.com/quangthe/docker-rabbitmq-stomp) when 0.8s at end of connect method, but timing out without, implies 6 ocurring before 5?
When running on cluster with Helm deployment, logs exception reached_max_restart_intensity: are subscriptions being called before the connection is up (i.e. 5 before 4?)

Actual behaviour:
test_stomptemplate.py::test_subscribe_before_connect
3
5
6
1
5
3
4
5
6
7
1
5
3
3
5
6
4

Race condition/subscribe_before_connect fixed


iOS - Universal links not configuring correctly

So I've looked everywhere and done everything I can do.  As best I can tell, this plugin isn't configuring the necessary entitlements in the packaged IPA file.
I used this web service to test the bnc.lt apple-app-site-association file to make sure my universal links are configured correctly on the branch side of things.  I was able to see the app I am looking for and it looks configured correctly.
Then I uploaded my test IPA file that was generated with this plugin.  It's telling me Must be able to find entitlements (looking in VeociDev/Payload/VeociDev.app/archived-expanded-entitlements.xcent).
I have the necessary Associated Domains configuration set up for this app ID in the apple developer portal.  This is what my plugin configuation looks like in the config.xml file for the build, with the appropriate flags filled in:
   <!--

Here is a screenshot of the result:

I may have asked this before, but does the plugin use Cordova hooks to setup the universal links config stuff?  That may be why this is failing.  Phonegap Build doesn't support hooks so I may be out of luck.

@gabaum10 , yes, there are hooks being executed upon building the plugin. I'm sorry to hear that, I think they don't have the intention on implementing it soon.

Crap, @renesansz or anyone else, are you aware of any cross platform tools that would support hooks?  The problem is I don't have access to a mac to do iOS builds.  I've tried Phonegap build and Intel XDK and neither of them support hooks.

Well, I guess this isn't really a problem with this plugin but rather shortcomings in PGB.  Here is a similar plugin here:


Added Assembly Resolve

Added logic to resolve referenced assemblies of generator assembly.
This should prevent problems with generators that uses other assemblies described in #61.
To use DependencyContext it was necessary to push target framework version to netstandard 1.6.

I also updated I also updated NedbankGitVersioning to 2.1.23 and removed the hack that was previous needed since Appveyor updated there build tools.
I hope you do not mind that I mix this up with this issue.


UI while performing operations

The enabled state of various controls should be reviewed when items are being saved and updated, and in tag management operations.

51ed2de
28fdfc3
c6e15f5
2c055ec
4c3ca25


Introduce Marshaling library

Add generic Marshaling library for TPM types

I think this build failure is unrelated. May have come from 0e72ba6a24413a8a438e5191c2fe97fd61055c83. If so then it's clang and FORTIFY_SOURCE having a bad interaction?

No, it doesn't look like it is from 0e72ba6.

Fixed issue introduced by 0e72ba6a24413a8a438e5191c2fe97fd61055c83 #484. This should resolve the build failure. Will start the review tomorrow.

New PR created


Exception during making request

Hi,
when I use c# telegram bot library after for example 1000 requests I get this error and the project stopped
"Exception during making request "
please help

Duplicate for #1106


Provide a way to create internal links between wiki pages and specific page sections

It is common to link between wiki pages with simplified syntax as described in GitHub wiki help:

To create a reference link, use two sets of square brackets. [[my internal link|internal-ref]] will link to the internal reference internal-ref.

Extend the Markdown parser to create a function that identifies and resolves such internal links.

https://github.com/redmatrix/hubzilla/pull/438


Remove css styles if extension/webpart is disposed

Category

[x] Question
[ ] Typo
[x] Bug
[ ] Additional article idea

spfx 1.8.
I noticed that each time an extension/webpart is disposed the css referenced to the page is not destroyed. E.g: an spfx extension for custom site header is disposed when moving between site/pages but the css <style/> is still intact on <head> and isn't removed. Is it possible to clean the css as well?

Closing as appears this is a dupe of #3461


conformance status for /docs/getting-started-guides/ubuntu

Per #7278, we are looking to identify guides that are stale vs actively maintained but need work to become conformant.
From the content of /docs/getting-started-guides/ubuntu it is unclear what version of Kubernetes user will get and whether resulting cluster will be conformant or not. However, there is a subsection on validation, which indicates how user can run e2e suite, however, it doesn't say very clearly whether the users should expect e2e tests to pass when their cluster installation is correct (to some definition of correctness, of course).
On the other hand, the index page leads Ubuntu website, which has a Certified Kubernetes logo.
PING owners/approvers/contributors @steveperry-53 @ktsakalozos @tvansteenburgh

Thanks @errordeveloper. We do submit passing conformance results, I think we just need to clarify some of the ambiguity in the docs, as you pointed out. Thanks for the review, we'll address this soon.

Thanks, Tim!
On Tue, 20 Feb 2018, 10:34 pm Tim Van Steenburgh<EMAIL_ADDRESS>wrote:

Thanks @errordeveloper https://github.com/errordeveloper. We do submit
passing conformance results, I think we just need to clarify some of the
ambiguity in the docs, as you pointed out. Thanks for the review, we'll
address this soon.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/website/issues/7464#issuecomment-367144600,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAPWS-cMLzjAxLha4_Yii_TyVdGst8K6ks5tW0h2gaJpZM4SMwgt
.


Changed disk to boot_disk and added  initialize_params to main.tf

I'm not sure if I pulled the wrong file, but terraform apply failed until the updates were made.
Thanks,
Jason

Looks like we fixed this for our bosh doc but not concourse.
Thanks for identifying this!


feat(BREAKING CHANGE): move out of beta

:tada: This PR is included in version 2.0.0 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


503 ERROR

Don't work, I get error:
503 ERROR
The request could not be satisfied.
The Lambda function associated with the CloudFront distribution is invalid or doesn't have the required permissions. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner.
If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
Generated by cloudfront (CloudFront)
Request ID: hiP1wRlybC_okraZxuX9rxaDKgTtBBOJ-e1_Ae2qh3QrGCtZzIfKtg==

I followed the instructions and still getting the same 503? I am using 3.8 in cloudformation template. I even did pip install with python-version set to 3.8. Any other ideas how to make this work or troubleshoot? Nothing is coming in cloudwatch?

To shed slightly more light on this issue.
When running the Lambda manually (using Python 3.11), I get this error:
{
  "errorMessage": "Unable to import module 'main': cannot import name 'awscrt' from 'botocore.compat' (/var/lang/lib/python3.11/site-packages/botocore/compat.py)",
  "errorType": "Runtime.ImportModuleError",
  "requestId": "f5ee8ffe-6bc6-4097-ae88-6ad63ad1d341",
  "stackTrace": []
}

This would explain the 503s.
I have tried various dependencies like botocore[crt] as alternatives. No luck.
Perhaps either @lovaarte or @rprentyaws could shed some light on this issue? I'd really like to get this pattern working 🙏

I ran into same error: module 'botocore.crt' has no attribute 'auth'
After investigating the issue, figured out that there's some conflict with the packages. So here is what I did:
I used GitHub copilot and regenerated the code and added some logs.
I've tested it and see that the request is now being signed using sig4 auth.
You can find the updated in my personal repo. (I did not submitted a merge as I am not entirely sure if I can do that after making use of GitHub Copilot :face_with_peeking_eye: :shushing_face: )
https://github.com/cheedallarajesh/amazon-cloudfront-with-s3-multi-region-access-points/tree/main/lambda
both lambda_function.py and requirements.txt are updated accordingly.
Please check the commit message for the lambda response showing signed request.

I was able to get this working. Here is what I did to resolve it:

The requirements.txt is referring to versions which needs to update to latest

awscrt==0.19.10
boto3==1.28.0
botocore==1.31.0
requests==2.31.0

As I am on Windows, for some reason the awscrt though I see the package, it is complaining about it. So, I used Ubuntu (WSL) and downloaded all the packages and latest ones to ./packages folder.
I included all the modules at the lambda_function.py level (root level). This may not be required but for some reason or maybe its lambda@edge, I couldn't get it work by keeping modules in /packages folder.

The key is, after having right versions of modules downloaded (in ubuntu environment) I could able to work it.

Here's my imports:

import boto3
import botocore
from botocore import awsrequest
from botocore.crt.auth import CrtS3SigV4AsymAuth
import awscrt.auth
import logging

Checked below line
https://github.com/aws-samples/amazon-cloudfront-with-s3-multi-region-access-points/blob/03a3a6f8c2b4ce71f57b979d21434772f662d561/lambda/lambda_function.py#L24

to this> with respect to updated imports
sigv4a = CrtS3SigV4AsymAuth(self._session.get_credentials(), service, region)


KAFKA-7098: Improve accuracy of throttling by avoiding under-estimating actual rate in Throttler

This PR modifies Throttler.scala by setting the periodStartNs to the current time instead of the time before the potential sleep call when throttling is needed. The reason behind is that if we reset periodStartNs to the time before sleep, we will increase the time window in the next actual rate calculation, which will underestimate the actual rate and may miss the throttling opportunity or sleep for less time. A unit test is also added to test the fix.
For example, if we use Throttler to throttle the pre sec rate to 10 with checkInterval 1s, in the original implementation:

15 events happen during [t0, t0+1s]
Throttler will sleep the thread until t0+1.5s, then reset period start time to t0+1s
10 events happen during [t0+1.5s, t0+2s], Throttler will not throttle this time because the estimated rate is 10 / [(t0+2s) - (t0+1s)] = 10

But the actual rate during [t0, t0+2s] is (10+15) / 2 = 12.5 > 10
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Ping @lindong28 for review.

@lindong28 Thanks for the review. PR updated to address comments.


Spitzer branch

I updated a bunch of pages please take a look. I tried to stay consistent with colors and stuff you all had.

sending new one


Tests are being discovered by two Python processes

Environment data

VS Code version: 1.33.0
Extension version (available under the Extensions sidebar): 2019.3.6558
OS and version: Ubuntu 16.04
Python version (& distribution if applicable, e.g. Anaconda): Python 3.5
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): venv
Relevant/affected Python packages and their versions: pytest-3.8.2

Expected behaviour
Tests to be shown only once in the tests tab
Actual behaviour
Same Tests are shown twice. During discovering them, two Python processes are spawned, taking up equally sized RAM, leading to the system RAM depletion and system stopping responding
Steps to reproduce:

Open a project with tests inside

Logs
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
Starting Jedi Python language engine.

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help; turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging)
-1555071013451.log
Snapshot of the unexpected behavior:

Reason was that the pytest arguments used were scanning the folder twice:
"python.unitTest.pyTestArgs": ["tests", "."]
If this the expected behavior, pleas close the issue.

If this is the expected behavior, pleas close the issue.

Yes it is.


Fix inverted was_killed logic

Motivation
The was_killed functions check that the node was not killed, and assert_was_killed errors on was_killed. This logic is inverted.
This bug isn't visible to callers of TestOutput, because the logic is inverted twice, so assert_was_killed correctly asserts that the node was killed.
Solution
Use the correct logic in those functions.
Also improve the error messages and code structure.
Review
This is a routine bug fix.

The testnet large sync failure will be fixed by #1789


Authorization

How to authorize by chat id?
How to make the bot answer only one chat id?

Unfortunately the begin() method is currently not sufficient to get the chat id.
You have to receive at least one message or for example use this address https://t.me/JsonDumpBot
Once you have the right chat id, compare it with msg.sender.id value in loop() and discard messages if don't match.

Unfortunately the begin() method is currently not sufficient to get the chat id.
You have to receive at least one message or for example use this address https://t.me/JsonDumpBot
Once you have the right chat id, compare it with msg.sender.id value in loop() and discard messages if don't match.


Post updated info for motion of KBOs

So, this is the absolute minimum and maximum velocities for an object at 30 AU (the inner range of our TNO searches and therefore the fastest) at various inclinations. DECAM's pixel scale is ~.26 arcsec/pixel so you can use that to see how much these objects would move between images in case we wanted to make coadds for difference imaging templates. @DinoBektesevic @smotherh

Radius (AU)
Inclination (deg)
Min Vel. (Arcsec/hr.)
Max Vel. (Arcsec/hr.)

30
0
0.02
5.64

30
15
0.01
5.65

30
30
0.01
5.67

30
45
0.02
5.70

30
90
0.02
5.83

30
135
0.01
5.97

30
180
0.00
6.03

Closed by #66


❓ How to stop camera usage

Question
Currently I have and app utilizing react navigation.
When I start the app all is fine.
When I navigate to the screen with the Camera view, all is also fine.
And there is a green dot  above network state on iPhone, signaling that camera is in use.
But when I navigate back to the main screen (CameraView is gone) the green dot stays.
Which means the camera is still in use.
When I leave the app the indicator dot disappears.
But when I return to the app, the dot appears again. Despite there is no more CameraView on the screen.
And looks like isActive, photo and video has no effect on the green dot...
So how to stop camera usage when CameraView is not on the screen?
My current usage code:
  const isForeground = visible && appState === 'active';
...
      {device ? (
        <Camera
          ref={camera}
          style={StyleSheet.absoluteFill}
          device={device}
          torch={visible && flash ? 'on' : 'off'}
          isActive={isForeground}
          frameProcessor={Platform.select({
            ios: frameProcessor,
            default: undefined,
          })}
          frameProcessorFps={2}
          photo={isForeground}       // <--- added flag here to check if this hash effect - no effect
          video={isForeground}       // <--- added flag here to check if this hash effect - no effect
        />
      ) : null}
...

You should only set isActive to false, photo and video should always stay true
Can you log isForeground? I just tested it using react-native-navigation and it works perfectly fine if I use a isForeground variable, did you read the "Lifecycle" documentation?

Seems weird to me that the green dot stays when you navigate back to the main screen, as that means that the Camera screen does not get destroyed correctly which seems to be wrong 🤔

Thank for fast feedback!
So.

Ok
Yes, I debugged with console.log and the isForgeround value changes to false once the screen with camera goes off the screen. It is currently placed in a PagerView along with other screens...
And yes, I read the Lifecycle docs about "camera pause" and I guess it is not the same as "camera stop".
In my case visible is true if current ViewPager page index is 1 (the page with the camera view.
I'm on 2.2.0 currently

Seems weird to me that the green dot stays when you navigate back to the main screen, as that means that the Camera screen does not get destroyed correctly which seems to be wrong 🤔

Hum 🤔
Is there an easy way to proof or disproof this? :sweat_smile:

If I pass isActive={false} to my Camera, the Camera pauses/freezes and the green dot at the top disappears. I'm currently on react-native-vision-camera 2.1.0.

Just checked again by force quit the app and relaunch.
No issue.
Looks like it was a chaotic glitch 😅

Perfect! 👍
Maybe it is a hot-reload/fast-refresh issue, if you can reproduce it again please create a bug report 🙏

Got same issue on a normal View, any updates ?

@icodeface did you resolve the issue ? I'm facing this issue right now

@icodeface did you resolve the issue ? I'm facing this issue right now

We found the issue was from our side, the Camara was not released correctly.

@icodeface did you resolve the issue ? I'm facing this issue right now

We found the issue was from our side, the Camara was not released correctly.

How to release the camera? In my case, I am navigating away to a different tab

Either pass false to isActive or just unmount the Camera component.


TODO: Context Events mids are generated using rand()

Context Events mids are generated using rand(), this is a temporary solution which needs to be improved because it can have unfortunate consequences:

There is a probability of mid collision (1 in 1 billion per session)
Idempotency broken in case of failure (might generate two events for one save)

What about a more complex id generation algorithm.
Something like epoch_timestamp (this will ensure time ordering of the id) + long enough random hex string creating a 16/32 bytes string making the chance of collision to become very very slim. (over 1 billion event per s)
(ruby -> Time.now.to_i.to_s(16) + SecureRandom.hex(12))

Hi, thanks for the suggestion. I agree a more complex id generation algorithm could significantly reduce the probability of collision. However if a checkpoint fails and the operation has to be retried, we will generate two events.
Alternatively I was thinking of keeping a table with the context version number, on every checkpoint  we could increase the version number and generate the event mid based on the version. This would guarantee no collision and consistency. The change is more involved and could have significant performance impact.

Hi,
The is could be very memory intensive. An alternative solution would be to use a bloomfilter there as you only need to check if the id already happen in the past and let the key expire overtime to avoid overflowing the filter.
The bloomfilter will then no impact performance that much and keep a low memory footprint.

Hi, just quick update on this issue. I pushed a fix to avoid rand() when generating event ids for checkpoints. I do keep an extra number for every state object.
To enforce idempotency, the engine keeps track of the event ids already seen (this code has existed for a while). Yes, we need to replace the lookup with a bloom filter as you suggest above.


MRPHS-3404: Added dummy methods for new methods of VirtualMachine interface

Jira id
MRPHS-3404
Problem
New methods have been added to VirtualMachine interface, thus dummy methods needs to be implemented in AWS/vm.go for build
Solution
Added dummy methods in vm.go

Have removed declaration of AddDisk, RemoveDisk and Reset from VM Interface. But have kept added dummy methods in aws/vm.go as anyway it will have to be implemented.


Remove Hamlet, Smile and Pun Pun from Thief objective

About the PR
title
Why / Balance
stealing ghostrole is asspain
Changelog
:cl:

remove: Removed Hamlet, Smile and Pun Pun from Thief objectives

“Remove hamlet” :godo:


construction of grants and requests are not async

Currently PermissionGrant and PermissionRequest have an async parse() method to instantiate them with a private constructor.
However there is currently no async action needed to parse the grant/request. Any objection to removing the parse() method in favor of just using the constructor?

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

Project coverage is 98.69%. Comparing base (a7543fc) to head (b75e8d3).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #791      +/-   ##
==========================================
- Coverage   98.69%   98.69%   -0.01%
==========================================
  Files          73       73
  Lines       11269    11259      -10
  Branches     1612     1610       -2
==========================================
- Hits        11122    11112      -10
  Misses        141      141
  Partials        6        6

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

Keeping the pattern of async parse() over constructors.


Unable to display progress for tag, company and total.

same here

fixing.
Thank you both.

bug has been fixed. It's a urgent fix, please let me know if you still meet bugs.
Thank you so much.

The total progress can be displayed now but progress over different companies and tags still cannot be displayed.

By total progress, I mean the bar chart at the bottom of the right column.

It works!


Add unpredictable number to Solidity code for ZK proofs

The Solidity part of issue #167
See section 2.2.1 in the Token-negotiator report.
See Jira issue 291.

UN should be signed, validation require more GAS, but if we need it then option2 can suit it (but we have to change UN flow to use ECDSA - https://github.com/TokenScript/attestation/issues/275):
https://github.com/TokenScript/attestation/issues/266#issuecomment-1171059211
but maybe option 1 will be enough? user always will be warned when he share attestation secret and we dont waste gas?
@jot2re , what do you think?

I am not sure option 1 form #266 is sufficient in this case. It depends on the use-cage. For example if the user needs to prove the same email used in an attestation as in the ticket, then such a proof could be reused. Of course the contract might disallow this, but in general it is not good to share cryptographic proofs on the blockchain which are not linked to a specific usage.

@jot2re  yes, option 1 solve bit different problem: avoid to share attestation+secret with anyone without confirmation (through hidden iframe)
for UN+ZKP: if we use ZKP for smartContract then context can be a smartContract address, but I am not sure how to do it in gas-efficient and secure way

I am also thinking something along the line of only using the address. When it comes to the UN on the blockchain, verification would require validating a signature (assuming we change UN implementation), which would be 3000 gas plus everything else.
So maybe it makes sense to have a different flow in off-chain and on-chain cases; using UN with optional context in the off-chain setting and simply using a context which is the address in the on-chain setting.

@jot2re , in case if we use smartContract address as context then we need definitely different context for off-chain (when we dont have smartContract address), domain can be good and simple option.
currently we check if both secrets fit each one. but how to mix context to this schema?


Use PHP-provided php.ini as default

Context
In the restructure work (#324), the PHP Dist buildpack is responsible for configuring the default php.ini file.
The PHP Dist buildpack (as it exists in https://github.com/paketo-buildpacks/php-dist/pull/341 for the restructure work) creates 2 php.ini files:

A static default php.ini file (config/default.ini)
A go-templated buildpack-provided php.ini (config/buildpack.ini)

Issue
This issue is to figure out how we can access the default php.ini file that ships with the PHP distribution, and use that in place of the static config/default.ini file. This is necessary because the default configuration might change slightly from version to version, so it may be problematic to use the same template for every version as we currently do.
The PHP source (from https://www.php.net/distributions/php-VERSION.tar.gz) we use to compile the buildpack-ready PHP distribution contains a php.ini-production file which could be used as the default php.ini. We should figure out we can retrieve that php.ini in the compiled PHP version, and swap that file in for the config/default.ini in the buildpack.
Acceptance
In order to close out this issue, I would expect that the default php.ini file used in the buildpack is taken from the PHP dependency from https://deps.paketo.io/php/... for all PHP versions we support in the buildpack.

This issue is blocked on the completion of #324


Support OAuth Endpoints

It would be great if APIEasy could take the hassle out of testing 2-legged & 3-legged OAuth resources (3-legged creating the biggest hassle.) Granted, there would have to be some DOM manipulation for entering u/p and submitting, but that would be easy to do with something like jsdom.

Going to throw out there: Request has support for oauth endpoints now.


Roll engine 93aa035dd469..2c25936ecdb2 (8 commits)

https://github.com/flutter/engine/compare/93aa035dd469...2c25936ecdb2
git log 93aa035dd46999353d8f7fe4be61e6599c794b4b..2c25936ecdb243492529a7cec51acadfba3729e3 --no-merges --oneline
2c25936ec Roll src/third_party/skia 2462ca36c800..5f5e1d57a4ce (7 commits) (flutter/engine#7699)
ac003c483 Roll src/third_party/skia 0783aca7ba31..2462ca36c800 (2 commits) (flutter/engine#7698)
e26eab83a Roll src/third_party/skia bb60677d5244..0783aca7ba31 (1 commits) (flutter/engine#7697)
ad525410d Roll src/third_party/skia 2d35a1c87553..bb60677d5244 (1 commits) (flutter/engine#7696)
cc27cafb8 Implemented Dark Mode for Android (#25525) (flutter/engine#7488)
9c05cbcfb Roll src/third_party/dart b53dceadaa..5823be65af (5 commits) 5823be65af [vm/compiler] Continued graph checker development (reland) 8231cdb7a3 [gardening] Update status for issue 35854 db7f848632 [vm] Remove dead BigInt code. 35ab1755f4 Support more type propagation for code-as-ui features 569ee07f91 [vm] Cleanup class finalization checks
ec5e6f6ef Ensure dart2js and kernel worker snapshots are copied out of gen dir (flutter/engine#7692)
8b5fa65c4 Roll src/third_party/skia 50ea3c06b80f..2d35a1c87553 (6 commits) (flutter/engine#7693)
The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
If the roll is causing failures, please contact the current sheriff (chinmaygarde@google.com), and stop
the roller if necessary.

Trybots failed. These were the failed builds: https://cirrus-ci.com/task/5544551977582592

Commit queue failed; closing this roll.


chore(main): release 2.5.5

:robot: I have created a release beep boop
2.5.5 (2023-10-18)
Bug Fixes

🚀 修复在 app 端环境下路由插件系统使用异常的问题 (894ca30)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/viarotel-org/vite-uniapp-template/releases/tag/v2.5.5 :sunflower: