BEAM-13612: This will fix the NPE because of absence of the projectId

This addresses #21405 NullPointerException because of the projectId's absence picking up the default (or the one provided via BigQueryOptions) project id rather than failing with NPE
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

fixes #29409

R: @slilichenko @damccorm

Looks like a good change to me. But I agree, it looks like this change breaks a number of checks

I now disagree with this change. It appears that all places where we query this value, we check if it's null first. if it is, we default to the .getProject value.

I think the key is to update in the .getTable instead

This has been resolved with #29471


Freezes with no response

Windows 10 Fall Creators Update 1709 When i upgrade , problem happens.
Freezes with no response after using few mins
Need to use task manager to end
Tried re-install, restart, not work

Expected Behavior

Current Behavior

Screenshots (if appropriate):

Possible Solution

Steps to Reproduce (for bugs)

Context

Your Environment

Franz Version used:  5.0.0-beta.12
Operating System and version: Windows 10, 1709

When you restart the app and press Ctrl+Alt+i -> go to the console tab. Is there any error output before the app freezes?

This error unfortunately isn't the issue.
If you disable both WhatsApp instances, does it happen as well?

when i receive message on one of the whatsapp, it freezes immediately.
No issue before the windows update to 1709

Ok this is weird. However, we are having issues with Windows 1709 (Fall Creators Update) #173 as Microsoft has changed their notification center quite much. Does the problem persist if you disable notifications?

It works when i disable the notifications. Will it fix soon? Thanks a lot


add bfloat16 support

Add bfloat16 support to composer.
Bfloat16 is supported in Pytorch >= 1.10 on both GPU and CPUs.
The implementation is relatively simple (see files changed), however, good performance is not guaranteed.
Ex 1: ResNet-50 Bfloat16 vs. AMP on A100 GPUs. ~27x worse training speed for Bfloat16 (similar accuracy).
Ex 2: GPT-2 Bfloat16 vs. AMP on 3090s/A100 GPUs. Bfloat16 and AMP have very similar training speed and performance.
We hypothesize that certain convolutional operations have not been optimized for Bfloat16 precision, and the fallback CUDA operations have high overhead, which causes models like ResNet-50 to see large performance drops using Bfloat16 compared to mixed precision. Transformer-based models (without convolutions) see similar performance using Bfloat16 vs. AMP.

One other bit -- we should add BF16 into our testing as well.


Fix icon spread problem when they are stacked at the end of map

This revision includes:

Fix icon spread problem when they are stacked at the end of map (Resolves #41)

Add method 'IsBoundary()': Checks position (x, y) is boundary
Add unit test for checking icon spread problem

@lssac7778 Can you check this PR? Thanks.

Good! Works well.


add linkedin badge

example code
Menno van der Graaf

You can use this for all sort's of fonts: http://fontawesome.io/

thanks for sharing the resource, currently only used googles icon database, but they lack all the brand icons. Will give it a look

If you want to see how you can us it, look at this project: DNS/index.html. This project also uses font awsome

btw, I did end up using the icons from fontawesome!
👍


Running a Julia recipe with the ESMValBot crashes often

Running a Julia recipe with the ESMValBot regularly does not work, see here for an example: https://github.com/ESMValGroup/ESMValTool/pull/2046#issuecomment-782170431
It looks like this happens because Julia re-uses the ~/.julia directory for every installation of the tool and over time this directory ends up in a conflicting state. It would be good to use a fresh directory for every installation of the tool by the ESMValBot.

There is a PR to make this change now in the bot repository and local changes on the VM are in place.


Not available with Carthage and Xcode 10.2

error: SWIFT_VERSION '3.0' is unsupported, supported versions are: 4.0, 4.2, 5.0. (in target 'Regex-OSX')

☹

also for other targets iOS/tvOS

@all
You can use my fork for now:
...
pod 'STRegex', :git => 'https://github.com/mohpor/Regex.git'
...

@sharplet Any chance to release a new version with Swift 5 (Xcode 10.2) support?

Sorry for the radio silence folks, I'll try take a look this week!

I’ve just released Regex 2, let me know if there’s any more issues!

@sharplet Yeah 🙌 Thank you.


Row level access?

How would you go about restricting row level access?

Do you mean restrict access to resources based on some kind of authorisation mechanism, @leondewey?

@pmcnr-hx Yes kind of, I can see how todo it on a resources level but what about if that resources was posts and you only want a user to be able to CRUD there own posts?

Hi @leondewey - We combine the authentication hook with custom wrappers around the CRUD handlers. Our auth hooks look something like this:
jsonApi.authenticate(function(request, callback) {
  // validate headers / cookie / whatever, check user is logged in, etc.
  // ...If OK, then attach user data to request
  request._userData = { };
  return callback();
});

We then wrap the base database handlers with some logic that enforces filtering upon the database, by using request._userData to limit the scope of the query. You can find an example of that in the comments of the example here: https://github.com/holidayextras/jsonapi-server/blob/master/documentation/suggested-project-structure.md#example-handler (you'd add to request.filter on the example line that currently reads tweak something?).

Thank you very much! That's really cool.


How to deal with IL2CPP build with unity 2018

Hello,
On Unity 2018, .NET scripting back end for UWP is deprecated. We now have to use IL2CPP scripting back end.
Because of that, I don't have a way to have IntelliSense and other tooling for UWP C# code (inside UNITY_WSA compilation symbols), since the dll and the compilation symbols are not available in the unity project. Is there a way to generate some kind of "scripting only project" with the proper .sln/csproj/dll files in order to add UWP targeted code more easily ?

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

ID: 5f00922d-8f87-0c40-4b9c-9994be4f8f7f
Version Independent ID: 75796fe2-31b2-734d-101d-9bf235222344
Content: Best practices for working with Unity and Visual Studio - Mixed Reality
Content Source: mixed-reality-docs/best-practices-for-working-with-unity-and-visual-studio.md
Product: windows
GitHub Login: @mattzmsft
Microsoft Alias: mazeller

This is kind of old now, but here probably many who has not converted yet, so here it goes anyway:
Read https://docs.unity3d.com/Manual/ManagedCodeDebugging.html under 'Debugging in the player'.
You should get separate projects in the editor-solution (not the UWP solution) that are 'MyCode.Player'. These will have the same code as 'MyCode', with the exception that compilation symbols will be set for Hololens instead of editor.
This is available from 2018.2.
WARNING: The FPS in IL2CPP debug mode is super-bad. We are talking a second per frame. It may be better to do this against the emulator if possible.

Yes I saw it, thanks !


FileOutputStream memory leak

Memory increases as files are written, even if the last file is closed and memory is not released.
demo code:
        NSUInteger offset = 0;
        NSInteger chunkSize = 65535;
        NSFileHandle *handle = [NSFileHandle fileHandleForReadingAtPath:localPath];
        NSData *data = [handle readDataOfLength:chunkSize];
        FileOutputStream* outStream = new FileOutputStream;//test code
        while ([data length] > 0) {

            IOSByteArray* byteArray = [IOSByteArray arrayWithNSData:data];

            [outStream writeWithByteArray:byteArray withInt:0 withInt:(int)[data length]];

            offset += [data length];

            [handle seekToFileOffset:offset];

            data = [handle readDataOfLength:chunkSize];
        }

        [handle closeFile];

        [outStream close];

        outStream = nil;

Are you converting a lot of files in a loop? j2objc uses an autorelease pool to free objects, so running this code in a loop may not fall out of scope of the current autorelease pool, and so it keeps increasing.  If this is the case, you should put the above code inside an autoreleasepool { ... } block, so autoreleased objects are deallocated after each file is processed.
To do this in Java code, put this code into a separate method, then annotate it with @AutoreleasePool. Here's an example where we do this in the JRE.


Add DockerFile

Create dockerfile where the app will be running

User story:
As a project owner,
I want our app to run independently in the docker container
So that the app won't be dependent on the environment it is launched in
Acceptance criteria:
Given the project is pulled
When the project compiles
Then the Docker image is built and container should run and output numbers from 1 to 5


IBPy reconfigures logging

I'm not sure if this is a bug (I am not a logging expert), but it seems like IBPy reconfigures logging globally when it runs:
   logging.basicConfig(level=level, format=format, datefmt=datefmt)
This line seems to redefine logging at the root level, which means it will apply it to all modules running in my application.
Is this the intended behaviour?
I'm running it inside a Jupyter notebook.

OK, I'm pretty sure the logger is badly behaved. I've monkey patched it in my code as such:
class ibpy_logger(object):
    def logger():
        return logging.getLogger('ibpy')
import ib.lib.logger
ib.lib.logger = ibpy_logger

I believe we should fix it in the module, so it plays nicely in a larger application.

Yep - came here to post this same issue.


[Azure Analysis Services] Replace config object with uri string

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[x] The title of the PR is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[x] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[x] If applicable, the PR references the bug/issue that it fixes.
[x] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[x] I have read the contribution guidelines.
[x] My spec meets the review criteria:

[x] The spec conforms to the Swagger 2.0 specification.
[x] The spec follows the guidelines described in the Swagger checklist document.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

@taiwu,
Thanks for your contribution.  To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla.microsoft.com.
The agreement will cover your contributions to all Microsoft-managed open source projects.
Thanks,
Microsoft Pull Request Bot

Refer to https://github.com/Azure/azure-rest-api-specs/pull/1296
Since the original backupConfiguration is not in used, no need to bump the version.

Hi There,
I am the AutoRest Linter Azure bot. I am here to help. My task to analyze the situation from the AutoRest linter perspective. Please review the below analysis result:
File: arm-analysisservices/2016-05-16/swagger/analysisservices.json
Number of linter errors/warnings before the PR: 11
Number of linter errors/warnings after the PR: 10
Thanks for your co-operation.

@vishrutshah Could you please take a look?

Hi @taiwu,
@jhendrixMSFT would be looking the PR. @jhendrixMSFT Please refer the previous conversation on https://github.com/Azure/azure-rest-api-specs/pull/1296 to get the context.
Thanks!

I'm reviewing this today.

Thanks!

No modification for AutorestCI/azure-sdk-for-python

No modification for AutorestCI/azure-sdk-for-node

 https://github.com/Azure/azure-sdk-for-ruby/pull/806

@taiwu I'm just curious. Is there a reason why we change old swagger if we have a new one. These kind of changes are API breaking changes.

@ravbhatnagar This's SDK breaking changes. Even if the removed optional property and type are never used by server, it breaks existing client code. Should we revert, add these types back?


Fetch templates for collate and oss.

Type of change:

[ ] Bug fix
[ ] Improvement
[ ] New feature
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] My PR title is Fixes <issue-number>: <short explanation>
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] For JSON Schema changes: I updated the migration scripts or explained why it is not needed.

