Running the UI locally does not work

Hello,
Thanks so much for the help in configuring the workflow I can confirm that I am able to deploy everything.
When I try to run the UI locally though I am not able to execute it.
Running the command npm
npm i --legacy-peer-deps
and
npm start
results in the following.
`><EMAIL_ADDRESS>start

react-scripts start

Cannot find module 'ajv/dist/compile/codegen'
Require stack:

/home/nicola/projects/ac/aws-mre-original/aws-media-replay-engine/source/frontend/node_modules/ajv-keywords/dist/definitions/typeof.js
/home/nicola/projects/ac/aws-mre-original/aws-media-replay-engine/source/frontend/node_modules/ajv-keywords/dist/keywords/typeof.js
/home/nicola/projects/ac/aws-mre-original/aws-media-replay-engine/source/frontend/node_modules/ajv-keywords/dist/keywords/index.js
/home/nicola/projects/ac/aws-mre-original/aws-media-replay-engine/source/frontend/node_modules/ajv-keywords/dist/index.js
/home/nicola/projects/ac/aws-mre-original/aws-media-replay-engine/source/frontend/node_modules/schema-utils/dist/validate.js
/home/nicola/projects/ac/aws-mre-original/aws-media-replay-engine/source/frontend/node_modules/schema-utils/dist/index.js
/home/nicola/projects/ac/aws-mre-original/aws-media-replay-engine/source/frontend/node_modules/webpack-dev-server/lib/Server.js
/home/nicola/projects/ac/aws-mre-original/aws-media-replay-engine/source/frontend/node_modules/react-scripts/scripts/start.js`

I tried to install the packages using the --force command and in this case I am able to run the UI locally but I get a lot of errors in the console log and the message "A network  Error has occurred" in the UI.
I configured the correct parameters in the .env file too.
I will try to deploy the front end too (even if I would like to avoid it) to see if I can run the UI in this way
Thanks again for the support

Hello @aravindkaws ,
So using force fixes the problem, in order to make the UI work locally it is also needed to create the cognito user pool manually and the identity pool.
I did that but I forgot to assign enough permissions to the user that I created for the login of the application.
After doing so, the UI was able to retrieve the data :)
Thanks for your assistance and an amazing job once again

Hello @araviraj-aws ,
I was referring to when you decide to run the front end in local mode and therefore you run the deploy command with the option --disableui. In this case, the procedure did not create the cognito pool for us and we had to create it manually. I don't know if this will happen to anyone or if we did something wrong.
Another problem we are facing is the fact that we cannot find the S3 bucket that (we think) the framework should create to host the source of the videos that should start the process.
Does it need to be created manually? We have read all the documentation but there is no mention of it so I think probably the installation process should make it, we ran the installation process multiple times but we cannot find any bucket that could be used as a source bucket.

Hi @Laazarus ! The --disable-ui option is to be used only when upgrading MRE and not for greenfield deployment (i.e., fresh install). Including this flag during a fresh install will make MRE skip creating all the UI related resources (including Cognito). Regarding your question on the S3 bucket to host source videos, the only relevant bucket that the solution creates is to store the HLS chunks streamed using something like MediaLive which will in-turn by used by MRE for processing (as MRE currently is based on HLS chunk processing). To host source videos owned by you (such as .MP4 videos), you have to create an S3 bucket outside MRE and for starters, configure a MediaLive channel using it for HLS streaming which can then be processed by MRE.

Thanks @araviraj-aws ,
Regarding the UI, this is exactly the effect we wanted. We did not want to create resources for the UI which we wanted to use it locally only to test the framework. As per the MediaLive service to kick-start the process we thought that the framework offered that as an option along with the S3 bucket one by reading the documentation and seeing the dropdown field in the creation of the event.
We will try to find a way to start the framework as this is still a problem for us.
Thanks so much for your help and your support and sorry if we asked so many questions.


Register media/ mime type with IANA

It would be great, if you could register the mime type here:
http://www.iana.org/assignments/media-types/media-types.xhtml
The data from this registry is used by other projects (especially in the node.js eco system).
A registration would solve many issues like templates being detected to be compressible with gzip etc.

I'm familiar with the use of MIME types for HTTP transfer, but handlebars templates really shouldn't be sent raw over the wire, not concatenated with anything else. What other benefits would this provide?

Well, we have a use case where we do transfer HBS templates on-the-go and compile them on the client side after they are loaded. This is because we have a lot of templates of which a user only needs a few and we cannot know which ones beforehand.
I know that this is bad practise and usually you compile and bundle everything at build time but let's just assume this is not feasible.
Also we have an admin application where we allow editing templates in an s3 like object store and also in this case they should be compressed on-the-fly on the server side.

Why not precompile them on the server and send down the javascript? Sending the full compiler to the client is normally something to avoid for a variety of reasons.
I don't know what is involved with registering with IANA and don't see a huge benefit for the ecosystem as a whole. That being said, if you wanted to register something and submit a PR with documentation on this, I would not be opposed.

Well again, if your server is just an s3 like remote filesystem and you have neither the possbilitiliy nor any benefits from precompiling, why would you do that?!
Also I think this discussion is to problem centric.
On a meta level, you should have a strong motivation to register it with IANA to manifest handlebars as a well known media type.
Again, this stuff may be used for purposes we don't even think about, so why preventing it?!


tutanota-desktop: 3.108.12 -> 3.109.4

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/tutanota-desktop/versions.
meta.description for tutanota-desktop is: Tutanota official desktop client
meta.homepage for tutanota-desktop is: https://tutanota.com/
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.109.4 with grep in /nix/store/hhywgc0jg8n10f5z58snc0w77bjrv9hy-tutanota-desktop-3.109.4
found 3.109.4 in filename of file in /nix/store/hhywgc0jg8n10f5z58snc0w77bjrv9hy-tutanota-desktop-3.109.4

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
tutanota-desktop

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/hhywgc0jg8n10f5z58snc0w77bjrv9hy-tutanota-desktop-3.109.4 \
  --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 tutanota-desktop https://github.com/r-ryantm/nixpkgs/archive/9ec7a4bb1243b9adaa32ab4a2f292e97bbfcd389.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/hhywgc0jg8n10f5z58snc0w77bjrv9hy-tutanota-desktop-3.109.4
ls -la /nix/store/hhywgc0jg8n10f5z58snc0w77bjrv9hy-tutanota-desktop-3.109.4/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

tutanota-desktop

Maintainer pings
cc @WolfangAukang for testing.

Tutanota is sending repeated emails such as below, so I suggest to backport this to unstable and 22.11, maybe even better with the latest 3.110.0

#219459

Superseded by #219489, which is updating to the latest version


train my own data?

where is the code to train my data????????

see the readme.md of https://github.com/Stick-To/Object-Detection-API-Tensorflow


Switch to newer release did not work

When switching to a newer release the file: redhat.repo is not updated to this release. (Still old version included) After deleting this file, unregistering the system and have a new plabook run everything worked as expected.

yum clean all + subscription-manager refresh should do the job as well


Enabling Hubble using the Cilium CLI doesn't work if Cilium was installed via Helm

The helm install method creates a CA for Hubble/Hubble Relay named hubble-ca-secret.  This CA is different than the one used for ClusterMesh. On the other end, when installing Cilium using the CLI, the same CA is used for both ClusterMesh and Hubble. As reported by this user, this means that when using cilium hubble enable, Hubble Relay is not able to connect to Cilium/Hubble nodes because the cert cannot be validated (see more details in this comment).
We should ensure that the two installation methods are consistent in this regard so that enabling Hubble works either way.

My two cents:
I think we should go the cilium cli way, i.e. one CA shared for Hubble and ClusterMesh (and anything internal to Cilium). It's simpler that what we currently do through Helm/certen (i.e. two different CAs) and moreover all the certs are for the internal $something.cilium.io so it's unusual to have two CAs responsible for the same domain, if that make sense.

Related: #300


Hide notifications for the currently open report

cc @Julesssss @cristipaval
Details
Adds context awareness to push notifications from Airship to hide notifications for a report the user is already reading (or messages the user may have already read). Reuses our existing logic for local notifications
Fixed Issues
$ https://github.com/Expensify/Expensify/issues/259220
Tests
No testing needed for mWeb Safari or mWeb Chrome. Notifications are not supported on those platforms.

Log into NewDot
Accept any prompt for notification permissions
Open a chat that is NOT from user A
Send a message from user A to your user
Verify a notification displays for the message
Open the chat for user A
Send another message
Verify a notification does NOT display for the message

Offline tests
None
QA Steps
Same as Tests
PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Mobile Web - Chrome

N/A

Mobile Web - Safari

N/A

Desktop

iOS

Android

@parasharrajat @neil-marcellini One of you needs to copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

Yeah I agree about splitting up the changes to notification display logic vs upgrading package versions. Please tag me for review on the new PRs.

Alright the PR for upgrading to Airship 15 is through! I've pulled the latest and retested for this PR and all is looking good so this is ready for another review.

Web: Should the notification be hidden for the active chat even if the window is not focused/active?

Oh good question. I imagine no, but what do you suggest?

How can I test the Notifications on Android and iOS? I built a release build and installed it but I didn't receive any notification. Am I missing something?

So you can't test iOS notifications due to missing certs, and simulators not showing them. It's possible on Android, but you'll need to make sure you use the production airship keys.
You have access to our internal StackOverflow right? If yes, try this. If not let me know.

