Backup to Google Cloud Storage

Hello, I am trying and failing to store backups to Google Cloud Storage.
I have set up Workload Identity to give the k8s service account the permissions to access the bucket.
I have also tried defining the AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY variables.
Still I get
Error: failed to take a full dump: failed to put dump.tar: operation error S3: PutObject, https response error StatusCode: 403, RequestID: , HostID: , api error SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided. Check your Google secret key and signing method.
Is there anybody who made backups to GCS working?
Thank you!

Backup to GCS is not supported now.
It can be added by implementing Bucket interface for GCS in this package.
https://github.com/cybozu-go/moco/tree/main/pkg/bucket
We are welcome to a pull request for adding GCS support.

@filiprafaj
GCS supports the S3 compatibility API. (Sorry, I have not verified this.)
Could you please refer to the documentation and try again?
refs:

https://cloud.google.com/storage/docs/interoperability#xml_api
https://vamsiramakrishnan.medium.com/a-study-on-using-google-cloud-storage-with-the-s3-compatibility-api-324d31b8dfeb

If it still doesn't work, it would be helpful if you could report it again, including the definition of BackupPolicy 🙏
https://cybozu-go.github.io/moco/usage.html#backuppolicy

Hi @d-kuro , I have tried now with interoperability credentials and I am getting:
Error: failed to take a full dump: failed to put dump.tar: operation error S3: PutObject, https response error StatusCode: 403, RequestID: , HostID: , api error SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided. Check your Google secret key and signing method. failed to take a full dump: failed to put dump.tar: operation error S3: PutObject, https response error StatusCode: 403, RequestID: , HostID: , api error SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided. Check your Google secret key and signing method.
the backup file looks like this:
apiVersion: moco.cybozu.com/v1beta2
kind: BackupPolicy
metadata:
  namespace: default
  name: daily
spec:
  schedule: "@daily"
  jobConfig:
    serviceAccountName: moco-test-mysqlcluster
    env:
    - name: AWS_ACCESS_KEY_ID
      value: ***
    - name: AWS_SECRET_ACCESS_KEY
      value: ***
    bucketConfig:
      bucketName: ***
      endpointURL: https://storage.googleapis.com
    workVolume:
      emptyDir: {}
    memory: 1Gi
    maxMemory: 1Gi
    threads: 1

Hi @filiprafaj  ,
This issue seems to be a good initiation of my journey towards contribution to FOSS projects.
Can you please assign this to me?

Hii @filiprafaj i want to contribute to this issue

@Prakharkarsh1
Hi,
Thank you for your intention to contribute to this project.
We will review your pull request when it's ready.

@Prakharkarsh1
MOCO uses aws-sdk-go-v2 to connect to s3-compatible storage.
However, aws-sdk-go-v2 is not compatible with third-party platforms and therefore cannot connect GCS.
https://github.com/aws/aws-sdk-go-v2/issues/1816
So it would be better to implement for gcs bucket in moco/pkg/bucket/gcs.

We use minio to test S3 bucket implementation.
Likewise, we may use these tools to test GCS bucket implementation.

https://github.com/oittaa/gcp-storage-emulator
https://github.com/fsouza/fake-gcs-server

@Prakharkarsh1
Hello,
Do you still want to contribute to this feature?

Released https://github.com/cybozu-go/moco/releases/tag/v0.16.1


Split servicebus component into three separate components