It's ok for now , but we should come up with something for all entities


V2 anonymizer improvements

improve runtime for analyzer results loop by reducing the list size and keeping the code clean.

I don't see how this is improving anything drastically, the list we are manipulating is not expected to be long, and even if it was, the change is not affecting complexity. Overall adds more stateful operations with more chance for a bug next time someone modifies the method.

@SharonHart moving the initialization and duplication of the list from each loop to a one time thing, changes a lot.
I think this is a really good change and we should keep it.
I won't be doing any further changes on this one for now...


Update scripts in dev/prepare_data to use new SCT config syntax (.yml)

Checklist
GitHub

[x] I've given this PR a concise, self-descriptive, and meaningful title
[x] I've linked relevant issues in the PR body
[ ] I've applied the relevant labels to this PR
[x] I've assigned a reviewer

PR contents

[ ] I've consulted ivadomed's internal developer documentation to ensure my contribution is in line with any relevant design decisions
[ ] I've added relevant tests for my contribution
[ ] I've updated the relevant documentation for my changes, including argparse descriptions, docstrings, and ReadTheDocs tutorial pages

Description

The scripts in this folder were using the outdated syntax (parameters.sh), which no longer works as of SCT v5.3.0. So, this PR updates the scripts so that they can work with the most recent version of SCT.
The files also reference an older version of data-multi-subject (called spineGeneric_multiSubjects), so I've updated the references accordingly.

I've requested a review from @charleygros and @kousu as I believe you were the last folks to work on these files, and might be able to provide some insight into their usage/development.
Linked issues

Fixes #948.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
281 unchanged lines in 7 files lost coverage.
Overall coverage decreased (-4.6%) to 70.753%

Files with Coverage Reduction
New Missed Lines
%

ivadomed/transforms.py
2
87.39%

ivadomed/metrics.py
4
92.97%

ivadomed/loader/utils.py
5
78.14%

ivadomed/scripts/automate_training.py
9
79.25%

ivadomed/utils.py
12
72.82%

ivadomed/main.py
106
13.59%

ivadomed/training.py
143
11.9%

Totals

Change from base Build<PHONE_NUMBER>:
-4.6%

Covered Lines:
4311

Relevant Lines:
6093

💛  - Coveralls


Using <React.StrictMode> doesn't render the step component

When using <React.StrictMode> the step doesn't get renderes initially. Only if the previous/next buttons are clicked the steps appear.
I added it to one of your examples. Take a look:
https://codesandbox.io/s/basic-render-props-example-forked-g8rez?file=/src/index.js

Also weirdly it does render if isActive is false , even when returning null and no apparent further execution happens.

same issue

Currently running into the same issue.
Did anyone research this further or find a workaround other than disabling strict mode? 🙂


Add metric, us legal and us customary cups to volume

As per #130 adds the three cup units to volume.
I didn't add an abbreviation for the three as it is too ambiguous IMHO.
I tried "metric cup" but that broke Volume.Parse which didn't like the two word combination

Nuget 3.25 out.


Bug : the obj test files don't work

Hi ,
I installed and run your code but found that the obj files don't work.
I even tried the one you wrote on your README markdown file.
do you happen to know why? did the norm change? what viewer are you using?

Hi, these OBJ files define splines and may not work with mesh viewers. The screenshots in the readme are from Rhino.


atob not supported in IE9

Similar to this issue: https://github.com/travist/jsencrypt/issues/1
atob is not supported until ie10, so an alternative encoding/decoding function is required.

spring cleaning


Copy chunk bytes in TSDB store before sending to client

During head compaction mmaped memory gets released while gRPC is marshaling bytes from that same memory region. This leads to a fatal segfault and crashes the receiver. The segfault happens when marshaling chunks specifically.
This commit modifies the TSDB store server to copy chunk bytes before sending them to the client. I tried running this for a while and saw no significant increase in memory usage.
Fixes https://github.com/thanos-io/thanos/issues/6196.

[ ] I added CHANGELOG entry for this change.
[ ] Change is not relevant to the end user.

Changes

Verification

I'll raise this PR against 0.31.


Differentiate between conflicting rules defined in different rule files

Bug Report
What did you do?
Create two rules files which both contain the same recording rule name but different expressions/values.
What did you expect to see?
Either a notification that these rules conflict or some way to differentiate them into different time series.
What did you see instead? Under which circumstances?
The rules will create a single metric with alternating values as they are recorded.

Prometheus version:
prometheus, version 2.14.0 (branch: master, revision: 23c0299d85bfeb5d9b59e994861553a25ca578e5)

Possible solution could be to add a rule filename label to each rule before they are stored to tsdb.

Although similar to #5529, this issue is different in that the two rules are defined in separate files and do not have any differences in labels.

This is a valid, though broken configuration. I don't think there's anything for us to do here.

If it's considered a broken configuration shouldn't prometheus provide some kind of error/warning?

We can't catch every possible way in which users can cause a label clash, though there should be at least metrics covering this already.

Are there potential problems with automatically adding a label which includes the filename of the source of the rule?

Yes, that will completely break many many use cases.

We have been looking into this into our bug scrub and we have decided that there is nothing we can reasonably do in Prometheus as there are many valid uses cases where this could happen. There is also a similar issue in #912 for verbatim rules.


Live reload does not always work

Sometimes live reload does not work. Even with a hard refresh nothing has changed. Its like the watch is failing to see the changes and transpile/compile. This happens somewhat frequently.

This problem actually only occurs in certain components (generated by the generator). i.e. I can save containers/app.js and it will refresh.

Can you provide more details?
The output of the webpack-dev-server command for example, should tell you when something changed and display:

webpack: Compiled successfully.

Also, the browser console will tell you when something changed:

[WDS] App updated. Recompiling...

And if it was able to apply the changes with hot module replacement (HMR) or if it had to do a full reload.
How well HMR works for you will depend on your application, magic doesn't exist, your entire app has to depend solely on the Redux state and React component's properties/state so it can restore itself at any given point. It is actually a nice way to test how well designed your app is.

@impavidum When you see things not refreshing, can you open the terminal window that's watching for the files, and press any key on your keyboard to see if it does anything? Lately I am seeing this pattern on my terminal (on Windows), pressing any key while on the terminal triggers the idle window to start watching again.


Click event not working for last item in the list

Summary:
Click event not working for last item in the list
Steps to reproduce:
Launch the Nearby Option List and tap on last item.

Device and Android version:
Tested on Xiaomi Mi A1 running Android 9 Pie with Stock Android
Commons app version:
betaDebug
Would you like to work on the issue?
Yes I want to fix this issue :)

I can reproduce, good find! :-)

Thanks @madhurgupta10 , it is yours. :)

@nicolas-raoul @misaochan I changed the issue title because the click event was working fine but the user needs to scroll manually to see the layout, also fixed it in PR #2491.


Adjust bbox to IFG grid, handle multipolygons

Addressed the following two issues:

Under the merged_productbbox function of the extractProduct.py script, bounding box shapefiles and bounds are now adjusted to ensure they are integer multiples of the standard interferometric grid increment. This is done by passing the 'target aligned pixels' option to the first call to gdalWarp in order to access the master bounds. These bounds are then inherited by all future warping calls. Addresses discussion in Issue #185
Handle area calculations for fringe cases where intersection of products and bounding boxes produces multipolygons (see Issue #188 for illustrations). Changes made toshapefile_area function under the shapefile_util.py script.

@sssangha please disentangle the PR. The area change is trivial the sampling change i would like to see vetted prior to merging.


libpipeline: 1.5.4 -> 1.5.6

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/libpipeline/versions.
meta.description for libpipeline is: "C library for manipulating pipelines of subprocesses in a flexible and convenient way"
meta.homepage for libpipeline is: "http://libpipeline.nongnu.org"
meta.changelog for libpipeline is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 1.5.5 with grep in /nix/store/2brsnld55pfsvc58gsn55h92lpnn149x-libpipeline-1.5.5

found 1.5.5 in filename of file in /nix/store/2brsnld55pfsvc58gsn55h92lpnn149x-libpipeline-1.5.5

Rebuild report (if merged into master) (click to expand)

19643 total rebuild path(s)

13764 package rebuild(s)

13744 x86_64-linux rebuild(s)
5898 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath

ArchiSteamFarm
AusweisApp2
CHOWTapeModel
ChowCentaur
ChowKick
CuboCore.coreaction
CuboCore.corearchiver
CuboCore.corefm
CuboCore.coregarage
CuboCore.corehunt
CuboCore.coreimage
CuboCore.coreinfo
CuboCore.corekeyboard
CuboCore.corepad
CuboCore.corepaint
CuboCore.corepdf
CuboCore.corepins
CuboCore.corerenamer
CuboCore.coreshot
CuboCore.corestats
CuboCore.corestuff
CuboCore.coreterminal
CuboCore.coretime
CuboCore.coretoppings
CuboCore.coreuniverse
CuboCore.libcprime
CuboCore.libcsys
DisnixWebService
EmptyEpsilon
HentaiAtHome
MIDIVisualizer
MMA
OSCAR
OVMF
OVMFFull
PageEdit
R
SDL
SDL2
SDL2_gfx
SDL2_image
SDL2_mixer
SDL2_net
SDL2_ttf
SDL2_ttf_2_0_15
SDL_Pango
SDL_gfx
SDL_gpu
SDL_image

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/2brsnld55pfsvc58gsn55h92lpnn149x-libpipeline-1.5.5 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A libpipeline https://github.com/r-ryantm/nixpkgs/archive/957c971917ad1719d66c65d2d5786c3fc8c96c7d.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/2brsnld55pfsvc58gsn55h92lpnn149x-libpipeline-1.5.5
ls -la /nix/store/2brsnld55pfsvc58gsn55h92lpnn149x-libpipeline-1.5.5/bin

Pre-merge build results
NixPkgs review skipped

Maintainer pings

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/libpipeline/versions.
meta.description for libpipeline is: "C library for manipulating pipelines of subprocesses in a flexible and convenient way"
meta.homepage for libpipeline is: "http://libpipeline.nongnu.org"
meta.changelog for libpipeline is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.5.6 with grep in /nix/store/pc8z6cs3hd6brhylkdvpgfayc8sxfl8r-libpipeline-1.5.6
found 1.5.6 in filename of file in /nix/store/pc8z6cs3hd6brhylkdvpgfayc8sxfl8r-libpipeline-1.5.6

Rebuild report (if merged into master) (click to expand)

27342 total rebuild path(s)

27342 package rebuild(s)

First fifty rebuilds by attrpath

ArchiSteamFarm
AusweisApp2
CHOWTapeModel
ChowCentaur
ChowKick
ChowPhaser
CuboCore.coreaction
CuboCore.corearchiver
CuboCore.corefm
CuboCore.coregarage
CuboCore.corehunt
CuboCore.coreimage
CuboCore.coreinfo
CuboCore.corekeyboard
CuboCore.corepad
CuboCore.corepaint
CuboCore.corepdf
CuboCore.corepins
CuboCore.corerenamer
CuboCore.coreshot
CuboCore.corestats
CuboCore.corestuff
CuboCore.coreterminal
CuboCore.coretime
CuboCore.coretoppings
CuboCore.coreuniverse
CuboCore.libcprime
CuboCore.libcsys
DisnixWebService
EBTKS
EmptyEpsilon
Fabric
HentaiAtHome
LibreArp
LibreArp-lv2
MACS2
MIDIVisualizer
MMA
OSCAR
OVMF
OVMFFull
PageEdit
R
SDL
SDL2
SDL2_gfx
SDL2_image
SDL2_mixer
SDL2_net

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/pc8z6cs3hd6brhylkdvpgfayc8sxfl8r-libpipeline-1.5.6 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A libpipeline https://github.com/r-ryantm/nixpkgs/archive/9bf8ddf3b30f6c49c1f83205f4cea84d124eb7b5.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/pc8z6cs3hd6brhylkdvpgfayc8sxfl8r-libpipeline-1.5.6
ls -la /nix/store/pc8z6cs3hd6brhylkdvpgfayc8sxfl8r-libpipeline-1.5.6/bin

Pre-merge build results
NixPkgs review skipped

Maintainer pings

@ofborg build libpipeline


Page for workshop links.

We will need a page where participants can access all the workshop links! Preferably categorized by topic (webdev, mobile, etc.).

Blocked: waiting on workshops and office hours to be finalized

Blocked: waiting on workshops and office hours to be finalized


Note about limiting concurency in Server

For better understanding of not overwriting LimitConcurency in Server

I just encountered the same issue, as I was seeing no speedups after 4 concurrent requests. I was using the php docker container which uses the default ini settings of memory_limit = 128M and post_max_size = 8M which results in only 4 concurrent requests.
https://github.com/php/php-src/blob/master/php.ini-development#L401
Since I'm not really handling any uploads, I added the following .ini file, which boosted it to 4096 concurrent requests.
[PHP]

post_max_size = 8K
memory_limit = 256M

The note in in the last paragraph of the Server section of the README does cover this already, but I was confused because the automatically added middleware was setting the upper bound.
I am curious about how to calculate a sensible number for concurrent requests and what the failure mode is if I push it too far? I guess I may have to do some more testing 😃

@woytam Thank you for filing this PR, I agree that it makes sense to add some documentation for this! :+1:
I've just filed #342 to add some additional documentation for the concurrency limit and how to possibly avoid hitting this limit. Let me know what you think about this :+1:


[fix] [proxy] Fix pattern consumer does not work when using Proxy

Motivation
https://github.com/apache/pulsar/pull/22854 added a new method List<Integer> getExistsPartitions(String topic), which depends on the new method GetTopicsResult.nonPartitionedOrPartitionTopics, but the author of the PR forgot the change the deserializer of Pulsar-Proxy, which may cause the following issue:

Broker respond: tp-partition-0
Proxy received tp-partition-0 and recreate a new response that may remove the suffix -partition-0 to client
Client received tp, which without -partition-0

Client assumed the parition 0 does not exists.

Modifications
Fix the bug
Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository: x

/pulsarbot rerun-failure-checks


Comparing okio and retrofit in performing network calls

Article checklist
Attention
Our Peer Reviewer and Content Moderator teams do NOT provide any revisions services. All revisions and edits should be completed on your own forked repo (as to not take up room in the queue) in order for our team to review them all in a timely manner.
ANY ARTICLE SUBMITTED WITH GLARING ERRORS WILL BE IMMEDIATELY CLOSED.

As a rule of thumb - please be sure to only submit articles (pull requests) that are fully polished and ready to be published. Be sure to go through our resources documents for extra and 3rd party (vetted) resources to help improve overall technical writing.

Pre-submission checks

Please ensure that you have only one open topic suggestion (issue) + in-review article (linked pull request) at a time. This will ensure that we complete the review process in a timely manner from inception to publishing

If you have not already, please go over our Resources Page for more tips and tricks on how to improve your overall technical writing so reviews are swifter, increase the chance of a payout and provide more value to our readers.

For first-time contributors and for more details on our submission guidelines, see our Contributing Guidelines.

Formatting and structure checks

[x] Have you used the correct folder and file structure? - see Contribution Guidelines

[x] Is your article properly formatted in Markdown? - see Github Markdown guide

[x] Have you used our preferred heading structure? - H3 (###) and up

[x] Does your article follow any of the suggested structure formats? - see example formats

[x] Is your article over 750 words? - Tool: Wordcounter.net

[x] Is the article you are submitting an in-depth and unique article? Does it go beyond what is in the official docs and what is covered in other blog sites. See these articles as examples.

[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.

[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.

[x] Have you included a hero image that is 600x400 pixels, under 300KB in size, and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid - Grammarly
[x] Please place your article through a 3rd party plagiarism checker. We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[x] Have you checked your article for readability? - Tool: Hemmingway
[x] Have you added sources for quotes and images that aren't yours?

Technical checks

[x] Are your code snippets properly formatted for syntax highlighting - see Syntax guide
[x] Have you checked your code runs correctly and you've highlighted all necessary dependencies for installation?
[x] Are the software programs and packages you're highlighting in your article up to date, using current versions and not deprecated?

Topic suggestion this closes

Remove the backticks and add the issue number below to link and close your Topic Suggestion (issue) when your article has been published (PR has been merged). See this video for more details.

This closes #6129

Finally, delete the article checklist notes in blockquotes and submit your PR. We look forward to reviewing your article.

Hello @nia-vee ,
Thanks for submitting this PR.
Your PR has entered our reviewing queue. Please wait until a peer-reviewer pings you to get started.
Meanwhile, we suggest you to go through existing approved PRs/published articles to see if you have missed out anything.
Thanks.

Hello @nia-vee, I have gone through the article and I feel that it does not cover the topic sufficiently. You have only talked about Okio rather than talk about both of them. Please have a look at other published comparison articles and make sure you follow their structure.
I'll close this PR until changes are done.
Ping me when you are done.


External triggering, toggling settings midway

external triggering is useful for, complex fm waves, and hard sync i guess
people have proposed using one wav filename as a trigger and another as a render
i've never implemented it
problem is, my table has too many columns already
adding separate trigger width and subsampling columns is +1, adding separate render width and subsampling is another +1
adding external sync is another +1
and most columns are empty too
ideally i could either hide empty rarely-used columns until you show them on a per-song? basis (hard)
or add a "channel editor" sidebar that only shows 1 channel at a time (harder)


Could you please to figure out how to train on Pascal VOC?

We are interesting to use cutmix in object detection. But the problem is that whats the bbox drop rule?

哥  我也想把这个做到检测数据里面 我的qq是531232693 加个qq一起探讨一下呗

Hi, we didn't try CutMix on the detection task directly.
The same q&a is here: #19 (comment)


⚠ ClamAV has degraded performance

In 0f88486, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 81 ms

Resolved: ClamAV performance has improved in 4c09cad.


I am unable to get the receiver message

I have downloaded code and update the pod. Integrated GoogleInfo.plist in the source code. When I run the code, I am able to send the message and message is storing on firebase database, while unable to get message of receiver if receiver reply for my message. Please suggest what am I missing. I am using two different simulator with different sender and receiverID.

Same problem


[BUG] DeepSpeedCPUAdam compatibility on ROCm

Describe the bug
Hi,
import torch
from deepspeed.ops.adam import DeepSpeedCPUAdam

fused_adam = DeepSpeedCPUAdam([torch.rand(10)])

yields [WARNING]  cpu_adam cuda is missing or is incompatible with installed torch, only cpu ops can be compiled! on a ROCm install of PyTorch & DeepSpeed. Is this expected?
Thank you!
To Reproduce
Use torch==2.1.1+rocm5.6 & deepspeed==0.12.4.
Expected behavior
A clear and concise description of what you expected to happen.
ds_report output
--------------------------------------------------
DeepSpeed C++/CUDA extension op report
--------------------------------------------------
NOTE: Ops not installed will be just-in-time (JIT) compiled at
      runtime if needed. Op compatibility means that your system
      meet the required dependencies to JIT install the op.
--------------------------------------------------
JIT compiled ops requires ninja
ninja .................. [OKAY]
--------------------------------------------------
op name ................ installed .. compatible
--------------------------------------------------
async_io ............... [NO] ....... [OKAY]
fused_adam ............. [NO] ....... [OKAY]
cpu_adam ............... [NO] ....... [OKAY]
cpu_adagrad ............ [NO] ....... [OKAY]
cpu_lion ............... [NO] ....... [OKAY]
 [WARNING]  Please specify the CUTLASS repo directory as environment variable $CUTLASS_PATH
evoformer_attn ......... [NO] ....... [NO]
fused_lamb ............. [NO] ....... [OKAY]
fused_lion ............. [NO] ....... [OKAY]
inference_core_ops ..... [NO] ....... [OKAY]
cutlass_ops ............ [NO] ....... [OKAY]
quantizer .............. [NO] ....... [OKAY]
ragged_device_ops ...... [NO] ....... [OKAY]
ragged_ops ............. [NO] ....... [OKAY]
random_ltd ............. [NO] ....... [OKAY]
 [WARNING]  sparse_attn is not compatible with ROCM
sparse_attn ............ [NO] ....... [NO]
spatial_inference ...... [NO] ....... [OKAY]
transformer ............ [NO] ....... [OKAY]
stochastic_transformer . [NO] ....... [OKAY]
transformer_inference .. [NO] ....... [OKAY]
--------------------------------------------------
DeepSpeed general environment info:
torch install path ............... ['/usr/local/lib/python3.10/dist-packages/torch']
torch version .................... 2.1.1+rocm5.6
deepspeed install path ........... ['/usr/local/lib/python3.10/dist-packages/deepspeed']
deepspeed info ................... 0.12.4, unknown, unknown
torch cuda version ............... None
torch hip version ................ 5.6.31061-8c743ae5d
nvcc version ..................... None
deepspeed wheel compiled w. ...... torch 2.1, hip 5.6
shared memory (/dev/shm) size .... 64.00 GB

System info (please complete the following information):

GPU count and types: MI250

FYI @rraminen and @jithunnair-amd

Hello, I have the same problem when using torch==2.2.0+rocm5.6 & deepspeed==0.12.4. How can this be solved? Any help would be greatly appreciated.

@xxtars - can you try with a newer version of DeepSpeed and let me know if you still repro this?  Specifically 0.14.0?

Thank you for your reply! I'm not  familiar with DeepSpeed and ZeRO.
What I am doing is training using zero2_offload, and I encounter this issue during compilation.
The versions I have tried are:
torch==2.2.0+rocm5.6 & deepspeed==0.12.4
torch==2.2.1+rocm5.6 & deepspeed==0.12.4
torch==2.2.1+rocm5.6 & deepspeed==0.14.0

There is my ds_report output. Any help would be greatly appreciated.
--------------------------------------------------
DeepSpeed C++/CUDA extension op report
--------------------------------------------------
NOTE: Ops not installed will be just-in-time (JIT) compiled at
      runtime if needed. Op compatibility means that your system
      meet the required dependencies to JIT install the op.
--------------------------------------------------
JIT compiled ops requires ninja
ninja .................. [OKAY]
--------------------------------------------------
op name ................ installed .. compatible
--------------------------------------------------
 [WARNING]  async_io requires the dev libaio .so object and headers but these were not found.
 [WARNING]  async_io: please install the libaio-devel package with yum
 [WARNING]  If libaio is already installed (perhaps from source), try setting the CFLAGS and LDFLAGS environment variables to where it can be found.
async_io ............... [NO] ....... [NO]
fused_adam ............. [NO] ....... [OKAY]
cpu_adam ............... [NO] ....... [OKAY]
cpu_adagrad ............ [NO] ....... [OKAY]
cpu_lion ............... [NO] ....... [OKAY]
 [WARNING]  Please specify the CUTLASS repo directory as environment variable $CUTLASS_PATH
evoformer_attn ......... [NO] ....... [NO]
fused_lamb ............. [NO] ....... [OKAY]
fused_lion ............. [NO] ....... [OKAY]
inference_core_ops ..... [NO] ....... [OKAY]
cutlass_ops ............ [NO] ....... [OKAY]
transformer_inference .. [NO] ....... [OKAY]
quantizer .............. [NO] ....... [OKAY]
ragged_device_ops ...... [NO] ....... [OKAY]
ragged_ops ............. [NO] ....... [OKAY]
random_ltd ............. [NO] ....... [OKAY]
 [WARNING]  sparse_attn is not compatible with ROCM
sparse_attn ............ [NO] ....... [NO]
spatial_inference ...... [NO] ....... [OKAY]
transformer ............ [NO] ....... [OKAY]
stochastic_transformer . [NO] ....... [OKAY]
--------------------------------------------------
DeepSpeed general environment info:
torch install path ............... ['/scratch/-/miniconda3/envs/llamavid_rocm5.6/lib/python3.10/site-packages/torch']
torch version .................... 2.2.2+rocm5.6
deepspeed install path ........... ['/scratch/-/miniconda3/envs/llamavid_rocm5.6/lib/python3.10/site-packages/deepspeed']
deepspeed info ................... 0.14.0, unknown, unknown
torch cuda version ............... None
torch hip version ................ 5.6.31061-8c743ae5d
nvcc version ..................... None
deepspeed wheel compiled w. ...... torch 2.2, hip 5.6
shared memory (/dev/shm) size .... 500.00 GB

@xxtars - can you please share the command you are running that produces the error?

@xxtars Sorry for the lack of updates. We are actively looking into this issue and should have an update by next week.

@loadams Initially, I was using transformers with deepspeed zero2_offload when I encountered llama-vid. Upon starting the compilation, this warning appeared. After seeing this issue, I conducted the same test and received the same warning.
import torch
from deepspeed.ops.adam import DeepSpeedCPUAdam
fused_adam = DeepSpeedCPUAdam([torch.rand(10)])

yields [WARNING] cpu_adam cuda is missing or is incompatible with installed torch, only cpu ops can be compiled!

@xxtars Sorry for the lack of updates. We are actively looking into this issue and should have an update by next week.

Thanks for any help.

Hello, any update on this ?  I am also working on MI250 GPUs (4) and I am using HF transformers with deepspeed zero 2 stage to train mistral-7B.

DS report output :

DeepSpeed C++/CUDA extension op report
--------------------------------------------------
NOTE: Ops not installed will be just-in-time (JIT) compiled at
      runtime if needed. Op compatibility means that your system
      meet the required dependencies to JIT install the op.
--------------------------------------------------
JIT compiled ops requires ninja
ninja .................. [OKAY]
--------------------------------------------------
op name ................ installed .. compatible
--------------------------------------------------
 [WARNING]  async_io requires the dev libaio .so object and headers but these were not found.
 [WARNING]  async_io: please install the libaio-devel package with yum
 [WARNING]  If libaio is already installed (perhaps from source), try setting the CFLAGS and LDFLAGS environment variables to where it can be found.
async_io ............... [NO] ....... [NO]
fused_adam ............. [NO] ....... [OKAY]
cpu_adam ............... [NO] ....... [OKAY]
cpu_adagrad ............ [NO] ....... [OKAY]
cpu_lion ............... [NO] ....... [OKAY]
 [WARNING]  Please specify the CUTLASS repo directory as environment variable $CUTLASS_PATH
evoformer_attn ......... [NO] ....... [NO]
fp_quantizer ........... [NO] ....... [OKAY]
fused_lamb ............. [NO] ....... [OKAY]
fused_lion ............. [NO] ....... [OKAY]
inference_core_ops ..... [NO] ....... [OKAY]
cutlass_ops ............ [NO] ....... [OKAY]
transformer_inference .. [NO] ....... [OKAY]
quantizer .............. [NO] ....... [OKAY]
ragged_device_ops ...... [NO] ....... [OKAY]
ragged_ops ............. [NO] ....... [OKAY]
random_ltd ............. [NO] ....... [OKAY]
 [WARNING]  sparse_attn is not compatible with ROCM
sparse_attn ............ [NO] ....... [NO]
spatial_inference ...... [NO] ....... [OKAY]
transformer ............ [NO] ....... [OKAY]
stochastic_transformer . [NO] ....... [OKAY]
--------------------------------------------------
DeepSpeed general environment info:
torch version .................... 2.3.1+rocm5.7
deepspeed info ................... 0.14.4, unknown, unknown
torch cuda version ............... None
torch hip version ................ 5.7.31921-d1770ee1b
nvcc version ..................... None
deepspeed wheel compiled w. ...... torch 2.3, hip 5.7

Thank you in advance :)

FYI @jithunnair-amd or @rraminen - I know we have an outstanding issue with CPUAdam here


Webhooks for time tracker

Feature Description
We like to practice timeboxing when handling issues, would be great to have time tracker changes fire webhooks, then we know when to take further action, e.g. send reminders etc
Screenshots
No response

seems to be a duplicate of #18582


Build actions for Mac

We need to make a build github actions to automate the process of generating executable files for Mac

Done


remove all v1 related content

/assign @gabemontero
our Makefile and CI jobs were already ignoring v1 (which is too bad, i was hoping we could speed them up by removing the v1 build/test step)

do we want to delete the openshift/imagestream json file references?

There is also this comment in the Makefile:  :# the image name (jenkins-1-centos7 in this case).  For the slave

do we want to delete the openshift/imagestream json file references?

no, we can never remove those.  People can still have resources that reference that imagestream tag.

There is also this comment in the Makefile: :# the image name (jenkins-1-centos7 in this case). For the slave

fixed

/lgtm


Updated dependencies

Removed flutter_test

This was preventing me from building Syrius

Updated reference to znn_sdk_dart

Related to https://github.com/zenon-network/znn_sdk_dart/pull/11

Not sure if this is related to this particular change, but I was not able to build syrius on Windows. Did a clean pull of the repo and changed the znn_sdk_dart dependency to alienc0der's master branch. The build fails with the following message.
Building Windows application...                                   152,9s
Build process failed.

I'm using the latest version of Flutter.
Flutter 3.10.6 • channel stable • https://github.com/flutter/flutter.git
Framework • revision f468f3366c (3 weeks ago) • 2023-07-12 15:19:05 -0700
Engine • revision cdbeda788a
Tools • Dart 3.0.6 • DevTools 2.23.1

That's strange. I effectively did the same thing before submitting this PR.
I'm using the same version of Flutter on Windows.
I've merged the SDK dependency PR and attempted to build this version of Syrius; without any modifications, it worked on my machine and with the Github Workflow.
Can you please post a more specific build error?

I have submitted another PR to fix the dependencies and bring them up to date with the Dart SDK.


deleted post shows empty body

before a feed is updated to remove a deleted post, the post displays with empty body (except friendica where it's stubbed to just return the pre-deleted post)

now showing deleted


Have the SSPR columns been updated for the converged 'Authentication Methods' experience?

I completed the migration described at How to migrate MFA and SSPR policy settings to the Authentication methods policy for Azure AD and everything appears to be working, including MFA and SSPR, but all of the reporting makes it appear as if SSPR is disabled.
This is all very, very confusing.

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

ID: cf2e7f7f-792d-3063-b672-f54f1e769cf3
Version Independent ID: fca17480-6c8d-d067-1469-2771953de47e
Content: Authentication Methods Activity - Microsoft Entra
Content Source: articles/active-directory/authentication/howto-authentication-methods-activity.md
Service: active-directory
Sub-service: authentication
GitHub Login: @sopand
Microsoft Alias: justinha

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

@npiasecki
It seems that you have completed the migration process for MFA and SSPR policy settings to the Authentication methods policy for Azure AD. However, the reporting makes it appear as if SSPR is disabled.
To troubleshoot this issue, you can try the following steps:
Check if the SSPR policy is enabled in the Authentication methods policy. You can do this by signing in as an Authentication Policy Administrator and going to Azure Active Directory > Security > Authentication methods > Policies
Check if the SSPR policy is enabled for the user or group that you are testing with. You can do this by going to Azure Active Directory > Password reset > Registration
Check if the user or group that you are testing with has been excluded from using SSPR. You can do this by going to Azure Active Directory > Password reset > Registration
If you are still experiencing issues after trying these steps, I'd recommend working closer with our support team via an [Azure support request] (https://docs.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request).
Thank you for your time and patience throughout this issue.

@npiasecki
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

@ManoharLakkoju-MSFT Thank you for your reply.
I checked this morning, and without making any changes since completing the migration, suddenly SSPR shows as Enabled for everyone.
So there must have been a lag of several hours to several days in the SSPR reporting, which I guess is typical of most things in the Microsoft Cloud, where you make a change and wait a few hours to see if anything happens.
It could be helpful to clarify with the team what the reporting delay typically is and mention it in the article, but otherwise I guess it is working as expected.
Thank you.


"skull_skin" in item script

# "op_" is the prefix of my options scripts

op_back:
    type: item
    material: SKULL_ITEM,3
    skull_skin: MHF_ArrowLeft
    display name: "<&7><&l>Back"

... does not show up with the skin in my GUI and in my inventory.
/ex give i@op_back[skull_skin=MHF_ArrowLeft] works.
But I want to set the skin directly in the item script.

No such item script key ( http://mcmonkey.org/denizen/lngs/item script containers )
You can do material: human_skull[skull_skin=MHF_ArrowLeft]

@mcmonkey4eva Ok, I thougt I can use any dItem mechanism in item scripts.

@mcmonkey4eva Why human_skull? Is this an alias implemented in Denizen? I can't see it on the Spigot Documentation.

Yes, Denizen has its own special list of items to handle the potential (Threatened by Mojang) future loss of datavalues.


Small typo in: Modelica.Mechanics.MultiBody.Sensors

Reported by adrpo on 29 Nov 2008 03:13 UTC
Am I mistaking or the model:
Modelica.Mechanics.!MultiBody.Sensors.TansformAbsoluteVector

should be:
Modelica.Mechanics.!MultiBody.Sensors.TransformAbsoluteVector

?
Cheers,
Adrian Pop/

Migrated-From: https://trac.modelica.org/Modelica/ticket/130

Comment by dietmarw on 9 Jan 2009 05:48 UTC
I think this should be fixed for the [milestone:MSL3.0.1 3.0.1 release].

Comment by dietmarw on 21 Jan 2009 09:35 UTC
Fixed in 7cf80992038f181187ddc65a1021104607d10856. All occurrences replaced.

Comment by dietmarw on 22 Jan 2009 08:35 UTC
I completely forgot about backward compatibility (thanks Martin for reminding and reverting).
All changes made in 7cf80992038f181187ddc65a1021104607d10856 and 9e2ce0ab10ba5d343621ab2281df6d3d6806a038 (a partly revert by Martin) are reverted in 189fb58ad7dfa2febf2f7565a7c569661c26bece.
Once the next backward compatible version is to come (probably milestone:MSL3.1) the necessary changes to fix this can be found in the attached [attachment:fixticket130.patch patch].

Comment by otter on 21 Jun 2009 09:58 UTC
Will be fixed for the next MSL version that is not backward compatible and requires conversion scripts.

Comment by dietmarw on 21 Jun 2009 14:30 UTC
I'd guess the earliest non-backward compatible version can only be 3.2 but not 3.1.1

Comment by dietmarw on 28 Feb 2010 17:42 UTC
Looks like the next version with conversion script will be milestone:MSL4.0. Therefore rescheduling.

Modified by dietmarw on 28 Feb 2010 17:45 UTC

Comment by dietmarw on 11 Sep 2012 16:43 UTC
FIXED in b399658cfc5ff52fd9e2b6b61ac6e4534fd9fbd8 in a backward compatible way.
TODO remove obsoleted models -> see #813

Changelog removed by dietmarw on 11 Sep 2012 16:43 UTC


tour: "Exercise: Images" should have a link to the previous image generation

Context: https://tour.golang.org/methods/25
It should have a link to: https://tour.golang.org/moretypes/18
In "Remember the picture generator you wrote earlier?"

Done in 03133cc9684f0d84f4b533c0b064683d8822e587. Closing.


drw vs carma psd

The drw and carma PSD normalization seems to offset by a factor of np.sqrt(2).

only when there is a second lorentzian?

also underflow encountered here:
https://github.com/ywx649999311/EzTao/blob/931127cb6adc539523064bce2a7c784dafb00d66/src/eztao/carma/model_utils.py#L119


[core] include<EMAIL_ADDRESS>for<EMAIL_ADDRESS>

Fixes #5646
React 15.4 requires the minimum version for react-tap-event-plugin to be 2.0.1.
The restriction was a bit lenient previously (which would fail with react 15.4), so hopefully raising the restriction exposes any other conflicts that were previously hidden.  The react version will be raised to 15.4 as well.

[x] PR has tests / docs demo, and is linted.
[x] Commit and PR titles begin with [ComponentName], and are in imperative form: "[Component] Fix leaky abstraction".
[x] Description explains the issue / use-case resolved, and auto-closes the related issue(s) (http://tr.im/vFqem).

Checking out error circleci now.  Did not have an issue locally.

@rosskevin Thanks


Unable to make an NVM backup, the backup freezes

Checklist

[X]  I am not using Home Assistant. Or: a developer has told me to come here.
[ ] I have checked the troubleshooting section and my problem is not described there.
[ ] I have read the changelog and my problem is not mentioned there.

Deploy method
Home Assistant Add-on
Z-Wave JS UI version
9.20.0
ZwaveJS version
plugin Jeedom 2024-11-16 01:03:20
Describe the bug
the backup starts then freezes after a few seconds
Home automation JEEDOM  4.4.19 with VM Debian 12 on NAS QNAP (virtualization station), USB key aeotec Z-Stick Gen5 SDK 6.81 firware 1.2
Everything works well except the possibility of making an NVM backup from the ZwaveJS-UI interface
Please find logs in attachment and a screenshot
To Reproduce
Other users in jeedom community have related this problem to backup NVM but no solution has been found
They used PC simplicity studio and PC controller but it's not so simple
Expected behavior
Have a backup NVM is interrested for me to restore on a new key 700 serial
Additional context
Archive.zip

@AlCalzone Works on my side
FW: v1.2
SDK: v6.81.6

So the problem is likely caused by the VM USB setup.
@roazhon do you have the possibility to create the backup on a different computer? E.g. by downloading and running one of the precompiled binaries from https://github.com/zwave-js/zwave-js-ui/releases/tag/v9.27.3 ?

hello, thank you for support... I will try to test on a windows pc the windows binary by following this process "How to Run Z Wave JS UI as a Windows Service" https://www.youtube.com/watch?v=6GD-DrpDdXo , could you confirm that this process works ?

Windows might need additional drivers for the stick. Check aeotec's website if you find something.

Drivers are installed, my AEOTEC key is detected on device manager on COM3 call UZB

Then just enter COM3 as the port.

Thanks for the update. Since this seems to be caused by something external (probably VM config), I'll close this issue as there's not much we can do about it.


README: archive project

This hasn't seen any activity in a while and there are no plans to
continue development.
[skip ci]

/skip

[skip ci]

/refresh


feat: create user and team tables in drizzle

Linting issues sort kr k merge kr dena

Could not fix the format issues, were already in main, will fix them eventually in subsequent prs.


Integrate EFR32 OTA Requestor app with the Generic Requestor Driver

Problem
EFR32 OTA Requestor app needs to be integrated with the Generic Requestor Driver
Change overview
Replace the OTARequestorDriverImpl class with DeviceLayer::GenericOTARequestorDriver
Testing
Verified successful build of the EFR32 OTA Requestor

Fast tracking as all the changes are confined to EFR32


🐞 [BUG] -

Issue Verification

[X] I have verified that this is a new bug report.
[X] I'm interested in working on this issue
[X] I'm part of GSSOC organization

Describe the bug
This website is not completely responsive.

Expected behavior
I can update this website into fully responsible for all devices.
Steps to reproduce
No response
Additional Context
No response

Duplicate issue. Please take a look at related issues


Dockerfile

Instead of running GO locally in dev environment with Make and relying on local system the build should be completed by using a Dockerfile , this way you will be able to build it anywhere that has standard docker installed
docker build -f Dockerfile . -t iconloop/rosetta-icon:latest

This should build entire process within container instead of locally, once its build you can use your docker-compose to run your node (will need to update docker-compose with correct naming for tag above)

We are considering it, but due to internal circumstances, we will not be able to apply the advice and will guide you to use our docker-compose.


Words of encouragement

Hi!
I just wanted to tell you that I can't wait to see this project at a finished state! I'm very familiar with python but not with javascript and even less with clojure so I've been waiting for solutions like yours to add more python to logseq :)
Cheers!

+1 - this looks really exciting!

Thank you! I have been away from computing/computers in general - but started using Logseq again and felt the need for some of my older plugins so checked the repo out to find your welcome words of encouragement :)


Chess: Move D8 to A5

My move

@JustinBui Whaaaat? The move d8a5 is invalid!
Maybe someone squeezed a move before you. Please try again.


Roxygen run + utils.R updates for issue #28

RE: #28
Looks like line endings got caught up in this (you're probably working on win / I'm on nix)
Files actually updated:

DESCRIPTION (Adding dplyr)
NAMESPACE (Adding dplyr)
Roygen updates
R/elasticsearch.R (for importFrom)
L404 of R/utils.R

Why this is not merged yet? Thanks a lot for the fixes! 🚀

My apologies - this completely fell off of my radar (I started a new job around the time this was originally submitted and I have been a bit saturated since then).
Am I right in thinking that there are only two line changes in the above?

I have moved this to a new PR - #52 - that container only those files that need to be changed.

I re ran roxygen with most recent version as no one had run it and if I
recall some pieces of docs were not in Rd format/missing. I did it with
intent. Although now I can't remember why.
On Fri, Jul 26, 2019, 4:44 AM Alex Ioannides<EMAIL_ADDRESS>wrote:

Closed #49 https://github.com/AlexIoannides/elasticsearchr/pull/49.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/AlexIoannides/elasticsearchr/pull/49?email_source=notifications&email_token=AADG7Y335RXZHKO2KGMESCDQBLBRJA5CNFSM4G5HMGFKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOSW5NWYA#event-2512051040,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADG7YZ3X64ZAANHIKPV5ALQBLBRJANCNFSM4G5HMGFA
.

This fix has been merged in #52 and submitted to CRAN as v0.3.1.


helm upgrade --install does not respect --namespace flag

I have a somewhat similar situation to https://github.com/kubernetes/helm/issues/2764 but basically I'm trying to install a chart via helm upgrade --install and do so in a specific namespace with the --namespace namespace flag, but it still only installs it into the default namespace.
I suppose even the linked PR won't fix my issue as I manually set the namespace of my kube context and it still installs it into default

I believe the linked issue is the exact same problem as described here. Can you please post there instead so we can keep it all in one ticket? Thanks.

Thank you for your response. I believe the linked issue talks about the behavior in absence of the --namespace flag. In my case, I'm explicitly specifying it?

It's the same code path and would be solved in the same PR, I'd believe. In this specific case I think it's fine to keep it in the same ticket for tracking helm upgrade --install namespace issues.

Got it!

I don't believe this was resolved with PR #2808 I'm having this exact issue with v2.6.1
eg helm upgrade --install --namespace andrew -f foo.yaml andrew . installs into the default namespace.

@macropin I could not reproduce this issue.
$ helm version
Client: &version.Version{SemVer:"v2.6.2", GitCommit:"be3ae4ea91b2960be98c07e8f73754e67e87963c", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.6.2", GitCommit:"be3ae4ea91b2960be98c07e8f73754e67e87963c", GitTreeState:"clean"}
$ helm upgrade --install --namespace foo ingressctl stable/nginx-ingress
Release "ingressctl" does not exist. Installing it now.
NAME:   ingressctl
LAST DEPLOYED: Mon Oct 16 21:48:39 2017
NAMESPACE: foo
STATUS: DEPLOYED

@bacongobbler after further investigation it looks like my issue is actually #3037. Helm reuses the namespace from the first revision of the release. helm delete <release> does not remove this reference. helm delete <release> --purge must be used before releasing into a different namespace.
I'm not sure if this is further evidence of a bug, or my misunderstanding of how helm retains configuration data.

This isn’t the first time I've heard about the confusing behaviour between helm delete with and without the —purge flag. It is working as intended, though “as intended” does not seem to match many user’s understanding.
You are absolutely right in that you were bitten by #3037. Let’s carry the conversation there. :)


Implement TypeScript Calculator Namespace with Basic Arithmetic Operations

This pull request introduces a TypeScript implementation of a simple calculator within the Calculator namespace. The calculator provides basic arithmetic operations including addition, subtraction, multiplication, and division. Each operation is implemented as a function within the namespace, ensuring type safety and proper handling of edge cases.
Changes:
Added a TypeScript file named calculator.ts in the tasks/typescript/medium directory.
Implemented the Calculator namespace with four methods: add, subtract, multiply, and divide.
Each method performs its respective arithmetic operation and returns the result.
The divide method checks for division by zero and returns null along with a warning message if encountered.
Included test cases to verify the correctness of each arithmetic operation.
Updated the README.md file with instructions on testing the solution.
Testing:
Ran the provided test command npx ts-node tasks/typescript/medium/calculator.ts.
Verified that the tests returned the expected values:
Addition: 8
Subtraction: 2
Multiplication: 15
Division: Approximately 1.666...
Division by zero: Warning message & null
This implementation satisfies the requirements outlined in the task and ensures a type-safe and functional calculator for basic arithmetic operations in TypeScript.

Merged

This is an automated message from Fork, Commit, Merge [BOT].

Thank you for your contribution! Your pull request has been merged. The files have been reset for the next contributor.
What's next?
If you're looking for more ways to contribute, I invite you to check out our forkcommitmerge.io website repository. The repository contain real issues that you can help to resolve or create some of your own if you see any bugs or want to add new features to the site, etc. You can also check out the Influences section in the README to find more projects similar to this one.
Also please leave a star to this project if you feel it helped you, i would really appreciate it.
I look forward to seeing your contributions!


not able to run docker registry:2

Hi,
I am trying to run very simple command, as root user
docker run -d -p 5000:5000 --name registry registry:2
The command end up with an error.
a4f511dceec1118ad215d77d67a890a0520cb82b80047415f4767641b704aac8
docker: Error response from daemon: OCI runtime create failed: container_linux.go:346: starting container process caused "process_linux.go:449: container init caused "rootfs_linux.go:58: mounting \"proc\" to rootfs \"/var/lib/docker/overlay2/d5d0325412378699c72901f8240877a3e2c7c13b824cc4d98933826ed80d7310/merged\" at \"/proc\" caused \"permission denied\""": unknown.
docker details:
docker version
Client: Docker Engine - Community
Version:           19.03.5
API version:       1.40
Go version:        go1.12.12
Git commit:        633a0ea838
Built:             Wed Nov 13 07:50:12 2019
OS/Arch:           linux/amd64
Experimental:      false
Server: Docker Engine - Community
Engine:
Version:          19.03.5
API version:      1.40 (minimum version 1.12)
Go version:       go1.12.12
Git commit:       633a0ea838
Built:            Wed Nov 13 07:48:43 2019
OS/Arch:          linux/amd64
Experimental:     false
containerd:
Version:          1.2.10
GitCommit:        b34a5c8af56e510852c35414db4c1f4fa6172339
runc:
Version:          1.0.0-rc8+dev
GitCommit:        3e425f80a8c931f88e6d94a8c831b9d5aa481657
docker-init:
Version:          0.18.0
GitCommit:        fec3683

This is a docker issue, rather than registry issue, I'm afraid. Please ask in moby/moby. Closing.


Should wrap try/catch

https://github.com/anchan828/nest-cloud-run-pubsub/blob/1abbc782056af547b07ed73e11b4329c299ca807/packages/worker/src/worker.controller.ts#L47

close https://github.com/anchan828/nest-cloud-run-pubsub/commit/2b860745bef24121d202376b9f5742a231ada6b2


SIGUSR1, SIGUSR2 and SIGPOLL should be excluded from signal handling.

SIGUSR1, SIGUSR2 and SIGPOLL should be excluded from signal handling.

Good point.


add action for releasing new docker image

add action for releasing new docker image
add todo

#640  👈
529_fix_dockerfile_add_test_gcroci2

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @gcroci2 and the rest of your teammates on  Graphite

I have not tested the new install instructions yet. Are these something I can test already, or only after the workflow has triggered at least once?

During the development I tested them on this branch (by changing the settings in the yml workflow), but as it is now it can't be directly tested. I plan to do a new release as soon as this PR is merged so we can be sure it all works fine, and worst case I'll open immediately a new issue.

Has the new workflow/changes to existing workflows been tested? If not, is there any way to do so before merging (without having to make a fork and release that on PyPi as well)?

There is no straightforward way. I'll try now to solve the merge conflicts paying attention, but then we will know for sure only with the first real release will be triggered.


Improvements to reveng on SQLite

Add nullable reverse typemapping.
Remove detection of "AUTOINCREMENT" -- this annotation is really only for migrations.
Detect Unique columns before adding foreign keys.
Assign uniqueness to foreign keys.
Add more functional testing.
#2820

:shipit: Looks good.


Added createEmote

The RestAction return type should be an Emote, no?

I thought the discord API would not return the emoji object but was wrong.


Clip rnn gradients in a chunk-wise manner

This PR aims to clip the rnn gradients in a chunk-wise manner, to solve the gradient explosion problem in the backward pass.
When computing each chunk, we clip the gradients of hidden states and cell states which are passed between chunks.
The gradient clipping strategy applied on hidden states and cell states is as follows:

If the gradient norm is lager than a specific threshould, we directly zero the gradients.
Scaling down the gradient by a factor of 0.9.
Limit the gradient norm to a maximum.

Now I am running the experiements with following options:

--rnn-clip-grad 1 --rnn-chunk-size 20 --rnn-grad-scale-factor 1.0 --rnn-grad-max-norm 0.5
--rnn-clip-grad 1 --rnn-chunk-size 20 --rnn-grad-scale-factor 1.0 --rnn-grad-max-norm 1.0
--rnn-clip-grad 1 --rnn-chunk-size 20 --rnn-grad-scale-factor 1.0 --rnn-grad-max-norm 2.0


[epic] Consolidate explorer code and components in this repo

Goal: core react components for data previewing and the explorer are in this repo and well documented.
My guess is we start with "docs driven" development showing how we would do a table preview in case X.
Background: https://tech.datopian.com/views/
Acceptance

[x] We have React components (or docs) for views e.g. ... Fixed See https://github.com/datopian/portal.js/tree/main/src/components

[x] Table view / explorer
[x] Graph
[ ] Map

[x] We have the builder components
[x] We have examples of how to connect this with data sources Fixed https://github.com/datopian/portal.js/tree/main/examples

Tasks

[x] Research merging Done https://hackmd.io/@risingodegua/BJpBEPrPu

[x] github.com/frictionlessdata/datapackage-transform-js
[x] github.com/datopian/datapackage-views-js
[x] github.com/datopian/data-explorer

@rufuspollock @anuveyatsu I did some analysis of this issue in this hackmd: https://hackmd.io/@risingodegua/BJpBEPrPu
Would love to hear your thoughts.

@risenW great!  Looks good and left a few comments as blockquotes. Please feel free to move forward on a recommendation on approach plus updated acceptance criteria and a set of tasks and estimate ...

@risenW great! Looks good and left a few comments as blockquotes. Please feel free to move forward on a recommendation on approach plus updated acceptance criteria and a set of tasks and estimate ...
@anuveyatsu @risenW my question here is whether we want to start consolidating components either as components in the package or as sub-packages a monorepo here rather than having stuff in multiple repos elsewhere. This would be similar to how next does stuff, see e.g. here https://github.com/vercel/next.js/tree/canary/packages where they have a bunch of packages plus components ...
packages/
   portal-chartbuilder
   portal-graphbuilder
   portal-views

Similar to how next.js have next-mdx or next-image

In regards to this. I like the idea of consolidating those repos into the packages folder just like nextjs. I think it's cleaner and will be easier to manage/update going forward.

@risenW can you update on status here with a comment - i think you have also updated the description. I also suggest you merge your hackmd stuff into the description as an analysis section.

@risenW can you update on status here with a comment - i think you have also updated the description. I also suggest you merge your hackmd stuff into the description as an analysis section. (and please suggest what would be next steps if any)

This is all done, besides the Map component. I don't think we need that atm. maybe someday

@risenW can you also update acceptance with links on each item to component, the docs for it and a description of what happened. That would really help me understand what happened (since it was a while ago).
/cc @anuveyatsu

@risenW can you also update acceptance with links on each item to component, the docs for it and a description of what happened. That would really help me understand what happened (since it was a while ago).
/cc @anuveyatsu

@rufuspollock Done

@risenW can this be closed now?

@risenW can this be closed now?

Yes!


[backport] Add Google Colaboratory installation steps and link to community examples

Backport of #5446

[automatic post] Jenkins, test this please.

Jenkins CI test (for commit a2ddaedf20d9e5d5be818f8931bc6460a2aa9532, target branch v5) succeeded!

LGTM!


Add possibility to input multiple sentences

In order to be able to fully benefit from parallelization, I propose to add the possibility to input the sentences into the transformer models by batch.
The work is not finished yet and I still have to pass the CI test (I will proceed as you suggest in #3) but it is working and would like to have your opinion before going further.
In order to make minimal change to your code, for now tokens_score return a list of log_probs, ids, tokens (one item for each sentence). However, it would be much more efficient to make the reduction when we still have the log_probs scores as a tensor. One possibility would be that _tokens_log_prob now return a tensor of shape (number sentences, max sentences length). What do you think of that ?
Also, I did not use the pad_sequence function from torch.nn.utils.rnn but recode it in order that it returns a mask (with 1 at the place of the padding value) which is useful latter in the code to remove the score from padding value. I think this function should not be in GPT2LMScorer class but somewhere else.

I have taking into account all your comments. There is still one typing issue, however not sure how to resolve this one. Am i supposed to use a # type ignore or is there an other possibility ?

Am i supposed to use a # type ignore or is there an other possibility ?

No, it is correctly pointing out a bug in the code

Will add some more tests concerning this new batch features in test_gpt2.

Would you mind if I ask you to split this PR in two?
It would be convinient to have a first PR (we can use this one) with the API changes + GPT2 implemented as just a for loop on the old single sentence code.
Then the second PR will actually optimize GPT2 using batching.
So we have the new API merged for #3

@dldk-gael Thanks!

No problem and thank you for your patience, I was not familiar with all those tools and good practices, I learned a lot from your code.


rc_reason_clients: 0.3.0-1 in 'galactic/distribution.yaml' [bloom]

Increasing version of package(s) in repository rc_reason_clients to 0.3.0-1:

upstream repository: https://github.com/roboception/rc_reason_clients_ros2.git
release repository: https://github.com/roboception-gbp/rc_reason_clients-release.git
distro file: galactic/distribution.yaml
bloom version: 0.10.7
previous version for package: 0.2.1-1

rc_reason_clients
* add rc_cadmatch_client and rc_load_carrier_client
* use refactored and updated rc_reason_msgs
* replace deprecated set_parameters_callback with add_on_set_parameters_callback

rc_reason_msgs
* refactor and update for v22.01

Holding for Galactic Sync


1.8 reorder eventloop wip

Enter [N/A] in the box, if an item is not applicable to your change.
Testing
Before we can approve your change; please submit the following in a comment:

[ ] Example configuration file for the change
[ ] Debug log output from testing the change

[ ] Attached Valgrind output that shows no leaks or memory corruption was found

Documentation

[ ] Documentation required for this feature

Fluent Bit is licensed under Apache 2.0, by submitting this pull request I understand that this code will be released under the terms of that license.

Note: Need to add support for fluent_bit library mode


feature: saga statemachine designer online demo

Provide an online demo of Saga StateMachine Designer

Would you please add a menu here ?


Flickering with deoplete

When used in conjunction with deoplete I get constant cursor flickering. This flickering disables when I disable tmux-complete so I'm pretty certain this plugin is the cause of it. I'm wondering why tmux-complete causes this however, is it because gathering candidates is slow?

@rgrinberg: Thanks for opening this issue, I've had noticed similar problems myself before.
Usually it is related to gathering candidates, especially if you have many tmux sessions and windows open, it can take a noticeable time to process all visible words. There are already some settings
g:tmuxcomplete#capture_args
g:tmuxcomplete#list_args

which can be used to control which sessions, windows and what scrollback to consider. I think most of these issues could be resolved by limiting the search space used for live autocompletion. For on demand completion a slightly longer delay is usually acceptable, that's why this wasn't always a priority.
Unfortunately these settings are currently not documented and I take this issue as motivation to do that. I'm planning to include some best practices to help with issues like the one you're seeing.
Unfortunately I can't promise that I'll come to this soon, but I'll definitely put it on my list :+1:
--
Side note: Maybe it's even possible to do all that processing in the background with Neovim, but I'm not too familiar how that would be done. If anyone would have some pointers that might give me a head start.

This may have been alleviated by https://github.com/Shougo/deoplete.nvim/commit/2f6f7b96984729544f57a4c48c241ef9f1c97951
@rgrinberg Can you confirm/deny?

I am using g:deoplete#auto_complete_delay = 50 (or 100), but it's still noticable.
Profiling shows this:
FUNCTION  tmuxcomplete#completions()
Called 12 times
Total time:   1.172690
 Self time:   1.172442
count  total (s)   self (s)
   12              0.000068     let pattern   = '^' . escape(a:base, '*^$][.\') . '.'
   12              0.000051     let list_args = get(g:, 'tmuxcomplete#list_args', '-a')
   12   0.000341   0.000093     let grep_args = tmuxcomplete#grepargs(a:base)

   12              0.000075     let command  =  'sh ' . shellescape(s:script)
   12              0.000048     let command .= ' -p ' . shellescape(pattern)
   12              0.000045     let command .= ' -s ' . shellescape(a:splitmode)
   12              0.000038     let command .= ' -l ' . shellescape(list_args)
   12              0.000043     let command .= ' -c ' . shellescape(a:capture_args)
   12              0.000041     let command .= ' -g ' . shellescape(grep_args)

   12              0.000029     if $TMUX_PANE !=# ""     " if running inside tmux
   12              0.000040         let command .= ' -e' " exclude current pane
   12              0.000010     endif

   12              1.163400     let completions = system(command)
   12              0.000178     if v:shell_error != 0
                                    return []
                                endif

   12              0.008093     return split(completions, '\n')

I could imagine that it would be better already when
rplugin/python3/deoplete/sources/tmuxcomplete.py would not call the Vim
function, but do the job itself.
And then it's also a matter of configuration probably: I would like to use the tmux completion on demand only, and not on-the-fly all the time.


Can't Configure

In a new directory, I'm trying to
theme configure <API_KEY> <PASSWORD> <STORE>
and I'm getting this error
'configure': undefined method 'to_yaml' for #<Hash:0x007feeaae61ea0> (NoMethodError).
I'm not sure what I need to do here.

What version of ruby are you running?

ruby 2.1.4p265 (2014-10-27 revision 48166) [x86_64-darwin14.0]

I'm having the same issue (i think):
/Library/Ruby/Gems/2.0.0/gems/shopify_theme-0.0.21/lib/shopify_theme/cli.rb:50:in configure': undefined method to_yaml' for #Hash:0x007f9a4b48c2f8 (NoMethodError)
from /Library/Ruby/Gems/2.0.0/gems/thor-0.19.1/lib/thor/command.rb:27:in run' 	from /Library/Ruby/Gems/2.0.0/gems/thor-0.19.1/lib/thor/invocation.rb:126:in invoke_command'
from /Library/Ruby/Gems/2.0.0/gems/thor-0.19.1/lib/thor.rb:359:in dispatch' 	from /Library/Ruby/Gems/2.0.0/gems/thor-0.19.1/lib/thor/base.rb:440:in start'
from /Library/Ruby/Gems/2.0.0/gems/shopify_theme-0.0.21/bin/theme:24:in <top (required)>' 	from /usr/bin/theme:23:in load'
from /usr/bin/theme:23:in `'

I ended up manually writing out the config.yml file, but now receive the following error when trying: theme upload
$ theme upload
/Library/Ruby/Gems/2.0.0/gems/shopify_theme-0.0.21/lib/shopify_theme.rb:101:in config': private method load' called for Psych:Module (NoMethodError)
from /Library/Ruby/Gems/2.0.0/gems/shopify_theme-0.0.21/lib/shopify_theme.rb:122:in whitelist_files' 	from /Library/Ruby/Gems/2.0.0/gems/shopify_theme-0.0.21/lib/shopify_theme/cli.rb:191:in block in local_assets_list'
from /Library/Ruby/Gems/2.0.0/gems/shopify_theme-0.0.21/lib/shopify_theme/cli.rb:190:in reject' 	from /Library/Ruby/Gems/2.0.0/gems/shopify_theme-0.0.21/lib/shopify_theme/cli.rb:190:in local_assets_list'
from /Library/Ruby/Gems/2.0.0/gems/shopify_theme-0.0.21/lib/shopify_theme/cli.rb:101:in upload' 	from /Library/Ruby/Gems/2.0.0/gems/thor-0.19.1/lib/thor/command.rb:27:in run'
from /Library/Ruby/Gems/2.0.0/gems/thor-0.19.1/lib/thor/invocation.rb:126:in invoke_command' 	from /Library/Ruby/Gems/2.0.0/gems/thor-0.19.1/lib/thor.rb:359:in dispatch'
from /Library/Ruby/Gems/2.0.0/gems/thor-0.19.1/lib/thor/base.rb:440:in start' 	from /Library/Ruby/Gems/2.0.0/gems/shopify_theme-0.0.21/bin/theme:24:in <top (required)>'
from /usr/bin/theme:23:in load' 	from /usr/bin/theme:23:in '

The lastest psych (2.0.13) seems to be buggy. Try Version 2.0.0 – works for me.
gem uninstall psych
gem install psych -v 2.0.0

I'm unable to replicate the issue. According to the comment by @dommmel you can try using psych:2.0.x and should be fine.
I used a Gemfile to try and force psych:2.0.13 but couldn't replicate the issue.

I've since bought a new machine without any problems. Sure I had a conflict
somewhere or something was outdated.
On Mon, Aug 31, 2015 at 10:24 PM Christopher Saunders <
<EMAIL_ADDRESS>wrote:

I'm unable to replicate the issue. According to the comment by @dommmel
https://github.com/dommmel you can try using psych:2.0.x and should be
fine.
I used a Gemfile to try and force psych:2.0.13 but couldn't replicate the
issue.
—
Reply to this email directly or view it on GitHub
https://github.com/Shopify/shopify_theme/issues/133#issuecomment-136488843
.


Index Corruption During Large Import

Describe the bug
We regularly import a large jtl file post test (we've previously discussed importing/feeding the file during the test but this is not possible).  But the import seems to work just fine however, we have recently increased our load profile meaning the jtl file has jumped from 800mb to 1gb and as a result we are seeing an index corruption message in the BE logs.
{"level":"error","message":"Error occurred during data parsing and saving into database: error: index \"_hyper_1_14_chunk_samples_item_idx\" contains unexpected zero page at block 28401, item_id: fb38060d-63a9-4703-b278-5a972734d624"}
We have reindexes this index and tried to import again and it fails with the same error message.
To Reproduce
Try and import a large (>1gb) jtl file
Expected behavior
The jtl file to successfully upload.
Screenshots

Hi @kierangirvan
what version do you run?

Looks like v4.10

Thanks. My advice would be to try to upgrade to v5 as this uses a newer version of timescaledb.
But to be fair, I have no idea, whether this going to solve your problem or not :|

We've decided to completely rebuild the service (unfortunately meaning we lose our previous tests), but this seems to have introduced a new issue:
{"level":"error","message":"Error occurred during samples aggregation in database: Error while processing dataId: 28f5f5c9-ac17-455d-9e97-49e4f7e50530 for item: 28f5f5c9-ac17-455d-9e97-49e4f7e50530, error: error: function lttb(timestamp with time zone, integer, unknown) does not exist, item_id: 28f5f5c9-ac17-455d-9e97-49e4f7e50530"}

What kind of database image do you use? it looks like you are not using the one from here https://github.com/ludeknovy/jtl-reporter/blob/main/db/Dockerfile

My cloud engineer shared the following from our AWS hosted jtl reporter, this is the same as my local install:
postgres=# \dx                                                List of installed extensions     Name     | Version |   Schema   |                                     Description -------------+---------+------------+-------------------------------------------------------------------------------------- plpgsql     | 1.0     | pg_catalog | PL/pgSQL procedural language timescaledb | 2.14.2  | public     | Enables scalable inserts and complex queries for time-series data (Apache 2 Edition) uuid-ossp   | 1.1     | public     | generate universally unique identifiers (UUIDs)

lttb function missing means, you dont have the timescale db toolkit installed.
If you use the FROM timescale/timescaledb-ha:pg16.4-ts2.16.1-all, then you dont have to do anything special as this is already preinstalled. If you've chosen different db image, you have to install it manually.

I have fed this back to the cloud engineer, I'll let you know if this fixes the issue.
Obviously the original error in this ticket is still a concern, and we had to entirely rebuild the stack therefore losing all of our historical tests.

But why didnt you make a backup of your data??

We do have backups of the jtl files, so we can re-upload them.


2FA Wonkiness w/ Firefox

Hi, I'm trying to use the extension in Firefox. My Apple account has 2FA enabled.
When I enter my email / password and get the 2FA prompt the extension login window goes away. When I click again, I get an empty login window rather than a prompt to enter 2FA.

Hi @JoeCotellese! Thanks a lot for flagging this issue. I have managed to replicate it on my setup.
Temporary work-around

After entering the email and password, hit the "Enter" key of your keyboard rather than clicking on the "Sign In" button. This should keep the extension pop-up open, letting it to transition to the next page which is the 2FA code authentication:

It is important that you do not navigate away from the pop-up before it has transitioned to the 2FA page.
Why this happens?

The extension is implemented as a state machine where each state represents a different page of the extension. The initial state is the sign-in page.
When submitting the sing-in form, the extension makes a sign-in request to the iCloud servers and waits for a response. The extension is designed to transition to the next state (2FA code authentication page) only upon the reception of a successful sign-in response from iCloud.
The iCloud backend pushes a 2FA notification to each of your authenticated devices.
The notification arrives at your device. A new MacOS dialog pops up which causes Firefox to close the extension pop-up before the extension receives the successfull sign-in response from iCloud.
The extension has not transitioned to the next state, even though the sing-in was successful. The extension is gong to render the initial sign-in state once the user re-opens the pop-up.

Essentially, this is a race condition between the 2FA notification arriving at the device and the extension receiving the successful sign-in response.
This behaviour does not happen on Chrome. There are very few cases where Chrome will close the extension pop-up without the user taking any action (such as a click outside the pop-up, or hitting the "Esc" key).
@JoeCotellese Let me know if the work-around works for you for the time being. I will be looking into putting a proper fix together.

Similar issue: https://bugzilla.mozilla.org/show_bug.cgi?id=1378527

It took a few tries but that did the trick. Thanks!

i had the same issue, but your temp workaround solved it perfetcly! thanks a lot

Tried several times but couldn't get it to work (though it worked on Edge). Isn't it possible to open the log in dialog in a new popup window?

Hi @rafacampoamor! Yes, it is possible to open the pop-up as a normal tab:

Open the pop-up and right-click on its background
Select "View Page Source". This will open a new tab with a URL that would look something like this: view-source:moz-extension://e39b22ff-52d1-4346-bd41-5b4fc89bf114/popup.html.
Remove the view-source: prefix and you have a URL pointing to the pop-up: moz-extension://e39b22ff-52d1-4346-bd41-5b4fc89bf114/popup.html.
Enter the URL and the pop-up interface would be opened as a regular web-page.

Note that pop-up URLs are unique per installation. Copy-pasting the above URL of mine won't work. You need to retrieve the URL of your own installation of the extension.

FYI, I've started working on a proper fix to this issue a few weeks ago but never got around to shipping it. I hope I will get some time by the end of the month to wrap this up.

@dedoussis It worked! Thank you so much for the workaround!

Hi @JoeCotellese! Thanks for taking the time to flag this issue. I have managed to replicate it on my setup.
Temporary work-around

After entering the email and password, hit the "Enter" key of your keyboard rather than clicking on the "Sign In" button. This should keep the extension pop-up open, letting it to transition to the next page which is the 2FA code authentication:

It is important that you do not navigate away from the pop-up before it has transitioned to the 2FA page.
Why this happens?
1. The extension is implemented as a state machine where each state represents a different page of the extension. The initial state is the sign-in page.

2. When submitting the sing-in form, the extension makes a sign-in request to the iCloud servers and waits for a response. The extension is designed to transition to the next state (2FA code authentication page) only upon the reception of a successful sign-in response from iCloud.

3. The iCloud backend pushes a 2FA notification to each of your authenticated devices.

4. The notification arrives at your device. A new MacOS dialog pops up which causes Firefox to close the extension pop-up before the extension receives the successfull sign-in response from iCloud.

5. The extension has not transitioned to the next state, even though the sing-in was successful. The extension is going to render the initial sign-in state once the user re-opens the pop-up.

Essentially, this is a race condition between the 2FA notification arriving at the device and the extension receiving the successful sign-in response.
This behaviour does not happen on Chrome. There are very few cases where Chrome will close the extension pop-up without the user taking any action (such as a click outside the pop-up, or hitting the "Esc" key).
@JoeCotellese Let me know if the above work-around works for you for the time being. I will be looking into putting a proper fix together.

This Workaround is not working for me on Mac OS Firefox 110. If I use enter instead of clicking the button it still closes my popup

Hi @rafacampoamor! Yes, it is possible to open the pop-up as a normal tab:

Open the pop-up and right-click on its background
Select "View Page Source". This will open a new tab to a URL of the following format: view-source:moz-extension://e39b22ff-52d1-4346-bd41-5b4fc89bf114/popup.html.
Remove the view-source: prefix and you have the URL of the pop-up: moz-extension://e39b22ff-52d1-4346-bd41-5b4fc89bf114/popup.html.
Open a new tab, enter that URL and the pop-up interface would be rendered as a regular web page.

Note that pop-up URLs are unique per installation. Entering the above URL of mine won't work. You need to retrieve the URL of your own installation of the extension.

@Futos you could try using the above workaround ☝


Link to chum web

I think it's worth mentioning the existence of Chum Web to explore apps in Chum.

Thank you. Merging


Preset canvas aspect ratios

(from conversation with @sammeltassen)

When modifying canvas dimensions, as well as offering free-form width and height as in the image above, also offer a set of useful aspect ratios (configurable). E.g., 4:3, 16:9, 2:1 etc. This is a good option when creating a blank canvas too. When the canvas has yet to acquire content the w,h can be set to multiples of 1000 in the aspect ratio, for simplicity. If I select 4:3 I get a 4000x3000 canvas.
If the user selects one of these for a canvas that already has content, the ME could either:

Adjust the canvas so that the content still fits but preserve whichever it can of the current dimensions
Pick a rounded up pair of dimensions, e.g., 4000:3000.

Content, including content that previously targeted the whole canvas, should have its own aspect ratio preserved. So if a 2000x1500 image was targeting a 2000x1500 canvas (no xywh target required), and you changed the canvas aspect ratio to 16:9, the canvas could either change to 2667x1500 and the painting now specifically targets 333,0,2000,1500; or the canvas could change to 16000x9000 and the painting anno now targets 2000,0,12000,9000.

This will not work for canvas creation, unless there is an additional behaviour or other property to tell Manifest Editor not to resize automatically when you add an image to it. We could have this on the edit properties page. There is an editor that specifically shows when there are multiple piece of media on a canvas.