Web: Should the notification be hidden for the active chat even if the window is not focused/active?

Looks like in staging the notification is still hidden even if the window isn't focused. I'd expect that to stay the same with this PR.

@arosiclair is it cool with you if I wait to review until tomorrow?

@arosiclair is it cool with you if I wait to review until tomorrow?

Yeah no worries

I think someone needs to trigger the builds.

Sorry forgot to manually run the workflow. It should be done in an hour or so.

Use the links below to test this build in android and iOS. Happy testing!

:test_tube::test_tube: Use the links below to test this build in android and iOS. Happy testing! :test_tube::test_tube:

android :robot:
iOS :apple:

https://ad-hoc-expensify-cash.s3.amazonaws.com/android/15858/index.html
https://ad-hoc-expensify-cash.s3.amazonaws.com/ios/15858/index.html

desktop :computer:
web :spider_web:

https://ad-hoc-expensify-cash.s3.amazonaws.com/desktop/15858/NewExpensify.dmg
https://15858.pr-testing.expensify.com

Might be a bug: Android: After a chat is active and the user goes back to LHN, no notifications are shown for that chat.

Yup known issue. When swiping back to the LHN, the chat is still "open" to the right. You have to deliberately select another chat to switch. This will be fixed by the navigation reboot.

Ok, glad to hear that. Do we have an issue added to the main tracking issue of the navigation reboot? or Should we create a new one?

I don't think another issue is necessary to track this specifically. It should be fixed by https://github.com/Expensify/App/issues/15847.
@parasharrajat Could we up the urgency for the checklist? This PR has been sitting around in limbo for a month now. It's a big UX improvement especially for busy rooms so let's try pushing this through ASAP.

The web does not show notifications for an active chat even when the window is not focused. But the Desktop shows the notification.

Yes this is pre-existing behavior I checked that here. The visibility behavior between web, desktop and native is not quite the same (code). We can log a separate bug to address that.

🎯 @parasharrajat, thanks for reviewing and testing this PR! 🎉
An E/App issue has been created to issue payment here: https://github.com/Expensify/App/issues/17219.

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/neil-marcellini in version: 1.2.98-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/francoisl in version: 1.2.98-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

This PR caused a regression. CONST here is incorrectly imported: expensify-common/lib/CONST does not have DEEPLINK_BASE_URL. It should have been imported from E/App.


Adding build tags as macro

Description
Adding build tags as macro
Type of change
What is it?

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Documentation update
[ ] Tests update
[ ] Refactor

Checklist:

[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] I run go fmt ./... to check that my code is properly formatted
[ ] I run go vet ./... to check that my code is free of common Go style mistakes

Codecov Report

Merging #497 (41d5477) into main (cd0a861) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #497   +/-   ##
=======================================
  Coverage   31.02%   31.02%
=======================================
  Files          33       33
  Lines        3226     3226
=======================================
  Hits         1001     1001
  Misses       2131     2131
  Partials       94       94

Continue to review full report at Codecov.

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


A little question about pytorch-seq2seq/3 - Neural Machine Translation by Jointly Learning to Align and Translate.ipynb

In the function forward of module Encoder, does variable outputs mean all of the stacked forward and backward hidden states from the encoder and variable hidden mean the context vector? I'm confused because the literal meaning of these two variables differs from what they actually stand for.
Thanks a lot.

In the function forward of module Encoder, does variable outputs mean all of the stacked forward and backward hidden states from the encoder and variable hidden mean the context vector? I'm confused because the literal meaning of these two variables differs from what they actually stand for.
Thanks a lot.

Oops! I think I know the meanings. There is no contradiction.

Yep, you're correct. I know these variable names aren't the most intuitive but the PyTorch official documentation refers to them as output and h_n.
I preferred outputs over output as I wanted it to be plural to highlight that this comes from more than one hidden state. hidden over h_n because it's just more readable.


tag version > 10

I have a tag that semtag has just moved to v19.1.1-beta.10.  This is generated with
source semtag beta

I have since done a few commits, when I run the semtag command it wont move passed 10.  Have you previously seen an example > 10?
Thanks,
Damian.

I've gone beyond 10, weird... I'll check it out, thanks Damian.

Something very similar here. My last tag, created with semtag, is: v0.1.0-rc.10.
With semtag getcurrent I get v0.1.0-rc.9.1+c6cc6f5
When I try adding a newer rc via semtag candidate -s minor semtag tries to create v0.1.0-rc.10 again which results in an error.
After another commit I added rc.11 tag manually and semtag getcurrent gives me v_0.1.0-rc.9.2+1d5515d_ then.

Similiar issue here. Instead v0.6.0-alpha.10 I get v0.6.0-alpha.a.
Tag was created manually but parsed by semtag. Since a is hex for 10 I guess it's a formatting problem somewhere 🤔

I tested the version from #13 and it fixes the problem. Please merge the pull request. Thanks.

Merged and fixed


Renaming 02 chapter, adding gitignore

i'm going to merge this so that the .gitignore makes its way into the other pull requests more easily.


Dateslider value doesn't update

The DateSlider widget value doesn't update in sync with the displayed value - it just stays at the initial value. I used the example code as is (other than formatting tweaks).

I tried the DateRangeSlider and IntSlider for comparison and their value property did update in sync with their displayed value no problem.
I'm using Windows Conda panel version 0.6.0 (from the conda-forge channel) - with jupyterlab 1.0.2

Fixed now that param supports datetime.date.


--save_outlines not working after upgrading cellpose

Previously, --save_outlines flag in the command-line argument used to save a txt file of outlines readable in ImageJ. After upgrading cellpose --save_outlines flag does not work that way, rather saves a png file of the outline. How to get the outlines' txt file?
The upgraded version of cellpose also doesn't run with --cellprob_threshold parameter and --no_npy flag does not suppress the generation of npy file.

Sorry for changing that on you! Use --save_txt to save those ImageJ outlines. We aslo changed cellprob_threshold to mask_threshold. I need to check out the --no_npy though.

Ah yeah, I might have toggled the default value a long time ago and forgot since I never use the npy files. Fixed now, thanks!


Sidre not storing updated mesh information

When the mesh object is mutated by a Solid module, the sidre-based output file does not contain this updated mesh information.

I think this needs an updateMesh method in Axom's MFEMSidreDataCollection class.


MlflowLogger: Invalid metric name: 'val/AR@100'. Names may only contain alphanumerics, underscores (_), dashes (-), periods (.), spaces ( ), and slashes (/)

Current mlflow logger doesn't support metrics logging from CocoMetric's proposal:
Metrics
val_evaluator:
  ann_file: ${data_root}/equifish_annotations/valdataset_toy.json
  type: CocoMetric
  metric: ['bbox', 'proposal']
  iou_thrs: [0.2]

Logger
# @package modules.MLflowVisBackend

type: MLflowVisBackend
save_dir: temp_dir #${paths.output_dir} #(str): The root directory to save the files produced by the backend.
exp_name: ${name}             #(str, optional): The experiment name. Default to None.
run_name: ${run_name}         #(str, optional): The run name. Default to None.
tags: null                 #(dict, optional): The tags to be added to the experiment. Default to None.
params: null                  #(dict, optional): The params to be added to the experiment. Default to None.
tracking_uri: http://${oc.env:MLFLOW_USERNAME}:${oc.env:MLFLOW_PASSWORD}@${oc.env:MLFLOW_HOST}
artifact_suffix: ['.json', '.log', '.py', 'yaml']     # (Tuple[str] or str, optional): The artifact suffix. Default to ('.json', '.log', '.py', 'yaml').

Are there some flags to fix this behaviour?
Env
mmcv                     2.0.0
mmdet                    3.0.0                /home/oem/Projects/aimosaic-roi/3rd/mmdetection
mmengine                 0.7.3
smmap                    5.0.0

@hhaAndroid
Fixed it by adding in
    scalar_dict_fixed = dict()
    for k, v in scalar_dict.items():
    scalar_dict_fixed[k.replace('@', '_at_')] = v

    @VISBACKENDS.register_module()
    class MLflowVisBackend(BaseVisBackend):

    ....

    @force_init_env
    def add_scalars(self,
                    scalar_dict: dict,
                    step: int = 0,
                    file_path: Optional[str] = None,
                    **kwargs) -> None:
        """Record the scalar's data to mlflow.

        Args:
            scalar_dict (dict): Key-value pair storing the tag and
                corresponding values.
            step (int): Global step value to record. Default to 0.
            file_path (str, optional): Useless parameter. Just for
                interface unification. Default to None.
        """
        assert isinstance(scalar_dict, dict)
        assert 'step' not in scalar_dict, 'Please set it directly ' \
                                          'through the step parameter'
        scalar_dict_fixed = dict()
        for k, v in scalar_dict.items():
            scalar_dict_fixed[k.replace('@', '_at_')] = v

        self._mlflow.log_metrics(scalar_dict_fixed, step)

It helped, of course. But is there a better way? Or should we make a Pull request?

@ihoholko This implementation should be put in mmengine, you can go to mmengine to create a pr?

https://github.com/open-mmlab/mmengine/pull/1125

Why is this not added yet???


How to use findAncestor?

Suppose I'd want to save the contentOffset of a UITableView whenever I click an element inside of it.
E.g.
List {
    ForEach(items, id: \.self) { element in
         Button(element) {
             navigation.contentOffset = // get tableview contentOffset
         }
    }
}