The current implementation uses the same component for all the topics so I believe that, even though we have a "slow" channel its connection is shared with the "rapid" channel, connectivity issues due to idle components would not manifest themselves in the current state.
Issue reference
This change aims to catch behavior where idle connections misbehave and lead to problems (potential cause of dapr/dapr#5621)

/cc @halspang


Expose camera-defined per-channel white level

This PR exposes the libraw_colordata_t::linear_max vector as RawPy.camera_white_level_per_channel. This property might be useful for rectifying magenta highlights when demosaicking (see #100) by setting a custom saturation level. Following the conversation with the author of LibRaw, we should be able to resolve the pink sky issue like so:
with imread("/path/to/raw.CR2") as raw:
    # Compute the saturation level
    black_level = np.array(raw.black_level_per_channel)
    white_level = np.array(raw.camera_white_level_per_channel)
    saturation_level = (white_level - black_level).min() # To be safe, use min
    # Demosaic
    rgb = raw.postprocess(
        no_auto_bright=True,
        user_sat=saturation_level,
        highlight_mode=HighlightMode.Clip,
    )

Can you edit the PR description and show some sample code on how to use the new field for your scenario?
Side note: It looks like libraw doesn't use linear_max for its own postprocessing. Wouldn't it make more sense to fix your specific pink-sky issue by fixing libraw so that every downstream consumer benefits from it? As you mentioned in https://www.libraw.org/node/2605 other softwares can do it correctly, so why not libraw?

Can you edit the PR description and show some sample code on how to use the new field for your scenario?

Updated the first post.

Side note: It looks like libraw doesn't use linear_max for its own postprocessing. Wouldn't it make more sense to fix your specific pink-sky issue by fixing libraw so that every downstream consumer benefits from it? As you mentioned in https://www.libraw.org/node/2605 other softwares can do it correctly, so why not libraw?

A few things:

I'm only just figuring this out in fact. I haven't implemented it just yet in my project, because I have to test it out on a variety of RAW images to ensure that it's a proper fix and not a workaround.
Following from the above point, I'm concerned about the actual coverage of the property. I don't yet know how common the property is across DSLR's.
Once we have a pretty good sense of how common it is, I'll propose using the value to Alex (LibRaw author), or at least mentioning it in the docs somewhere.

For some context, at Homedeck we're building an automated image editing solution for professional photography. We've built our entire editing pipeline around raster image formats, but photographers use RAW's and we'd like to free them of the hassle of converting to JPEG in ACR or some other processor. And as simple as "convert a RAW to a JPEG" sounds, we've seen--with tons of hair pulling and incredible frustration--that it's pretty complicated. But ups to you and Alex for building these solutions.

Thanks for the details. Given that all other rawpy properties always return a useable value (either computed or from camera metadata), this one stands out a bit and I have the fear that people start using it because it worked for a couple of images but then don't consider the zero case and therefore introduce hard-to-find bugs in their code. In general, rawpy tries to expose the nice/sensible bits of libraw only, just to keep it simple. My suggestion would be that you experiment with for a while until we're comfortable it's the right thing to do. The CI wheels should be enough to do all necessary tests.

Also, what does this give you that already exposed white_level (colordata.maximum) doesn't?
IMHO, the LibRaw documentation is a bit misleading... white_level (colordata.maximum) is not AFAIK calculated from data, but form data bit width. So if you have a 14-bit ADC on the sensor of your camera and no hard-coded white level for the specific camera model, the resulting white_level will be always be 2^14-1=16383, not what max you happen to have in the particular raw data frame (you have colordata.data_maximum for that). That's how much I managed to gather form LibRaw source, but I might be wrong as well...
Relying on colordata.linear_max could be risky as it clearly states that they will be set to 0 if not present in the metadata...

Thanks for the details. Given that all other rawpy properties always return a useable value (either computed or from camera metadata), this one stands out a bit and I have the fear that people start using it because it worked for a couple of images but then don't consider the zero case and therefore introduce hard-to-find bugs in their code.

This is fair. I'll get back to you on coverage once we have a good amount of folks test it out with their cameras.

Also, what does this give you that already exposed white_level (colordata.maximum) doesn't?

The libraw_colordata_t::maximum property seems erroneous, at least on the Canon camera we've tested on so far. Setting the saturation level to this value still produces overflow, creating pink highlights. The linear_max property from this same camera doesn't. The value it reports is less than that of maximum. We're seeing a similar phenomenon on a Sony DSLR.

IMHO, the LibRaw documentation is a bit misleading... white_level (colordata.maximum) is not AFAIK calculated from data, but from data bit width. So if you have a 14-bit ADC on the sensor of your camera and no hard-coded white level for the specific camera model, the resulting white_level will be always be 2^14-1=16383, not what max you happen to have in the particular raw data frame (you have colordata.data_maximum for that). That's how much I managed to gather form LibRaw source, but I might be wrong as well...

I haven't yet looked through LibRaw's sources, but I wouldn't be surprised by this.

Relying on colordata.linear_max could be risky as it clearly states that they will be set to 0 if not present in the metadata, and I'm not sure how many cameras actually supply this...

Yup, and that's what we wanna test out. We're gonna see the coverage of the property, whether it's commonly included or not. In our code, if the values are all zeros, we fall back to the maximum. This heuristic works for the Sony (both linear_max and maximum report similar values) and the Canon (linear_max reports a correct value for the saturation level, but maximum reports a wrong value). I wonder how Darktable and RawTherapee handle it, because they both do the correct thing. Will inspect the sources today or tomorrow.

I wonder how Darktable and RawTherapee handle it, because they both do the correct thing.

They get camera specific model white level values (e.g. Canons) from the hard-coded lists they maintain individually. For darktable this is in librawspeed's https://github.com/darktable-org/rawspeed/blob/develop/data/cameras.xml and for RT it is in https://github.com/Beep6581/RawTherapee/blob/dev/rtengine/camconst.json
I haven't looked into where LibRaw keeps this info and how up date is it, so it's possible it's missing for the models you're having trouble with...

It seems they're here: https://github.com/LibRaw/LibRaw/blob/master/src/tables/colordata.cpp

If tested for enough cameras, and idea might be to recode 'white_level' to return the min of colordata.maximum and colordata.linear_max[] if it exists?

@kmilos hey Milos thanks for pinpointing these. I'm still a bit confused by those values stored. I should preface this with a disclaimer: I'm not familiar with the intricacies of working with RAW files; I only just got into the weeds this past weekend.
The values reported by LibRaw are indeed hard-coded, and the value reported for one of our test cameras reflects this. The problem is that unless I'm missing something terribly obvious, the value is wrong. I've been testing some exposures and setting the saturation level (in LibRaw's dcraw_emu) to white_level - black_level still produces blown-out highlights.
Interestingly, Darktable's per-ISO saturation level would actually produce the correct value. And the same goes for RawTherapee's. This would indicate that LibRaw's values are substantially lacking.

If tested for enough cameras, an idea might be to recode 'white_level' to return the min of colordata.maximum and colordata.linear_max[] if it exists?

I agree with this. At @homedeck, we built a lightweight proof of concept to optimize TCA values then cache them in a publicly available Firebase database. I can imagine building a similar system for this, once we're able to verify how much coverage to expect from linear_max.
On a final note, @kmilos and @letmaik thank you both so much. This has been incredibly helpful.

Btw, I created an issue over on LibRaw.

Just a side note, @olokobayusuf I'm sure you're aware but just in case, lensfun has a database of cameras and lenses partially filled with TCA calibrations as well: https://wilson.bronger.org/lensfun_coverage.html. Unfortunately that project has stalled though.

Just a side note, @olokobayusuf I'm sure you're aware but just in case, lensfun has a database of cameras and lenses partially filled with TCA calibrations as well: https://wilson.bronger.org/lensfun_coverage.html. Unfortunately that project has stalled though.

Yup that's why we started working on our implementation. There's a bunch of useful resources scattered online on the topic. Our proof of concept runs an optimization using a quadratic radial (un)distortion model, then saves the computed coefficients in the cloud. The optimization does take quite some time even on CUDA, but once we have the values we can pull them without recomputing. So far the approach doesn't work too well, likely because our objective function is pretty naive. But it's one of the next things on my plate.

The values reported by LibRaw are indeed hard-coded, and the value reported for one of our test cameras reflects this. The problem is that unless I'm missing something terribly obvious, the value is wrong. I've been testing some exposures and setting the saturation level (in LibRaw's dcraw_emu) to white_level - black_level still produces blown-out highlights.

For this particular Canon 5D Mark III example, the LibRaw/rawpy constant white level of 15488 (0x3c80) is "wrong" some of the time indeed. From RT and dt tables, it seems it can be as low as approx. 13200 for ISO 160, 320. etc. (note these are not "prime" ISOs and likely use a multi-stage amplifier in the ADC, hence the different behaviour of the sensor in those modes). For "main" ISO cases it's approximately correct (RT and dt seem to think 15180-15200 for ISO 100). For fun, you can identify these multi-stage ADC cameras from the kinks in the dynamic range and read noise charts here.
As there's no obvious way of measuring and managing this across all camera vendors (and don't think LibRaw devs rightly want to maintain metadata for all the possibilities as they focus on decoding raws, not processing quality), I'm now inclined to support your original intention to expose linear_max[] (maybe as None in python rather than array of 0's if the data doesn't exist?) separate to white_level (maximum). Even if "wrong", it is useful to know white_level because that is used by default in postprocess() (and LibRaw internals) for scaling and explains the output value range if not other options are set. The advanced user then has the responsibility to adjust user_sat given these two pieces of info.

For this particular Canon 5D Mark III example, the LibRaw/rawpy constant white level of 15488 (0x3c80) is "wrong" some of the time indeed. From RT and dt tables, it seems it can be as low as approx. 13200 for ISO 160, 320. etc. (note these are not "prime" ISOs and likely use a multi-stage amplifier in the ADC, hence the different behaviour of the sensor in those modes). For "main" ISO cases it's approximately correct (RT and dt seem to think 15180-15200 for ISO 100). For fun, you can identify these multi-stage ADC cameras from the kinks in the dynamic range and read noise charts here.

I presume this is your area of research. I'm only vaguely familiar with how the camera sensors themselves work, but both links are incredibly useful.

As there's no obvious way of measuring and managing this across all camera vendors (and don't think LibRaw devs rightly want to maintain metadata for all the possibilities as they focus on decoding raws, not processing quality), I'm now inclined to support your original intention to expose linear_max[]

While this is likely @letmaik 's final decision, we're only going to begin testing on a wider range of user cameras tomorrow at Homedeck. I'm wanting to go through a handful of these to get a good sense of how common the metadata is. But so far from inspecting the LibRaw sources, I would expect it to have very high coverage. LibRAW reads the value from MakerNote tags in the RAW's EXIF metadata, which in my experience are typically abundant.

I'm now inclined to support your original intention to expose linear_max[] (perhaps as more pythonic None rather than array of 0's if the data doesn't exist?) separate to white_level (maximum). Even if "wrong", it is useful to know white_level because that is used by default in postprocess() (and LibRaw internals) for scaling and explains the output value range if no other options are set. The advanced user then has the responsibility to adjust user_sat given these two pieces of info.

I totally agree with this. Currently, here's what we have:
white_level = array(raw.camera_white_level_per_channel).min()
saturation_level = raw.white_level if white_level == 0 else white_level

This seems like a popular topic lately ;)
https://www.libraw.org/node/2620

@kmilos @letmaik sorry for the radio silence on this PR; I've been so swarmed with other work. At @homedeck we eventually decided to drop support for RAW files entirely; processing them ended up being too much of a hassle, especially since we've developed learning algorithms that completely remove the need for RAW data. I've updated the docstrings as we discussed above. Pending CI builds, I think this PR is ready to merge.

Looks like the Windows build failed for Python 3.6:
Exception: D:\a\rawpy\rawpy\.github\scripts\build-windows.ps1:16
Line |
  16 |          throw ("ERROR exit code $lastexitcode")
     |          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | ERROR exit code 1

@olokobayusuf Regarding CI failure, I filed a bug... https://github.com/AnacondaRecipes/tifffile-feedstock/issues/1

Thanks for merging @letmaik


simplefs: no error when getting sync config for non-existent TLF

The test is kind of useless but it still seemed like a nice reminder that we should handle this case.

We might not go with this PR, and just handle the existing error in the GUI.  So I'll remove the reviewers for now.


Build failing on Windows

Hello, I'm trying to install hie with stack ./install.hs hie-8.8.3 and the build fails every time. FYI this is in a short path (C:\hie) and I have also enabled Win32 long paths.
Here is the full output:
PS C:\hie> stack install.hs hie-8.8.3
# stack (for check)
# git (for submodules)
# git (for submodules)
Options:
    Verbosity level: Info
# stack (for hie-8.8.3)
Linking C:\\sr\\setup-exe-cache\\x86_64-windows\\tmp-Cabal-simple_Z6RU0evB_<IP_ADDRESS>_ghc-8.8.3.exe ...

Access violation in generated code when writing 0x0

 Attempting to reconstruct a stack trace...

   Frame        Code address
 * 0x461da80    0x37f7b66 C:\Users\chuan\AppData\Local\Programs\stack\x86_64-windows\ghc-8.8.3\bin\ghc.exe+0x33f7b66
 * 0x461da88    0x3277bb9 C:\Users\chuan\AppData\Local\Programs\stack\x86_64-windows\ghc-8.8.3\bin\ghc.exe+0x2e77bb9
 * 0x461da90    0x3
 * 0x461da98    0x69a2db1
 * 0x461daa0    0x3d80c90 C:\Users\chuan\AppData\Local\Programs\stack\x86_64-windows\ghc-8.8.3\bin\ghc.exe+0x3980c90
 * 0x461daa8    0x76e6c30

--  While building simple Setup.hs using:
      C:\Users\chuan\AppData\Local\Programs\stack\x86_64-windows\ghc-8.8.3\bin\ghc-8.8.3.EXE -rtsopts -threaded -clear-package-db -global-package-db -hide-all-packages -package base -main-is StackSetupShim.mainOverride -package Cabal-<IP_ADDRESS> C:\sr\setup-exe-src\setup-Z6RU0evB.hs C:\sr\setup-exe-src\setup-shim-Z6RU0evB.hs -o C:\sr\setup-exe-cache\x86_64-windows\tmp-Cabal-simple_Z6RU0evB_<IP_ADDRESS>_ghc-8.8.3.exe
    Process exited with code: ExitFailure 11

********************************************************************************
Building failed, Try running `stack clean` and restart the build
If this does not work, open an issue at
        https://github.com/haskell/haskell-ide-engine
********************************************************************************

Error when running Shake build system:
  at want, called at src\Development\Shake\Internal\Args.hs:83:69 in shake-0.18.5-7VS8ovPeUeSCopHgkQQ1Vu:Development.Shake.Internal.Args
* Depends on: hie-8.8.3
  at command, called at src\\Stack.hs:80:3 in hie-install-<IP_ADDRESS>-92nHWHZTzvm7FeYed5xR9u:Stack
* Raised the exception:
Development.Shake.command, system command failed
Command line: stack --stack-yaml=stack-8.8.3.yaml install --verbosity=info
Exit code: 1
Stderr:
Linking C:\\sr\\setup-exe-cache\\x86_64-windows\\tmp-Cabal-simple_Z6RU0evB_<IP_ADDRESS>_ghc-8.8.3.exe ...

Access violation in generated code when writing 0x0

 Attempting to reconstruct a stack trace...

   Frame        Code address
 * 0x461da80    0x37f7b66 C:\Users\chuan\AppData\Local\Programs\stack\x86_64-windows\ghc-8.8.3\bin\ghc.exe+0x33f7b66
 * 0x461da88    0x3277bb9 C:\Users\chuan\AppData\Local\Programs\stack\x86_64-windows\ghc-8.8.3\bin\ghc.exe+0x2e77bb9
 * 0x461da90    0x3
 * 0x461da98    0x69a2db1
 * 0x461daa0    0x3d80c90 C:\Users\chuan\AppData\Local\Programs\stack\x86_64-windows\ghc-8.8.3\bin\ghc.exe+0x3980c90
 * 0x461daa8    0x76e6c30

--  While building simple Setup.hs using:
      C:\Users\chuan\AppData\Local\Programs\stack\x86_64-windows\ghc-8.8.3\bin\ghc-8.8.3.EXE -rtsopts -threaded -clear-package-db -global-package-db -hide-all-packages -package base -main-is StackSetupShim.mainOverride -package Cabal-<IP_ADDRESS> C:\sr\setup-exe-src\setup-Z6RU0evB.hs C:\sr\setup-exe-src\setup-shim-Z6RU0evB.hs -o C:\sr\setup-exe-cache\x86_64-windows\tmp-Cabal-simple_Z6RU0evB_<IP_ADDRESS>_ghc-8.8.3.exe
    Process exited with code: ExitFailure 11

I have also followed the advice in the error message and ran stack clean before rerunning the same command, but it gets the same error.
Also it's worth mentioning, stack and git are on my PATH, as is the Stack local bin directory

Hi! i am afraid the error is due a general ghc bug and it is triggered for lot of packages, see for example https://github.com/haskell/haskell-language-server/issues/86
We cant do much things here but suggest some workarounds until a ghc release that fixes it:

build with cabal instead stack
use stack-8.6.5.yaml

I've just seen that the fix for that bug will be backported to ghc.8.8.4, 🎉 : https://gitlab.haskell.org/ghc/ghc/-/merge_requests/3373


MATELCLI does not care for the idea of sending large files.

CLARIFICATION.  The sending of large files is slow.
A relevant portion of the output of time yes | dd if=/dev/stdin of=/dev/stdout bs=8192 count=1024 > /dev/null is as follows:
    0m00.28s real     0m00.29s user     0m00.08s system
A relevant portion of the output of time (yes | dd if=/dev/stdin of=/dev/stdout bs=8192 count=1024 | matelcli send file blah $ROOM) is as follows:
    0m29.38s real     0m00.80s user     0m00.56s system


Indentation in src/train.py

Hi -- I get the following when I run training:
File "src/train.py", line 250
    for i, batch in progress:
                            ^
TabError: inconsistent use of tabs and spaces in indentation

Do you not get this? I have manually standardized the use of tabs/spaces in that file locally so that it runs. Maybe your environment deals with indentation differently. Regardless, was wondering if, to the extent you agree with what I'm seeing, you'd be open to a pull request on this file so it works "out of the box" (e.g. on Colab).
Thanks for any input

It should be fixed now. Let me know if it still doesn't work with you.

Hi, thank you for sharing this repository. I have just begun trying it out, and I think there still may be an indentation error in train.py. The code says (from line 244):
def train_global():
	for epoch in range(opt.epoch, opt.n_epochs):

		losses = {'G': [],'D': []}
		progress = tqdm(enumerate(dataloader),desc='',total=len(dataloader))

	for i, batch in progress:

		# For each target, randomly choose a source for training
		for trg_id in range(opt.n_spkrs):

This way, the first n_epochs-1 only show an empty progress bar, and training seems to only be performed in the last epoch. This is what running train.py looks like when I run it, with default settings:
Namespace(b1=0.5, b2=0.999, batch_size=4, channels=1, checkpoint_interval=1, dataset='../dataset', decay_epoch=50, dim=32, epoch=0, img_height=128, img_width=128, lr=0.0001, model_name='test', n_cpu=8, n_downsample=2, n_epochs=100, n_spkrs=2, plot_interval=-1)
/path_cropped/lib/python3.8/site-packages/torch/optim/adam.py:74: UserWarning: optimizer contains a parameter group with duplicate parameters; in future, this will cause an error; see github.com/pytorch/pytorch/issues/40967 for more information
  super(Adam, self).__init__(params, defaults)
  0%|                                                                                | 0/299 [00:00<?, ?it/s]
  0%|                                                                                | 0/299 [00:00<?, ?it/s]
 ...
  0%|                                                                                | 0/299 [00:00<?, ?it/s]
  0%|                                                                                | 0/299 [00:00<?, ?it/s]
  0%|                                                                                | 0/299 [00:00<?, ?it/s]
[Epoch 99/100] [D loss:<PHONE_NUMBER>94] [G loss:<PHONE_NUMBER>00] : 100%|██████████████████████████████████████████████████████| 299/299 [02:15<00:00,  2.21it/s]

I've cropped the printout, for obvious reasons. Also, weights for only the last epoch are saved.
I believe that the code from for i, batch in progress: (line 250) until the end of the function ought to be indented one step. Doing so, training seems to work, although I get ever increasing loss:
[Epoch 0/100] [D loss:<PHONE_NUMBER>23] [G loss:<PHONE_NUMBER>44] : 100%|███████████████████████████████████████████████████████| 299/299 [02:07<00:00,  2.34it/s]
[Epoch 1/100] [D loss: 9796634.948892] [G loss: 52316289.617057] : 100%|████████████████████████████████████████████████████| 299/299 [02:08<00:00,  2.33it/s]
[Epoch 2/100] [D loss: 79114831.829431] [G loss: 421571117.859532] : 100%|██████████████████████████████████████████████████| 299/299 [02:08<00:00,  2.33it/s]
[Epoch 3/100] [D loss: 298369365.244147] [G loss:<PHONE_NUMBER>.010033] : 100%|████████████████████████████████████████████████| 299/299 [02:08<00:00,  2.33it/s]
[Epoch 4/100] [D loss: 764677369.311037] [G loss:<PHONE_NUMBER>.110368] : 100%|████████████████████████████████████████████████| 299/299 [02:07<00:00,  2.34it/s]
[Epoch 5/100] [D loss:<PHONE_NUMBER>.852843] [G loss:<PHONE_NUMBER>.749165] : 100%|███████████████████████████████████████████████| 299/299 [02:08<00:00,  2.33it/s]
[Epoch 6/100] [D loss:<PHONE_NUMBER>.153846] [G loss:<PHONE_NUMBER>5.264214] : 100%|██████████████████████████████████████████████| 299/299 [02:07<00:00,  2.35it/s]

But this is perhaps a different problem?

put the second for loop under the first for loop
def train_global():
	for epoch in range(opt.epoch, opt.n_epochs):

		losses = {'G': [],'D': []}
		progress = tqdm(enumerate(dataloader),desc='',total=len(dataloader))

	    for i, batch in progress:

		    # For each target, randomly choose a source for training
		    for trg_id in range(opt.n_spkrs):


TCP logs do not show updated request.uri

Summary
I am developing a custom plugin which is modifying the uri of an API like this - ngx.req.set_uri(newUri).
For instance, my API is configured as below :
{   "http_if_terminated": true,   "strip_uri": true,   "retries": 5,   "preserve_host": false,   "created_at":<PHONE_NUMBER>825,   "upstream_connect_timeout": 60000,   "upstream_url": "http://localhost:8080",   "uris": [     "/testapi/points/some_id/accumulation"   ],  ... }
In my plugin source code, I modify the uri ngx.req.set_uri("/testapi/points/123456/accumulation")
ngx.var.request_uri still shows /testapi/points/some_id/accumulation, but if I print out ngx.var.uri it shows /testapi/points/123456/accumulation
Infact, Kong is redirecting to the modified url, but this is not getting reflected in the tcp-logs. In the tcp-log plugin, request information is generated like
https://github.com/Mashape/kong/blob/master/kong/plugins/log-serializers/basic.lua
line 17
request = {       uri = ngx.var.request_uri,       request_uri = ngx.var.scheme.."://"..ngx.var.host..":"..ngx.var.server_port..ngx.var.request_uri,      ...     }
But while routing, you are using https://github.com/Mashape/kong/blob/fc70be2cf67a0d0edd05c0a14134b1d02bfeae68/kong/core/router.lua
line 619
local uri  = ngx.var.uri
Hence, while viewing the tcp logs on Kibana, request.uri still shows the old uri.
I think using ngx.var.uri would be more appropriate as ngx.var.request_uri shows the original uri always.
Additional Details & Logs

Kong version ($ kong version) : 0.10.0
Kong debug-level startup logs ($ kong start --vv)
Kong error logs (<KONG_PREFIX>/logs/error.log)
Kong configuration (registered APIs/Plugins & configuration file)
Operating System

I think using ngx.var.uri would be more appropriate as ngx.var.request_uri shows the original uri always.

Maybe we should show both to avoid confusion.

(This is labelled as a beginners issue but being worked on in #2445)

Oops, didn't mean to close

Closing this as we now have merged #2445 and scheduled it for our next major release. Thanks again for your contribution @shiprabehera! :grin:

Thanks for merging it @thibaultcha


Beekeeper linter code review highlights wrong lines of code

The code reviews in This pull request all point to the wrong lines.

Wrong repository 😨


Do it support swift in iOS?

The cordova plugin supports iOS of course. https://github.com/Telerik-Verified-Plugins/NativePageTransitions


TS5095 error when building

I'm getting this error when I build my local graphclient package:
Failed to generate the schema Error: Failed to fetch introspection from https://api.thegraph.com/subgraphs/name/graphprotocol/compound-v2: error TS5095: Option 'preserveValueImports' can only be used when 'module' is set to 'es2015' or later.

What am I missing in my Vue 3 / Apollo 3 / TypeScript implementation? The react example with the same graph client config and example query compiles just fine so that leads me to believe it might be a tsconfig misconfiguration, but I can't seem to nail it down. Any help would be much appreciated, thank you!

My repository: https://github.com/datanexus-vincent/graph-client-vue3-apollo-example
Full debug log:
yarn run v1.22.15
$ graphclient build
💡 GraphClient Cleaning existing artifacts
💡 GraphClient Reading the configuration
@graphql-tools/load: normalizePointers ./src/queries/example-query.graphql: 0.077ms
@graphql-tools/load: normalizePointers: 0.228ms
@graphql-tools/load: collectDocumentString ./src/queries/example-query.graphql: 0.064ms
@graphql-tools/load: collectSources ./src/queries/example-query.graphql: 0.326ms
@graphql-tools/load: loadFile ./src/queries/example-query.graphql: 10.006ms
@graphql-tools/load: collectFallback ./src/queries/example-query.graphql: 10.225ms
@graphql-tools/load: collectSources queue: 34.474ms
@graphql-tools/load: parseSchema /home/vincenttaglia/WebstormProjects/graph-client-vue3-apollo-example/src/queries/example-query.graphql: 0.014ms
@graphql-tools/load: parseRawSDL /home/vincenttaglia/WebstormProjects/graph-client-vue3-apollo-example/src/queries/example-query.graphql: 0.057ms
@graphql-tools/load: useComments /home/vincenttaglia/WebstormProjects/graph-client-vue3-apollo-example/src/queries/example-query.graphql: 1.309ms
@graphql-tools/load: collectValidSources /home/vincenttaglia/WebstormProjects/graph-client-vue3-apollo-example/src/queries/example-query.graphql: 0.016ms
@graphql-tools/load: parseSource /home/vincenttaglia/WebstormProjects/graph-client-vue3-apollo-example/src/queries/example-query.graphql: 2.087ms
@graphql-tools/load: prepareResult: 0.005ms
@graphql-tools/load: loadTypedefs: 38.218ms
💡 GraphClient Generating the unified schema
🐛 GraphClient - GetMesh Getting subschemas from source handlers
🐛 GraphClient - uniswapv2 Generating the schema
🐛 GraphClient - compoundv2 Generating the schema
💥 GraphClient - compoundv2 Failed to generate the schema Error: Failed to fetch introspection from https://api.thegraph.com/subgraphs/name/graphprotocol/compound-v2: error TS5095: Option 'preserveValueImports' can only be used when 'module' is set to 'es2015' or later.

    at GraphQLHandler.getMeshSource (/home/vincenttaglia/WebstormProjects/graph-client-vue3-apollo-example/node_modules/@graphql-mesh/graphql/cjs/index.js:302:23)
    at async /home/vincenttaglia/WebstormProjects/graph-client-vue3-apollo-example/node_modules/@graphql-mesh/runtime/cjs/get-mesh.js:132:28
💥 GraphClient - uniswapv2 Failed to generate the schema Error: Failed to fetch introspection from https://api.thegraph.com/subgraphs/name/uniswap/uniswap-v2: error TS5095: Option 'preserveValueImports' can only be used when 'module' is set to 'es2015' or later.

    at GraphQLHandler.getMeshSource (/home/vincenttaglia/WebstormProjects/graph-client-vue3-apollo-example/node_modules/@graphql-mesh/graphql/cjs/index.js:302:23)
    at async /home/vincenttaglia/WebstormProjects/graph-client-vue3-apollo-example/node_modules/@graphql-mesh/runtime/cjs/get-mesh.js:132:28
💥 GraphClient Error: Schemas couldn't be generated successfully. Check for the logs by running Mesh.
    at getMesh (/home/vincenttaglia/WebstormProjects/graph-client-vue3-apollo-example/node_modules/@graphql-mesh/runtime/cjs/get-mesh.js:166:15)
    at async Object.handler (/home/vincenttaglia/WebstormProjects/graph-client-vue3-apollo-example/node_modules/@graphql-mesh/cli/cjs/index.js:304:53)
error Command failed with exit code 1.

this subgraph seems to not be returning valid introspection result https://api.thegraph.com/subgraphs/name/graphprotocol/compound-v2

Hey Saihaj, appreciate the response!
Unfortunately, I'm not sure that is the true source of the issue. I copied the .graphclientrc.yml file and the example query from the example project https://github.com/graphprotocol/graph-client/tree/main/examples/apollo which successfully builds the local .graphclient package without any introspection result errors.
From what I can tell the only inputs for building the local .graphclient package are the .graphclientrc.yml file and any query files you have linked in there. Is there anything else I can configure that would give me a different result when using the same .graphclientrc.yml and query files between different projects?

Hey @datanexus-vincent, if I remember correctly, the Compound V2 subgraph was manually enhanced on the hosted service with query-time computation as seen here: https://github.com/graphprotocol/compound-subgraph-wrapper. It might be that this manual change messed up with the schema introspection as @saihaj pointed out. I did not check myself.
I suggest that you use the one developed by Messari here: https://thegraph.com/explorer/subgraphs/6tGbL7WBx287EZwGUvvcQdL6m67JGMJrma3JSTtt5SV7?view=Overview&chain=mainnet
The enhancements done manually on Compound V2 should be reproducible with Graph Client. Let us know if you try to do this and how it goes.

Hey @schmidsi, appreciate you jumping in on this.
I'm actually not even really interested in using the Compound V2 subgraph. I just wanted to create an example Vue 3/Apollo project that I could submit a pull request for so that I and others could better understand how all of these pieces work together, and so I used the same graph client config and example query as the React/Apollo example. But, for some reason, while the local graph client compiles just fine for the React/Apollo example, it doesn't compile with my implementation. At this point, I'm just trying to figure out why a graph client config and example query works in one project and not another.
Here is the debug output of a successful compile for the React/Apollo example in the graph client repo, which uses the exact same graph client config and example query as my example project. Do you have any idea why it might work in one project but not another?
yarn run v1.22.15
$ graphclient build
💡 GraphClient Cleaning existing artifacts
💡 GraphClient Reading the configuration
@graphql-tools/load: normalizePointers ./src/example-query.graphql: 0.087ms
@graphql-tools/load: normalizePointers: 0.255ms
@graphql-tools/load: collectDocumentString ./src/example-query.graphql: 0.066ms
@graphql-tools/load: collectSources ./src/example-query.graphql: 0.3ms
@graphql-tools/load: loadFile ./src/example-query.graphql: 10.733ms
@graphql-tools/load: collectFallback ./src/example-query.graphql: 10.955ms
@graphql-tools/load: collectSources queue: 29.082ms
@graphql-tools/load: parseSchema /home/vincenttaglia/WebstormProjects/graph-client/examples/apollo/src/example-query.graphql: 0.008ms
@graphql-tools/load: parseRawSDL /home/vincenttaglia/WebstormProjects/graph-client/examples/apollo/src/example-query.graphql: 0.067ms
@graphql-tools/load: useComments /home/vincenttaglia/WebstormProjects/graph-client/examples/apollo/src/example-query.graphql: 1.447ms
@graphql-tools/load: collectValidSources /home/vincenttaglia/WebstormProjects/graph-client/examples/apollo/src/example-query.graphql: 0.017ms
@graphql-tools/load: parseSource /home/vincenttaglia/WebstormProjects/graph-client/examples/apollo/src/example-query.graphql: 2.117ms
@graphql-tools/load: prepareResult: 0.005ms
@graphql-tools/load: loadTypedefs: 32.678ms
💡 GraphClient Generating the unified schema
🐛 GraphClient - GetMesh Getting subschemas from source handlers
🐛 GraphClient - uniswapv2 Generating the schema
🐛 GraphClient - compoundv2 Generating the schema
🐛 GraphClient - uniswapv2 The schema has been generated successfully
🐛 GraphClient - uniswapv2 Analyzing transforms
🐛 GraphClient - compoundv2 The schema has been generated successfully
🐛 GraphClient - compoundv2 Analyzing transforms
🐛 GraphClient - GetMesh Schemas have been generated by the source handlers
🐛 GraphClient - GetMesh Merging schemas using the defined merging strategy.
🐛 GraphClient - stitchingMerger Stitching directives are being generated
🐛 GraphClient - stitchingMerger Checking if any of sources has federation metadata
🐛 GraphClient - stitchingMerger Stitching the source schemas
🐛 GraphClient - stitchingMerger sourceMap is being generated and attached to the unified schema
Transformed schema is not set yet. Returning a dummy one.
💡 GraphClient Generating artifacts
💡 GraphClient Generating index file in TypeScript
💡 GraphClient Writing index.ts for ESM to the disk.
💡 GraphClient Cleanup
💡 GraphClient Done! => /home/vincenttaglia/WebstormProjects/graph-client/examples/apollo/.graphclient
Done in 3.91s.


To include the forwarding EmbeddingStatusNotification in the CONFIG file

For the /v1/notify-embedding-status-changes API , there is a callback EmbeddingStatusNotification specified in the OAS.
But , there is no forwarding defined for this callback in the CONFIG file.
Proposal :
kindly please consider the following proposal ,
Shall we include a callback EmbeddingStatusNotification in the CONFIG.json , forwarding.yaml
- forwarding-name: EmbeddingStatusNotification
    management-requests:
      operation-client-update:
        - server-name: /v1/notify-embedding-status-changes
          uuid: ro-2-1-0-op-s-is-013
    initiating-requests:
      - server-name: /v1/regard-updated-approval-status
        uuid: ro-2-1-0-op-s-is-003
    consequent-requests:
      - client-name: TAR://v1/document-embedding-status
        uuid: ro-2-1-0-op-c-im-tar-2-0-1-007

Forwarding EmbeddingStatusNotification added to ForwardingList and CONFIGfile.


menu position, sorry i copied from material 1, was wrong question

Actual Behavior:

What is the issue? *

WIth static menu position works, with dynamic position not working.
<md-menu [y-position]="yPosition" x-position="before" #menuTheme="mdMenu">
            <cory-mat-theme-menu></cory-mat-theme-menu>
        </md-menu>

export class ThemeButton {

    @Input('cory-y-position')
    yPosition: MenuPositionY = 'below';

Can't bind to 'y-position' since it isn't a known property of 'md-menu'.
1. If 'md-menu' is an Angular component and it has 'y-position' input, then verify that it is part of this module.

What is the expected behavior?

dynamic position
CodePen (or steps to reproduce the issue): *

CodePen Demo which shows your issue:
Details:
Simple, y-position not working with a dynamic directive

AngularJS Versions: *

AngularJS Version:
AngularJS Material Version:
latest

Additional Information:

Browser Type: *
Browser Version: *
OS: *
Stack Traces:
all

Shortcut to create a new CodePen Demo.
Note: * indicates required information. Without this information, your issue may be auto-closed.

Do not modify the titles or questions. Simply add your responses to the ends of the questions.
Add more lines if needed.

See #4169


CRUD Modules Generator Module Naming Policy

I improperly used a capitalized name as the module name in the command (php artisan twill:module Posts), and met the error of

Route [admin.posts.index] not defined.

It looks like the generator created Posts folders under views.admin
To avoid this kind of error,
I think maybe a detail naming spec documentation and further validation is needed for the CRUD module generate command:
php artisan twill:module yourPluralModuleName .
another approach is to convert the module name received directly to an appropriate name.

Definitely @yanhao-li. I agree just saying yourPluralModuleName as an example of using the CLI can be quite confusing, and the CLI output is not helping either.
Considering that Laravel relies heavily on pluralization, we should convert the input, I'm with you!

Sounds like in this case, capitalization – not pluralization – is what caused this error.
Casting to camel case as a first step might help when the module name is provided in pascal case.
That said, I've run into errors due to providing a singular module name before. It'd be great if it could accept both singular and plural module names as arguments. I'd love it if this:
php artisan twill:module yourPluralModuleName

...and this...
php artisan twill:module yourSingularModuleName

...both produced the same result.
For example, it should pluralize the module name when generating its table (e.g. lightboxes).
I believe it already singularizes the module's name when generating related tables:
https://github.com/area17/twill/blob/bd84f41/src/Commands/ModuleMake.php#L98-L102
https://github.com/area17/twill/blob/16ec480/src/Commands/stubs/migration.stub#L30-L46

@IllyaMoskvin exactly, I'm preparing a fix on my fork, should create a pull request shortly once I'm done.

Just wanted to mention that I also had problems with underscore and pluralization with other languages than english.
In german sonderangebote is plural and I got an error when I migrated, because somewhere the logic appended an 's' to the name. Then I switchted to the english translation special_offers. Migration did work, but later I got a problems with a dependency (somehow the underscore broke when importing special_offersRepository).
It may be the case that there is well-known naming convention for tables, but I did not know of it until now. I think some clarification in the documentation would help future Twill users very much.

This PR should be able to fix it.
Close the issue.


Alphabetize and group resources in importer README

Let me fix the code backticks

Would it be better to just alphabetize all resources?


[Gally]: master <- dev

Automatically created by Git-Ally

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Quiet the watchdog on the first run

Prevents:
[23:28:04] [Server thread/INFO]: Done (10.520s)! For help, type "help" or "?"
[23:28:04] [Server Watchdog/FATAL]: A single server tick took 71.62 seconds (should be max 0.05)
[23:28:04] [Server Watchdog/FATAL]: Considering it to be crashed, server will forcibly shutdown.
[23:28:04] [Server Watchdog/ERROR]: This crash report has been saved to: /home/github/SpongePowered/SpongeForge/run/./crash-reports/crash-2015-12-30_23.28.04-server.txt
[23:28:06] [Server thread/WARN]: Can't keep up! Did the system time change, or is the server overloaded? Running 2034ms behind, skipping 40 tick(s)

If this happens on forge I think it would be useful to patch it on forge too


Update SDK dependency to 10.2.6-2

We have provided updates to our ArcGIS Android SDK, current version is 10.2.6-2.  We need to update our samples to pull from the latest SDK version.

Verified fixed


[Hardware][Intel] Optimize CPU backend and add more performance tips

This PR optimized CPU backend performance and added more performance tips.

Optimized input shape of torch_sdpa to use fast code path for better TTFT (~40% reduction).
Added tip and example to use TCMalloc, it will significantly improve the performance.
Initially integrated Paged attention from Intel Extension for PyTorch.
Updated related doc.

 PR Checklist (Click to Expand)
Thank you for your contribution to vLLM! Before submitting the pull request, please ensure the PR meets the following criteria. This helps vLLM maintain the code quality and improve the efficiency of the review process.
PR Title and Classification
Only specific types of PRs will be reviewed. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:

[Bugfix] for bug fixes.
[CI/Build] for build or continuous integration improvements.
[Doc] for documentation fixes and improvements.
[Model] for adding a new model or improving an existing model. Model name should appear in the title.
[Frontend] For changes on the vLLM frontend (e.g., OpenAI API server, LLM class, etc.)
[Kernel] for changes affecting CUDA kernels or other compute kernels.
[Core] for changes in the core vLLM logic (e.g., LLMEngine, AsyncLLMEngine, Scheduler, etc.)
[Hardware][Vendor] for hardware-specific changes. Vendor name should appear in the prefix (e.g., [Hardware][AMD]).
[Misc] for PRs that do not fit the above categories. Please use this sparingly.

Note: If the PR spans more than one category, please include all relevant prefixes.
Code Quality
The PR need to meet the following code quality standards:

We adhere to Google Python style guide and Google C++ style guide.
Pass all linter checks. Please use format.sh to format your code.
The code need to be well-documented to ensure future contributors can easily understand the code.
Include sufficient tests to ensure the project to stay correct and robust. This includes both unit tests and integration tests.
Please add documentation to docs/source/ if the PR modifies the user-facing behaviors of vLLM. It helps vLLM user understand and utilize the new features or changes.

Notes for Large Changes
Please keep the changes as concise as possible. For major architectural changes (>500 LOC excluding kernel/data/config/test), we would expect a GitHub issue (RFC) discussing the technical design and justification. Otherwise, we will tag it with rfc-required and might not go through the PR.
What to Expect for the Reviews
The goal of the vLLM team is to be a transparent reviewing machine. We would like to make the review process transparent and efficient and make sure no contributor feel confused or frustrated. However, the vLLM team is small, so we need to prioritize some PRs over others. Here is what you can expect from the review process:

 After the PR is submitted, the PR will be assigned to a reviewer. Every reviewer will pick up the PRs based on their expertise and availability.
 After the PR is assigned, the reviewer will provide status update every 2-3 days. If the PR is not reviewed within 7 days, please feel free to ping the reviewer or the vLLM team.
 After the review, the reviewer will put an  action-required label on the PR if there are changes required. The contributor should address the comments and ping the reviewer to re-review the PR.
 Please respond to all comments within a reasonable time frame. If a comment isn't clear or you disagree with a suggestion, feel free to ask for clarification or discuss the suggestion.

Thank You
 Finally, thank you for taking the time to read these guidelines and for your interest in contributing to vLLM. Your contributions make vLLM a great tool for everyone!

@WoosukKwon Hi, gentle ping, could you please help to take a look on this patch when available? This patch has a big optimization for CPU backend
thanks, -yuan

@WoosukKwon thank you for the review and merge, much appreciated!
thanks, -yuan

Hi @bigPYJ1151 , I tested the IPEX but seems no performance gain on CPU.
Could you please tell us how can we test for the performance boost?
Thanks.


Inplement in codes is different with paper, and I think it's not a graph convolution.

What is implemented in 'GraphConvolutionalLayer.py' is not a graph convolution, I think it's just a mapping with a matrix. And what confuses me most is that each node of the result in the code is not related to any other nodes in a sentence. Where am I wrong? Thanks a lot.

And I also have a question: there is an adjacency matrix in the common GCN, but here there is not this matrix, instead, there is a mask, but what the mask does is just a 'multiply' operation element-wise not a matrix multiply in the common GCN. Any ideas? Thanks!


feat(merge-tree): add SequencePlace to the merge-tree package

In preparation for allowing range expansion on obliterate, add the SequencePlace and Side concepts to merge tree (instead of only using them in sequence). Eventually, I'd like to have these defined in one place that can be accessed by both packages, but they are currently exposed as a part of sequence's public API, so this would be a breaking change.
AB#9064

In preparation for allowing range expansion on obliterate, add the SequencePlace and Side concepts to merge tree (instead of only using them in sequence). Eventually, I'd like to have these defined in one place that can be accessed by both packages, but they are currently exposed as a part of sequence's public API, so this would be a breaking change.

Are these new types and the existing types in sequence structurally identical? If so, it would be safe to move them into merge-tree, and re-export them from sequence.


JBPM-4934 AuditService obtained from RuntimeEngine doesn't work with Local transacations

Can one of the admins verify this PR? Comment with 'ok to test' to start the build.

Can one of the admins verify this PR? Comment with 'ok to test' to start the build.

ok to test

@agiertli fyi, if you accept the invitation to droolsjbpm org. unit, your PRs will get a test build automatically.

These are the unit tests for the fix which is part of different PR:
https://github.com/droolsjbpm/jbpm/pull/396

The failed tests seems to be unrelated to the code changes done in this PR.

jenkins retest this


Issue 1132: Fix invalid handling of buffers of sequence copies

Closes #1132

I have added another case to the allocator (Head attribute on comprehension over sequence field of message) and extended a test case to get full test coverage.


tests: ztest: fix error_hook test case fail in some board

Enlarge the test thread stack size, to fix test case fail
in some board which need more stack size for testing, when
CONFIG_EXCEPTION_DEBUG is enabled.
Signed-off-by: Enjia Mai<EMAIL_ADDRESS>

Hi @nashif,  just corrected it, thanks.


add HyperVGeneation in GetVMImage

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Automation for azure-sdk-for-python

Can one of the admins verify this patch?

Automation for azure-sdk-for-go

@openapibot sdkautomation rebuild

LGTM

LGTM

This property only appears in response body. So we don't need to set it as read-only, right?

Yeah, that's fine. I was asking the question to confirm that this is not a breaking change. Based on your answer (it only shows up on GET responses), it's not a breaking change.


Debug deadlock on a 4-process 2 tps workload

Steps to reproduce
Build the Iroha binary.
cargo build --bin iroha

Create the file target/iroha_client_cli
touch target/iroha_client_cli

Setup bare metal test environment
scripts/test_env.sh setup

checkout the load script
git clone https://github.com/appetrosyan/iroha2-longevity-load-rs/tree/bench_load

Run the test
cargo run -- --tps 10 --accounts 100000000

Expected behaviour

Blocks are produced at a steady rate, with approximately 2-3 blocks per second, each containing 2-4 transactions.
Memory consumption between peers is approximately the same and grows equally across the four peers
Transactions get either committed or rejected and the load script is notified to keep accurate statistics.

Actual behaviour

Blocks stop being produced at approximately the 400 total transactions mark.
One peer can consume 3-4× the memory of the second largest consumer. The longer the load is applied, the bigger the disparity.
Transactions expire in the pipeline. They aren't marked as rejected in the load script, but they can never be committed to a block.

As shown by testing on s1 what we witnessed wasn't a deadlock, but rather low throughput. We will need to revisit this later after the account re-structuring is complete.


flipperzero: Enable Miri to start running the tests

It doesn't successfully run the tests because Miri doesn't yet support FFI, but these changes enable the following command to actually start:
MIRI_NO_STD=1 cargo miri test --target thumbv7em-none-eabihf

Part of flipperzero-rs/flipperzero#100.

Rebased on main.

Force-pushed to address comments.

Rebased on current main.

Pushed a commit to switch to latest nightly for stabilised cfg_target_abi (and fix resulting Clippy lints).


Support private_key_jwt from https://openid.net/specs/openid-connect-core-1_0.html#ClientAuthentication

What version of UAA are you running?
What output do you see from curl <YOUR_UAA>/info -H'Accept: application/json'?

Develop / 76.x.x

How are you deploying the UAA?
I am deploying the UAA

locally only using gradlew
using a bosh release I downloaded from bosh.io
using cf-release
using cf-deployment
as part of a commercial Cloud Foundry distribution
other (please explain)

What did you do?
Authenticate OAuth clients without secrets. Public Flow does not solve all cases, e.g. client_credential or password grant .
Private_key_jwt and https://www.rfc-editor.org/rfc/rfc8705 would solve that issue.
Private_key_jwt is part of OIDC standard , e.g.
https://openid.net/specs/openid-connect-core-1_0.html#ClientAuthentication
And therefore this is Expected to be Part of UAA
What did you expect to see? What goal are you trying to achieve with the UAA?
Private_key_jwt is part of OIDC standard , e.g.
https://openid.net/specs/openid-connect-core-1_0.html#ClientAuthentication
What did you see instead?
secret based authentication only

Was this fixed by #2385?

Was this fixed by #2385?

No but https://github.com/cloudfoundry/uaa/pull/2385 is a preparation for it

Next stepp is, that oauth_client_details table will be extended with client_keys  or client_key_config so that an admin can upload trusted keys. The pure validation is a smaller step.
Tokens with private_key_jwt will have this authentication method in the token.

@Tallicia @bruce-ricard Started to work in this. I created https://github.com/cloudfoundry/uaa/pull/2433 and I would like to discuss with you in next sync about the possible options to add the key configuration into DB table oauth_client_details.

Add an extra column e.g. private_key_jwt_config
Migrate additonal_information into text (to have capacity for it) and add the keys in map additional_information.

If you agree / vote for 1. then this PR https://github.com/cloudfoundry/uaa/pull/2433 is a pre-requisit. We need then to decouple from spring security oauth2 classes

I have added this to the agenda.

Added private_key_jwt into my spring demo app
https://github.com/strehle/spring-openid-client/commit/26a52b809ffd2a5ff3f69c20be930821089c7d09
Works with OIDC providers which support private_key_jwt, tested with Okta, SAP Authentication and MS Azure AD.
Plan: UAA supports this as well......


Services: first build: abs added

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_9fqzgf2vsu/clone/recipe/meta.yaml:1: missing_pip_check: For pypi packages, pip check should be present in the test commands
WARNING: /tmp/abs_9fqzgf2vsu/clone/recipe/meta.yaml:15: avoid_noarch: noarch: python packages should be avoided
ERROR: /tmp/abs_9fqzgf2vsu/clone/recipe/meta.yaml:20: missing_wheel: For pypi packages, wheel should be present in the host section
WARNING: /tmp/abs_9fqzgf2vsu/clone/recipe/meta.yaml:44: missing_doc_source_url: The recipe is missing a doc_source_url
WARNING: /tmp/abs_9fqzgf2vsu/clone/recipe/meta.yaml:44: missing_license_url: The recipe is missing a license_url
Errors were found


Deleted some state from the stateless file, but the generated state code was still there.

Hello,
In StatelessDesigner, I deleted some state from the stateless file, but the generated state code was still there.

@wavebit the generated code is updated when you save the .stateless file


style: ovious code simplification

I've executed all the tests, but the module spring-cloud-function-kotlin always failed when mvn test is launched on spring-cloud-function-parent, but pass when launched individually.
I've adapted some tests to make them more resilient (java vs java.exe), don't know if it's the best way to do it.
The dependency spring-cloud-function-kotlin in module spring-cloud-function-samples seemed incorrect.


Add a Dockerfile for building a kubetop-running Docker container

Fixes #36
Fixes #34 (I think)

Codecov Report

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

@@            Coverage Diff             @@
##           master      #39      +/-   ##
==========================================
+ Coverage   50.92%   51.45%   +0.53%
==========================================
  Files          10       10
  Lines         377      377
  Branches       46       46
==========================================
+ Hits          192      194       +2
+ Misses        181      180       -1
+ Partials        4        3       -1

Impacted Files
Coverage Δ

src/kubetop/_textrenderer.py
82.87% <0%> (+1.36%)
:arrow_up:

Continue to review full report at Codecov.

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


User . Failed to modify the employee ID.

修改员工工号，保存成功。查看已修改的数据，员工工号仍是修改前的数据

Changed the employee ID field in the employee edit page to non-editable

编辑员工无重置密码功能

员工工号不可编辑


Nothing returned to console

When executing any of the examples, nothing is returned back to the console. I would expect to get credential errors or some sort of console log but I am just greeted with the command prompt again. Any help on troubleshooting this problem would be appreciated. I am using node 5.6.0 and npm 3.7.2. Do I need to possibly downgrade my versions? I also forgot to add I know my RETS server is looking for POST request instead of GET. Could this also be the issue?

That is strange.  I generally use node 4.x and npm 2.x, but I just tested with your versions and confirmed the problem does not exist.  (I did, however, find a couple typos in the example code, and have fixed them in latest/v4.0.4.)
It sounds like you're pasting code into the terminal.  Are you returned to the actual command prompt (which generally looks like > ) or do you get the 'waiting for more input' prompt (which generally looks like ... )?  I often find node does not work well when pasting more than a line or two at once.  It is generally better to put code into a file, and then run e.g. node sample_code.js rather than pasting code into the terminal.
If the above doesn't help, try setting the DEBUG environment variable to rets-client:*, and see if you get any logging that way.

I did have my code in a file and executed it with node sample code.js. I cut and pasted the code from the readme, should I cut and paste from another source? Thanks again

That's correct, but I did make a couple changes to the example code in the readme after you opened this issue.  Are you still having the same problem?  If so, please try again after setting DEBUG to rets-client:* and let me know what happens.

Ok thanks I will check it out when I get home and report back

GET vs POST will not cause errors? With Trulia RETS client, libRETS, and PHRETs I have to configure my library to use POST. Is this necessary with rets-client?

ok it looks like the fixed code in the README works now, thanks a lot!

After checking the examples and issuing a query for a property I am greeted with a 404 error, I have looked at the DMQL string in debug and compared it to the one used for Openhouse (Which works fine), I have double checked my fields and suitable values for a query and everything looks fine, it is using a GET request and I think I need it to use a POST request for my Listing class, how can I configure this?

Hmm.  There is currently no way to configure that.
I'll take a look at the RETS standard and see if it says when to use GET versus POST.  If it does, I should be able to change the code behind the scenes to do this properly.  If it doesn't (and it is a server-specific requirement), then I'll have to add a feature to allow selecting the method as an option.  I'll try to get to this soon.

Could I add the parameter method: 'POST' to the request in the base code? If so where would I add this just to verify its my issue?

I think you could change all requests to use POST instead of GET by changing lines 25-27 of retsHttp.js to:
return retsSession.post({
   form: queryOptions
});

But since that's in a helper function used for all requests, I'm not sure a simple change there will work -- that would change all requests to POST, and since some of your queries worked fine (login, Openhouse, maybe some others) they might need to stay with GET.
Even to test whether that's the problem, you'll probably need to add an option so you can specify whether to use the POST code above or the existing:
return retsSession({
   qs: queryOptions
});

Ok thanks I'll give it a try. I think all my queries will work with POST. With other libraries I've configured them to use POST and had no issues.

Great, let me know the results.

Do you have any resources I can look over to implement this library, requesting certain fields, and how to utilize the streams? I'm not a Nodejs or Javascript guru but this seems like the best library for my purposes I have tried so far.
Thanks for the help I was able to get rets-client to submit post requests by modifying lines 67-71 of client.js to look like this
      defaults = {
        jar: request.jar(),
        headers: this.headers,
        method: 'POST'
      };

Ok, thanks for the info, it has been very helpful.
The RETS standard seems to say both GET and POST should be fine, except for update actions which are not possible with rets-client anyway.  So, this seems to be yet another case of "some servers just don't obey the standards".  :-/
Based on your results, I've added a client setting to allow specifying the method (v4.1.0 release).  For backwards compatibility, I'm leaving GET as the default.
As for resources, other than the example code in the README, sorry, no there isn't anything available.  Maybe someday -- I'd be happy to merge any PRs that do improve the documentation.


Could you please explain how does the evaluation work when the grades are taken from two different ranges?

Dear developers,
I'm using your tool to estimate evaluation metrics for information retrieval research and I got a bit stuck with some behaviour, which doesn't look intuitive for me. Could you please help me to figure out what's going on?
Question:
Suppose I have a qrel file, where the grades are all integers and can take the values: {0, 1, 2, 3}. It's an initial qrel file for RelevanceEvaluator.
To evaluate the result I take another file where the grades are float and vary from 0 to 100 - [0, 100]. How does the RelevanceEvaluator behave in that case? Does it use any normalization?

I tried to relabel all {2, 3} values to {1} in the intial qrel file and initialized the  RelevanceEvaluator with such a qrel file with binary grades. And nothing changed... Is it OK?

I used one more run-file for evaluation where grades are float and vary from 0 to 2 - [0, 2] and the results significantly changed with binary initial grades in comparison with {0, 1, 2, 3} initial grades. Why?

Thanks in advance.

The problem has been solved.


fix fix database cannot be chosen bug

Proposed changes
Issue Number: close #32025

Fix database cannot be chosen bug.
Fix UI page always redirects to the login page bug.

run buildall


Given nonce too small.

Hey,
I keep getting that error (given nonce too small, so I used a bigger nonce but still getting that error)
line 36 on code.
private static long GetCurrentUnixTimestampMillis()

Nonce frequency incremented.


Up to date Flutter Bangla course resource

What does this PR do?
Added Bangla flutter full tutorial by Rabbil Hasan
For resources
Rabbil Hasan is one of the best App developer from bangladesh and worked with many internation companies and opened free workshops for new programmer and teaching app development for many yearn through social platform.
Why is this valuable (or not)?
Its rare to have this level flutter course in Bangla .
How do we know it's really free?
Its totally free .Its available on Youtube .
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[ ] Read our contributing guidelines.
[ ] Search for duplicates.
[ ] Include author(s) and platform where appropriate.
[ ] Put lists in alphabetical order, correct spacing.
[ ] Add needed indications (PDF, access notes, under construction).
[ ] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

Thanks, and welcome to free-programming-books!


stripe: Remove invalid comment.

We use error_description in upgrade.ts to determine if the error was related to customer's card. Doesn't seem like there is any harm in doing so since we are explicitly handling "stripe.CardError" and raising these errors with "card error" description.

Merged, after rewriting the second commit, thanks @amanagr!


[bug] fswatcher error when starting z2m

Version
Build/Run method

[x] Docker
[ ] PKG
[ ] Manually built (git clone - npm install - npm run build )

Zwave2Mqtt Docker version: 4.0.1
Describe the bug
When starting the container I get the following error:
z2m     | /usr/src/app/lib/Gateway.js:51
z2m     |         fn()
z2m     |         ^
z2m     |
z2m     | TypeError: fn is not a function
z2m     |     at FSWatcher.<anonymous> (/usr/src/app/lib/Gateway.js:51:9)
z2m     |     at FSWatcher.emit (events.js:315:20)
z2m     |     at FSEvent.FSWatcher._handle.onchange (internal/fs/watchers.js:135:12)

To Reproduce
Steps to reproduce the behavior:

Run the 4.0.1 image with no customDevices file
Observe the container fail with the error

Expected behavior
The container starts with no error
Additional context
This may be related to changes introduced by #670 and #675
Downgrading to 4.0.0 makes it work again.
Cheers,

I'm still seeing this error even when building against master.
 z2m:App Listening on port 44920
/opt/lib/Gateway.js:51
        fn()
        ^

TypeError: fn is not a function
    at FSWatcher.<anonymous> (/opt/lib/Gateway.js:51:9)
    at FSWatcher.emit (events.js:315:20)
    at FSEvent.FSWatcher._handle.onchange (internal/fs/watchers.js:135:12)

For me 4.0.2 fixed this issue. Pulled from docker hub.

Would you mind confirming which SHA you're building? git rev-parse HEAD
Farther down in lib/Gateway.js, there are calls to watch, at lines 106, 107. What do these look like in your copy?
On August 24, 2020 2:08:05 PM UTC, Blake Niemyjski<EMAIL_ADDRESS>wrote:

I'm still seeing this error even when building against master.
z2m:App Listening on port 44920
/opt/lib/Gateway.js:51
       fn()
       ^

TypeError: fn is not a function
   at FSWatcher.<anonymous> (/opt/lib/Gateway.js:51:9)
   at FSWatcher.emit (events.js:315:20)
at FSEvent.FSWatcher._handle.onchange (internal/fs/watchers.js:135:12)

Yep, I think so as well; either docker cache, or maybe forgot to git pull, or other git wackiness. I wanted to confirm & make sure it's not something else, though.

I delete and rebuild the image locally. I'll ensure it's not being cached thanks!


Deferred keys and weakening early error timing

The current proposal as specified treats namespace keys as known at the time of execution deferral so that all instantiation errors have already been thrown, and all async work has been done. All early errors thus happen at "import defer time". And touching the namespace object, ie "namespace evaluation time" only ever gives execution errors.
With the PR in https://github.com/tc39/proposal-defer-import-eval/pull/53 is labelled "Hide .then", it actually does a lot more than this - it makes keys only available after execution.
This late key listing hasn't been explicitly and publicly motivated strongly, and needs to be. As far as I can tell:

There is a desire for keys to be found late because that is the semantics of JS bundling on CommonJS today
There is a hope that late keys might allow defer to also defer named exports validations and instantiation validations

We need to much more clearly dig into these two points above since they are guiding the proposal design right now.
Specifically to delve deeper into (2), this involves a weakening of the design of the spec, where it is potentially entirely a host decision when it gives errors at defer time or at namespace evaluation time, over all of:

Named exports validations
Syntax errors and early errors
Fetch / readfile errors
And potentially even new "found an async module" errors at the namespace evaluation time

Having all of the above errors happen potentially at different times in browsers versus Node.js-like environments seems to me to introduce a little more variation than one would hope for in a standard.
If we are to move in this direction it would help to understand what execution framework it can fit in that isn't just a weakening of existing guarantees.
For this reason I think we need to explicitly call out this change in behaviour of this specification at plenary as a normative change in direction under Stage 2.7.

I think https://github.com/tc39/proposal-defer-import-eval/pull/53 still clearly does not report linking errors "at evaluation", but we could make it clear that they are not deferred by adding a node either in .Link() or in EnsureDeferredNamespaceEvaluation() making it explicit.
In the end we cannot prevent platforms from defining their own types of module records (for example, regardless of this proposal they could define a hypothetical Source Text Metadata Module Record that exports a boolean telling whether there are syntax errors, and a function that when called will either throw those syntax errors or evaluates the module). However, we can make it clear that it's not what the import defer semantics prescribe.

it's worth noting many precompiled environments benefit from the opposite - compile-time evaluation work (eg Fastly's JS SDK).

Last time we talked about this I remember that the conclusion was that for platforms like Fastly's SDK the best approach is to:

first run "normally", skipping deferred modules as other platforms would do
in HostLoadImportedModule, keep track of all the modules that are loaded
once evaluation completes (i.e. before you take the snapshot), iterate through the remaining modules and trigger their evaluation, as if the host was importing them

This keeps the same ordering that import defer currently has in other platforms, while still evaluating everything so that you can cache the partially evaluated state.
This is not affected by any of the proposed changes, right?

The InnerModuleLoading and InnerModuleLinking algorithm are written to recourse into child modules regardless of whether they are deferred or not, so that normatively all errors happening in those two phases are required to be reported eagerly. This is different from InnerModuleEvaluation, which explicitly checks the import phase and branches on it.
An implementation that defers all errors would have to explicitly violate InnerModuleLoading and InnerModuleLinking, adding some checks and early returns that those algorithms do not contain.
At the end of InnerModuleLoading there is now also a note that explicitly points out that there is no special-casing for deferred imports.


Support for cbench via command-line switch

Added -cbench / --cbenchSupport command-line parameters for Floodlight,
making it work with cbench (a dumb OpenFlow switch) without requiring
changes in the code. By default, cbench is not supported.
Class PortSettings was renamed to CmdLineSettings, as it nows handles
not only (openflow and rest) port settings, but rather any command-line
arguments.

Sergio - This got fixed in cbench so it looks like we don't need to add it Floodlight too.  My apologies for suggesting the change -- I didn't realize it was possible to get cbench changed so easily!
Of course, you still get your Floodlight t-shirt though.  I sent you an email about this separately.


Register tracer to GlobalTracer

@jpkrohling had a great question: why the tracer is not registered into GlobalTracer?
At the moment spec only defines that the tracer should be available via CDI. Here is some documentation of GlobalTracer https://github.com/opentracing/opentracing-java/tree/master/opentracing-util#globaltracer
Benefits

implementation of tracer provider could be standardized e.g. smallrye project could provide a basic implementation. The producer would provide GlobalTracer.get() as a bean. Configuration and tracer resolution would still be vendor specific.
GlobalTracer is directly provided by OT API and nicely fits into ecosystem of instrumentations

Drawbacks

TCK injects tracer and invokes methods to get reporterd spans https://github.com/eclipse/microprofile-opentracing/blob/master/tck/src/main/java/org/eclipse/microprofile/opentracing/tck/application/TracerWebService.java#L95 this would not work as global tracer wraps the tracer. unwrap on the tracer should solve this problem https://github.com/opentracing/opentracing-java/issues/282.
as the OT readme say https://github.com/opentracing/opentracing-java#accessing-the-tracer CDI should be a preffered way how the tracer is shared.

The current implementation of the GlobalTracer stores the tracer in a static field, making it tricky to support different concrete tracers for different applications on a single JVM (which is the usual case for application servers).
One possible solution is for runtimes to provide their own tracers and register them with the GlobalTracer. This custom tracer would then retrieve the concrete tracer from, say, the servlet context. This would then require a standard to be set for the servlet context attribute name to store the tracer.


Rootless should inherit init_path from default libpod.conf

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Rootless podman runs do not currently inherit init_path from the default libpod.conf (in /etc or /usr/share or whatever).
Steps to reproduce the issue:

Remove any existing per-user configs/dbs

Update init_path in system libpod.conf

podman run --init -it registry.access.redhat.com/ubi8/ubi-minimal

Describe the results you received:
Error: container-init binary not found on the host: stat /usr/libexec/podman/catatonit: no such file or directory

Output of podman version:
podman version
Version:            1.3.2-dev
RemoteAPI Version:  1
Go Version:         go1.12.3
Built:              Tue May 28 23:29:36 2019
OS/Arch:            linux/amd64

Proposed patch that appears to work for me:
diff --git a/libpod/runtime.go b/libpod/runtime.go
index 1f8dd98b..098607b6 100644
--- a/libpod/runtime.go
+++ b/libpod/runtime.go
@@ -250,6 +250,7 @@ type runtimeConfiguredFrom struct {
    volPathSet            bool
    conmonPath            bool
    conmonEnvVars         bool
+   initPath              bool
    ociRuntimes           bool
    runtimePath           bool
    cniPluginDir          bool
@@ -475,6 +476,9 @@ func newRuntimeFromConfig(ctx context.Context, userConfigPath string, options ..
        if tmpConfig.ConmonEnvVars != nil {
            runtime.configuredFrom.conmonEnvVars = true
        }
+       if tmpConfig.InitPath != "" {
+           runtime.configuredFrom.initPath = true
+       }
        if tmpConfig.OCIRuntimes != nil {
            runtime.configuredFrom.ociRuntimes = true
        }
@@ -512,6 +516,9 @@ func newRuntimeFromConfig(ctx context.Context, userConfigPath string, options ..
            if !runtime.configuredFrom.conmonEnvVars {
                runtime.config.ConmonEnvVars = tmpConfig.ConmonEnvVars
            }
+           if !runtime.configuredFrom.initPath {
+               runtime.config.InitPath = tmpConfig.InitPath
+           }
            if !runtime.configuredFrom.ociRuntimes {
                runtime.config.OCIRuntimes = tmpConfig.OCIRuntimes
            }

Something that may be worth discussing is whether the config layering can be more automatic and not require explicit passthrough like this.

@llchan Please open a PR.

I would love to, esp since the patch is right there, but I'm unfortunately still awaiting legal's sign-off to push :(

the patch LGTM

@giuseppe Could you take the patch and open a PR with it, giving @llchan credit.

I am fine with that.  @llchan is it ok for you?

I just got the green light on this, so I can send up a PR.  Thanks for asking first though!


[Skype, Azure Bot Service] No Skype metrics in the Bot analytics

Hello everybody,
we would like to observe the metrics for our Bot Framework bots in the Microsoft Azure portal. But in the analytics section we can only find metrics for Kik and Telegram. Skype is missing, although there are multiple Skype users.
Any ideas?
Our subscription ID: 4abe19a3-a03b-4c74-9b8b-49878b010bea
Thanks,
Timo

How long did you wait between the users sending messages to your bot and checking the analytics? It takes about a day for this information to be published to the bot, so it may not have propagated by the time you checked. That said, I am confirming if the Skype analytics are accessible myself, and I will have more information on this one way or the other tomorrow.

So I've confirmed that this is recreate-able, could you please send me your botID so we can look into this a bit further?

We are currently looking into the root cause of this, I will update this issue when we find a fix.

Same here, but on Skype for Business, no analytics for this channel

Same issue. No anyltics for skype, cortana and ms teams.

Analytics not showing is being tracked here: https://github.com/Microsoft/BotBuilder/issues/4500  I'm closing this issue as a duplicate.  Please follow along @ #4500


Allow claiming ranges; fix IDs for some tag types and temporary buffers [phab:D211]

Created by zarko at 2015-04-21 22:03:19:

jdennett commented inline (context lost during migration) at 2015-04-22 04:51:00:
Why is that safe?

jdennett commented inline (context lost during migration) at 2015-04-22 04:51:00:
Please document this.

zarko wrote at 2015-04-22 17:10:36:

Address comments and rebase.

jdennett commented inline (context lost during migration) at 2015-04-24 16:56:44:
How about "The SourceManager that generated loc"? (Or "owns", maybe.)

jdennett commented inline (context lost during migration) at 2015-04-24 16:56:44:
Maybe a comment on why this is better than not setting a path would be good.

zarko commented inline (context lost during migration) at 2015-04-24 17:10:50:
There's no benefit to end-users to setting this here, so I'll just remove it.

zarko wrote at 2015-04-24 17:10:55:

Address comments.

jdennett accepted this revision at 2015-04-24 17:35:12

zarko closed via commit cb576f038c478b7a4b3d63acdcf1ff2621ae025c at 2015-04-24 17:39:10


Camera projection problem

Hi, i am using Scene View without arcore. I found that when i set activity to landscape the scene will become old(stretched ?) while rotating camera. I wonder if this is a camera projection problem ?  And how can I solve this ?
Landscape mode:
https://user-images.githubusercontent.com/39475537/135002660-9cd96307-66d0-42c4-b9c0-2dc9104215a6.mp4
Portrait mode:
https://user-images.githubusercontent.com/39475537/135002738-a7429084-03d2-45c0-9fec-80bc94ba307c.mp4

Hi!
The vertical field of view of the camera is fixed and the horizontal field of view is calculated based on the aspect ratio.
https://github.com/ThomasGorisse/sceneform-android-sdk/blob/193442f519fa6d1fb64768d47207770444a1c846/core/src/main/java/com/google/ar/sceneform/Camera.java#L50
There is a fish-eye effect in the horizontal orientation because the horizontal field of view becomes much higher than it was in the vertical orientation.
If you want to preserve the fields of view along the short and long sides of the device, you need to calculate the vertical field of view in the horizontal orientation (taking into consideration that the horizontal field of view should be now 90 degrees) and set it using this method:
https://github.com/ThomasGorisse/sceneform-android-sdk/blob/193442f519fa6d1fb64768d47207770444a1c846/core/src/main/java/com/google/ar/sceneform/Camera.java#L123

@grassydragon Thank for your reply. I got your idea, but how to calculate vertical field of view in the horizontal orientation ?

First, convert the horizontal field of view to radians.
tan(vertical_fov / 2) = (height / 2) / near
tan(horizontal_fov / 2) = (width / 2) / near
tan(vertical_fov / 2) = tan(horizontal_fov / 2) / width * height
vertical_fov = 2 * atan(tan(horizontal_fov / 2) / width * height)
Finally, convert the vertical field of view to degrees.

Thanks you very much !  I try your method and it seems to got working, but i am not sure.
https://user-images.githubusercontent.com/39475537/135056018-8117f980-b43f-4c67-af5c-f36a0ebff647.mp4


Where to put postprocessing/visualization routines?

@sloede in https://github.com/trixi-framework/Trixi.jl/pull/403#issue-543686261:

In general, I am currently reconsidering whether the decision to pull the plotting functionality into the Trixi package was the right decision. Maybe instead of consolidating these auxiliary methods in the main package, we should consider creating a "postprocessing package" (TrixiPostprocessing?) that consolidates things such as the plot recipes, interpolation methods, plot methods, VTK writing etc.? But maybe this is something that does not to be (or even can be) answered right now but that we should get the functionality first and consider these structural decisions separately in a refactoring step.

@ranocha in https://github.com/trixi-framework/Trixi.jl/pull/403#issuecomment-749359325:

The advantage of having the plot recipes in Trixi.jl is that users don't need to load another package just to be able to plot(sol) - implementing the plot recipes in another package would also be type piracy. Of course, the situation is different for things like additional callbacks, VTK stuff etc. Your suggestion to get the features first, mark them as experimental, and see where they should live after working with them sounds good to me.

I don't see us creating a separate visualization package for the time being: for once, we have seemed to converged on a usable file/directory structure. Furthermore, this clearly creates new testing headaches (as it would be a "downstream" package like Trixi2Vtk.jl, which already causes headaches during testing).
@ranocha I think this can be closed and will do so, unless you have objections.


Fix for coreos provisionning with google driver

Signed-off-by: David Gageot<EMAIL_ADDRESS>

LGTM


Elements at (0, 0) are ignored

We are currently executing specs which validate angular-off-click works correctly on our pages. In the specs we use placeholder divs which have no dimensions. When we simulate a click event it will have a pageX and pageY of 0.
It could also be that on a real page a button is on the upper left and the user clicks on (0, 0). What do you think?
Could we simply remove the following line? https://github.com/TheSharpieOne/angular-off-click/blob/master/offClick.js#L17

Yeah, that came from #3... probably shouldn't had added it to the solution.  I'll remove it.

I read through the issue and I also find it very interesting, not to say potentially problematic. However, if you are interested in solving this I wouldn´t recommend for just checking pageX and pageY for a value 0. As far as I know these are valid values. Thanks for the removal.


Specify default network by name

It would be nice to be able to specify the default network by name in the multus configuration file. This has a couple advantanges:

It allows for CNI configurations that are more dynamic
It works well with existing self-hosted plugins, e.g. Calico, that write their CNI configuration file via a daemonset
It also solves the readiness problem fixed in #98 in a slightly neater way.

It could take advantage of the already existing getCNIConfigFromFile function, so this should be pretty easy.
Thoughts? I can have a PR for this relatively quickly.

Hey Casey, just trying to verify my understanding of this so...
Like today, we have the default network CNI configuration packed into say /etc/cni/net.d/00-multus.conf that looks like:
    {
      "name": "multus-cni-network",
      "type": "multus",
      "delegates": [
        {
          "type": "flannel",
          "name": "flannel.1",
          "delegate": {
            "isDefaultGateway": true
          }
        }
      ],
      "kubeconfig": "/etc/cni/net.d/multus.d/multus.kubeconfig"
    }

Instead, we'd have a way to otherwise specify the default network with something like...
    {
      "name": "multus-cni-network",
      "type": "multus",
      "default": "calico",
      "kubeconfig": "/etc/cni/net.d/multus.d/multus.kubeconfig"
    }

And then it'd pull up say, Calico either via CRD object or file on disk?

@dougbtv yeah, that was my idea - thanks for elaborating it!

@squeed Thanks for the thoughts on it. @dougbtv PR is help us to check a plugin readiness, it need not to be default network.
I see your idea is making sense to use the on-disk file as the default network. so delegate, gives a opportunity to attach multiple networks, with out any Network CRD objects itself. So I am thinking we can change the name delegates to defaultnetworks and make it to accept both network name or array of networks conf ? Is that ok for you guys ?

I really like this idea, and I'm all for it. I also have uses for making the default plugin more flexible, so, I'm all for it for sure. Thanks @squeed

cc @dcbw, who wanted to take a look.

Let's close it because #169 address the issue and now we can specify network-attachment name to specify defaultNetwork as well as clusterNetwork.


how to set autocomplete with htmlmixed  mode?

how to set autocomplete with htmlmixed  mode?
this is my code:
var editor2 = CodeMirror.fromTextArea(document.getElementById("sourceCode2"), {
extraKeys: { "Ctrl": "autocomplete" },
mode: "htmlmixed",
indentUnit: 2,
lineNumbers: true,
theme: "panda-syntax",
lineWrapping: true,
foldGutter: true,
matchBrackets: true,
});
when i press Ctrl ，it's don't work and has no error

What kind of autocomplete do you want? HTML, CSS, JavaScript? Have you loaded show-hint.js and the module that provides completions for the language you want?

What kind of autocomplete do you want? HTML, CSS, JavaScript? Have you loaded show-hint.js and the module that provides completions for the language you want?

I want to three autocomplete together.
like this :

You still didn't tell me what modules you've loaded, and your screenshot shows an editor with only JavaScript, which isn't what the htmlmixed mode provides.

You still didn't tell me what modules you've loaded, and your screenshot shows an editor with only JavaScript, which isn't what the htmlmixed mode provides.

thank you for reply!
loaded this:

html code :

js code:
var editor2 = CodeMirror.fromTextArea(document.getElementById("sourceCode2"), {
extraKeys: { "Ctrl": "autocomplete" },
mode: "htmlmixed",
indentUnit: 2,
lineNumbers: true,
theme: "panda-syntax",
lineWrapping: true,
foldGutter: true,
matchBrackets: true,
});
but it's don't work

Could it be that addon/hint/show-hint.css isn't loaded?

Could it be that addon/hint/show-hint.css isn't loaded?

it's loaded ,and i replace mode 'htmlmixed to 'javascript' ,autocomplete is worked

Well, then I'm out of ideas. If I load these files into mode/htmlmixed/index.html and add an extraKeys option like you have, autocompletion works fine for me, in each of the languages.


Adding a 'help' function

This is what the help message the bot sends looks like :

I'm hoping the wording and format is self explanatory for a user


jkiss.org is down.

Cannot install the plug-in. jkiss.org is down. Is it a permanent or a temporary issue? Thank you.

I'm also seeing same issue.

Please don't download from any shady sites, use https://github.com/serge-rider/dbeaver/releases instead.

jkiss.org it' back.
@icyerasor Thanks for reasonable warning.
Yeah, it was a hot day. For some reason our hosting provider (digitalocean if anybody cares) decided to shutdown jkiss.org machine. They suspected some malicious activity, like ddos. I'm pretty sure it was just some glitch in their software.
Anyhow, now this issue is resolved. Hopefully this won't happen again.


Case-insensitive matching on the UkLW prefix in 776

Context: https://wellcome.slack.com/archives/C8X9YKM5X/p1615483335044200

You're right, I'm being lazy


Added query logging for prometheus. Issue #1315

Flags added:

active.queries.filepath: Filename where queries will be recorded
active.queries.filesize: Size of the file where queries will be recorded.

Functionality added:
All active queries are now logged in a file. If prometheus crashes unexpectedly, these queries are also printed out on stdout in the rerun.
Here's a flow chart depicting how its implemented
Queries are written concurrently to an mmaped file, and removed once they are done. Their positions in the file are reused. They are written in json format. However, due to dynamic nature of application, the json has an extra comma after the last query, and is missing an ending ']'. There may also null bytes in the tail of file.

I think you forgot to push.

The file should be under the data directory, as we know we can write there, rather than pwd.

The file should be under the data directory, as we know we can write there, rather than pwd.

Should I put it under its own folder, like data/active_queries/queries.active, or just data/queries.active ?

I'd put it directly under.

Could you run benchmark on it?
And I could rebase it down to one commit if this is satisfactory.

Is there some particular reason you want a benchmark? I would expect no noticeable change from this PR, and we'd catch it at release if it was an issue.
GitHub lets me do the squash on merge these days.

No particular reason. Just wanted to do it as a sanity check.

Thanks!


Do we need a Max gas setting for external/ internal messages

With the global fee module we have some protection agains low fee messages spamming the system.
But gas is not tight to fees so that an attacker could call a malicious contract with super hight gas settings but low fee.

If we need to make any changes, these should be in wasmd.
I would create an issue in wasmd if still desired, and close this issue. O just close it.

Closing this now as with the globalfee handler we have gas and fees tight. wasmd ante handler takes care of a max gas.


aks provisioning fails

The line az aks create --resource-group myResourceGroup --name myAKSCluster --node-count 1 --enable-addons monitoring --generate-ssh-keys fails with error:
(BadRequest) The VM size of AgentPoolProfile:nodepool1 is not allowed in your subscription in location 'switzerlandnorth'.  For more details, please visit https://aka.ms/cpu-quota
Code: BadRequest
Message: The VM size of AgentPoolProfile:nodepool1 is not allowed in your subscription in location 'switzerlandnorth'.  For more details, please visit https://aka.ms/cpu-quota

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: e6abc877-3392-fdc7-5897-dcbf160b5d5a
Version Independent ID: 214faee1-d559-8525-f8ab-47f06ee0c8e8
Content: Quickstart: Deploy an AKS cluster by using Azure CLI - Azure Kubernetes Service
Content Source: articles/aks/learn/quick-kubernetes-deploy-cli.md
Service: container-service
GitHub Login: @zr-msft
Microsoft Alias: zarhoads

@joniba
Thanks for your feedback! We will investigate and update as appropriate.

@joniba It looks like you'll need to increase your vCPU quota:
https://docs.microsoft.com/en-us/azure/azure-portal/supportability/per-vm-quota-requests
It's worth noting that there are vCPU quotas both for your VM family as well as for regional vCPUs (this would prevent someone from using all the GPU family VMs or blocking out availability in US East, for example).  In addition to the portal, you can use Azure CLI or PowerShell to check your current quota usage and availability.
https://docs.microsoft.com/en-us/azure/virtual-machines/linux/quotas
https://docs.microsoft.com/en-us/azure/virtual-machines/windows/quotas

@joniba We are going to close this thread as resolved but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.

@joniba Availability is a known issue which we are working on around the clock and our Microsoft Q&A sticky as well as our blog regarding advancing reliability provides some additional details that may be useful.
As a result, not every subscription will see the same options for every region.  Trying a different region with less demand like you mentioned is the quickest way around this although you can create a support request to increase your quota for that region if location is a priority.
Using az vm list-skus is a good way to quickly check availability for your subscription:
https://docs.microsoft.com/en-us/azure/azure-resource-manager/troubleshooting/error-sku-not-available?tabs=azure-cli#solution


Add API docs with typedoc

This PR adds typedoc to generate the latest documentation of the types available and updated in index.d.ts.

Released in v0.11.0.


DB-transaction after removing processed pages is not committed

I got an exception from BerkleyDB about a bunch of open transactions after a crawl as the method to remove processed pages returns before committing the transaction

Committed in https://github.com/yasserg/crawler4j/pull/68


fix(esl-share): fix focus behavior to a loop inside esl-share-popup

:tada: This PR is included in version 5.0.0-beta.1 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add information about licensing

Thanks for your information, I have added Apache License

Thank you for information!


fqdn/dnsproxy: Improve error wrapping

This commit fixes the error wrapping inside the dnsproxy package.
When a DNS response is being processed by the DNS proxy inside
NotifyOnDNSMsg(), we check ProxyRequestContext. If the request response
timed out, we annotate the metrics specifically to indicate that it
timed out. This relies on the errors being properly wrapped.
In order to do this, errors.As() is used and all errors are properly
wrapped with '%w'.
Signed-off-by: Chris Tarazi<EMAIL_ADDRESS>Improve Cilium DNS Proxy-related error metrics

/test


Cant login from dative.jrwdunham.com

i forced the upstream to match jrwdunham, which triggered deployment on dativebeta
https://travis-ci.org/OpenSourceFieldlinguistics/dative/builds/61163475so we can see what is the problem, is the server refusing the origin of jrwdunam, or is the CORS request missing stuff.


configuration and logging

re-orgainzed and refactored configuration

added logging funcationality (address #47)

cleaned some code.

First pass through.  Looking good.
Don't forget to resolve the flake8 error.

Still have some pep8 errors ...

Can we overhaul the parsing to explicitly handle sam output, rather than blast output.
We need all of the uniref sequences that hit, for the cache.

do u want to add that? just another static function in the class and return
pd.DataFrame.
On Tue, Mar 8, 2016 at 10:41 PM, Jamie Morton<EMAIL_ADDRESS>wrote:

Can we overhaul the parsing to explicitly handle sam output, rather than
blast output.
We need all of the uniref sequences that hit, for the cache.
—
Reply to this email directly or view it on GitHub
https://github.com/biocore/micronota/pull/54#issuecomment-194140750.

Yup.  Adding that now.

This is still missing tests.  Can we have some really basic tests to just run to through the code?

Also, note that the tests are a little out-dated, since search_protein_homologs has changed names.

First pass through.  It think it's ready to merge after these comments are addressed.


Application is unable to handle files that contains spaces/-/_ in-between their names

Currently while generation of java class files , the application is unable to handle files or folders that contains spaces/ - / _ in-between their names.

Made changes in TestCaseGenerator.java to handle file names with spaces/_/-