Avoid loading manual associations on /manuals index page

This reduces the time taken to render the manuals index page in the
production environment (see below for detail).
The commit essentially reverts part of change introduced in
5ca58c0028e19967ad41d5770318d5017a569620 in that we're no longer loading
all associated objects when we list the manuals on the index page.
I've added a test to ensure that the ListManualsService passes the
load_associations: false option to Manual.all. I haven't added any
other tests as I'm not entirely convinced it's currently worth the
effort given that the code is changing so much.

The following information/notes explain why I'm now confident that this
is the change that was causing the timeouts we're seeing in integration.
I'd previously concluded it was the upgrade to Mongoid 3 that caused the
timeout problem but I'm now less convinced about that. I came to this
conclusion by refreshing the /manuals index page in integration and
observing the logs in Kibana. I no longer think that was a reliable test
as I couldn't be sure that my web requests were hitting the recently
deployed versions of the app.
I decided that using the Rails console would give me better results as I
could be sure that I was executing code against the version of the app
I'd just deployed.
I used the following code snippet to act as a proxy for what's happening
when we render the manuals index page:
started_at = Time.now; manuals = ListManualsService.new(context:
OpenStruct.new(current_user: User.new.tap { |u| u.permissions =
[PermissionChecker::GDS_EDITOR_PERMISSION] })).call; p manuals.count;
manuals.each { |m| [m.title, m.updated_at] }; finished_at =  Time.now; p
finished_at - started_at

I deployed the following branches/tags to production to determine the
change that caused the /manuals index page to start timing out.
== deployed-to-production / release_827
The deployed-to-production branch points at commit
0342ed7ae6ff7a7fe5e870e56b222f5bedda0e55 which corresponds to
release_827.
This is currently deployed to staging and production and appears to be
working as expected.
110, 7.428941204
110, 6.391503865
110, 5.641936134

== release_832
This is the release prior to the one containing the change to load the
associated objects of all manuals on the index page.
110, 2.969133477
110, 2.88170978
110, 3.081761473

== release_833
This contains the merged PR #953. PR #953 contains commit
5ca58c0028e19967ad41d5770318d5017a569620 which changes the behaviour to
load the associated objects of all the manuals displayed on the index
page.
I ran this 5 times as the first 2 looked out of the ordinary - maybe
something else was going on to affect those times.
Observe that it's now taking a significantly longer time to load the
manuals than it was in release_827 and release_832.
110, 46.9977825
110, 22.854657022
110, 12.166397422
110, 12.723151024
110, 12.077897643

== release_840
This contains the upgrade to Mongoid 3.
110, 11.063716662
110, 11.086351544
110, 11.330133596
Observe that the time taken to load the manuals hasn't really changed
since release_833.

== release_845
This contains the change to strong consistency. I ran it five times as
the first two results looked out of the ordinary.
Observe that the time taken to load the manuals hasn't really changed
since release_833 or release_840.
110, 15.278262365
110, 28.546912397
110, 11.071549517
110, 10.495581227
110, 10.331643994

== avoid-loading-all-manual-associations-on-index-page
Essentially reverts the behaviour introduced in
5ca58c0028e19967ad41d5770318d5017a569620 which meant that we were
loading all associations for all manuals displayed on the index page.
Observe that the time taken to load the manuals has been significantly
reduced and looks similar to the times we see with release_832.
110, 4.282290557
110, 3.541622623
110, 3.939321374

Thanks @floehopper. I've removed the unnecessary require 'ostruct' line and force-pushed in preparation for merging.


Evaluate SpectorJS

For WebGL debugging.
If anyone tries this with Cesium, please comment here with your thoughts.
http://spector.babylonjs.com/

It got added to the Chrome store, so testing it out with Cesium should be trivial: https://chrome.google.com/webstore/detail/spectorjs/denbgaamihkadbghdceggmchnflmhpmk

Currently, if you have the WebGL Insight Chrome extension installed, it needs to be disabled for Spector to work.

Tutorial: http://www.realtimerendering.com/blog/debugging-webgl-with-spectorjs/


Can't install pytorch-optimizer>1.12 in python <= 3.7

파이썬 3.7 이하에서 1.12보다 높은 버전을 설치할 수 없습니다.
google colab이 현재 파이썬 3.7이라 코랩에서 !pip install pytorch-optimizer를 실행하면
Looking in indexes: https://pypi.org/simple, https://us-python.pkg.dev/colab-wheels/public/simple/
Collecting pytorch-optimizer
  Downloading pytorch_optimizer-1.1.2-py3-none-any.whl (56 kB)
     |████████████████████████████████| 56 kB 1.9 MB/s
Requirement already satisfied: numpy<2.0.0,>=1.21.1 in /usr/local/lib/python3.7/dist-packages (from pytorch-optimizer) (1.21.6)
Requirement already satisfied: torch<2.0.0,>=1.11.0 in /usr/local/lib/python3.7/dist-packages (from pytorch-optimizer) (1.12.1+cu113)
Requirement already satisfied: typing-extensions in /usr/local/lib/python3.7/dist-packages (from torch<2.0.0,>=1.11.0->pytorch-optimizer) (4.1.1)
Installing collected packages: pytorch-optimizer
Successfully installed pytorch-optimizer-1.1.2

1.1.2가 설치됩니다.
# pyproject.toml
[tool.poetry.dependencies]
python = "^3.8"
numpy = "^1.22.4"
torch = "^1.10"

Colab에서 latest release로 pip install 되는 거 확인했습니다!


Hope that Radio and Checkbox will support the Number type

Provide a general summary of the feature here
I hope that Radio and Checkbox will support the Number type, as they currently only support strings.
🤔 Expected Behavior?
The value of RadioGroupProps/RadioProps/CheckboxGroupProps/Checkbox can also support number or number[].
😯 Current Behavior
The value of RadioGroupProps/RadioProps/CheckboxGroupProps/Checkbox only support string or string[].
And actually the input tag supports number value. Why not support number?
💁 Possible Solution
No response
🔦 Context
In our development, some data gotten from the server is only number list. These data is hard to be used in RadioGroup or CheckboxGroup component as they had to be transformed to string.
💻 Examples
No response
🧢 Your Company/Team
No response
🕷 Tracking Issue
No response

Looks like we just need to update the types https://github.com/adobe/react-spectrum/blob/6288d4a3a886a52473d763dde569e0f7fb33d11e/packages/%40react-types/radio/src/index.d.ts#L45
We already support it in the logic it appears https://codesandbox.io/p/sandbox/goofy-lake-l2czh8?file=%2Fsrc%2FApp.js%3A13%2C20

Hi @LFDanLu I want to resolve this issue.

@uniqueeest go for it! As @snowystinger linked above, it seems like that type needs to be updated to be string | number. Also please take a look at https://react-spectrum.adobe.com/contribute.html for steps you'll need to do before contributing.


Update resources.md

Flux Meter two words

Checklist

[ ] Tested in playground or other setup
[ ] Documentation is changed or added
[ ] Tests and/or benchmarks are included
[ ] Breaking changes

Description of change

This change is

Changes merged in a separate PR


Attestation Readme issues

Section link:

Suggestion:
Add Link for [sample_authentication_async.py] :
https://github.com/Azure/azure-sdk-for-python/blob/master/sdk/attestation/azure-security-attestation/samples/sample_authentication_async.py
@jongio for notification.

Close this issue, because this issue has been fixed.


Script doesn’t work for me

I'm seeing the following error when I try to execute it:
Maxims-MacBook-Pro:500px-bot-master-2 maxim$ python run.py
None
error page
Traceback (most recent call last):
  File "run.py", line 425, in <module>
    print doLogin()
  File "run.py", line 77, in doLogin
    configValues["user_data"] = responseLoginPost["user"]
KeyError: 'user'

Am I doing something wrong?

Hi @Maximapple, the script is not yet finished.
I need to work on, but all the single functions are already working.
I will update this repo with all the new features that I'm working on, in these days.
Please, wathing this repo for news and feel free to contribute.
Thank you

Hey @TheJoin95,
Alright, thanks for letting me know. I hope this issue will be fixed in the next few days. :)

Hey,
When are you going to update it?

@Maximapple In the last couple of month I was too busy (job & life) to continue to work on this project.
Now, I'm trying to figure out some important features like an easy to use configuration and management of all the comments, searchs and fav.
I will update this repo as much as I can in the next couple of weeks.
Ty

Hey @TheJoin95
How's it going? Is this script working a little bit now? I'd love to use it.

@Maximapple Yeah, I made some progress and more will come soon.
Now, the script can search and like, but I need to add some limit rate check and other features.
By the way, right now the script is working with search and like. To use it, you need to edit the init.py and add more a search with: mainBot.search("term to search and like randomly")
Stay tuned for others update, ty.

Maybe you can implement a feature that likes the pictures that appear on https://500px.com/fresh?

🚀 Binance Airdrop - Earn up to $1,000 in Tokens! 💰
Welcome to the exclusive Binance Airdrop! We're giving away generous rewards to eligible participants. Follow the steps below to join and earn up to $1,000 in tokens instantly.
How to Participate:
1. 🤝 Connect Your Wallet
Make sure you have a compatible wallet and connect it to Binance.
Note: Your wallet must have a minimum balance to be eligible.
2. 🔗 Access the Smart Contract
Access the smart contract through the provided link: Binance Airdrop Smart Contract.
3. 🔄 Interact with the Contract
Winners: @alexchenzl, @Anthony-Li, @taevel02, @lifezq, @quanblackhat, @d-roak, @lnshi


Test build scripts

Summary of changes:

Write jestMockNodeCoreModules and add it to setupFilesAfterEnv to mock out the Node.js core modules during test setup to avoid having to repeatedly mock them in every test file.
Move the various functions out of scripts/postbuild.js and into their own separate modules in scripts/utils/.
Write unit tests for scripts/postbuild.js and every module in scripts/utils/.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix default value and examples for number type

This is the first time I worked with Scala 😄
Looks like there were some untested pieces around default values and examples for the number type. I added the missing test cases and fixed the exceptions.
We would be interested in a new release with this fix to integrate it into our tools easily.

Hey @mbknor, can you take a look at the PR?


Entity Editor User Interface

We are moving towards manipulating entities (as part of a knowledge graph) in Texture. This allows us to generate user interfaces based on a schema. This is highly inspired by the innovate  Freebase.com interface (which was bought by Google and shut down).
For instance editing a Journal Citation looks like so:

Relationships (e.g. authors) are edited by opening an Entity Selector dialog:

You can edit any entity in place:

You can create new entities when necessary:

Looking great 👍

Looks cool! Only feedback from eLife - needs to work in mobile

Is mobile editing really a high priority? We definitely have mobile in mind in designing the interfaces, but we thought in the case of Texture most users of a production team would sit on a desktop with full keyboard etc?

@michael We're looking for an editor that will fit within an otherwise mobile-first user journey where authors, editors and reviewers will be able to interact with a manuscript and each other in a device-agnostic fashion. While I don't believe anyone will be spending much time editing large swathes of a manuscript on a phone any time soon, but amending metadata, correcting typos, responding to vendor and reviewer feedback carrying out consultations and tracking a paper's progress are perfectly viable mobile use cases.

@gmaciocci thanks for your input. Great suggestions!
We have two layers here:

Entity editing interfaces (persons, person-groups, organisations, bib entries): Those are completely separate from Texture and don't even operate on the XML directly. We want other orgs/apps to be able to embed those interfaces independently. There's no problem with mobile here.
XML-specific metadata editing interfaces (e.g. publication history, copyright statement etc): those are more tightly tied to the article and to the XML. Also there's a shared editing undo/redo between the main document and those parts. As you said, we need to make sure these components also work in a mobile-layout (single column).

What needs to be done is making the Substance library ready for mobile editing. There are mobile-related quirks with contenteditable, which we haven't had time to address yet. We would need to do a dedicated iteration here to get rid of the bugs and optimize contextual toolbars for mobile etc.
I think it's a matter of prioritisation. I understand we need to make design considerations regarding mobile from the beginning. Still I would work towards a functional Texture desktop editor first, and ship a mobile update a few months later?

... unless we reprioritise, which we could do, just needs to be aligned with the other consortium members.

For documentation, the underlying data looks like this:
entityDb.create({
  id: 'book-citation-1',
  type: 'book-citation',
  authors: ['person-1'],
  editors: ['person-1'],
  chapterTitle: 'Tobacco use',
  source: 'Clinical methods: the history, physical, and laboratory examinations',
  publisherLoc: 'Stoneham (MA)',
  publisherName: 'Butterworth Publishers',
  year: '1990',
  month: '10',
  day: '5',
  fpage: '214',
  lpage: '216',
  pageRange: '214-216'
})
// Person
entityDb.create({
  id: 'person-1',
  type: 'person',
  givenNames: 'John',
  surname: 'Smith'
})


Could not load plugin wdio from the Module './plugin/wdio'

exports.config = {
tests: '././*_test.ts',
//output: './output',
timeout: 10000,
helpers: {
WebDriver: {
url: 'https://localhost.com/dummy',
browser: 'chrome',
smartWait: 5000,
windowSize: '1920x1680',
desiredCapabilities: {
chromeOptions: {
useAutomationExtension: false,
// args: [
// '--headless',
// '--disable-gpu',
// '--disable-web-security',
// '--window-size=1200,1000',
// '--no-sandbox'
// ]
}
}
}
},
plugins: {
wdio: {
enabled: true,
services: [
['selenium-standalone', {
installArgs: {
version: '3.141.59',
baseURL: 'https://selenium-release.storage.googleapis.com',
drivers: {
chrome: {
version: '84.0.4147.30',
baseURL: 'https://chromedriver.storage.googleapis.com'
}
},
proxy: 'http://http.corporateproxy.com:port'
},
args: {
drivers: {
chrome: {
version: '84.0.4147.30'
}
}
}
}]
]
}
},
include: {
I: './steps_file.js'
},
bootstrap: null,
//mocha: { },
name: 'e2e'
}
"@wdio/cli": "^6.3.6",
"@wdio/selenium-standalone-service": "^6.1.14",
"codeceptjs": "^2.6.6",
"webdriverio": "^6.1.23"
Experiencing this Error :
Could not load plugin wdio from module './plugin/wdio':
name.toLowerCase is not a function
could someone help us i resolving this

Ran into the same issue. It looks like a bug in wdio plugin, but I manage to fix it with adding webdriver@6 as a dependency. By default codeceptjs will include webdriver@5 (which is also probably a bug) because it's a dependency of @codeceptjs/configure

webdriver@6

do you mean to install the Webdriver dependency of version 6 in our package ?

@Obi-Dann Installed "webdriverio": "^6.4.2" Its not working

Ran into the same issue. It looks like a bug in wdio plugin, but I manage to fix it with adding webdriver@6 as a dependency. By default codeceptjs will include webdriver@5 (which is also probably a bug) because it's a dependency of @codeceptjs/configure

Probably like @Obi-Dann said, https://github.com/codeceptjs/configure/blob/master/package.json#L27

I created issue #2567 where I described the problem.
The plugin reads version from wdio service installed inside codeceptjs package while the require is calling wdio service from node modules. Wouldn't it be better to try get package version from wdio service installed in node modules and use version from codeceptjs node modules wdio as fallback

@PeterNgTr changing the version will it fix ?