How can I use findAncestor to get the parent UITableView's contentOffset?
I've tried using this
Introspect.findAncestor(ofType: UITableView, from: UIButton) as? UITableView

but the compiler returns:
Cannot convert value of type 'UIButton.Type' to expected argument 'PlatformView' (aka 'UIView')

I've already tried using a UILabel instead of UIButton and it gives me the same error.

Couple things. You should provide a Type for the "ofType" parameter: UITableView.self. The error you're getting is because you need to pass an instance of a PlatformView to the function, not the type.
Not sure where you're trying to use that Introspect.findAncestor static function, but for this use case, you should just introspect from within the view hierarchy. Using your example, you could try something like this:
@EnvironmentObject var navigation: NavigationCoordinator
@ObservedObject var viewModel = ViewModel

var body: some View {
    List {
        ForEach(viewModel.items, id: \.self) { element in
             Button(element) {
                 self.navigation.contentOffset = viewModel.listOffset
             }
        }
    }
    .introspectTableView { tableView in
        self.viewModel.listOffset = tableView.contentOffset
    }
}

This doesn't seem to be an Introspect bug and the issue hasn't had any activity for months, therefore I'll go ahead and close it.


python310Packages.sphinxcontrib-autoapi: 1.8.4 -> 1.9.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.sphinxcontrib-autoapi is: "Provides 'autodoc' style documentation"
meta.homepage for python310Packages.sphinxcontrib-autoapi is: "https://github.com/readthedocs/sphinx-autoapi"
meta.changelog for python310Packages.sphinxcontrib-autoapi is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 1.9.0 with grep in /nix/store/r6nij8m2ygwi8l7jsyj0ly22l6zjdqhp-python3.10-sphinx-autoapi-1.9.0
found 1.9.0 in filename of file in /nix/store/r6nij8m2ygwi8l7jsyj0ly22l6zjdqhp-python3.10-sphinx-autoapi-1.9.0

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

4 total rebuild path(s)

2 package rebuild(s)

2 x86_64-linux rebuild(s)
2 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
python310Packages.sphinxcontrib-autoapi
python39Packages.sphinxcontrib-autoapi

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/r6nij8m2ygwi8l7jsyj0ly22l6zjdqhp-python3.10-sphinx-autoapi-1.9.0 \
  --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 python310Packages.sphinxcontrib-autoapi https://github.com/r-ryantm/nixpkgs/archive/4cad954b31d528d6bbbc5f9da292c31ac374dc06.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/r6nij8m2ygwi8l7jsyj0ly22l6zjdqhp-python3.10-sphinx-autoapi-1.9.0
ls -la /nix/store/r6nij8m2ygwi8l7jsyj0ly22l6zjdqhp-python3.10-sphinx-autoapi-1.9.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

python310Packages.sphinxcontrib-autoapi
python39Packages.sphinxcontrib-autoapi

Maintainer pings
cc @karolchmist for testing.

Result of nixpkgs-review pr 182948 run on x86_64-linux 1

2 packages built:

python310Packages.sphinxcontrib-autoapi
python39Packages.sphinxcontrib-autoapi

I don't use this package any longer, so I can't test it unfortunately.


Update OVA postmortem collection example

Can we replace the example in the README with this one
./generate_postmortem.sh 0 --ova --pull-appliance-logs --diagnostic-manager

so we are consistent with the mustgather for v10

@xor76
The referenced command is specific to pulling logs for the management cluster.  Would not recommend pulling appliance logs nor generating diagnostics in all cases.

@xor76
The referenced command is specific to pulling logs for the management cluster.  Would not recommend pulling appliance logs nor generating diagnostics in all cases.


cog can't access docker through a proxy registry

For security reasons, my development environment requires a proxy registry to access docker base images. I couldn't find any info in the docs about configuring cog to access a proxy instead of docker.io. Here is the stdout/stderr from running cog in this air-gapped environment:
> cog run python
Building Docker image from environment in cog.yaml...
[+] Building 0.4s (2/2) FINISHED                                 docker:default
 => [internal] load build definition from Dockerfile                       0.1s
 => => transferring dockerfile: 162B                                       0.0s
 => ERROR resolve image config for docker-image://docker.io/docker/docker  0.2s
------
 > resolve image config for docker-image://docker.io/docker/dockerfile:1.4:
------
Dockerfile:1
--------------------
   1 | >>> #syntax=docker/dockerfile:1.4
   2 |     FROM r8.im/cog-base:python3.11
   3 |     WORKDIR /src
--------------------
ERROR: failed to solve: failed to resolve source metadata for docker.io/docker/dockerfile:1.4: failed to do request: Head "https://registry-1.docker.io/v2/docker/dockerfile/manifests/1.4": read tcp <IP_ADDRESS>:37026-><IP_ADDRESS>:443: read: connection reset by peer
ⅹ Failed to build Docker image: exit status 1

Hi @danbgoldman. Cog wraps docker CLI invocations when building and pushing images, so it should be straight forward to use behind a proxy.
In this case specifically, it looks like the issue is that your proxy needs the Dockerfile syntax repository to build. You should be able to load it by running these commands:
# Pull the syntax image from Docker Hub
docker pull docker/dockerfile:1.4

# Tag it for your internal registry
docker tag docker/dockerfile:1.4 your-internal-registry.example.com/docker/dockerfile:1.4

# Push it to your internal registry
docker push your-internal-registry.example.com/docker/dockerfile:1.4

The same goes for the Cog base image on the next line.
You can see the Dockerfile that Cog will use to build the image by running cog debug.

Even after pushing it to my internal registry, I get exactly the same error. And, if I run cog debug the syntax line still refers to the original docker/dockerfile:1.4, not the fully-qualified name in my internal registry. So even though I have a local copy of the image, cog isn't referring to it. Is there a flag or config to force cog to prepend the full host name of the internal registry?
> cog debug
#syntax=docker/dockerfile:1.4
FROM r8.im/cog-base:python3.11
WORKDIR /src
EXPOSE 5000
CMD ["python", "-m", "cog.server.http"]
COPY . /src

@danbgoldman Cog doesn't currently have a way to prepend host names. But you should be able to configure your internal registry as a mirror to get docker/dockerfile:1.4 resolving correctly.
If all else fails, you can eject from Cog by doing cog debug > Dockerfile, making any changes you need, running docker build, and then running cog push.


Changes in the Preview option

[x] Add the Preview option for single-word replacement.
[x] Reduce the length of sentences in the preview window.

Added single replace for single word change in global replace. c7050eea1ba9b1ccf9d1bb246a01ddcc0e7a3a9d

We have completed the requirement and also shown the video of the same. It will be released soon.


Guard against invalid schedule loading

If a bad crontab is published to a schedule this will blow up and cause the process to become corrupted.   This causes lots of schedules to be missed.

@taf2 Hello!  Can you rebase against master, and please edit your commit message to remove the profanity?  Thank you! 😸

@taf2 friendly reminder on this PR!


Added the disable Minimap feature

I would suggest to set the visibility in CtrlRace2DMap::calcSelf instead as this would allow for dynamic switching.

I cannot merge because there are still conflicts in MenuSP_U.bmg.json5. Please also run clang-format on CtrlRace2DMap.cc.

closes #389 ?


Move everything from development to main branch

And keep creating feature branches for non-trivial updates.

Done, thanks @rkpasia


ARTEMIS-2327 ExceptionListener invoked when connection level exception

Add tests
Add fix - if timeout occurs on sending packet, calls same code that is invoked if timeout occurs on during ping aligning logic, and ensuring JMS connection exception listener gets invoked to inform the client logic to react. Such libs like Spring JMS reply on exception listeners to react to connection level errors.

The JIRA notes that "the exception is returned to calling code". I'm not clear if it means through to the application code or not. I bring it up as if the exception is being explicitly reported elsewhere, e.g a send method throwing, its generally not meant to be reported to the ExceptionListener according to the JMS spec.

Yes it does. But if its a connection exception it should also make it to the connection exception listener. Typically frameworks such as spring rely on that.

It perhaps depends what the exception is, and what reaction is being taken to it (e.g killing the connection, or considering it already dead), but the specs fairly clear about what it wants overall:

"If an exception is thrown on a JMS call it, by definition, must not be delivered to an ExceptionListener (in other words, ExceptionListener is not for the purpose of monitoring all exceptions thrown by a connection)"

So as i said, the code is doing this for others, and in this case because spring wasnt notified on the exception listener it doesnt let go of what became a stale connection, when this specific issue occurred.
As per here, it is meant to be notified of a critical connection exception async, and in this side case it wasn't
https://docs.oracle.com/javaee/6/api/javax/jms/ExceptionListener.html

Something else doing something isnt necessarily a reason to copy it. The async is in reference to the application not having already been told synchronously via a method call, which as above the spec doc is clear on.
As I said, it perhaps depends what the exception is, and what reaction is being taken to it. If this exception always represents the connections ultimate failure and isnt in response to a particular method call then telling the exception listener does seem reasonable. If it doesnt, e.g its failing over, or its only a single methods failure and everythign else is fine, then it often might not be appropriate.
In particular the async ExceptionListener is good for things only using MessageListeners, which will never find out otherwise since they dont call methods [if theres no delivery happening]. Spring uses synchronous receive calls (by default at least) so it should already discover failures that result in the connection being considered broken, without the ExceptionListener. If it doesnt that might point to another issue.

re:
If this exception always represents the connections ultimate failure and isnt in response to a particular method call then telling the exception listener does seem reasonable
yes, if failover was occuring that would have been caught further up in the checks (notice method about 10ish lines up, waitOnFailover), and from experience of the issue, it seems to be that way once it hits here the connection is no longer recoverable..

Didnt see most of your edits when replying earlier, but my reply essentially fits anyway. I havent looked at and am not familiar with the client code outside the context of this diff. I'm just saying 'always call the exception listener' for connection exceptions seems out of line with the specs general desire, except perhaps if those exceptions are always classed as connection-ending failures, or if the surrounding code such as the failover stuff is intercepting and handling that, in which case ok.

As i said, failover is handled before it gets to this, so we know best efforts to failover etc have taken place, so if it gets here, its terminal, you need to inform listeners so they can react.

Missed another edit:
"ExceptionListeners is used by caching and pooling cf wrappers (e.g. springs CachingConnectionFactory), as such they're only access to if issue with exception is by exception listener, so its not just MessageListeners as a use case here."
As wrappers they can have access to all exceptions thrown anywhere if they want it. They might choose not to bother of course.

Thats why exception listener is there, its been like that for as many years as i can remember, all frameworks that pool or cache connections im aware of not just spring, rely heavily on the exception listener and being notified by the client.

As i said, failover is handled before it gets to this, so we know best efforts to failover etc have taken place, so if it gets here, its terminal, you need to inform listeners so they can react.

I was talking about any failover starting to happen in response to this 'connection ending exception', not any checks happening before it.

If there is no such response, and this is the end, then sure notify the exception listener.

And thats what we're doing. Calling the same connection.fail(e) method that other blocks and code paths do.

I'm not sure where I was when this PR was originally sent, but I came across these changes while investigating another issue. I'm considering reverting these changes for a handful reasons:

As Robbie pointed out originally, this doesn't fit with the JMS specification which clearly indicates that an ExceptionListener should only be invoked when the exception has nowhere else to go. The main use-case here is when a client implements MessageListener (which is invoked asynchronously by the underlying implementation) but still wants to know when its connection dies. Given that, in this situation, the client itself isn't invoking e.g. javax.jms.Consumer#receive() it has no way to receive the exception other than through the ExceptionListener. I'll quote (again) the salient part section 6.1.7 from the JMS 2 specification:

The exceptions delivered to ExceptionListener are those that have no other place to be reported. If an exception is thrown on a JMS call it, by definition, must not be delivered to an ExceptionListener (in other words, ExceptionListener is not for the purpose of monitoring all exceptions thrown by a connection). [emphasis mine]

As far as I can tell by looking through the code-base sendBlocking is only ever called from a JMS client application in response to a specific JMS API call, and it is from these calls that the exception must be thrown to the caller and not to the ExceptionListener.

I'm not convinced by the counter-argument that Spring et al. rely on this. The specification clearly says that the ExceptionListener is not a way to monitor all connection exceptions. Therefore, well-written frameworks/wrappers should have other ways to detect or be notified of connection problems. If the wrappers don't implement such functionality I see that as their problem, not ours. We shouldn't violate the JMS specification to suit their deficiencies.

The "ping" functionality was mentioned as the example to follow here. However, I don't think that comparison is apt in this case. The pinging functionality is an implementation specific behavior to monitor the validity of the connection. If a ping fails then by definition the connection has failed. This functionality executes without any action from the client application. Therefore, a ping failure has nowhere else to be reported but in an ExceptionListener. This is categorically different from a call to sendBlocking() which is the result of an explicit JMS API call from the client application.

The underlying issue here is that the client did not receive a response from the broker for a single "packet" within the specified timeout. That's all. There are a number of reasons this situation might arise. Perhaps the broker is under heavy load and simply didn't have time to respond. Perhaps the network is slow for some reason. Perhaps the timeout is simply too low for the use-case. The connection is not necessarily dead. It's plausible that the client might, in fact, catch the JMSException and retry the failed operation or eventually make another call. The comment on o.a.a.a.c.p.c.i.ChannelImpl#sendBlocking(Packet, int, byte) even notes this. If the connection actually is dead then the underlying pinger/monitor should detect that.

This change gives the impression to users that exceptions like this which get thrown to a caller should also invoke the ExceptionListener which is incorrect per the specification.

I looked through the client code-base for uses of o.a.a.a.s.c.p.RemotingConnection#fail(o.a.a.a.a.c.ActiveMQException) aside from the one added via this PR, and I only found 3 others which were all truly asynchronous use-cases where the exception had nowhere else to go.

So if exception occurs on blocking send a connection exception is meant to be raised if it is terminal. I dont see in jms spec it stating otherwise

Otherwise without that frameworks like spring etc would be unable to react to this. I would ask this is discussed and consult in the spring group the framework is too pervasivrly used in java ecosystem. Jms spec here is sometimes not specific enough and here its unfortunately open a little to interpretation two ways, one which spring has taken is that it has coded and relied of for years...

If a JMS provider detects a serious problem with a Connection object, it informs the Connection object's ExceptionListener, if one has been registered. It does this by calling the listener's onException method, passing it a JMSException argument describing the problem.
An exception listener allows a client to be notified of a problem asynchronously. Some connections only consume messages, so they would have no other way to learn that their connection has failed.
A JMS provider should attempt to resolve connection problems itself before it notifies the client of them.

https://docs.oracle.com/javaee/6/api/javax/jms/ExceptionListener.html

There is no mention what so ever that it should not be called if a connection level exception is raised else where.

I  wont argue on this as i dont work for the company where this caused a significant prod outage due to lack of it, and other brokers do send the exception and no issues with spring. Im sure that company may have issue if that problem regresses, i believe the org you work for supports them still so that will be something you should be aware of.

When I last looked this was useful for the case when a connection issue caused an exception.
Back then there was a case where a disconnect was silently failing.
But we should only call the exception listener on that case.
What is the case where this is failing ?

So if exception occurs on blocking send a connection exception is meant to be raised if it is terminal. I dont see in jms spec it stating otherwise

As noted previously, a failure to get a response from a blocking call is not necessarily a fatal or terminal connection error. If, for example, a JMS client is attempting to send a persistent message and the blocking call fails to receive a response then the caller will receive a javax.jms.JMSException as described in the API documentation. Since the javax.jms.JMSException can be reported to the caller then it should not, according to the specification, be sent to any ExceptionListener.

Otherwise without that frameworks like spring etc would be unable to react to this.

As noted in #2 of my previous comment, the specification clearly states that the "ExceptionListener is not for the purpose of monitoring all exceptions thrown by a connection." Therefore, if frameworks like Spring are relying on the ExceptionListener to monitor the connection for all exceptions then it would seem they are improperly implemented. I'm not familiar enough with Spring to say whether or not that's true about it.

Jms spec here is sometimes not specific enough and here its unfortunately open a little to interpretation two ways, one which spring has taken is that it has coded and relied of for years...

I'm not familiar enough with Spring to say authoritatively how it is or isn't implemented so I'll leave that bit alone.
However, the JMS specification seems crystal clear on these points:

Exceptions that can be reported elsewhere must not go to the ExceptionListener.
Therefore, the ExceptionListener should not be relied upon to monitor for all connection exceptions.

For clarity's sake I'll quote a larger chunk of section 6.1.7 of the JMS 2 specification which essentially includes the portions that both you and I have quoted together:

If a JMS provider detects a problem with a connection, it will inform the connection’s ExceptionListener, if one has been registered. To retrieve an ExceptionListener, the JMS provider calls the connection’s getExceptionListener() method. This method returns the ExceptionListener for the connection. If no ExceptionListener is registered, the value null is returned. The connection can then use the listener by calling the listener’s onException() method, passing it a JMSException describing the problem.
This allows a client to be asynchronously notified of a problem. Some connections only consume messages, so they would have no other way to learn their connection has failed.
...
A JMS provider should attempt to resolve connection problems itself prior to notifying the client of them.
The exceptions delivered to ExceptionListener are those that have no other place to be reported. If an exception is thrown on a JMS call it, by definition, must not be delivered to an ExceptionListener (in other words, ExceptionListener is not for the purpose of monitoring all exceptions thrown by a connection).

In summary, if a JMS provider detects a problem with a connection it will inform the connection's ExceptionListener of the exception if that exception has no other place to be reported. This allows a client to be asynchronously notified of a problem when no exception can be synchronously delivered to the client from a JMS API invocation. The ExceptionListener is not for the purpose of monitoring all exceptions thrown by a connection.

There is no mention what so ever that it should not be called if a connection level exception is raised else where.

In my estimation, that is exactly what the JMS spec means when it says, "The exceptions delivered to ExceptionListener are those that have no other place to be reported. If an exception is thrown on a JMS call it, by definition, must not be delivered to an ExceptionListener"
For what it's worth, I didn't mean to imply that there wasn't a legitimate problem at the root of this issue. My claim is simply that this is the wrong way to fix it.

So all i would say to revert this an alternative fix should be supplied to fix that original isshe. Not just a plain revert else you will cause an immediate regression. One that caused a prod outage.

I do not see in the detail any mention of what you summarise as

if that exception has no other place to be reported.

I assume also other brokers and spring also didnt read it the way you do. As noted i suggest a discussion with spring community should be had to agree a interpretation and then agree a way forward. Spring as i mentioned is too pervasive used just to go break it.

For what its worth, i dont have access to original case tickets (as i moved on) but i believe the route issue was a producer never recovered and it was later found it was because the connection had failed to reconnect itself but spring didnt invalidate the connection, im sure you probably have access to the original case/issue details and logs though.