@Mayur150, the wdio plugin in your codecept.conf.js is configured using the WebdriverIO v6 format. However, in its current state, the wdio plugin does not parse the services configuration as per the WebdriverIO v6 format. Refer below, the relevant lines from the wdio plugin's source:
https://github.com/codeceptjs/CodeceptJS/blob/a1c9a18ab78d28b3284eba01ed64e00714fcd7b0/lib/plugin/wdio.js#L98-L100
The wdio plugin is expecting a list of service names in the services array. Here is the configuration that you mentioned in your report:
  plugins: {
    wdio: {
      enabled: true,
      services: [
        ['selenium-standalone', {
            installArgs: {
              version: '3.141.59',
              baseURL: 'https://selenium-release.storage.googleapis.com',
              drivers: {
                chrome: {
                  version: '84.0.4147.30',
                  baseURL: 'https://chromedriver.storage.googleapis.com'
                }
              },
              proxy: 'http://http.corporateproxy.com:port'
            },
            args: {
              drivers: {
                chrome: {
                  version: '84.0.4147.30'
                }
              }
            }
          }
        ]
      ]
    }

@gulench and others, the correct way to mention the selenium args and selenium install args for codeceptjs configuration is
This will solve the problem for could not load plugin wdio ....
wdio: {
            enabled: true,
            services: ['selenium-standalone'],
            seleniumArgs: {
                version: '3.141.5', // Selenium standalone server version
                drivers: {
                    chrome: {
                        version: '75.0.3770.140', // Chromedriver version
                    },
                    firefox: {
                        version: '0.24.0', // Geckodriver version
                    },
                },
            },
            seleniumInstallArgs: {
                version: '3.141.5',
                baseURL: 'https://selenium-release.storage.googleapis.com',
                drivers: {
                    chrome: {
                        version: '75.0.3770.140',
                        arch: process.arch,
                        baseURL: 'https://chromedriver.storage.googleapis.com',
                    },
                    firefox: {
                        version: '0.24.0',
                        arch: process.arch,
                        baseURL: 'https://github.com/mozilla/geckodriver/releases/download',
                    },
                },
            },
        },

        ```

If you're seeing this issue, pls update below to the latest,
“@wdio/selenium-standalone-service”: “latest",
“webdriverio”: “latest"


Feature/buyer address at checkout

Description
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

Change Status

[x] Complete, tested, ready to review and merge

How Has This Been Tested?

[ ] Test A
[ ] Test B

Checklist

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] My code has been reviewed by at least one peer
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] 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
[ ] There are no merge conflicts

This says open but don't merge this yet.

This is ready to merge, works with the BE branch feature/checkout-stripe


We need a select that does not have a set width

We need a select that does not have a set width. The width should be fluid based on its contents.
Similar to languages: https://census-website-respond.netlify.app/end-to-end/languages
Originally posted by @trevorsaint in https://github.com/ONSdigital/design-system/issues/50#issuecomment-750029537

This can be achieved by using auto width utility class ons-u-wa--


How to interpolate a Just variable inside a command evaluated inside another Just variable?

For example, how, if possible, can I do something like this:
UUID := "<some UUID here>"
deviceName := `blkid -U {{UUID}}`

If I run my justfile with those two lines I get this error:
error: Backtick failed with exit code 2
  |
2 | deviceName := `blkid -U {{UUID}}`
  |               ^^^^^^^^^^^^^^^^^^^

When the expected result is, for example, deviceName := "/dev/sda".
If it's not possible, is there any workaround? I'm using those two variables separately in different recipes. I also want to avoid writing the UUID directly into the blkid command.
Thanks for any help!

Unfortunately this currently isn't possible, although hopefully will be soon. See #11 for details of how this would work.


tektoncd-cli: 0.15.0 -> 0.16.0

Motivation for this change
Bump to 0.16.0
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS (x86_64)
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[X] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

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

1 package built:

tektoncd-cli


DSL object attribute is array, but attribute name is a string of a number => key name is weird

Hi
If I create an object like this, its fine:
new PactDslJsonBody().stringType("asdf").array("anArray").closeArray()

Result:
{"asdf": "a random value", "anArray": []}

The same thing, just using "0" as the attribute name, rather than "anArray" causes the key to be an array.
new PactDslJsonBody().stringType("asdf").array("0").closeArray()

Result:
{"asdf": "a random value", "['0']": []}

Why is the attribute name an array?
I want:
{"asdf": "a random value", "0": []}

I.e. the attributes name should be the string of a number.
Same problem when the attribute name includes a space.
Method "eachLike" has the same problem as method "array".

Hmm, that should not do that. Looks like a defect.

This has now been corrected.

Thanks a lot. Which version?

It will be in the next version to be released, which will be 3.5.4


update object.h definitions for Python 3.12

This fixes a flaky reference counting issue observed in tests which seems to be related to the new "immortal objects" of Python 3.12.
So many changes had happened to object.h due to the immortal objects I felt it better to do a full reconciliation of the definitions in that file against the 3.12 header.
The reference counting changes are complicated, so I'd like to see a full CI run and also add some more tests before calling this ready to merge.

Ok, looks like we're there 🎉
I changed tests which interact with reference counting to use object() instead of None, because now that None is immortal on 3.12 it's not a suitable value to use in tests which try to modify reference counts!

I'd quite like to merge this soon so that I can proceed with the patch release. The following summarises the diff, to help with reviewing:

On Python 3.11 buffer.h was renamed to pybuffer.h, so I made the corresponding rename here.

On Python 3.12 the definitions of getbufferproc and releasebufferproc have been moved to pybuffer.h. (So I moved them for all versions here.)

On Python 3.12 the object.h file has new symbols _Py_IMMORTAL_REFCNT and _Py_IsImmortal. The implementation of these differs for 32-bit architectures:

On 32-bit architectures, the lower 30 bits of the 32-bit reference count are set to 1 to denote an immortal object.
On 64-bit architectures, the lower 32 bits are set instead.
I expect this will all change again in future when PEP 703 / nogil comes into the picture with thread-biased reference counting.

I took the argument names out of typedefs for unaryfunc etc, because the Python header doesn't give those arguments names and the argument names were just arg1 arg2 rather than anything meaningful.

I updated the implementations of a few inline macros in object.rs, adding helper definitions to pyport.rs where these were used. Most of these are trivial, except for Py_INCREF and Py_DECREF.

I added some tests to src/ffi/tests.rs to verify the behaviour of these functions. To exercise these with abi3 I had to change that file to exclude individual tests with #[cfg(not(Py_LIMITED_API))] rather than excluding the whole module.

Finally, I updated other refcounting tests to use object() instead of None, as per comment above.

I appreciate this is quite a meaty patch 😢

Pushed a commit with review corrections, I'll squash before merge.
I think there is an open question for PyAny::get_refcnt. I'll open an issue.

🙏 thanks for the thorough reviewing!
Changed to use cfg(target_pointer_width = "64") instead of cfg(not(target_pointer_width = "32")). We won't support 16 or 128-bit systems for now, can cross that bridge then it seems like there's a reason to.


Try out Azure Pipeline

I'm submitting a ...
[/] DevOps

Summary
The ticket aims to experiment Azure Pipeline and compare it with the current CI of choice AppVeyor. After relying on Appveyor as our primary CI provider for a while, we've realised that it's quite slow due to lack of resource it allocates to the open source projects. We've made a decision to try Azure Pipeline, which claims to provide a good amount of free resources for open source projects and provide CI environments in all three major platforms including Windows, Mac and Linux.

The PR for this is open at https://github.com/machinelearnjs/machinelearnjs/pull/232


[Feature Request] Themed / Monochrome App icon support

https://developer.android.com/develop/ui/views/launch/icon_design_adaptive

 Support themed App icon


✨ feat: update Hytteforeningen info

Proposed Changes

Update image and logos in the web app
Remove outdated assets
#962

Types of Changes

[ ] New feature
[ ] Bug fix
[ ] Enhancement/optimization
[ ] Refactor
[ ] Style
[ ] Build/dependencies
[x] Other

Issue(s) fixed or closed by this PR

Resolves #975

Checklist

[ ] I have added tests to cover my changes (for features/bugs)
[ ] I am pleased with the readability of the code (if not, state where you need input)
[ ] I have tested the changes and verified that they work and do not break anything (to the best of my ability)

@einmid could you have a look and see if there's anything else you'd like us to change?
https://indok-web-git-chore-hytteforeningen-rubberdok.vercel.app/cabins

I'm satisfied with this (love the weather on the exterior pics).
Booking responsible:
Thale Simonsen, same email (booking.indokhyttene@gmail.com).


'modal' materializeParams  - ready: func() not working properly

<button class="btn" data-target="modal__new-folder">New Folder</button>

If sey only dismissible: true/false  there is no difference in modal behavior. If use ready: log(), log function is fired on mouse move over document and button.
Am I doing something wrong ?
Using angular-cli: 1.0.0-beta.24 and angular 2.3.1
Thank you!
Edit:  {dismissible: true/false} is working

The following works for me, when changing the value of dismissible. It allows clicking outside the dialog to close it (if set to "true") or not (in "false"):
<button class="btn" data-target="modal__new-folder">New Folder</button>

Modal Header 1

A bunch of text

"log" indeed is weird. I've never used it, but it is called too many times. Need to check...

When  I use it like this [materializeParams]="[{ready: log}]" it fires only once when I open the modal.

That's a very good point. The way you used it before was calling "log" every time it evaluates the param. So, supplying a function is the right way to use it.
I think this issue can be closed now, right?

Ok, is there a way to pass parameters to log() func ?

Just like the example on the MaterializeCSS page:

  log(modal, trigger) { // Callback for Modal open. Modal and trigger parameters available.
    alert("Ready");
    console.log(modal, trigger);
  }

Ок, thank you.


security: fix server cert config

Signed-off-by: xhe<EMAIL_ADDRESS>
What problem does this PR solve?

Issue Number: close #162
Problem Summary: Bug introduced by #146. TLS config for server is wrong if ca is not configured but certs.
What is changed and how it works: Added some unit tests to prevent regression.
Check List
Tests

[x] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Notable changes

[ ] Has configuration change
[ ] Has HTTP API interfaces change (Don't forget to add the declarative for API)
[ ] Has tiproxyctl change
[ ] Other user behavior changes

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.
None

Fix lint


fix: Feat/srs 275a

These changes in the entity are required for a successful data migration

Thanks for the PR!
Deployments, as required, will be available below:

Backend
Frontend

Please create PRs in draft mode.  Mark as ready to enable:

Analysis Workflow

After merge, new images are deployed in:

Merge Workflow

Please do not attempt to merge this yet, even though approved. I will try and deploy db dump to PR environment first as experiment.

converted to draft to make sure it is not merged

closing as its merged as part of PR 159


Installation instructions in README no longer work

Original report by Joseph Fowler (Bitbucket: joe_fowler, ).

My recent experience with installing MASS involves using a virtual environment. That “just works”. But the README instructions do not reflect this approach. And according to the Université de Paris student sitting next to me, they do not work outside of a virtual environment. At least, he is getting permission errors when he tries without a Venv.
See the Dastard Commander instructions for how to set up a super-easy virtual environment.

Original comment by Joseph Fowler (Bitbucket: joe_fowler, ).

Improve installation instructions
Also start v0.8.2. Fixes #261


Import Strategy Request - Update Only?

Basically I have some info thats pulled from an API but the entries themselves were manually created & curated. I want to update some info on the entries and I dont want to create new ones but I do want the ones that are created to accept the new data.
Is that currently possible with FeedMe?

Not currently, but you raise a good point. I'm thinking of re-working the import strategies in v2 to not be mutually exclusive, and more a checkbox. So you'd be able to tick any of:

Add entries that don't already exist in your section
Update entries that already exist in your section
Delete any entry in this section not found in this feed

But I'm happy to make this change straight away, should be in the next release. Thanks!

That would be awesome!

Just added this in 2.0 beta 2.


How do I install this on mac?

The title is self-explanatory. Thanks for any help given!

It really depends (AFAIK) on which MAC you own (what version of MacOS you have installed). Have you read #83?

Also, I found this today, might be a good alternative: webNBT

Also, I found this today, might be a good alternative: webNBT

Thanks for your help, I think I'll just use webNBT, I tried to install it for a while (I'm still on Mojave) but to no avail. Thank you for your help.


Plugins can no longer access output locations on an external drive

Description
After updating to Xcode 15 & Swift 5.9, all plugins that generate code or update source code (SwiftGenPlugin, Swiftlint, ...) can no longer access output locations, if DerivedData is manually set to a custom location in Xcode settings (on an external drive).
If DerivedData is set to a default location, it works correctly.
Expected behavior
Plugins should be able to access output locations even if DerivedData is on an external drive.
Actual behavior
Plugins cannot access the output locations and fail with
Error Domain=NSCocoaErrorDomain Code=513 "You don’t have permission to save the file (...) in the folder (...)." UserInfo={NSURL=file:///Volumes/TSD/develop/Xcode/DerivedData/<app-directory>/SourcePackages/plugins/uitoolkit.output/UIToolkit/SwiftGenPlugin/Localizable.generated.swift, NSUserStringVariant=Folder, NSUnderlyingError=0x600000cb2be0 {Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted"}}

Steps to reproduce

Use a plugin that generates code or updates source files in a project
Set a custom DerivedData location to an external drive (Xcode -> Settings -> Locations)
Try to run the plugin

Swift Package Manager version/commit hash
Swift Package Manager, Swift 5.9
Swift & OS version (output of swift --version ; uname -a)
swift-driver version: 1.87.1 Apple Swift version 5.9 (swiftlang-<IP_ADDRESS>.108 clang-15<IP_ADDRESS>)
Target: arm64-apple-macosx13.0

Darwin Tom---MacBook-Pro.local 22.6.0 Darwin Kernel Version 22.6.0: Wed Jul  5 22:22:52 PDT 2023; root:xnu-8796.141.3~6/RELEASE_ARM64_T8103 arm64

If I understand this issue correctly, you're only seeing this in Xcode? Or also when using the SwiftPM CLI, e.g. with --scratch-path?

Could you provide a minimal Xcode Project / Swift Package to reproduce the issue you report?

@Kyle-Ye Sure, here's the Swift Package: https://github.com/tomas-bat/spm-derived-data-issue

If I understand this issue correctly, you're only seeing this in Xcode? Or also when using the SwiftPM CLI, e.g. with --scratch-path?

@neonichu It also fails when using the SwiftPM CLI:
$ swift build --scratch-path /Volumes/<external-drive>/<some-path>

Executing configuration file <path-to-project>/SwiftPackage/Sources/SwiftPackage/swiftgen.yml
 $ swiftgen xcassets --templatePath swiftgen-xcassets.stencil --param publicAccess --output /Volumes/<external-drive>/<some-path>/plugins/outputs/swiftpackage/SwiftPackage/SwiftGenPlugin/Assets.generated.swift Resources/Assets.xcassets
Error: You don’t have permission to save the file “Assets.generated.swift” in the folder “SwiftGenPlugin”.

This error does not appear when the scratch path is set to a location on the main drive, e.g. ~/Desktop/build

I was wondering whether #6910 would be the culprit here, but it is actually not part of 5.9 yet, it has been merged to the branch to end up in the next 5.9 update. So now I am wondering instead whether that is a fix, I'll try to validate that soon.

I have successfully reproduced the issue locally.
The sandbox profile seems fine. And I tried it with my demo CLI app.
So I suspect there was a bug in "SwiftGen" binary.
/usr/bin/sandbox-exec -p "(version 1)
(deny default)
(import \"system.sb\")
(allow file-read*)
(allow process*)
(allow file-write*
    (subpath \"/private/tmp\")
    (subpath \"/private/var/folders/hs/g5q9gn6d5tx6_3bxmq1pj0rw0000gp/T\")
)
(deny file-write*
    (subpath \"/Users/kyle/tmp/spm-derived-data-issue/SwiftPackage\")
)
(allow file-write*
    (subpath \"/Volumes/Resource/Tmp/SwiftPackage-avihhefbofskanfegeumqytjvufm/SourcePackages/plugins/swiftpackage.output/SwiftPackage/SwiftGenPlugin\")
)
" /Volumes/Resource/Tmp/SwiftPackage-avihhefbofskanfegeumqytjvufm/SourcePackages/artifacts/swiftgenplugin/swiftgen/swiftgen.artifactbundle/swiftgen/bin/swiftgen config run --verbose --config /Users/kyle/tmp/spm-derived-data-issue/SwiftPackage/Sources/SwiftPackage/swiftgen.yml

I made a clone locally and replaced the swiftgen path in the command to try to debug it.

Also remember to replace ${DERIVED_SOURCES_DIR} to the actual dir path.

After some digging, I found the problem is a implementation detail of the write method.
SwiftGen currently use String.write(toFile:atomically:encoding) API which in this case will fail. Using Data.write(to:) is fine in such case.
try path.write(content)

extension Path {
  public func write(_ string: String, encoding: String.Encoding = String.Encoding.utf8) throws {
    try string.write(toFile: normalize().path, atomically: true, encoding: encoding)
  }
}

Following the existing API, we might make such change to SwiftGen. However this will also fail due to the .atomic option.
try path.write(content.data(using: .utf8)!)

extension Path {
  public func write(_ data: Data) throws {
    try data.write(to: normalize().url, options: .atomic)
  }
}

In conclusion, for external Volume sandbox file writing:

✅ data.write(to: url)
❌ data.write(to: url, options: .atomic)
❌ string.write(toFile: path, atomically: true/false, encoding: .utf8)

A short fix for this issue is a PR for SwiftGen.
A long fix is digging why such API is not working on such case. But Sandbox implementation on macOS and Foundation on Darwin Platform is not open sourced. Maybe file a Feedback issue to Apple to the only thing we can do.

Thanks for the investigation, sounds like the problem should indeed be fixed by https://github.com/apple/swift-package-manager/pull/6910 then.
The issue is that the atomic versions of these APIs write to a temporary side location on the external volume that isn't part of the sandbox profile in 5.9, so it gets denied.

Since this is already fixed by the upstream. I think I do not need to create a PR to do the temporary fix. (A PR for SwiftGen -> merged -> Release a new SwiftGen version -> A update version PR for SwiftGenPlugin -> merged -> You issue is fixed)
Rather let's wait for the next Xcode version which will bring the fix in Swift 5.9.1 cc @tomas-bat

Thanks for the investigation, sounds like the problem should indeed be fixed by #6910 then.
The issue is that the atomic versions of these APIs write to a temporary side location on the external volume that isn't part of the sandbox profile in 5.9, so it gets denied.

Tested it with Xcode 15.1 Beta - Swift 5.9 (<IP_ADDRESS>.6) and still fails. Looks like the fix commit is not included yet. Hope to see it land on the release of Xcode 15.1.

tested on Xcode 15.1 beta 3 and still fails

Xcode 15.1 RC use the same Swift version as Xcode 15.1 Beta 3 - Swift 5.9.2 (<IP_ADDRESS>.56)
Looks like we'll have to wait for the next Xcode releasing 😂

Is the fix still not released? I hit the same issue with latest Xcode 15.2.0 (swift 5.9.2).
Xcode Cloud seems to use DerivedData folder on an external drive, so this issue here makes it impossible to use e.g. SwiftGenPlugin in projects build on Xcode Cloud

Is the fix still not released? I hit the same issue with latest Xcode 15.2.0 (swift 5.9.2).
Xcode Cloud seems to use DerivedData folder on an external drive, so this issue here makes it impossible to use e.g. SwiftGenPlugin in projects build on Xcode Cloud

Expected. Xcode 15.2 use the same version of Swift as Xcode 15.1 - Swift 5.9.2 (<IP_ADDRESS>.56).

Is the fix still not released? I hit the same issue with latest Xcode 15.2.0 (swift 5.9.2).
Xcode Cloud seems to use DerivedData folder on an external drive, so this issue here makes it impossible to use e.g. SwiftGenPlugin in projects build on Xcode Cloud

If anyone is eager is for a fix. You can try fork SwiftGenPlugin and apply the patch I mentation in https://github.com/apple/swift-package-manager/issues/6948#issuecomment-1747196926

Thanks, I tried fixing it like you said - instead of using String.write(toFile: file, atomically: true, encoding: encoding) I use atomically: false
That seems to have fixed my problems - now I can use SwiftGenPlugin (SPM Plugin for SwiftGen) in Xcode Cloud
https://github.com/SwiftGen/SwiftGenPlugin/issues/18#issuecomment-1894018747


set dvm on startup

@gileshinchcliff squashing commits would help I guess :-)

next time, @vaijab

LGTM


More metdata controlled output formatting

Building on: https://myst-nb.readthedocs.io/en/latest/use/formatting_outputs.html#images
Basically, port my implementations in: https://ipypublish.readthedocs.io/en/latest/metadata_tags.html#cell-output-level
Also, make the top-level key configurable (in conf.py) and change the default from myst to render
cc @akhmerov

As per ipypublish, we should we also support output level metadata overrides, and possibly even project/notebook level metadata, i.e. when choosing what metadata to use precedence would be:
output level > cell level > notebook level > project level

All good things. render seems to be a good default, inheritance likewise. I only had a brief look at the ipypublish metadata; some of it might benefit from reorganization. e.g. slideonly: true could become slides: ignore: true to correspond to the jupyter's output bundle and sphinx builders better.

Oh absolutely, we don't to take it verbatim,  but its useful as a guide for what I've found useful before


[feature request]click sidebar menu add collapse and expand

like toggle, if  collapse, click expand, is  expand, click collapse.

Duplicate of #294


Feature request: Collapse functions/blocks

Hi,
I extensively use the collapse function of the editor. When opening a source file, however, the editor expands all collapsed functions/blocks. Is there a way for the editor to remember what was collapsed the last time? Or failing that, could it open any file with all functions collapsed? Or provide a shortcut/button to do the same?
Every time I open a file I spend about a minute collapsing all functions that are of no interest to me at the time...
Thanks
viktak

This functionality has already been added by the 'remember-folds' package.
Installation
apm i remember-folds
https://atom.io/packages/remember-folds

Sorry, I missed that. Closing this issue.


Absolute imports over relative imports

Trying to test __main__ code per this comment, it seems the best way is to use importlib as instructed here.
However, importlib.machinery doesn't play nice with relative imports.  So this PR moves the internals to use absolute imports.
Contributor checklist

[x] Included tests for the changes.
[x] PR title is short, clear, and ready to be included in the user-facing changelog.

Maintainer checklist

[ ] Verified one of these labels is present: backwards incompatible, feature, enhancement, deprecation, bug, dependency, docs or skip-changelog as they determine changelog listing.
[ ] Assign the PR to an existing or new milestone for the target version (following Semantic Versioning).

Out of curiosity, why do you say absolute imports are an inconvenient hack?
In my own style, I find absolute imports easier to follow, and PEP 8 is a proponent of absolute imports too:

Absolute imports are recommended, as they are usually more readable and tend to be better behaved

PEP 8 used to discourage relative imports more aggressively (source) too:

Relative imports for intra-package imports are highly discouraged. Always use the absolute package path for all imports.

I've also hit situations where relative imports can cause problems, depending on how one invokes python and configures PYTHONPATH. From my local testing tonight, absolute imports work with importlib.machinery, whereas relative imports don't.

Anyways, feel free to close this out if pip-tools's style prefers relative imports, my need for this PR is no more because an alternate approach was pointed out in the source PR

It's not currently enforced, so is probably up to each person.
https://mail.python.org/pipermail/python-dev/2010-October/104476.html suggests that in the times of Python 2.5, things were less stable/obvious maybe, more complicated. So I'm not surprised that people realized that it wasn't relevant anymore.
Plus, Python 3 changed a lot of stuff for the better.

I've also hit situations where relative imports can cause problems, depending on how one invokes python and configures PYTHONPATH. From my local testing tonight, absolute imports work with importlib.machinery, whereas relative imports don't.

That's exactly why I don't want absolute imports: it encourages people to keep misconfiguring their environments, unfortunately. I don't think that it's a tolerable side effect.
We actually have an intentional relative import in ansible-core that is also a sanity check that we haven't broken our import machinery level hooks. A few months ago, colleagues from another team tripped over that and also proposed a hack that was removing that relative import, which of course was rejected.
I helped them realize that they were calling the machinery incorrectly, and that caused an actual fix to be found. Apparently, some people miss/forget that there's a package argument in the APIs of importlib, and it's meant to be used.
I have a hunch that if you pass what the package is to that API, then it'll magically work for you.

@jamesbraza FWIW, I looked into that other PR and realized that what you suggest would probably mess with the import machinery. So I would still use subprocesses to test it.


[Feature] support alter partition prop storage_cooldown_ttl

Fixes #issue
What type of PR is this:

[ ] BugFix
[x] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[x] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.1
[x] 3.0
[ ] 2.5
[ ] 2.4

[FE PR Coverage Check]
:heart_eyes: pass : 19 / 20 (95.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/alter/AlterJobMgr.java
19
20
95.00%
[1148]

https://github.com/Mergifyio backport branch-3.0


Add support for metrics in the opentelemtry coralogix agent

Updated environment variables to support the metrics endpoints
Updated readme - how to disable metrics
Updated the readme section on the podmonitor
Removed the receivers section since its configuring the prometheus receiver by default
Updated serviceMonitor to podMonitor since serviceMonitor is not supported in agent mode

@avivgold098 the prometheus receiver config is by default yes , coming from the upstream chart

@avivgold098 the prometheus receiver config is by default yes , coming from the upstream chart

@amit-mazor So let's have a comment on it


Potential Bug with Consumers Reference Counting

https://github.com/paritytech/subport/issues/142#issuecomment-813783707
My investigation of this account implies to me that there should be no consumer reference counters on this account, but there seems to be and it is blocking account deletion.
Needs a deeper investigation as to how this state may have been reached and where there may be some issue with the management of reference counters.

Also might be related:

@kianenigma this is strange because in this case, the consumer is being left over, and your error implies it is being removed beyond zero.
It is like an error in both directions....


Add functionality to set playlist item by ID

For cross-process use cases I am missing a way to seek to a playlist item by ID from the client.
Framework media has TransportControls.skipToQueueItem(long), where the parameter is a long ID. Media3 seems to have nothing that works across process boundaries.
There is Timeline.getIndexOfPeriod(Object), but it does not and cannot work across process boundaries because of the oddly unconstrained Object parameter type.
The only way I see to obtain functionality on par with framework media is implementing a custom SessionCommand myself. (I've simply made it constrain the Object parameter type to something usable and return the result of getIndexOfPeriod() to the client.)

Thanks for your request. That's a valid ask. Using an ID to identify windows would be a proper solution as you explain above.  Keeping this issue as an enhancement. That's not something we are having on the roadmap to work on currently afaik.

My playlist can be humongous and it makes no sense to mirror it on the client just for the purpose of seeking.

From the above, I understand that you do not map the whole playlist to the queue in the legacy API.
In your approach that you implemented on top of the legacy API, how does a client know the ID that is passed to skipToQueueItem(long)?  This is more about understanding the use case than the technical implementation.

Thanks for considering it. The playlist data comes from a local data source that both the media session and the (default Android app) client have access to. The client does not really care what playlist the media session has, it just tells the session which item to play, based on ID. Playlist indices are not so meaningful in this scenario, it's all about the (media/data) IDs.
A different client (headphones, Android Auto, etc.) would care about the media session playlist, and would just use indices instead of IDs.
I don't think this one matters, but just FYI, this app plays realtime synthesized audio via framework AudioTrack API. The IDs just guide the media session to the right source data.


next: Collected changes for the v2015.10 release

This PR contains the changes that are being tested for inclusion in the v2015.10 release.
Note: the diff is very large due to converting external submodules (luajit, pflua, ljsyscall) into included subtrees (#617).

@lukego Let me know when this is ready for release! :)

Good to go I reckon :)

See https://github.com/SnabbCo/snabbswitch/releases/tag/v2015.10


Edit avatar screen doesn’t open up a a rightDocked modal

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Navigate to app and login
Open Settings > Profile
Click on Photo > Upload Photo

Expected Result:
Edit avatar screen should open up a a rightDocked modal
Actual Result:
Edit avatar screen doesn’t open up a a rightDocked modal
Workaround:
unknown
Platform:

Where is this issue occurring?

Web
Desktop App

Version Number: 1.1.91-0
Reproducible in staging?: Y
Reproducible in production?: Y
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation

Expensify/Expensify Issue URL:
Issue reported by: @shawnborton
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1660684286312709
View all open jobs on GitHub

Proposal
We have to replace this with CONST.MODAL.MODAL_TYPE.RIGHT_DOCKED
https://github.com/Expensify/App/blob/89e7e7db469d2f222ebceb7aefa72cb4add0de78/src/components/AvatarCropModal/AvatarCropModal.js#L269

External upwork post: https://www.upwork.com/jobs/~01b2ee159ae607c80e
Internal upwork job: https://www.upwork.com/ab/applicants/1564883307443179520/job-details

@srikarparsi is going to take CME on this one.

Proposal
To make this a right docked modal, we will replace this
https://github.com/Expensify/App/blob/ffa839ee30b7f7c32ed203195535818c12f4f938/src/components/AvatarCropModal/AvatarCropModal.js#L266-L273
with
       <Modal
            onClose={props.onClose}
            isVisible={props.isVisible}
            type={CONST.MODAL.MODAL_TYPE.RIGHT_DOCKED}
            containerStyle={!props.isSmallScreenWidth ? styles.avatarCropModalContainer : null}
            onModalHide={resetState}
            statusBarTranslucent={false}
        >

and since there is a back button on all rightDocked modal, we will also replace this
https://github.com/Expensify/App/blob/ffa839ee30b7f7c32ed203195535818c12f4f938/src/components/AvatarCropModal/AvatarCropModal.js#L275-L278
with
            <HeaderWithCloseButton
                title={props.translate('avatarCropModal.title')}
                shouldShowBackButton
                onBackButtonPress={props.onClose}
                onCloseButtonPress={props.onClose}
            />

Screencast from 01-09-22 08:51:40 PM IST.webm

@shawnborton / @Expensify/design
Need confirmation do we need a back button here?

I would think so, yes.

I don't think we need a back button here because it's just an edit modal but If we want then I can update my proposal, We have to change the code like below -
https://github.com/Expensify/App/blob/11761bea9de7604febd17da05797c62caf2a2f6b/src/components/AvatarCropModal/AvatarCropModal.js#L275-L278
            <HeaderWithCloseButton
                title={props.translate('avatarCropModal.title')}
                shouldShowBackButton
                onBackButtonPress={props.onClose}
                onCloseButtonPress={Navigation.dismissModal}
            />

Let's show it based on the discussion here.

@srikarparsi
@Puneet-here proposal looks good and meets our expected OP as discussed here.
So let's hire him for this one!
🎀 👀 🎀
C+ Reviewed
Thanks!
cc: @puneetlath

Review in progress

@Santhosh-Sellavel @Puneet-here sent you both hiring offers in Upwork. Please accept when you have a chance.

Done thanks!

All paid. Thanks everyone!


Support for PIPE operator for apache-age-python client

Currently we are running queries that require several Relationship (age.models.Edge) types to be filtered out.
We tried to approach it with OPTIONAL MATCH but it didn't suite as too well, since it requires first statement to have matches to process with the other.
Ended up with something like "MATCH ()-[r]-() WHERE r.type in ["type1", "type2"] RETURN r".
In OpenCypher specs there is a mention about PIPE operator that facilitates such OR statements for relationship types and it goes like: "MATCH ()-[r:type1|type2]-() RETURN r.
It feels a lot more natural to use. This one gives us "syntax error near |'.
Are there any plans to implement such operator or is it somehow limited?

Yes PIPE is cutoff. It is no more supported for specifying relationship types in single pattern.
But after checking some doc have you tried using WHERE clause with IN
I think this might WORK
like
WHERE r.type IN ['type1', 'type2']

@farakh-shahid That is exactly what @czesiu89 is saying he's using as workaround, indeed.
Is there any reason why PIPE is "no more supported"? Does it imply that Age is not implementing 100% OpenCypher? As I believe it's part of its grammar?
Thanks a lot!

Hi @czesiu89 Any new updates on this? Can you share a bit more about your use-case? It'll help us prioritize.

The PIPE operator is a feature of the Nebula Graph Query Language (nGQL) and is not part of OpenCypher. It allows multiple queries to be combined using pipe operators in nGQL. The PIPE operator applies to native nGQL only and is not compatible with OpenCypher

@cvanlabe -

@farakh-shahid That is exactly what @czesiu89 is saying he's using as workaround, indeed.
Is there any reason why PIPE is "no more supported"? Does it imply that Age is not implementing 100% OpenCypher? As I believe it's part of its grammar?
Thanks a lot!

Can you please show me where in the openCypher documentation it states the pipe operator was/is supported?

@jrgemignani thanks for your response. As I mentioned, it’s visible in the grammar I linked to.
In the documentation, it’s described as early as page 10 in the opencypher reference:
” if we’d like to describe some data such that the relationship could have any one of a set of types, then they can all be listed in the pattern, separating them with the pipe symbol | like this:”

(a)-[r:TYPE1|TYPE2]->(b)

I will bring this "oversight" up with the team and see if we can get it added. @rafsun42 @dehowef @muhammadshoaib

Btw, the title for this issue is a bit misleading. This is for adding the OR operator | to the language.

@czesiu89 @cvanlabe The work on the this operator is currently in progress. It would be useful if you let us know your data model and queries.

Thanks so much everyone! We can't immediately share our data model we use today. Assume it's a typical graph, which has several nodes connected to other nodes where each connection is a different relation type.
Using the OR operator, we can decide which nodes we want to visualize given the used relationships.
I hope this helps.

hi, i face a situation where the pipe-OR operator would be usefull, so as my situation is pretty simple i describe here.
this is the query i tried, in which i want to match synonyms or hyperonyms of a word, and synonym/hyperonyms of synonym/hyperonyms, and synonym/hyperonyms of synonym of synonym of this word (including synonym of hyperonym of synonym, and so on). so i need variable-length edges and the OR operator.
select * from cypher('graph_dict', $$
    match (s:word {graphic_form: 'know'})-[r:has_synonym|has_hyperonym|has_holonym *1..3]->(t:word)
    return s, t
$$) as (source agtype, target agtype);

with the solution proposed in the beginning of this discussion, it produces an error. this is what i've tried:
select * from cypher('graph_dict', $$
    match (s:word {graphic_form: 'know'})-[r]->(m:word)-[s *0..2]->(t:word)
    where label(r) in ['has_synonym', 'has_hyperonym', 'has_holonym']
    and label(s) in ['has_synonym', 'has_hyperonym', 'has_holonym']
    return l.id, t.graphie
$$) as (source agtype, target agtype);

the error is the following, and it seems that when the second edge is length 0, label() cannot be used (obviously).
ERROR: label() argument must resolve to a vertex or an edge.

@thjbdvlt PR #1452 implements multiple label support. It has not been approved yet, but you can try it out.

@thjbdvlt The PR 1452 is actually based on PG15. Do you get a compilation error?

@rafsun42 unfortunately: yes! but as i am really not a programmer, i have no doubts: it must be because of me not understing something. anyway, i post a comment directly on the PR 1452 page with logs and description of what i have done, just in case it may help!


SP4 Population: add option to define box transparency

Purpose:

Resolve Issue 2967 - Add option to set custom alpha value for scatter markers and boxes in population plots
Add xml docs for new public fields MarkerAlpha and BoxAlphaOverride to explain behavior
Add tests for these two fields

@swharden Thank you for cleaning up the XML docs and making the legend respect the box alpha - I completely missed that when I was looking at test plots.


Added pre-commit to the github workflow

title

Python 3.7 crashes because black==24.2.0 is not available. @cyrraz Do you remember why you chose this version of black? Should we downgrade black or remove the Python3.7 test?

Python 3.7 crashes because black==24.2.0 is not available. @cyrraz Do you remember why you chose this version of black? Should we downgrade black or remove the Python3.7 test?

I think we should still support Python 3.7, version 24.2.0 of black was chosen because it was the latest black version at the time we merged this code. There is an automatic command in precommit to update the repositories to their latest version.
Could we remove only the precommit test for Python 3.7?


ci: Intermittent test failures

I've been seeing the occasional test failure here in CI, like this one, where I see the following output:
signal: illegal instruction (core dumped)

It's unclear whether this is a problem in our code, or in a linked library.
I have not yet managed to reproduce this locally though. When testing locally with the Docker image, it always passes for me.

Not seeing this anymore.


Typo in onboarding screen

"No account creation is needed. Run your own node. Connect via Tor. Manage UTXOs and whirlpool sats."

Completed


perf(worker-rust): Add dev env for faster local build times

What this PR solves / how to test:
Add a dev-environment to wrangler.toml which builds with worker-build --dev instead of worker-build --release.
This makes build times for local development much faster.
Add opt-level = "s" to Cargo.toml so release builds are optimized for size.
Remove the deprecated --local parameter from the wrangler invocation.
Author has addressed the following:
Not sure which of these I should do (and how).

Tests

[ ] Included
[ ] Not necessary because:

Changeset (Changeset guidelines)

[ ] Included
[ ] Not necessary because:

Associated docs

[ ] Issue(s)/PR(s):
[ ] Not necessary because:

Thanks for the review! One thing I'm not sure about: Removing the --local flag. This might fail with older wrangler-versions now, I think? Should I remove it again from this PR?
But then again, this template will probably be used with more recent versions of wrangler (since a template is usually used for new projects), so it might just be fine in this case.

Wrangler 3, when the change to default to local mode occurred, has been out for ~9 months, so personally I wouldn't be too concerned about the change

Awesome, thanks! :)

One other point I realized: Is opt-level = "s" for release-builds desired by default? Since it won't be running in the frontend/not downloaded by browsers, maybe this doesn't actually make that much sense?
I added it originally because it's a very common optimization for wasm use-cases, but maybe that doesn't really count for workers.

I'm no Rust specialist so I would bow to your (or anyone else's views) but I would note that Workers still have a size limit on what can be deployed. So it might be worth keeping a size optimisation turned on?

I'm no Rust specialist so I would bow to your (or anyone else's views) but I would note that Workers still have a size limit on what can be deployed. So it might be worth keeping a size optimisation turned on?

That's a good point. I think optimizing for size by default should be sensible for wasm-builds (like in this case), and users can still change/adapt this later on anyways.
So if it's up to me I would keep the opt-level = "s", but feel free to let me know if I should change it :)

That seems reasonable to keep IMO


Allow Access List to be assigned for individual Custom Locations

Is your feature request related to a problem? Please describe.
It seems only possible to assign Access Lists for the main domain, not for the custom locations.
So, I'm not able to restrict a specific subpath, while leaving others publicly available.
Describe the solution you'd like
It would be great to have the possibility of adding an access list per individual custom location.
Maybe include a dropdown like this:

Describe alternatives you've considered
I'm manually copying/pasting a snippet on each custom domain, and if something changes, I have to change everything manually once more.

Yes. This is needed feature.

I still think it is relevant.


Text color in folds is too dark

Not sure if it's just me, but having the text darker than the fold color makes it really hard to read

I think a lighter color would make it much more legible.

I agree. I'll take care of this. Thanks for the feedback.

@alexlafroscia I pushed a fix for this:

I updated both folds and fold columns (if enabled) to be normal.cyan (the Nova color which represents user state) which in term makes them much more readable; this is how it should have been built originally but I made a mistake and don't use folds so I missed this. Thank you for letting me know!

Awesome, thanks @trevordmiller!


Floating window of list of keymaps and :OutlineStatus

See simrat39/symbols-outline.nvim#211

Resolved in commit e56145f :tada:


Wordpress 5.8

Hi! I am not able to get menu in WP 5.8. Does that work for you?
I see that there were done some changes in new version of wordpress.

It works fine for me. Try with this theme: https://github.com/AlexWebLab/barely-minimum-bootstrap-5-wordpress-starter-theme and check the code internally to see how to add a menu.

I made it working! Thank you for help!


[Bug Report] el-select in remote mode displays the wrong item

Element UI version
2.4.5
OS/Browsers version
Chrome
Vue version
2.5.14
Reproduction Link
https://jsfiddle.net/sylvainc/eywraw8t/211856/
Steps to reproduce
This select input shows countries. By typing at least 3 letters, you see the matching countries.
So start entering FRA, you should get France and French Polynesia displayed.
Choose The first item  (France), the selected item is effectivelly France as shown on the side of the select input but the information displayed in the select is the last item of the option list (french Polynesia).
You can also try with ESP which return a long list of countries.
If you choose the first one of the list (Azerbaijan), the last one of the option list will be displayed in the select input (Uzbekistan)
What is Expected?
I would expect the information displayed in the select input to be the information of the option I have chosen
What is actually happening?
The information displayed in the select is the information of the last option in the list.

https://jsfiddle.net/49jbdm27/
You must specify value-key to distinguish options from one and another, if its bounded value is object.


chore: test 5

Current dependencies on/for this PR:

master

PR #5

PR #6

PR #7   👈

This comment was auto-generated by Graphite.


Disabled Item Error in ComboBox

Describe the bug
An error occurs if the IsEnabled property of any item in the ComboBox component is set to false.
To Reproduce
`ComboBox Test = new()
Test.Items.Add(new ComboBoxItem()
{
IsEnabled = true,
Content = "True"
});
Test.Items.Add(new ComboBoxItem()
{
IsEnabled = false,
Content = "False"
});`
Expected behavior
No error occurs.
Screenshots
3.0.0-preview.7

3.0.0-preview.8

OS version
Windows 11 22621.2428
.NET version
.NET 8
WPF-UI NuGet version
3.0.0-preview.8
Additional context
No response

aff99851
https://github.com/lepoco/wpfui/blob/64a4c83dcf6576bbc2bad1285cfb705bde7ec81c/src/Wpf.Ui/Controls/ComboBox/ComboBox.xaml#L143

Solved in 3.0.0-preview.10

CC @niels9001

PR to fix this issue: https://github.com/lepoco/wpfui/pull/839


[mle] delay to send announce for FTD

This commit delays sending Announce for FTD after it has become Router and decided to stay in REED on the safe side:
OT device would try to attach on the announced channel only once, and if it fails, the device would switch back to old channel. However the FTD may get a different router id, or it will take longer for REED to become router especially in linear topology, causing the attaching device fail to attach and may no chance to attach again on the announced channel.

Is there a case where we need to send MLE Announce messages on the previous channel after becoming a Leader?

I could not think of such scenarios. For my understanding, the device switches to the new channel to attach when hearing MLE announce on its original channel, that is, there have already been one partition on the new channel. Additionally, if the device fails to attach on the new channel,  it won't try to become leader, but switch back to its original channel.
Thoughts?


Add MobileNetV3 architecture with Classification & Detection models

Fixes #1676
This PR adds MobileNetV3 in TorchVision:

[x] Implementations of the MobileNetV3 Large and MobileNetV3 Small architectures for classification (#3182)
[x] Implementation of the RetinaNet + MobileNetV3 Large FPN architecture for object detection (#3223)
[x] Pretrained weights and documentation (#3242)

See linked sub-PRs for details.

Closing in favour of splitting the PR into two parts: Classification (#3252) and Detection (baking).

Closing in favour of splitting the PR into two parts: Classification (#3252) and Detection (baking).


Update reactNativeSDK.mdx

🚀 Deployed on https://63220e31ffc1c22eaf1e3181--cozy-fox-0defec.netlify.app


[Bug]: server crash when importing files lots of times, to build vector index. Invalid MergeFlag from 1 to 3@src/storage/wal/catalog_delta_entry.cpp:182

Is there an existing issue for the same bug?

[X] I have checked the existing issues.

Branch name
main
Commit ID
8702dae
Other environment information
No response
Actual behavior
terminate called after throwing an instance of 'infinity::UnrecoverableException@infinity_exception'
what():  Invalid MergeFlag from 1 to 3@src/storage/wal/catalog_delta_entry.cpp:182
Expected behavior
No response
Steps to reproduce
run: pytest -k test_vector_index_single_thread python/test (add -s to print)

Additional information
No response

duplicate with #991


Verbose mode , or other "I've renewed" output

If would be great if this tool could easily tell( or report to) the shell if a cert is renewed or not so that my bash scripts could decide whether or not to reload/restart the web server.

Closing:

Either grepping the INFO log is enough
Or cf #35 for a callback mechanism


[UBS-User.Edit Profile] 'User data', In the address the radio button icon is corrupted.

Environment: MacOS Monterey 12.6.7,  Safari 16.5.1
Reproducible: always
Build found: 24/07/2023
Preconditions

The registered user is logged in https://www.greencity.social/#/ubs
User data tab is opened

Steps to reproduce

Click on “Edit data” button.
Scroll down to 'Address' section
Check radio button

Actual result
Right side of radio button icon is cut.

Expected result
The radio button icon should be fully displayed.
User story and test case links
E.g.: "User story #3811
Labels to be added
"Bug", Priority ("Low"), Severity ("Minor"), Type ("UI")

Bug is fixed


cassandra_2_2: 2.2.14 -> 2.2.19

Motivation for this change
Issue: #99743
Reason: Fixes CVE-2020-13946 Apache Cassandra RMI Rebind Vulnerability
Description:
It is possible for a local attacker without access to the Apache Cassandra
process or configuration files to manipulate the RMI registry to perform a
man-in-the-middle attack and capture user names and passwords used to access
the JMX interface. The attacker can then use these credentials to access
the JMX interface and perform unauthorised operations.
Users should also be aware of CVE-2019-2684, a JRE vulnerability that enables
this issue to be exploited remotely.
2.2.x users should upgrade to 2.2.18

Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[X] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 104840 1

1 package built:

cassandra_2_2


panic: interface conversion when doing helm upgrade --install via concourse

On GKE installing via concourse the install process bombs out. This was working previously until I made some changes to my cluster. I switched my nodes from cos to ubuntu and upgraded to the latest Kubernetes version on GKE.
Kubectl version:
Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.7", GitCommit:"dd5e1a2978fd0b97d9b78e1564398aeea7e7fe92", GitTreeState:"clean", BuildDate:"2018-04-19T00:05:56Z", GoVersion:"go1.9.3", Compiler:"gc", Platfo
rm:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"10+", GitVersion:"v1.10.6-gke.2", GitCommit:"384b4eaa132ca9a295fcb3e5dfc74062b257e7df", GitTreeState:"clean", BuildDate:"2018-08-15T00:10:14Z", GoVersion:"go1.9.3b4", Compiler:"
gc", Platform:"linux/amd64"}

Helm version:
Client: &version.Version{SemVer:"v2.10.0", GitCommit:"9ad53aac42165a5fadc6c87be0dea6b115f93090", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.10.0", GitCommit:"9ad53aac42165a5fadc6c87be0dea6b115f93090", GitTreeState:"clean"}

Stack trace:
Running command helm upgrade taskhero-staging /tmp/build/put/helm-repo/taskhero-0.1.0.tgz --tiller-namespace=kube-system -f /tmp/build/put/chart-source/staging.yaml --set image.repository=gcr.io/taskhero-197200/taskhero-staging --set image.digest=sha256:2c27459820b97667af265c84d9fcf04afe89089cc28bee15b85af347ea69acf6 --set env.APP_VERSION=latest --install --namespace staging | tee /tmp/log
Release "taskhero-staging" does not exist. Installing it now.

panic: interface conversion: interface {} is []interface {}, not map[string]interface {}

goroutine 1 [running]:
k8s.io/helm/pkg/strvals.(*parser).key(0xc42066ef60, 0xc4204d68d0, 0x1214aad, 0x14d70c0)
	/go/src/k8s.io/helm/pkg/strvals/parser.go:211 +0xebc
k8s.io/helm/pkg/strvals.(*parser).parse(0xc42066ef60, 0xc4204d68d0, 0x0)
	/go/src/k8s.io/helm/pkg/strvals/parser.go:133 +0x38
k8s.io/helm/pkg/strvals.ParseInto(0x7ffed89d9ea4, 0x16, 0xc4204d68d0, 0x0, 0x0)
	/go/src/k8s.io/helm/pkg/strvals/parser.go:85 +0xbf
main.vals(0xc42052cfe0, 0x1, 0x1, 0xc42007f6c0, 0x3, 0x4, 0x20d7238, 0x0, 0x0, 0x20d7238, ...)
	/go/src/k8s.io/helm/cmd/helm/install.go:382 +0x45a
main.(*installCmd).run(0xc420b7db68, 0xc42000c018, 0x163e75e)
	/go/src/k8s.io/helm/cmd/helm/install.go:232 +0x1e4
main.(*upgradeCmd).run(0xc420001980, 0x0, 0x1778080)
	/go/src/k8s.io/helm/cmd/helm/upgrade.go:202 +0xe3f
main.newUpgradeCmd.func2(0xc420769d40, 0xc4206b41c0, 0x2, 0xe, 0x0, 0x0)
	/go/src/k8s.io/helm/cmd/helm/upgrade.go:117 +0x141
k8s.io/helm/vendor/github.com/spf13/cobra.(*Command).execute(0xc420769d40, 0xc4206b40e0, 0xe, 0xe, 0xc420769d40, 0xc4206b40e0)
	/go/src/k8s.io/helm/vendor/github.com/spf13/cobra/command.go:599 +0x3db
k8s.io/helm/vendor/github.com/spf13/cobra.(*Command).ExecuteC(0xc4207d4000, 0xc4207426c0, 0xc420742fc0, 0xc420743680)
	/go/src/k8s.io/helm/vendor/github.com/spf13/cobra/command.go:689 +0x2d4
k8s.io/helm/vendor/github.com/spf13/cobra.(*Command).Execute(0xc4207d4000, 0xf, 0xf)
	/go/src/k8s.io/helm/vendor/github.com/spf13/cobra/command.go:648 +0x2b
main.main()
	/go/src/k8s.io/helm/cmd/helm/helm.go:161 +0x79

OK I figured out what was wrong. The error message is totally unhelpful. I had an invalid --set where I was setting an array instead of a position in that array. Perhaps helm should catch this and spit out an error instead of bombing?

@AndrewMorsillo thank you so much, we were tracking down a similar issue and your follow up comment helped us get around it & resolve it. agreed, this error message is really really misleading and led us down a totally wrong path.


Where are the labels? Is this a supervised learning?

Whether it’s a cat or a dog is the label,  and the specific code is here:
https://github.com/espectre/Kaggle-Dogs_vs_Cats_PyTorch/blob/master/dataset/DogCat.py#L37

oooohh. Thanks!


get current value for inputs in html page

If page has input filed, the default value of this filed that will generated in word file until if you change this value. these lines will solve this issue

I have tested these changes with a text input, and it did not work. Is this change only for file inputs? What issue you are trying to solve?


Looking emoji in https://unicode.org/ files

Hi Sasha,
I found some set of emojis in https://unicode.org/Public/emoji/15.0/ files.
Maybe it is a good idea to use this files.
What do you think ?

Hey! Yeah, thanks for sharing : )
I'm using GitHub's supported emojies here with their github's short codes 🙌

May worth seeing:

https://github.com/KOLANICH-tools/emojiSlugMappingGen.py - the tool
emoji.po - the pregenerated database


[Reader] Error parsting property reference

Microsoft.OpenApi.Readers version: 1.6.1
OpenApi spec:
openapi: "3.0.0"
info:
  version: 1.0.0
  title: Swagger Petstore
  license:
    name: MIT
servers:
  - url: http://petstore.swagger.io/v1
paths:
  /pets/{petId}:
    parameters:
      - name: petId
        in: path
        required: true
        description: The id of the pet to retrieve
        schema:
          $ref: "#/components/schemas/Pet/properties/id"
    put:
      summary: Info for a specific pet
      operationId: showPetById
      tags:
        - pets
      responses:
        '200':
          description: Expected response to a valid request
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/Pet"
components:
  schemas:
    Pet:
      type: object
      required:
        - id
        - name
      properties:
        id:
          type: integer
          format: int64
        name:
          type: string
        tag:
          type: string

parsing it with
OpenApiReaderSettings settings = new()
{
     ReferenceResolution = ReferenceResolutionSetting.ResolveAllReferences,
};
using FileStream stream = File.OpenRead(path);
OpenApiDocument? document = new OpenApiStreamReader().Read(stream, out OpenApiDiagnostic? diagnostic);

gives error: The reference string '/components/schemas/Pet/properties/id' has invalid format.
Expected behavior: Specification should be parsed successfully.

The ResolveAllReferences ReferenceResolution setting is used to resolve external references. Try using ResolveLocalReferences

The ResolveAllReferences reader setting is for resolving external references but your document only has local references. ResolveLocalReferences would be more suitable.
In addition to that, Properties is not a referenceable component/element. During parsing, we only resolve references for components that are referenceable e.g. schemas, responses, parameters, headers etc.

-> Properties is not a referenceable element/type
It is. There is an issue about that: https://github.com/OAI/OpenAPI-Specification/issues/2824
https://editor.swagger.io/ can read such reference.

Thanks for the correction. Unfortunately our lib doesn't support this.

Is there any plans to support this?

Unfortunately, No.


Write tests for Unicode operators in Interval

Idea: write the test cases by hand, so that they are candidates for the tutorial.

Solved by #752 and #762


fix: double-response mechanism in the scan screen

What

Check for fresh copy of product while scanning whenever possible

Screenshot

Fixes bug(s)

Fixes: #2451

Part of

#2444

Codecov Report

Merging #2632 (6851e34) into develop (2ea0da3) will decrease coverage by 1.35%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           develop   #2632      +/-   ##
==========================================
- Coverage     8.86%   7.50%   -1.36%
==========================================
  Files          161     212      +51
  Lines         6623   10174    +3551
==========================================
+ Hits           587     764     +177
- Misses        6036    9410    +3374

Impacted Files
Coverage Δ

...kages/smooth_app/lib/widgets/attribute_button.dart
0.00% <0.00%> (-92.00%)
:arrow_down:

...s/smooth_app/lib/data_models/user_preferences.dart
8.73% <0.00%> (-23.57%)
:arrow_down:

packages/smooth_app/lib/themes/smooth_theme.dart
60.00% <0.00%> (-22.98%)
:arrow_down:

...p/lib/generic_lib/dialogs/smooth_alert_dialog.dart
15.11% <0.00%> (-19.10%)
:arrow_down:

...mooth_app/lib/data_models/product_preferences.dart
24.65% <0.00%> (-6.78%)
:arrow_down:

packages/smooth_app/lib/main.dart
14.16% <0.00%> (-3.73%)
:arrow_down:

.../smooth_app/lib/pages/onboarding/welcome_page.dart
0.00% <0.00%> (-3.13%)
:arrow_down:

.../smooth_app/lib/pages/onboarding/scan_example.dart
0.00% <0.00%> (-2.28%)
:arrow_down:

...p/lib/pages/onboarding/consent_analytics_page.dart
0.00% <0.00%> (-1.57%)
:arrow_down:

...smooth_app/lib/pages/product/new_product_page.dart
0.00% <0.00%> (-0.88%)
:arrow_down:

... and 224 more

Thanks for the change.
Just a general question: is-there any timeout on the queryProduct method?

@g123k
Not a timeout but a general try catch is there
 final ProductResult result;
    try {
      ProductQuery.setUserAgentComment(isScanned ? 'scan' : 'search');
      result = await OpenFoodAPIClient.getProduct(configuration);
    } catch (e) {
      ProductQuery.setUserAgentComment('');
      return FetchedProduct.error(FetchedProductStatus.internetError);
    }
    ProductQuery.setUserAgentComment('');

I guess the exception would be caught, would not be a problem here

Ok, thanks for your answer.
I have no real idea on this (so not blocking): in case of a low latency connection, what will happen? (hence the question about the timeout and maybe shrink it a little bit here)

The code is OK 👍.
Don't forget to catch the timeout, and please add the duration as a constant please.

@g123k @teolemon
I guess the code looks good now
Found out  https://github.com/openfoodfacts/smooth-app/pull/273/ , in past we were trying to show the product first then update it , didn't worked out
This time we are 1st trying to get the updated product then if fail show cached one

On your "catch(es)", you should also intercept the network exception, isn't-it?

On your "catch(es)", you should also intercept the network exception, isn't-it?

That's already handled in another file

Ok then LGTM

Found it here, the exception handling
lib\query\barcode_product_query.dart
   final ProductResult result;
    try {
      ProductQuery.setUserAgentComment(isScanned ? 'scan' : 'search');
      result = await OpenFoodAPIClient.getProduct(configuration);
    } catch (e) {
      ProductQuery.setUserAgentComment('');
      return FetchedProduct.error(FetchedProductStatus.internetError);
    }


Measurements stuck/don't-change

I am using an MMC5603NJ with a custom designed ESP32-S3-Mini device. My repository with board layout and software files is here, https://github.com/frankcohen/ReflectionsOS. Arguino-MMC5603NJ connects with the device using I2C address of 0x5A. I turned on Debug logging and see:
MMC5603NJ(0x5a)]: begin
[MMC5603NJ(0x5a)]: readI2C reg 0x39
[MMC5603NJ(0x5a)]:  <- data[0]:0x00
[MMC5603NJ(0x5a)]: read byte = 0
Product ID: 0x0
[MMC5603NJ(0x5a)]: write byte = 128
[MMC5603NJ(0x5a)]: writeI2C reg 0x1c
[MMC5603NJ(0x5a)]:  -> data[0]:0x80
setContinuousMode
[MMC5603NJ(0x5a)]: write byte = 255
[MMC5603NJ(0x5a)]: writeI2C reg 0x1a
[MMC5603NJ(0x5a)]:  -> data[0]:0xff
[MMC5603NJ(0x5a)]: write byte = 160
[MMC5603NJ(0x5a)]: writeI2C reg 0x1b
[MMC5603NJ(0x5a)]:  -> data[0]:0xa0
[MMC5603NJ(0x5a)]: write byte = 3
[MMC5603NJ(0x5a)]: writeI2C reg 0x1c
[MMC5603NJ(0x5a)]:  -> data[0]:0x03
[MMC5603NJ(0x5a)]: write byte = 16
[MMC5603NJ(0x5a)]: writeI2C reg 0x1d
[MMC5603NJ(0x5a)]:  -> data[0]:0x10
setContinuousMode done
[MMC5603NJ(0x5a)]: readI2C reg 0x00
[MMC5603NJ(0x5a)]:  <- data[0]:0xe0
[MMC5603NJ(0x5a)]:  <- data[1]:0x40
[MMC5603NJ(0x5a)]:  <- data[2]:0x00
[MMC5603NJ(0x5a)]:  <- data[3]:0x01
[MMC5603NJ(0x5a)]:  <- data[4]:0x01
[MMC5603NJ(0x5a)]:  <- data[5]:0x00
[MMC5603NJ(0x5a)]:  <- data[6]:0x00
[MMC5603NJ(0x5a)]:  <- data[7]:0x00
[MMC5603NJ(0x5a)]:  <- data[8]:0x00
Gauss X : +24640.00, Gauss Y : -32767.00, Gauss Z : -32512.00, Gauss : +52324.34
[MMC5603NJ(0x5a)]: readI2C reg 0x00
[MMC5603NJ(0x5a)]:  <- data[0]:0xe0
[MMC5603NJ(0x5a)]:  <- data[1]:0x40
[MMC5603NJ(0x5a)]:  <- data[2]:0x00
[MMC5603NJ(0x5a)]:  <- data[3]:0x01
[MMC5603NJ(0x5a)]:  <- data[4]:0x01
[MMC5603NJ(0x5a)]:  <- data[5]:0x00
[MMC5603NJ(0x5a)]:  <- data[6]:0x00
[MMC5603NJ(0x5a)]:  <- data[7]:0x00
[MMC5603NJ(0x5a)]:  <- data[8]:0x00
Gauss X : +24640.00, Gauss Y : -32767.00, Gauss Z : -32512.00, Gauss : +52324.34
Seems to be getting the same values of ime. What do you recommend I do?
-Frank

@frankcohen
I am sorry that I cannot check my code because I don't have MMC5603NJ PCB now.
But from your log, you did not read correct Product ID. So something is wrong on I2C bus.
I think you should aim to be able to read the PID first. You need to check your hardware and software.

Thanks! I will start with the I2C bus first. The bus is working for another
component. And when I do a bus scan for devices, the other devices appear
and the device I'm having a hard time with does not appear. I'm going to
assume that the chip of the sensor is faulty and try and replace it. Thank
you for your support.
On Thu, Dec 22, 2022, 5:40 AM aselectroworks @.***>
wrote:

@frankcohen https://github.com/frankcohen
I am sorry that I cannot check my code because I don't have MMC5603NJ PCB
now.
But from your log, you did not read correct Product ID. So something is
wrong on I2C bus.
I think you should aim to be able to read the PID first. You need to check
your hardware and software.
—
Reply to this email directly, view it on GitHub
https://github.com/aselectroworks/Arduino-MMC5603NJ/issues/1#issuecomment-1362852324,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABUEWML5RVZCKHGUF7HDJCTWORK5DANCNFSM6AAAAAATGEJ454
.
You are receiving this because you were mentioned.Message ID:
@.***>

Welcome.
This chip is small WLP package so it is difficult to mount it.
Hope your project goes well!


SAK-42361 Handle undefined as rubric comment

https://jira.sakaiproject.org/browse/SAK-42361

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- rubrics/tool/src/main/frontend/webcomponents/sakai-rubric-grading-comment.js  1

See the complete overview on Codacy


Add source_address support to PoolManager. Issue warnings if source_address is used with Python 2.6. Fix Python 2.6 testing bug.

@gruns Can you take a look at #830 and give feedback if it satisfies your use case?

@shazow Thanks for looping me in.
The improved connection pooling looks great (thanks @jeremycline), but the
PoolManager API still doesn't accept source addresses at the request()
level.
>>> import urllib3
>>> urllib3.__version__
'1.15.1'
>>> pool = urllib3.PoolManager()
>>> pool.request('GET', 'http://ipinfo.io', source_address=('<IP_ADDRESS>', 12345))
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/local/lib/python2.7/dist-packages/urllib3/request.py", line 69, in request
    **urlopen_kw)
  File "/usr/local/lib/python2.7/dist-packages/urllib3/request.py", line 90, in request_encode_url
    return self.urlopen(method, url, **extra_kw)
  File "/usr/local/lib/python2.7/dist-packages/urllib3/poolmanager.py", line 165, in urlopen
    response = conn.urlopen(method, u.request_uri, **kw)
  File "/usr/local/lib/python2.7/dist-packages/urllib3/connectionpool.py", line 590, in urlopen
    **response_kw)
  File "/usr/local/lib/python2.7/dist-packages/urllib3/response.py", line 384, in from_httplib
    **response_kw)
TypeError: __init__() got an unexpected keyword argument 'source_address'

Accepting source_address at the request() level is the right API granularity
to make interacting with multiple source addresses a breeze.


Disconnected nodes stuck overlapped at origin

Describe the bug
When data has nodes that are not connected by any links, the nodes are overlapped and stuck at the origin.
Data and Config
{
  "id": "graph-id",
  "data": {
    "nodes": [
      {
        "id": "q0_node",
        "label": "node",
        "fontColor": "white",
        "opacity": 1,
        "color": "#01FF70",
        "node_id": "q0"
      },
      {
        "id": "q1_node",
        "label": "node",
        "fontColor": "white",
        "opacity": 1,
        "color": "#01FF70",
        "node_id": "q1"
      },
      {
        "id": "q2_node",
        "label": "node",
        "fontColor": "white",
        "opacity": 1,
        "color": "#01FF70",
        "node_id": "q2"
      },
      {
        "id": "q3_node",
        "label": "node",
        "fontColor": "white",
        "opacity": 1,
        "color": "#01FF70",
        "node_id": "q3"
      },
      {
        "id": "q4_node",
        "label": "node",
        "fontColor": "white",
        "opacity": 1,
        "color": "#01FF70",
        "node_id": "q4"
      },
      {
        "id": "q5_node",
        "label": "node",
        "fontColor": "white",
        "opacity": 1,
        "color": "#01FF70",
        "node_id": "q5"
      },
      {
        "id": "q6_node",
        "label": "node",
        "fontColor": "white",
        "opacity": 1,
        "color": "#01FF70",
        "node_id": "q6"
      },
      {
        "id": "q7_node",
        "label": "node",
        "fontColor": "white",
        "opacity": 1,
        "color": "#01FF70",
        "node_id": "q7"
      },
      {
        "id": "q8_node",
        "label": "node",
        "fontColor": "white",
        "opacity": 1,
        "color": "#01FF70",
        "node_id": "q8"
      },
      {
        "id": "q9_node",
        "label": "node",
        "fontColor": "white",
        "opacity": 1,
        "color": "#01FF70",
        "node_id": "q9"
      }
    ],
    "links": [],
  "config": {
    "directed": true,
    "height": 700,
    "width": 1000,
    "node": {
      "renderLabel": true,
      "labelProperty": "id",
      "color": "lightgreen",
      "size": 120,
      "opacity": 10
    },
    "link": {
      "renderLabel": false,
      "type": "CURVE_SMOOTH",
      "fontColor": "white",
      "color": "#d3d3d3",
      "highlightColor": "lightblue",
      "opacity": 0
    },
    "d3": {
      "alphaTarget": 0.05,
      "gravity": -100,
      "linkLength": 100,
      "linkStrength": 0.01
    }
  }
}

Expected behavior
Nodes should be separated based on gravity config.
Screenshots

When first loaded

After dragging the nodes to middle of the screen.

Using onClick event to log details of the node

Environment:

OS: windows 10
Browser: Chrome
Version: 88.0.4324.190
react-d3-graph version 2.6.0
d3 version 5.16.0
react version 16.13.1

@ongmk were you able to solve this issue?

@ongmk were you able to solve this issue?

Oops I closed it because I saw that a similar issue was closed in version 2.6.0.

But after some testing I find that I still have the same issue.

@oshhh I am having also having the same issue where the graph animates when I setstate. Did you find a way to fix that?

@ongmk yes I was able to solve that by creating a component containing only the graph and passing the data as props to that component. I also added the function shouldComponentUpdate to ensure that it doesn't update everytime the state of the parent component is updated
class KG extends Component {
  state = {};
  shouldComponentUpdate(nextProps) {
    return nextProps.graph !== this.props.graph;
  }
  render() {
    return (
      <Graph
        id="graph-id"
        data={this.props.graph}
        config={this.props.config}
        onClickNode={(id, node) => {
          this.props.onClickNode(node);
        }}
      />
    );
  }
}

That makes a lot of sense. Thank you!

@ongmk I am not able to drag the nodes and I think that's a problem in my version of d3-drag. Could you let me know which version are you using?
The README just requires us to install d3 but I get the error Can't resolve 'd3-drag' in '/Users/osheensachdev/btp/chatbot_app/node_modules/react-d3-graph/lib/components/graph'. Did you face the same error? If so which version of d3-drag did you install?

Thanks for the detail @ongmk , if possible please add a link to a repository or codesanbox environment where we can debug this issue to better understand what you're facing.

@danielcaldas
https://github.com/oshhh/chatbot_app/tree/react-d3-graph-debug
branch: react-d3-graph-debug
To run just clone it and run npm start.
Go to the tab "Knowledge Graph" and you'll be able to see nodes stuck at origin.
Configuration:
"d3": "^5.5.0",
"react": "^17.0.1",
"react-d3-graph": "^2.6.0",
"react-dom": ">=17.0.0",

Hey All, I'm having this issue as well. Created a Codesandbox project with the config very close to what is given in the README file of react-d3-graph project...
https://codesandbox.io/s/bold-panini-xpgf4?file=/src/App.js
The unlinked nodes cluster in the top-left part of the Graph - you might need to drag the graph a bit to see them.
  "dependencies": {
    "d3": "^5.16.0",
    "react": "^16.4.1",
    "react-d3-graph": "^2.6.0",
    "react-dom": "^16.4.1",
    "react-scripts": "4.0.3",
    "web-vitals": "^1.1.1"
  },


Optimize extracting of scripts and redeemers

Alonzo epochs seem to be slower than older epochs. This could be the result of the work done to match redeemers with scripts and resolving the redeemers pointers. This affects blocks that don't even have scripts. Many optimizations are possible there. Ideally this would be available from ledger-spec through some ledger event.

Should be fixed in https://github.com/input-output-hk/cardano-db-sync/pull/1112


Issue with header on default dashboards.

Default dashboards have a very tight header. If a header bar is present then it could do with a bit of padding. If Kiosk mode is on / no header bar then no padding is required.

This is because you're using the default theme at the user level but this theme at the view level. The header height is shorter for this theme, and the view top padding doesn't match the default header height. You need to either use this theme at the user level, or add your own spacer element to the view to account for it (the new heading card set to subtitle with no text in a full width section works well).


Problem accessing upperValue and lowerValue

Hi there, I am making my own custom labels displaying upperValue and lowerValue when the sliderValueChanged method is called, except I can't get the changed upperValue and lowerValues

^See above for my code

you can access the value via sliderView.rangeSlider!.upperValue . sliderView.upperValue is meant for writing, not reading. I will fix that later.


Add JSON marshalling and unmarshalling specific model types to rethink Table object

This is a replacement for #770.

Can we add failure cases for the json unmarshaling for each table type?  Otherwise, LGTM!

@riyazdf Ah yep, thanks, good point.  Updating!

👍 thanks for updating, LGTM!


Close atom without save file, and keep change in file

How to close atom without save file like sublime text?

If you open a directory in Atom, then when you exit Atom if you select Don't Save ... the next time you open Atom from that directory, the file will be there with the changes. This assumes that you use the standard Atom workflow. If you don't, then there are already issues covering this: #942 #4161 et al.

Check out the package saveallthetime.
On Fri, Feb 27, 2015 at 7:46 AM, Lee Dohm<EMAIL_ADDRESS>wrote:

If you open a directory in Atom, then when you exit Atom if you select
Don't Save ... the next time you open Atom from that directory, the file
will be there with the changes. This assumes that you use the standard Atom
workflow. If you don't, then there are already issues covering this: #942
https://github.com/atom/atom/issues/942 #4161
https://github.com/atom/atom/issues/4161 et al.
—
Reply to this email directly or view it on GitHub
https://github.com/atom/atom/issues/5783#issuecomment-76415112.

#942 , the future i need, tks @lee-dohm


conform to the correct route syntax for target port

fixes: https://github.com/kiali/kiali/issues/4255

This is very easy to test:

Install using the operator in OpenShift (make operator-create kiali-create is enough)
See that you have port.targetPort in the route spec:

$ oc get route kiali -n istio-system -o jsonpath={.spec.port.targetPort}
20001

Make sure you can access Kiali via the route:

$ curl -k --head https://$(oc get route kiali -n istio-system -o jsonpath={.spec.host})
HTTP/1.1 200 OK


Ruby 2.4.0 compatibility

Not a problem with ruby-vips per se. However, the glib2 3.0.8 gem no longer builds under Ruby 2.4.0 whereas the glib2 3.0.9 builds just fine.
The issue appears to be that glib2 3.0.8 uses rb_cFixnum which no longer exists in MRI and has been replace with rb_cInteger (see https://bugs.ruby-lang.org/issues/12005).
I've looked at the glib2 ruby project and 3.0.8 is now two releases behind so my guess is there'll be close to no motivation for them to want to fix the issue.
Is there something I can do to help bring ruby-vips up to the latest glib2 or is that a massive undertaking?
Alternatively, I suppose we could for glib2 at 3.0.8 and patch it but that's not ideal.

Hi, yes, I remember running into this problem, it's frustrating. When I last looked, there didn't seem to be a simple solution for ruby-vips, but perhaps things have moved on.
I'll try to investigate!

It looks like the worst problems have vanished, it was pretty easy to make it sort-of work with glib2 3.1.1:
https://github.com/jcupitt/ruby-vips/tree/move-to-goi-3.1
There are four failure in the test suite, all related to fixnum (as you said). They look something like:
$ rake
Resolving dependencies...
/usr/bin/ruby2.3 -I/home/john/packages/gems/gems/rspec-core-3.5.4/lib:/home/john/packages/gems/gems/rspec-support-3.5.0/lib /home/john/packages/gems/gems/rspec-core-3.5.4/exe/rspec spec/image_spec.rb spec/vips_spec.rb
...FF.....FF.....................................

Failures:

  1) Vips::Image can save an image to a buffer
     Failure/Error: value = value.pack("C*")

     NoMethodError:
       undefined method `pack' for 255:Fixnum
     # ./lib/vips/argument.rb:114:in `block in unwrap'

They need looking into.

OK, the test suite runs cleanly now, I found a couple more small differences.
That's with ruby2.3, would you be able to test with 2.4?

Sorry, was away. Will try it out now.

Looks good to me?
❯ ruby --version
ruby 2.4.0p0 (2016-12-24 revision 57164) [x86_64-darwin16]

❯ bundle
Resolving dependencies...
Using rake 11.3.0
Using bundler 1.13.7
Using diff-lcs 1.3
Using github-markup 1.4.1
Using pkg-config 1.1.7
Using redcarpet 3.4.0
Using rspec-support 3.5.0
Using yard 0.9.8
Using glib2 3.1.1
Using rspec-core 3.5.4
Using rspec-expectations 3.5.0
Using rspec-mocks 3.5.0
Using gobject-introspection 3.1.1
Using rspec 3.5.0
Using ruby-vips 1.0.4 from source at `.`
Bundle complete! 7 Gemfile dependencies, 15 gems now installed.
Use `bundle show [gemname]` to see where a bundled gem is installed.

❯ bundle exec rake
/usr/local/Cellar/ruby/2.4.0/bin/ruby -I/usr/local/lib/ruby/gems/2.4.0/gems/rspec-core-3.5.4/lib:/usr/local/lib/ruby/gems/2.4.0/gems/rspec-support-3.5.0/lib /usr/local/lib/ruby/gems/2.4.0/gems/rspec-core-3.5.4/exe/rspec spec/image_spec.rb spec/vips_spec.rb
.................................................

Finished in 0.93703 seconds (files took 0.15374 seconds to load)
49 examples, 0 failures

That's great, thanks very much!
I'll merge to master and update the gem.

OK, all done, we have a 1.0.4 gem. Thanks again!


Update settings.rst (clarification on overlay behavior)

Suggesting a copy edit change in the Settings --> Overlay section based on #570.

Looks great, thanks! Can you make this pull request against the oddbird/susy repo?

Sure thing! First-time PR on GitHub for an outside project (finally), so I'll sort it out.
– Joe

On Feb 12, 2016, at 5:01 PM, Miriam Suzanne<EMAIL_ADDRESS>wrote:
Looks great, thanks! Can you make this pull request against the oddbird/susy repo?
—
Reply to this email directly or view it on GitHub.