I do not see in the detail any mention of what you summarise as, "if that exception has no other place to be reported."

I'm not sure why this information is absent from the JavaDoc for ExceptionListener. This seems like an oversight since the expected semantics are clearly outlined in the specification. To quote once more:

The exceptions delivered to ExceptionListener are those that have no other place to be reported. If an exception is thrown on a JMS call it, by definition, must not be delivered to an ExceptionListener (in other words, ExceptionListener is not for the purpose of monitoring all exceptions thrown by a connection).

To be clear, this was not added in JMS 2. The same language exists in section 4.3.8 of the JMS 1.1 and 1.0.2 specifications.
Take a look at the assertions for the JMS 2 TCK. Search for "JMS:SPEC:109". This is the specific TCK assertion dealing with this particular semantic, and it quotes the corresponding bit of the JMS specification (which both Robbie and I also quoted - which is absent from the ExceptionListener JavaDoc). It's clearly called out here, but also note that the "testable" column is marked as false. My guess is that it's just not possible to reliably inject failures into any arbitrary JMS implementation in order to test this. However, it's worth noting that several other very important bits of the spec also have "testable" set to false (e.g. JMS:SPEC:116, JMS:SPEC:133, JMS:SPEC:135, etc.) - ones that you wouldn't expect implementers to just ignore. For what it's worth the same JMS:SPEC:109 assertion is in the JMS 1.1 TCK, but I couldn't find a public copy of that document to share.

I assume also other brokers and spring also didnt read it the way you do.

Other brokers may implement things differently. Spring may rely on the ExceptionListener for all connection exceptions. If that's the case then I think they're running afoul of the specification, and that's bad for compatibility among other things.
I want to be pragmatic about this so my plan is to make the particular semantic you introduced configurable via a URL parameter, but the behavior will be disabled by default.

I want to be pragmatic about this so my plan is to make the particular semantic you introduced configurable via a URL parameter, but the behavior will be disabled by default.

This sounds a good compromise. I assume the param would also be settable on the cf programatically as well like other url pram settings.


Delete "Configure the auto-enrollment Group Policy for a single PC" section

Hello.
The entire section "Configure the auto-enrollment Group Policy for a single PC" should be merged into the "Configure the auto-enrollment for a group of devices", by replacing the procedure using Local Group Policy with one just using Group Policy.
As you correctly suggest yourselves, using Local Group Policy to auto-enroll a PC is not a recommended procedure. Instead, for testing with a limited scope of devices, why not simply recommend them to use Group Policy linked to an OU or with the appropriate security filtering?
As it stands, this section is simply cluttering the document with a procedure that the author themselves acknowledge is inadvisable. Just delete it. If someone has a valid reason to use Local Group Policy (such as not wanting to be burdened by change control procedures regarding Group Policy just for testing purposes), they'll already know how to do it, and can adapt the procedure for using Group Policy without it being explicitly documented, cluttering the document's primary purpose.

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

ID: ad012591-5c74-f1cd-d3a2-443768e8ceee
Version Independent ID: 918ea4bc-0849-3745-5d9d-a21a973bcd3b
Content: Enroll a Windows 10 device automatically using Group Policy - Windows Client Management
Content Source: windows/client-management/mdm/enroll-a-windows-10-device-automatically-using-group-policy.md
Product: w10
Technology: windows
GitHub Login: @ManikaDhiman
Microsoft Alias: dansimp

Hello,
Even though it is not recommended, it is supported, so it should be covered in docs.
Also, this method allows to join computers in scenarios where AD is not integrated with Azure AD.
I believe it shouldn't be deleted, as long as it is clearly noted that the method is not advisable.
Thank you


Error after training finishes (Test image display issue?)

Describe the bug
After running the training file, the training runs fine but after it is done I get an error message which I am fully unsure what it is. The test image doesn't display either. I used a master version of branch from around early-mid February.
Console log: error.txt
To Reproduce
Steps to reproduce the behavior:
Run the training file.
Training file (Included both as notebook and python file): training.zip
Desktop (please complete the following information):

OS: [openSUSE]
Version [Leap 15.1]

@Paasu it doesn't seem like you are using a venv as explained here

Actually, there also seems to be a missing import in a file.
apply_modely.py is calling numpy using np, so it should have an import numpy as np call at the top, and it doesn't.
Tests didn't fail to flag us that, and they should have.
They didn't fail because apply_model is not tested in it's own test, but only through coverage of integrity_test.py and/or other functions, which happens to import segmentation_scoring.py, which in turn imports numpy as np.
Because @Paasu calls apply_model directly in his script, it's causing the error he's experiencing.
I'll do a quick fix and create a pull request; @Paasu you'll need to pull (redownload) the changes from master for it to be resolved for you.

I downloaded the new version and ran the training.py in it but I get another error.
error2.txt

@Paasu, I tried to resolve the issue, could pull the recent changes mode in the #290 and see if it resolves your issue ?

@vs74 Tried it on the changes you made and the new master branch I downloaded today, same error. For what it is worth, I have had to type import os in train_network.py everytime I have tried to train on a new AxonDeepSeg.

@Paasu I think your config struct in the training.py file you shared is missing an option, which is what your error is indicating.
In the file you uploaded above, you would need to change

# Data augmentation parameters:
  "da-type": "all",  # Type of data augmentation procedure. Option "all" applies all selected data augmentation transformations sequentially, while option "random" only applies one of the selected transformations (randomly) to the sample(s). List of available data augmentation transformations: 'random_rotation', 'noise_addition', 'elastic', 'shifting', 'rescaling' and 'flipping'.
  "da-0-shifting-activate": True,
  "da-1-rescaling-activate": False,
  "da-2-random_rotation-activate": False,
  "da-3-elastic-activate": True,
  "da-4-flipping-activate": True,
  "da-5-noise_addition-activate": False

to

# Data augmentation parameters:
  "da-type": "all",  # Type of data augmentation procedure. Option "all" applies all selected data augmentation transformations sequentially, while option "random" only applies one of the selected transformations (randomly) to the sample(s). List of available data augmentation transformations: 'random_rotation', 'noise_addition', 'elastic', 'shifting', 'rescaling' and 'flipping'.
  "da-0-shifting-activate": True,
  "da-1-rescaling-activate": False,
  "da-2-random_rotation-activate": False,
  "da-3-elastic-activate": True,
  "da-4-flipping-activate": True,
  "da-5-noise_addition-activate": False,
  "da-6-reflection_border-activate": False

Thank you very much @mathieuboudreau everything seems to working fine. I did this on #290 and there is no current issues.


Make extension setting to not underline definitions

Nice work on the extension. It's 100% rad.
As shown in this image here, when I install this extension, it underlines all the controller definitions in web.php:

So I would like to request an extension setting that disables this. It would be nice to have a setting here to enable/disable it:

And as a bonus, it would be nice if F12 would also goto the definition. I have other extensions that open files when I press F12, so it would be nice if this extension could do it also. The example extension I could cite is called Vue Peek.

Opened 2 separate issues, please follow: #11 & #12


Add redirects

Feels like https://docs.api3.org/dapps and https://docs.api3.org/oev-searchers should land somewhere rather than giving a 404. I'm not sure how that's done.

Hello @bbenligiray ik I was not assigned, but seeing as nobody has completed this issue yet, I pulled the issue to a fork and was able to make a minimal solution to resolve the problem.
I included redirects that will bring a user from /dapps to /dapps/overview automatically and from /oev-searchers to /oev-searchers/overview the same way.
I will be making a PR, please let me know if you would need anything else for this issue

There is no file index.md in the root of the /dapp or /oev_searcher folders. Probably a carry over from when these were part of vitepress-docs. Moving and renaming the current target files would be simple but then there is the risk of breaking external links. Not sure if anyone is calling these links outside of the API3 website.

Hello @wkande, I created the index.md files with the intent of allowing for the redirect Hope this cleared up any confusion with that. I am assuming this is okay, as I went through a lot of the links and nothing previously implemented was affected by my changes. All that was affected was the two 404 directed routes of /dapp and /oev-searchers now redirect to the proper pages that a user would look for as per the original request of the issue.

@cduarte3 yes that would work but there will most likely be screen flicker for the redirect. I will clone your repo and run it locally on Friday and see how it behaves.
The better solution is to move the pages you are redirecting to become the index.md file of the root of the URL. This, as I mentioned before, might be an issue in that external links that reference the current files will break. If the solution is not to move/rename the files then another solution is to add redirects to the file https://github.com/api3dao/oev-docs/blob/main/firebase.json. One would need to build the project and them run a local firebase instance to test it.
If I had my way I would move/rename the files and communicate with the owners of the external links.

Thanks for the PR @cduarte3 . I'll have to agree with @wkande here, avoiding an explicit redirect would be ideal, the main objective is for these links to not 404.


Overriding the starting Home Directory: is it rude?

When using a Custom Notebook Image.
In previous versions, when the user would log into the terminal, their location would be their home directory as defined in the image, i.e. /home/jovyan.
Now, in recent versions, when the user logs into the image's Terminal, they land in /opt/app-root/src/.
Upon investigation, in the YAML for the notebook pod, the following statement appears
This workingDir statement apparently overrides the defaults of the customer image.
Jira issue: https://issues.redhat.com/browse/RHODS-6349

Already in Jira from before:  https://github.com/opendatahub-io/odh-dashboard/issues/1817


Correction for raw affiliation Department of Geography, Université Lumière-Lyon 2, CNRS UMR 5600, 86 rue Pasteur, 69365 Lyon cedex 07, France

Correction needed for raw affiliation Department of Geography, Université Lumière-Lyon 2, CNRS UMR 5600, 86 rue Pasteur, 69365 Lyon cedex 07, France
raw_affiliation_name: Department of Geography, Université Lumière-Lyon 2, CNRS UMR 5600, 86 rue Pasteur, 69365 Lyon cedex 07, France
new_rors: 02feahw73;03rth4p18;0256r1e04
previous_rors: 02feahw73;03rth4p18
works_examples: W2078844972
contact: 276aeb296da6e80c4723b3fbc84b5530:0f1ba558655ba4fe6a6cc9c7b241 @ ens-lyon.fr

This issue was accepted and ingested by the OpenAlex team on 2024-12-21. The new affiliations should be visible within the next 7 days.


Checking steamID of refresh token not working

Impossible to confirm validity of steamID refresh token has the wrong field is used (steamID instead of _steamid)
https://github.com/DoctorMcKay/node-steam-user/blob/a3cacf3b1e701c1e560e829cbfab49a4b1640849/components/08-logon.js#L117-L122

I have the same problem.

Thanks, this is fixed in 4.26.1.


Link to awesome-sec-talks

Adds a link to the awesome-sec-talks repository.

add awesome security to awesome-sec-talks?

@sbilly Are you asking whether we should add this site/list to the other, in addition to this PR (which adds the other to this site)? If so, I'm good with that. Just unsure whether you're requesting a change to this PR. Thank you! -K


kitematic doesn't update images that are pulled via command line

Need to remove image, go to my images, re-add image. Then it works.

We have new instructions now and I'm not sure what the issue was in the Philly workshop.


Fixed composer scripts

The repo is still using old CS library and tools
/cc @ezimuel

@webimpress Thanks!


Update tools-for-managing-visual-studio-instances.md

Add more explanatory text on vswhere.exe

@timsneath,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/install/tools-for-managing-visual-studio-instances.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Quick start for CKKS Average/InnerSum

Is it possible to have an example on how to use the evaluator.average/innerSum functions, along with generating and using the necessary rotation keys?

Hello @cutukmirza,
You can find such examples in the ckks_test.go file.

Hello @Pro7ech, thank you for a quick reply and for your help!


Array for..in loop

Flow version: v0.98
Expected behavior
type MyItem = { stuff?: boolean, doSomething: boolean };
class A {
  someArray: Array<MyItem> = [];

  myFunc() {
    for (let i in this.someArray) {
      this.someArray[i].doSomething = false; //ok, because index exists always
    }
    this.someArray.push({doSomething: true});
  }
}

Actual behavior
type MyItem = { stuff?: boolean, doSomething: boolean };
class A {
  someArray: Array<MyItem> = [];

  myFunc() {
    for (let i in this.someArray) {
      this.someArray[i].doSomething = false; //cannot use for .. in because of string index
    }
    this.someArray.push({doSomething: true}); //if type is {[string]: MyItem} i can't use array functions
  }
}

Link to Try-Flow or Github repo: link

This is correct, you shouldn't use for .. in on an array. for .. in iterates over object keys. Use  a for .. of loop or a for loop with numeric index variable.


use NaverThirdPartyLogin.framework can't upload  to AppStore

The old SDK contains uiwebview and has system bugs. When we use the naverthirdpartylogin.framework of GitHub, we find that the upload Appstore reports errors, including the unsupported architectures i386 and x86 ʄ. I hope it can be fixed. Thank you.

@Miko-J
Hi. I think it will be resolved if you download the latest version(4.1.1) of the SDK through cocoapods.
Thanks 👍


PostgreSQLDB(..) constructor doesn't handle port

Passing a port (as an int or a string) isn't honored as it runs against 5432 no matter what you pass in to the constructor.
mara_db.config.databases \
    = lambda: {'mara': mara_db.dbs.PostgreSQLDB(host='localhost', port=25432, user='etl', password='etl', database='etl')}

Follow up - this works for configuring access during run but fails during migration - it's the migration code that does not honor the port:
import mara_db.auto_migration
...
mara_db.auto_migration.auto_discover_models_and_migrate()


Create horizontal_advection.jl

Fixes #3

@ctessum Hmm do you know what happened?

@ctessum Hi Chris, I tried to upload my code (functions in the .jl file) but it has failed. Do you have any idea??

@ctessum Hi Chris, I tried to upload my code (functions in the .jl file) but it has failed. Do you have any idea??

The red x is say that you haven't signed the contributor license agreement: https://github.com/EarthSciML/EnvironmentalTransport.jl/pull/5#issuecomment-1960404770
If you agree to the agreement, you can type "I have reviewed and hereby sign the CLA" below and then it should turn green

I have reviewed and hereby sign the CLA.

recheck

recheck

I have reviewed and hereby sign the CLA

recheck

Hi Chris! I think now it passed all the tests. Could you confirm to merge this change? Let me know if there is anything I need to do!

 Gov4Git notices
On Wednesday, 08-May-24 22:35:07 UTC by Gov4Git dev
Notice gtveop
Started managing this PR as Gov4Git proposal 5 with initial approval score of 0.000000.
This project is managed by Gov4Git, a decentralized governance system for collaborative git projects.
To participate in governance, install the Gov4Git desktop app.
Notice eaxkzk
This PR's approval score is now 0.000000.
The cost of review is 0.000000.
The projected bounty is now 0.000000.
Notice ge4zcz
The set of eligible issues claimed by this PR is now empty.

 Gov4Git notices
On Sunday, 21-Jul-24 07:38:56 UTC by Gov4Git dev
Notice n3awnr
This PR, managed as Gov4Git proposal 5, has been closed 🎉
The PR approval tally was 0.000000.
Bounty of 0.000000 credits was donated to the community's matching fund.
Resolved issues:
Rewarded PR reviewers:
Tally breakdown by user:


Add JSONL specification to README

Sure, I just ripped this from the issue on the spec repo, can update


merge to live

Docs Build status updates of commit 4592049:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Closing. OPS does pass on the latest commit. Will need to force update the live branch as the main branch is out of date.


'sparse submit' should use the user's existing ssh config file

This allows sparse to reuse any user configured ssh keys.
This requires the addition of a single line to the streamparse/ext/fabric.py file, to the activate_env function.
env.use_ssh_config = True

I've added "from fabric.api import env env.use_ssh_config = True" to the fabfile.py, but I get the following error when I ran the "sparse submit" command
Deploying "topology" topology...
bind: Cannot assign requested address
ssh tunnel to Nimbus <IP_ADDRESS>:6627 established.
Routing Python logging to None.
Running lein command to submit topology to nimbus:
lein run -m streamparse.commands.submit_topology/-main topologies/topology.clj --option 'topology.workers=2' --option 'topology.acker.executors=2' --option 'topology.python.path="/home/hadi/Desktop/Storm//topology/bin/python2.7"'
{:option {topology.python.path /home/hadi/Desktop/Storm//topology/bin/python2.7, topology.acker.executors 2, topology.workers 2}, :debug false, :port 6627, :host localhost, :help false}
channel 1016: open failed: administratively prohibited: open failed
channel 1017: open failed: administratively prohibited: open failed
Caught exception: org.apache.thrift7.transport.TTransportException
What should I do?

@hadisotudeh see http://unix.stackexchange.com/questions/14160/ssh-tunneling-error-channel-1-open-failed-administratively-prohibited-open and in the future, for SSH errors, try Googling the error first (found this just by Googling "channel 1016: open failed: administratively prohibited: open failed").

yes, I've searched before, but the problem didn't solve and I thought maybe this problem is special for streamparse projects.

I agree with @amontalenti and made this happen by default now.


Icon optimization - spaces around negatives?

The README contains this section:

Editor icons must be first optimized before being added to the engine, to do so:

Add them to the "/engine/icons/svg" folder.
Run the "optimize.py" script (you must have scour installed).

However, when I run python3 optimize.py, it results in over 300 changed files. Looking in my git client, it appears that they are all removals of spaces around negative numbers:

So, what's up with this? Is this intended behavior? If so, why aren't the fixed versions committed in the repository?

@aaronfranke Is this still relevant with the move to svgcleaner?

@Calinou It's not, but the icons in this repository don't use svgcleaner. If #52 is closed, this can be too.


Can not parse message

When i using this lib to verify message that be sent from siwe client library, it always throw exception can not parse message

Did you solve your problem?
If not, can you post a sample SIWE string that causes the exception?


Update make mth5

This PR is intended to address issue #76. It adds logic to handle request were the run metadata and requested time series data are inconsistent with one another. This PR is stand alone and does not require any changes in MT_metadata. If a run is available in the metadata, that run will be defined in the resulting MTH5 file, but its time series content will all zeros. That is the logic defined at:
https://github.com/kujaku11/mt_metadata/blob/429bd6b85dcd2ab6bc7c866fe6d74dad539b87d9/mt_metadata/timeseries/stationxml/xml_inventory_mt_experiment.py#L92
Only requested times series streams will be loaded into the MTH5 object. If we want MTH5 objects that only contain requested time series and metadata, not all of the runs contained within the stationxml, we could consider changing MT metadata but that logic may be lossy.

Codecov Report

Merging #78 (cf0bf48) into master (8e5cf4b) will decrease coverage by 1.60%.
The diff coverage is 7.14%.

@@            Coverage Diff             @@
##           master      #78      +/-   ##
==========================================
- Coverage   49.33%   47.72%   -1.61%
==========================================
  Files          50       50
  Lines        6334     6164     -170
==========================================
- Hits         3125     2942     -183
- Misses       3209     3222      +13

Impacted Files
Coverage Δ

mth5/clients/make_mth5.py
59.34% <7.14%> (-3.84%)
:arrow_down:

mth5/io/lemi424.py
24.17% <0.00%> (-7.51%)
:arrow_down:

mth5/io/usgs_ascii.py
15.50% <0.00%> (-6.20%)
:arrow_down:

mth5/io/zen.py
10.53% <0.00%> (-3.33%)
:arrow_down:

mth5/io/nims.py
12.04% <0.00%> (-2.96%)
:arrow_down:

mth5/groups/survey.py
52.12% <0.00%> (-2.42%)
:arrow_down:

mth5/groups/master_station_run_channel.py
46.47% <0.00%> (-2.09%)
:arrow_down:

mth5/timeseries/channel_ts.py
62.57% <0.00%> (-1.96%)
:arrow_down:

mth5/mth5.py
58.15% <0.00%> (-1.95%)
:arrow_down:

mth5/tables/mth5_table.py
33.33% <0.00%> (-1.49%)
:arrow_down:

... and 10 more

Continue to review full report at Codecov.

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

@kkappler I reviewer @timronan 's changes.  They all pass on my machine and the resulting MTH5 looks good. Have a look, if you think its all good I will merge the pull request.

tests also passing locally here.  Looks like an improvement - merge away!


Roadmap

deck.gl-community is under open governance through the OpenJS / Linux Foundations. Join the discussion on our slack or attend our bi-weekly meetings: https://www.openvisualization.org/#get-involved
Trackers for individual modules

#80
#38
#78
#79

Candidate modules

raster-layers
earthengine-layers
viv-layers

Hi, are there any plans to support brush mode? Including brush add and remove


PHOENIX-6514 Exception should be thrown

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  6s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ master Compile Tests _

+1 :green_heart:
mvninstall
21m 34s
master passed

+0
hbaserecompile
28m 20s
HBase recompiled.

+1 :green_heart:
compile
1m  4s
master passed

+1 :green_heart:
checkstyle
0m 40s
master passed

+1 :green_heart:
javadoc
0m 50s
master passed

+0 :ok:
spotbugs
3m  3s
phoenix-core in master has 965 extant spotbugs warnings.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
13m 35s
the patch passed

+0
hbaserecompile
23m  6s
HBase recompiled.

+1 :green_heart:
compile
1m  2s
the patch passed

+1 :green_heart:
javac
1m  2s
the patch passed

+1 :green_heart:
checkstyle
0m 40s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
javadoc
0m 50s
the patch passed

+1 :green_heart:
spotbugs
3m 19s
phoenix-core generated 0 new + 964 unchanged - 1 fixed = 964 total (was 965)

_ Other Tests _

-1 :x:
unit
116m 28s
phoenix-core in the patch failed.

+1 :green_heart:
asflicense
0m 44s
The patch does not generate ASF License warnings.

181m 26s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1267/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/phoenix/pull/1267

Optional Tests
dupname asflicense javac javadoc unit spotbugs hbaserebuild hbaseanti checkstyle compile

uname
Linux 3679f3e611bb 4.15.0-65-generic #74-Ubuntu SMP Tue Sep 17 17:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev/phoenix-personality.sh

git revision
master / a1044c9

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

unit
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1267/1/artifact/yetus-general-check/output/patch-unit-phoenix-core.txt

Test Results
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1267/1/testReport/

Max. process+thread count
11755 (vs. ulimit of 30000)

modules
C: phoenix-core U: phoenix-core

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1267/1/console

versions
git=2.7.4 maven=3.3.9 spotbugs=4.1.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

The unit test passed but somehow failed during jacoco step, which is unrelated.

The jacoco failures are a known problem


Tighten up our keep alive usage.

Provide the Connection (keep alive) header automatically for users.  They could conceivably override this -- it's set before the route callback is invoked -- but right now, headers are additive only... so that might be a problem down the line.  This at least gets things a little more streamlined.
Let me know what you think.  This should work OK with a HTTP/1.0 connection, I believe, if they send the right headers... but obviously HTTP/1.0 doesn't officially support keep alives.

I like how you've restructured things :) But I don't think this is following the HTTP 1.1 section 14.10: Connection specification.
By default in HTTP 1.1 connections are persistent by default unless the Connection; close header is defined.

HTTP/1.1 defines the "close" connection option for the sender to signal that the connection will be closed after completion of the response. For example,
  Connection: close

I suppose we should support modifying headers huh? Can you create another GitHub issue related to that so we can track it please? :)

I can create another PR for modifying headers, yeah, but let's fix this one, too.
Let's see, so, going over a few things again -- namely the RFC and "HTTP Made Really Easy" -- this is what I came up with:

if HTTP/1.1, and no Connection header from sender: stay open, no Connection header in response
if HTTP/1.1, and Connection header from sender:
-- if "close": close after request, no Connection header in response
-- if anything else: stay open, no Connection in response
if HTTP/1.0: close after request, no Connection header in response
if disabled entirely (future config?): close after request, send "Connection: close" in response

That seems to jive with most stuff: if you're HTTP/1.1, then you don't need to advertise that you support keep-alives, but you need to say if you don't.  Same with the client.
Sound reasonable to you?  I can take a 2nd pass, if so.

I would need to double check this, but I think if a client using HTTP/1.1 sends a Connection: close, the server echos that Connection: close header back.  This tells the client to close the socket after it has finished reading the response representation.  This avoids the client having to remember that it sent a Connection:close header with the request.

So, spot testing reveals that you are, at least empirically, correct.  The biggest hiccup I saw was that some web servers actually send back "Connection: keep-alive" even when I specifically the "Connection: close" header.  This only happened on a redirect from Yahoo, but it happened from Apache Traffic Server.. so it's not a superrrr esoteric web server.

What's the status of this? Are we handling HTTP 1.1 currently in this PR?


Interface bug

Version: [mw3.0_sqr-0.7.21 BETA_mc1.12.2]
There are certain bugs with the interfaces of such mods as: Galacticraft or Techguns, which makes it impossible to open one of them

latest.log

latest.log


Revert "Support split broadcast join condition into ast and non-ast […

…databricks] (#9760)"
This reverts commit 7c307d489b099bd1d73f8ec4b9b953a05ca24dec.
There is an issue reported by NDS https://github.com/NVIDIA/spark-rapids/issues/10047 WIP on a fix.

build

build

build


Refactored out move generation

Fixes #25
Adds to #30

Current coverage is 81.94%

Merging #32 into master will increase coverage by +35.22% as of 130c9bf

@@            master     #32   diff @@
======================================
  Files           16      24     +8
  Stmts          336     349    +13
  Branches        53      55     +2
  Methods          0       0
======================================
+ Hit            157     286   +129
- Partial          0      13    +13
+ Missed         179      50   -129

Review entire Coverage Diff as of 130c9bf

Powered by Codecov. Updated on successful CI builds.


Not able to slide in IE 11

In IE 11, everything is loading fine except the slider stays in the middle and is not able to be dragged.

Did anyone find a solution to this? I've just used this plugin for a project and stumbled across the same issue in testing :/

I just tested with IE11 (and emulated as IE9) and the plugin worked fine.

@AllenMay I managed to get around the issue by changing the version of jQuery Event Move - it seems like the issue is with that dependency rather than the plugin itself.

I have the same problem. This plugin use jQuery.event.move, which use ES6 feature such as Symbol and customEvent, so solution is add support for them in ie 11:

Use babel-polypill (for add support Symbol) https://babeljs.io/docs/usage/polyfill/
Use polypill for customEvent https://developer.mozilla.org/ru/docs/Web/API/CustomEvent/CustomEvent

@jamie-endeavour could I get a zip of your files that work in IE? I am still having a hard time getting it to run in IE11. Thanks.

@OneSprague yes of course, I'll put something together this evening. The setup of the project I worked on meant resorting to an older version of jQuery Event Move - but as a result I noticed that newer versions of jQuery had conflicting issues as well... I'd stick with polyfill's if you can rather than reverting to older version of jQuery and jQuery.event.move but I'll try and put something in more detail together tonight - have you tried something like this (following on from @loyko-vitaliy's suggestion) https://github.com/krambuhl/custom-event-polyfill - see custom-event-polyfill.js ?

@jamie-endeavour Thanks - I gave that a try, but still no luck. I have re-downloaded twentytwenty and even it's index.html does not work in ie11, but strangely it works on their landing page? :(

@OneSprague I managed to get this working with a Polyfill. I've tested in Browser stack and found this worked okay - I've only tested IE11 as didn't have much time like but I assume it should be okay, you'll need to check...
https://github.com/jamie-endeavour/twentytwenty
Feel free to fork this and let me know how it goes. The polyfill I used was https://polyfill.io/v2/docs/ - note that I've just included directly from the CDN.

I did manage to get it to work with the Polyfill from the CDN. Thank You!

Awesome that's great news glad to have been of assistance @OneSprague!

It would be cool if a core maintainer could add this gotcha to the documentation/examples. I've cloned this repo and created a branch locally but I'm unable to push a branch and therefore raise a PR. Can anyone advise on how to contribute as I'd be willing to do the above 😃

Same issue, but even with the polyfill the slider isn't working on IE11. Could it potentially be any other jquery files that are clashing with it once minified!? Can't post a link to the site at the moment as it's not yet live, just under development. @jamie-endeavour

@ChrisWebWales it sounds like it could be a conflict with a dependency are you getting any errors in the console? If so are you able to paste it here? Also what version of jQuery/jQuery.event.move are you using? I'm happy to take a look this weekend to see if I can help you figure out a work around?

Hi Jamie. First up, thanks for your help.
Is it ok to look at it Monday? I've finished for the weekend, All the work
is in my office and I have no way of retrieving it over the weekend.
Many thanks either way :)
On Fri, 18 Aug 2017 at 17:01, Jamie Bradley<EMAIL_ADDRESS>wrote:

@ChrisWebWales https://github.com/chriswebwales it sounds like it could
be a conflict with a dependency are you getting any errors in the console?
If so are you able to paste it here? Also what version of
jQuery/jQuery.event.move are you using? I'm happy to take a look this
weekend to see if I can help you figure out a work around?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/zurb/twentytwenty/issues/78#issuecomment-323393285,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AdseNuF6rFZLMH7gvvP2Hh074rLr7rOsks5sZbUwgaJpZM4N9arj
.

--
Kind Regards,
Chris Broad
07947 346643
<EMAIL_ADDRESS>www.websolutionswales.com

Build simple example with last version jQuery and other plugins...Try this in archive below, I'm tested on virtual mashine - all good work on ie 11.[
sample.zip
](url)

@loyko-vitaliy
Perfect, thank you very much, this fixed it.

@loyko-vitaliy on resize is still a little funky as it doesn't adjust the height dynamically as it does in Chrome, but it's at worst functional which is brilliant.

ChrisWebWales,  this can fixed  by written styles.
I'm not show example how you need write html and css..., only working plugin.
Fix resize ...
sample.zip

I believe this is now addressed in the library itself. I included a polyfill for customEvent and made the Symbol optional.


TypeError: cannot pickle 'SSLContext' object

Hi!I found this problem while running the program:“TypeError: cannot pickle 'SSLContext' object”.
According to my observation, this problem occurs when saving the Agent after each round.
In simulator.py, line1312 :
recagent.save(os.path.join(config["simulator_dir"]))

and line 111:
 dill.dump(self.__dict__, f)

I found that the agents in the state in self.__dict__ contain information about all agents in the system. Among these information is a variable named memory, which contains:
llm = {ChatOpenAI} client=<openai.resources.chat.completions.Completions object at 0x000002638B3C7100 >

Such informations.
This includes the type of LLM you have chosen, your api_key, and other information.
This object is exactly the 'SLContext' object.
How can I solve this problem?

Hi @Diuyilu,
We have fixed the issue with saving the simulator. Please pull the latest code to apply the fix.

Hi @Paitesanshi，
Sorry for taking so long to reply to the message.
After trying, I found that this bug still exists.
Due to poor CPU performance on the server, I switched the word embedding model ’all-mpnet-base-v2"‘ back to the previous OpenAI embedding model. In this situation, how should I save it?

Hi @Diuyilu ,
Could you share more information about the error you're encountering? Also, is it the same issue as before or are there any new differences?

Hi @Diuyilu,
We've identified the root cause of the error. Could you please pull the latest code from the main branch and install the following versions?
langchain==0.0.186
openai==0.27.8

Let us know if you encounter any further issues.

Hi @Paitesanshi,After using the old versions of Langchain and OpenAI, the issue of saving has been resolved! Thanks for your answer! This question is really a bit strange……

Thank you for your feedback! We will proceed with closing this issue if there are no further questions.

True!

Sure.


Add TargetMethod() to Affinity

Useful to getting types that are not available at compile time
Adding TargetMethods() too would be nice
https://harmony.pardeike.net/articles/patching-auxilary.html#auxilary-patch-methods

Could you provide an example of how you'd want this to look like with the Affinity system?

Adding a [AffinityTargetMethod] attribute to complement [HarmonyTargetMethod]
Instead of needing to specific method to patch from [AffinityPatch], call a method that returns what method to patch.
[HarmonyTargetMethod]
private static MethodBase CalculateMethod()

[AffinityTargetMethod]
private MethodBase CalculateMethod()

An example is where you need to target a private type
[AffinityPostfix]
[AffinityPatch(typeof(BeatmapObjectsInTimeRowProcessor.SliderTailData), "GetCopy")]
// not possible, as this is a private class
private void Postfix()

[AffinityTargetMethod]
private MethodBase TargetMethod()
{
  Type type = Type.GetType("BeatmapObjectsInTimeRowProcessor+SliderTailData,BeatmapCore");
  return AccessTools.Method(type, "GetCopy");
}

[AffinityPostfix]
private void Postfix()

What about when you want multiple target methods for different affinity patches? How do you think they should be distinguished?

Following how Harmony does it: only allow one target method for a class and disallow using individual annotations with [AffinityTargetMethod]
https://github.com/BepInEx/HarmonyX/blob/master/Harmony/Public/PatchClassProcessor.cs#L142
[AffinityTargetMethod]
private MethodBase TargetMethod()
{
  return AccessTools.Method(typeof(something), "something");
}

[AffinityPostfix]
[AffinityPatch(typeof(something), "something")]
// invalid to use this while [AffinityTargetMethod] defined and will throw
private void Postfix()


Can't build tour example for wasm32, pulling in net2 as dependency

When trying to build the tour example for wasm32 cargo build --example tour --target wasm32-unknown-unknown, I am getting a compilation error due to it trying to compile the net2 library. This dependency appears to be pulled in by window_clipboard in iced_winit, which seems like a relatively recent addition.
window_clipboard v0.1.0-alpha.2 (https://github.com/hecrj/window_clipboard?rev=22c6dd6c04cd05d528029b50a30c56417cd4bebf#22c6dd6c)
├── clipboard_wayland v0.1.0-alpha (https://github.com/hecrj/window_clipboard?rev=22c6dd6c04cd05d528029b50a30c56417cd4bebf#22c6dd6c)
│   └── smithay-clipboard v0.3.6
│       └── smithay-client-toolkit v0.6.4
│           ├── wayland-client v0.23.6
│           │   ├── calloop v0.4.4
│           │   │   ├── mio v0.6.21
│           │   │   │   ├── net2 v0.2.33

This is a duplicate of #142. I should add a note in the iced_web readme.
window_clipboard is only used in iced_native, though. The issue is most likely in a dev dependency, probably async-std.

Ahh, sorry for opening a duplicated issue. Thanks for the clarification. I'll wait for the 0.1.0 release.

No worries! Duplicate issues are fine!
There is a big native PR landing soon, I'll try to get iced_web up to speed soon after that!

Awesome! Thanks so much for your work on this crate. I really like the direction this project is going and can't wait to see where it goes.


Add pyAPNG to Conda Forge

Hi,
Any chance to make pyAPNG available on Conda Forge?

I have no experience with Conda but I can take a look if there are some instructions.

I have found this: https://blog.gishub.org/how-to-publish-a-python-package-on-conda-forge.
This is the official guide: https://conda-forge.org/docs/maintainer/adding_pkgs.html.
I have never done on my own, but in previous cases I asked, the maintainers got it pretty quickly.
So probably it shouldn't be too much work.

https://github.com/conda-forge/staged-recipes/pull/24180

Done

Indeed: https://anaconda.org/conda-forge/apng.


WhoAmI / me commands not returning anything

System info:
ProductName:	Mac OS X
ProductVersion:	10.10.3
BuildVersion:	14D136

Running me and whoami return nothing when I'm not logged in, when it seems they should return You are not logged in.
$ gitter-cli me

$

Thanks @travs for reporting this!


req.body.long_url is undefined

Hey,
Thanks for creating this! Awesome library!
I'm running into an issue req.body.long_url being undefined no matter if I try raw json, form-data or any other option I have for a parameter.
Do you have any advice?
Thanks!

Which tool your using to make post request?
Below are sample codes
For cUrl request
curl -X POST \
  http://localhost:3000/api/v1/shorten \
  -H 'content-type: application/x-www-form-urlencoded' \
  -d long_url=https%3A%2F%2Fgoogle.com%2F

for jQuery ajax
var settings = {
  "async": true,
  "crossDomain": true,
  "url": "http://localhost:3000/api/v1/shorten",
  "method": "POST",
  "headers": {
    "content-type": "application/x-www-form-urlencoded",
  },
  "data": {
    "long_url": "https://google.com/"
  }
}

$.ajax(settings).done(function (response) {
  console.log(response);
});


fix: Add GlobSourceResult to globSource return type in unixfs.

Title
fix: Add GlobSourceResult to globSource return type.
Description
This is a small PR that modifies the return type on the globSource utility in @helia/unixfs to return the GlobSourceResult in addition to the ImportCandidate type. This means that the path property will be a string instead of string | undefined.
Notes & open questions
This PR makes it a bit easier to use globSource since it is a bit annoying to have to check if path is defined when it always is.
Is there any reason why we had the GlobSourceResult type but globSource does not return it?
Change checklist

[x] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation if necessary (this includes comments as well)
[ ] I have added tests that prove my fix is effective or that my feature works

Thanks!

Is there any reason why we had the GlobSourceResult type but globSource does not return it?

No, just an oversight, I think.


Signup template

Just the template.
should i link routes and push again?

Yes, we can reuse the components