Update scodec-bits to 1.1.27

Updates org.scodec:scodec-bits from 1.1.26 to 1.1.27.
GitHub Release Notes - Changelog - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scodec", artifactId = "scodec-bits" } ]

labels: library-update, semver-patch

Codecov Report

Merging #126 (953f55b) into master (04aea7f) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master      #126   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            3         3
  Lines           48        48
=========================================
  Hits            48        48

Continue to review full report at Codecov.

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


[Form] Add a prop in order to clean the store in create mode

Current behaviour
When a store is loaded with values (ex: a block in consult mode), when we display a block in creation linked to the same store, the old values (values from the consult mode) are still displayed in the block even if we override the initial state.
The only offical way to do it is to clean the store by hand, by dispatching a empty objet in the initial state.
Expected behaviour
Please add a 'isCreate' props (like the 'isEdit' one) managed by the framework, which will clean the store in this case.
Versions
Focus-core: 0.12.3
Focus-components: 0.8.5

@durandx  you can use the status information on the store node and in your action builder in order to achieve this, then you can read the information in your store .

There is also a property inside the action builder which is called  shouldDumpStoreOnActionCall
https://github.com/KleeGroup/focus-core/blob/30811ee3170a06a6305659920256cf2d7d8e10ca/src/application/action-builder.js#L102


Rename flatten array to flatten

Opened from a discussion in exercism/xpython#374.
I think this exercise should be renamed to use more generic terminology.  flatten is sufficiently generic.  Arrays in Python are different than lists and are not frequently used.
Thoughts on renaming this exercise?  Would it need to be renamed in all languages that currently include it?

Some reasons why renaming might not be a good idea:

It requires all the language tracks that implement the problem to also update their configurations.
There are implications for maintaining history with the solutions of 'flatten-array' which have already been completed and stored in the Exercism database.
There are many things you could flatten, having 'array' in the name doesn't seem unreasonable.
It is possible to add track specific information to the readme that the Python track could use to point out that they're using Lists.

This was also discussed in xElixir. The name does not make sense there as we use lists rather than arrays.
https://github.com/exercism/xelixir/pull/185
At the end of the discussion @kytrinyx outlined the steps need to make this change. Sorry, @treyhunner, you may have bitten off more than you thought with this PR.
Here is what @kytrinyx said verbatim:

OK, cool. So I think we need to

[ ] duplicate the exercise files here in x-common (so we can migrate individual language tracks independently of one another
[ ]  create a blazon issue that can be submitted to all the languages that have implemented flatten_array (javascript, kotlin, ruby) to describe how to migrate the problem. I think this requires

renaming the problem directory
renaming the files
updating any code that refers to the old name
updating any comments or documentation that refer to the old name

[ ] make sure we have a rake task that can be run in production to migrate existing solutions to the new name as soon as we deploy the migrated (see below)

We used to have a rake task that kind of did this, but it was all hard coded:

    desc "migrate deprecated problems"
    task :deprecated_problems do
      require 'bundler'
      Bundler.require
      require_relative '../exercism'
      {
        'point-mutations' => 'hamming'
      }.each do |deprecated, replacement|
        UserExercise.where(slug: deprecated).each do |exercise|
          if UserExercise.where(slug: replacement, user_id: exercise.user_id, language: exercise.language).count > 0
            next
          end

          exercise.slug = replacement
          exercise.save
          exercise.submissions.each do |submission|
            submission.slug = replacement
            submission.save
          end
          ACL.authorize(exercise.user, exercise.problem)
        end
      end
    end

It would be nice if we could have this task, but it would take two command-line arguments, one for the track_id and two from the problem slugs (src, dest).

This is going to take some work, can you create a separate x-common issue with all that info @parkerl

The most important thing to note is that we need to copy, not move the files.
We should also add a .deprecated file to the flatten-array directory (we can add text to it to explain that it's been renamed to flatten, since any text in the file gets ignored. Or not, the git blame will end up pointing to this discussion, I think).

Would it be simpler to introduce this as a new exercise, and deprecate the old?  Seems like a lot of coordination for something that if done as a new exercise would avoid all of it.

It's clear that the work involved in changing the name of the exercise is more than the contents of this Pull Request.
I will close this pull request, but I have created an issue: https://github.com/exercism/x-common/issues/454 about this issue if anyone wishes to continue working on it.


Update template for 60s connection timeout

Add connection timeout of 60s to API Client with Template modification
Update Makefile to build with template

EPT Changes are happening because some manual modifications were made to 4.10 Swagger Spec after our SDKs were last released. Including them based on the current Github Workflows auto commit.

Same thing here for PrecisionTimeServices A.K.A. EPT: https://github.com/equinix-labs/fabric-go/pull/18#discussion_r1372253828


Add macCatalyst support

Hi Google team.
Do you have any raw estimations of when you'll add macCatalyst support?
Thank you

Hopefully sometime this year.  More detail on future releases coming soon.

Thanks for the response. Looking forward to it.

I tries catalyst right now and it is working.. :) I made login on catalyst app on big sur

Also working on catalyna and monterey

Mac Catalyst is now supported with the release of Google Sign-In 6.1.0.

Great news, Thanks for the response


The clickHandlerFunc parameter dont work

Hi, mpetroff. Sorry to bother you again.
My question now is how to use clickHandlerFunc correctly. I have use
hotSpots: [
              {
                pitch: -10,
                yaw: 0,
                type: "scene",
                sceneId: "place-three",
                cssClass: "custom-hotspot",
                createTooltipFunc: this.hotspot,
                createTooltipArgs: "someplace",
                clickHandlerFunc: this.clickHotspot,
                clickHandlerArgs: "args",
              },
            ],

to create the viewer instance, and the "clickHotspot" defined as follows(I am using Vue):
clickHotspot(hotSpotDiv, args) {
      console.log(args);
 },

but when I click the hotspots, I can't see any information on the console.
I have been struggling with this problem for a day, I want to know what went wrong. Thank you in advance for your help！

Are you sure this.clickHotspot is defined? I would recommend trying clickHandlerFunc: function(d, a) {console.log(d, a)}, and seeing if that works.

Thank you! I have known where the problem is.
I set the sceneId so when I click to switch scene, the 'clickHandlerFunc' is not triggered. If I don’t use sceneId, the 'clickHandlerFunc' works.

Thank you! I have known where the problem is.
I set the sceneId so when I click to switch scene, the 'clickHandlerFunc' is not triggered. If I don’t use sceneId, the 'clickHandlerFunc' works.

I'm not sure why having both defined doesn't work for you. You should end up with two different click handlers on the hot spot, and both the scene change handler and the custom handler should be called.

Thank you, I will try it again.


Protocol version confusion

Hello everybody,
Upon implementing the TUS protocol in our API, we ran into this version: https://www.ietf.org/archive/id/draft-tus-httpbis-resumable-uploads-protocol-00.html#name-authors-addresses and there has been a bit of a confusion what is this protocol, are they related, etc?
Thank you in advance for you response!

Hi!
The protocol you are linking to is the next version of the tus spec. We are working with the IETF to make this a http standard. The latest version of the IETF draft spec can be found here and it explains the difference pretty well:

The tus v1 protocol (https://tus.io/) is a specification for a
resumable file upload protocol over HTTP.  It inspired the early
design of this protocol.  Members of the tus community helped
significantly in the process of bringing this work to the IETF.

Hope it clears it up!

There is also this blog post now, which helps understand the relationship between the two protocols: https://tus.io/blog/2023/08/09/resumable-uploads-ietf In a nutshell: the work from the IETF is the part from tus we are trying to standardize.


1.4 directive is not refreshing after redirect

Hello,
i have another issue with 1.4. Am not sure if this is issue or this is new 1.4 behavior.
Scenario:
i have a button click in firs screen
addMessage = () => {
        var test: ISpaGlobalMessage = {
            messageType: SpaGlobalMessageType.Error,
            text: 'test message'
    }

        this.$spaGlobalMessages.add(test);
    }

    testClick = () => {
        this.addMessage();
        this.$state.go(impStates.login.login);
    }

$spaGlobalMessages is service and store messages in array nothing fancy.
Also i have directive wich responsable for showing those messages (will paste only code that matters):
 template: string = 'messages from directive: {{globalMessages[0].text}}

controller:
if ($scope.globalMessages == null) {
            $scope.globalMessages = <ISpaGlobalMessage[]>[];
        }

$scope.$on('globalMessageAdded', () => {
            $scope.globalMessages = $spaGlobalMessages.getMessages();
        });

When i press button in screen 1 and redirect to screen 2 $scope.globalMessages is not empty but they are not shown in template. (This used to work with AngularJs 1.3). Debugger shows that $scope.globalMessages contains one message (the one i have added in screen one before redirect and it is not empty because just before redirection it was shown in screen 1 because of $scope.$on - since directive is singleton $scope transfers to screen 2 after redirection).
And it fails to work until I add this line to controller:
$scope.globalMessages = $spaGlobalMessages.getMessages();

which basically creates I dont know what, local scope variable maybe??? But why:

It worked in 1.3.0
Debuger shows that $scope.globalMessages is not empty

Also if I add button to the same screen it works perfectly without that line.

@vytautas-pranskunas- could you please provide a plunker with a minimal reproduce scenario? It would be much easier to understand what is going on, determine if this is a bug and fix it eventually. Thnx!

Amm dont think i have time for this :( sry
But basic idea is very simple. As far as directive is singleton and is injected into page 1 and 2.

Add value to directive scope in page 1
Redirect to page 2
Same directive is not showing added value on page 2

i created a plunkr but it does not show the error: http://plnkr.co/edit/tBth2b?p=preview
did i understand this issue correctly @vytautas-pranskunas-  ?
directives get new scopes whenever they are instantiated, e.g. upon navigation. shared state would have to be kept outside (e.g in a service) and that works in my plunkr

Can you replace ngRouter wit ui.router? after if it will still work i will fork and trye to modify the code one to one scenario as i have

I was playing around with your example:
Added controller as syntax, add storing sharedValue in $rootScope (my case), then accessing it in directive directly {{storedValue}} without invoking getSharedValue and cannot reproduce issue.
In my case service stores value in $rootScope and after redirecting to another view debugger sees that value ($scope.sharedValue) but directive template {{sharedValue}} does not render anything.
If you can only add ui.router to your example so i can play around and see maybe this causes that bug

@vytautas-pranskunas-  I updated it to use ui-router and it  works for me -- http://plnkr.co/edit/tBth2b?p=preview
http://plnkr.co/edit/tBth2b?p=preview
Dont forget that all controllers are rebuilt on navigation though, if you removed line 10 from the plunkr it would always reset the root variable after each navigation for example.

Line 10 in which file?
I think it may be because of lazy loading. But logically when controller lazy loaded it is registered to angular and is not loading any more so second time rootScope should not be reset.
Hmm seems like it is our system issue and i will solve it other ways.
We can close this ticket.
Thanks for your time.

In Module.js the if statement that initiates the shared variable
Von meinem Windows Phone gesendet
-----Original Message-----
From: "Vytautas Pranskunas"<EMAIL_ADDRESS>Sent: 06.05.2015 11:28
To: "angular/angular.js"<EMAIL_ADDRESS>Cc: "matthiasg"<EMAIL_ADDRESS>Subject: Re: [angular.js] 1.4 directive is not refreshing after redirect(#11707)
Line 10 in which file?
I think it may be because of lazy loading. But logically when controller lazy loaded it is registered to angular and is not loading any more so second time rootScope should not be reset.
Hmm seems like it is our system issue and i will solve it other ways.
We can close this ticket.
Thanks for your time.
—
Reply to this email directly or view it on GitHub.


asRopedText sometimes causes "Improper store into indexable object" error

Converting a BlRopedRawText into a BlRopedText can sometimes case an error. For example, running this code causes an error:
| string rawText  |
string := '//1234567890/123456789012' , String lf, String lf, 'line2', String lf.
rawText := BlRopedRawText string: string.
rawText asRopedText

works now


commit yarn.lock changes

we recently merged a big feature update with changes to the package.json. this PR applies the changes to yarn.lock that yarn makes when running yarn.

analysis of actual additions

secp256k1 5.0.0

elliptic 6.5.4

bn.js 4.12.0
brorand 1.1.0
hash.js 1.1.7
hmac-drbg 1.0.1
minimalistic-crypto-utils 1.0.1

node-addon-api 5.1.0
node-gyp-build 4.6.0

js-sha256 0.8.0

Related to https://github.com/oasisprotocol/ledger-js/pull/627


Add support of non-amazon S3 endpoint, fix bugs in swift underfs.

Added support of non-amazon S3 endpoint.
Fixed bugs in swift underfs.

Can one of the admins verify this patch?

ok to test

Jenkins, add to whitelist

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9251/Failed Tests: 1org.alluxio:alluxio-underfs-swift: 1alluxio.underfs.swift.SwiftUnderFileSystemTest.stripPrefixIfPresentTest
Test FAILed.

If don't trim "/" in "/dir/file", then API calls in JOSS will fail, I guess I should modify the test case to avoid this check.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9252/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9253/
Test PASSed.

@rlzhang thank you for the PR! I left one comment.

@ifcharming , have updated the docs.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9285/Failed Tests: 2org.alluxio:alluxio-tests: 2[1].[1]alluxio.worker.block.meta.TieredStoreIntegrationTest.alluxio.worker.block.meta.TieredStoreIntegrationTest
Test FAILed.

Jenkins, test this please.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9289/
Test PASSed.

@rlzhang thanks for submitting the change! I put a few comments regarding the documentation. Please let me know if they make sense to you. Thanks.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9341/
Test PASSed.

Merged build finished. Test PASSed.

@apc999 I adjusted a few things in the documentation files, incorporating your comments. I tried to match the linguistic conventions as much as possible; let us know if I've missed something or should make additional tweaks.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9342/
Test PASSed.

Merged build finished. Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9343/
Test PASSed.

@calvinjia @rlzhang I want to understand the joss / swift path issue. It does look like joss constructs the full path with container + '/' + path, so if the path starts with '/', it will fail.
However, when would the path start with '/'? If the path had the full URI, the container (with the trailing '/') will be stripped and the stripped path would not start with '/'. This situation would not cause a problem.
In which other situations would a path NOT have the scheme and authority, but also start with a '/'?
Maybe @gilv has some thoughts?
Thanks.

Hi @rlzhang , the PR that added swift to the client pom is merged. Could you merge the master branch into this PR. Thanks!

Hi @gpang, have merged. Thanks!

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9487/
Test PASSed.

Merged build finished. Test PASSed.

@calvinjia @gilv @rlzhang I think I am fine with the swift strip() change. If I take a look at the s3 underfilesystem, it does a similar thing (strips away the first '/').

LGTM

LGTM

LGTM

I am also fine with it, but i completely agree with previous remark of @calvinjia :"In which other situations would a path NOT have the scheme and authority, but also start with a '/'?"


Set name of current route as transaction

:scroll: Description

:bulb: Motivation and Context

:green_heart: How did you test it?
:pencil: Checklist

[ ] I reviewed submitted code
[ ] I added tests to verify changes
[ ] I updated the docs if needed
[ ] All tests passing
[ ] No breaking changes

:crystal_ball: Next steps

Codecov Report

Merging #560 (8800f80) into main (36e4db2) will increase coverage by 0.05%.
The diff coverage is 80.00%.

@@            Coverage Diff             @@
##             main     #560      +/-   ##
==========================================
+ Coverage   91.42%   91.47%   +0.05%
==========================================
  Files          75        7      -68
  Lines        2471      258    -2213
==========================================
- Hits         2259      236    -2023
+ Misses        212       22     -190

Impacted Files
Coverage Δ

.../lib/src/navigation/sentry_navigator_observer.dart
95.55% <80.00%> (-4.45%)
:arrow_down:

dart/lib/src/protocol/sentry_exception.dart

dart/lib/src/protocol/contexts.dart

dart/lib/src/sentry.dart

dart/lib/src/protocol/sentry_runtime.dart

dart/lib/src/sentry_envelope.dart

dart/lib/src/transport/rate_limit.dart

dart/lib/src/protocol/sentry_app.dart

dart/lib/src/transport/http_transport.dart

dart/lib/src/utils.dart

... and 59 more

Continue to review full report at Codecov.

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

although this makes sense, it'd conflict with the performance API that comes next, since this field kinda got changed, let's not merge for now


BC break: Calling a method unnecessarily

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

Fixed issues
#19272

Remake of #19804

Hello @bizley
Please check if this is what you expected.

Yes, thank you 👍🏻  We need to also update the changelog line, something like Remove the unnecessary call to $this->oldAttributes in BaseActiveRecord::getDirtyAttributes().

@bizley  Changelog updated.
Sorry for my bad english :upside_down_face:


Add convenience stuff

I fear you all hate convenience stuff. But I would be happy to find this pre-cut and pre-chewed stuff:
import Math(floor)

-- Takes a range _low_ _high_ and returns a random int uniformly distributed in the
-- closed interval [lo,hi]. It is unspecified what happens if lo>hi.
randomInt :: forall e . Number -> Number -> Eff (random :: Random | e) Number
randomInt low high = do
    rand <- random
    return (floor (rand * (high - low + 1)) + low)

-- Returns a random number between min (inclusive) and max (exclusive)
randomRange :: forall e . Number -> Number -> Eff (random :: Random | e) Number
randomRange min max = do
    r <- random
    return (r * (max - min) + min)

If you are willing to accept it, I will be happy to provide a patch.

I don't think we all like convenience stuff. I think this library just isn't used much, so not many functions like this have been made.
I'm :+1: though!

:+1:


Added touch events support

Great works @kortykotropina
I think we need to merge this, so this will work on the mobile..
or is there any way to do so without merge this? Thanks
CC @ssthouse

@ssthouse
Hey, any update on this PR?

@ssthouse any updates on this PR ? need to merge this PR , otherwise should use another plugin as its not working on mobile ((


Replace 'exact' lookup_type with 'icontains' in Groups API.

Since groups and skills models share some similarities I suggest we do the same to skills as well.

Since we are changing our public api we should update the docs as well.

@johngian  pr updated. Thanks!

By changing the default lookup type for these fields we are braking the functionality for our current consumers.
I suggest we:

Leave the default lookup_type as it is
Add an extra lookup_type that introduces the new functionality.

@johngian pr updated

Instead of adding extra fields its better to extra lookup_types. This gives us flexibility to build more on top.

https://django-filter.readthedocs.org/en/latest/usage.html#the-filter
Multiple lookup types

@johngian pr updated

r+


Fix unexpected crash during SSL tests

Crash (didn't affect tests, but gave off the impression something was wrong) was:
=ERROR REPORT==== 29-Oct-2020::11:08:45 ===
Elli request (pid #Port<0.86655>) unexpectedly crashed:
shutdown

=ERROR REPORT==== 29-Oct-2020::11:08:45 ===
Elli request (pid <0.396.0>) unexpectedly crashed:
{shutdown,{gen_statem,call,[<0.437.0>,{recv,0,60000},infinity]}}

In OTP 20.3, at least, it did make 1 test fail, though.

Coverage decreased (-0.3%) to 75.546% when pulling 4b633252436da3aaa146849ac96c2376c79c4de7 on paulo-ferraz-oliveira:fix/unexpected_test_crash into 968afee385f46c053fd46858713261db7dc03af4 on elli-lib:main.

Coverage decreased (-0.3%) to 75.546% when pulling 4b633252436da3aaa146849ac96c2376c79c4de7 on paulo-ferraz-oliveira:fix/unexpected_test_crash into 968afee385f46c053fd46858713261db7dc03af4 on elli-lib:main.

Now that I see the tests failing in Travis CI, executing them locally shows that "sometimes" they fail on OTP 23. Might it be a timing issue?

pang

@tsloughter: is this OK for merge?

Ah yea. One sec, let me just rerun travis once more.

Maybe I'll finally move this to github actions soon...

relates to #90


Pls update for ARM64 version

Can you update this for ARM64 version on the future?

https://hub.docker.com/repository/docker/overtrue/gradient-bot/tags

https://hub.docker.com/repository/docker/overtrue/gradient-bot/tags

HI I just pull the docker for arm and got error with
"Error occurred: Error: Unable to obtain browser driver"
For more information on how to install drivers see
2|gradient-2  |         https://www.selenium.dev/documentation/webdriver/troubleshooting/errors/driver_location/. Error: Error executing command for /app/node_modules/selenium-webdriver/bin/linux/selenium-manager with --browser,chrome,--language-binding,javascript,--output,json,--proxy,http://<IP_ADDRESS>:40685: /app/node_modules/selenium-webdriver/bin/linux/selenium-manager: 1: Syntax error: "(" unexpected
2|gradient-2  |     at getBinaryPaths (/app/node_modules/selenium-webdriver/common/driverFinder.js:38:11)
2|gradient-2  |     at thenableWebDriverProxy.createSession (/app/node_modules/selenium-webdriver/chromium.js:627:45)
2|gradient-2  |     at thenableWebDriverProxy.createSession (/app/node_modules/selenium-webdriver/chrome.js:219:42)
2|gradient-2  |     at createDriver (/app/node_modules/selenium-webdriver/index.js:153:33)
2|gradient-2  |     at Builder.build (/app/node_modules/selenium-webdriver/index.js:674:16)
2|gradient-2  |     at /app/app.js:207:8
2|gradient-2  |     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)


'bus error python' on M1 Mac in the 00-SystemCheck notebook

When I try to run the sentiment analysis, as soon as I execute
nlp("I feel good"),
I get

zsh: bus error  python

The problem turned out to be this code:
nlp = pipeline("sentiment-analysis")
After this step, I get - among other info - this line back:

Hardware accelerator e.g. GPU is available in the environment, but no device argument is passed to the Pipeline object. Model will be on CPU.

So I decided to provide the 'device' argument. If MPS is present on the machine, I can create the pipeline like this:
nlp = pipeline("sentiment-analysis", device="mps")
The documentation is here:
https://huggingface.co/docs/transformers/v4.44.0/en/main_classes/pipelines#transformers.pipeline
Now the sentiment analysis runs.

Yeah, similar issue happened in Mac book M1 pro, keep crashing Jupiter notebook when running the pipeline. it works after specified GPU acceleration:
nlp = pipeline("sentiment-analysis", framework='pt',device=0).
device=0 means using GPU, -1 means use CPU, default value is -1.

Interesting, so there seems to be more than one way to specify the device.


Treeview with multiselect mishandles right-click outside the selection

I've been adding multi-select support to GitLens treeview and noticed a few issues with tree views with canSelectMany enabled

So in that image, I have a group of commits selected, and then right-clicked a commit outside that group. And in that case, VS Code leaves the original selection in place (unlike if you left-click), but doesn't change the listMultiSelection context key (which besides listDoubleSelection is the only content key that really can be used to shape a content menu for multi-select) and also when a command is executed doesn't provide the selected items, only the item you right-clicked on.
Ideally VS Code would either:

Clear the previous selection (as if you left-clicked on the item) and only have the right-clicked item selected
OR
Change listMultiSelection to be false so that the content will match how the commands will get executed.

/cc @alexr00

I think instead it should keep the selection, then include the node that was right-clicked-on as part of the selection. Does that seem reasonable?
Regarding how to shape the context menu: with https://github.com/microsoft/vscode/pull/210754, I've made it so only command that apply to all the selected nodes (and the one you right clicked on) are included in the context menu.

Hmm, actually, after looking at who the Explorer view works I've changed my mind:

keep the multi select
when the command is executed use the selection, not the right click target.

and also when a command is executed doesn't provide the selected items, only the item you right-clicked on.

Will fix this bug.

Behavior when right click is done in a tree where there's a selection:

First argument is always the right click target
Second argument is always the selection array, even when the right click target isn't part of the selection

I believe i verified the original issue, but there is some weirdness on selection using shift to select multiple items in the tree view. i don't know if this is a big issue tho 🔢
https://github.com/microsoft/vscode/assets/54879025/1052625a-aff6-49fc-bb07-8d8958b976ad

Looks like https://github.com/microsoft/vscode/issues/208802, I'll see if I can repo using the steps you followed!

So the experience here will be, if I have 1-3 rows selected, and then I right click on row 5 -- the context menus will behave as I clicked rows 1-3? This seems very confusing from a user point of view.
Both Mac (finder) and Windows (explorer) handle this differently, but they are consistent that if you right-click outside of the selection you get actions related to the item you right-clicked on. Windows clears the previous selection, so that the only thing is the right-clicked item, while Mac leaves the previous selection.
IMO VS Code should do one of those 2 things -- either clear the selection and the menu options will be provided for the single right-clicked item OR leave the selection intact but still only provide menu options for the single right-clicked item.

Discussed during standup, and the proper behavior should be:

When the right click occurs within the selection, show context menu actions that apply only to the entire selection. The command should get the selection as an argument.
When the right click occurs outside the selection, show only context menu actions for the right click target. The command should not receive the selection as an argument.

I've reopened this as the question of listMultiSelection has not been addressed. @eamodio is this as important now that for multi-select + right click in the selection the context menu only shows commands which apply to all the elements in the selection?

@alexr00 not sure I'm following. The behavior of right-clicking on an item within the current selected items was correct (listMultiSelection was correct and the callback with the items was correct). But right-clicking outside the current selected items is the broken case.

@eamodio above you had:

Ideally VS Code would either:
Clear the previous selection (as if you left-clicked on the item) and only have the right-clicked item selected
OR
Change listMultiSelection to be false so that the content will match how the commands will get executed.

I haven't changed the behavior to match either of these, and I would like to continue to leave the behavior as is since visually it matches our other trees and there is still a multi selection in the tree.
You were using listMultiSelection as a context to determine what needs to go in a context menu. With https://github.com/microsoft/vscode/pull/210754, we only show the menu items that apply to the selection (or if you right click outside the selection, then the context menu items that apply to the right click target). I'm wondering if you still care about clearing the previous selection or changing listMultiSelection given https://github.com/microsoft/vscode/pull/210754.

Closing because of lack of activity.


Error

Cannot read properties of undefined (reading 'style')
Evaluating react-native-elements.js
Evaluating App.js
Loading App.js
I am getting this error when I run my app on web app

Can Someone Please Help Me

⚠ You did not follow the contributing guidelines!
As stated in these:

You need to fill out the issue template. This step is mandatory! Not doing so will result in your issue getting closed. Don't take this personally if this happens, and feel free to open a new issue once you've gathered all the information required by the template.
Although we might still help you without all these informations, it would be unfair to let some people post issues without filling everything.


Conversations: visits not being persisted

For some reason, visits isn't being saved to Mongo. 👎

Hm. It is being saved:
"characterData" : [ { "characterId" : "630c303ec2994d010590b8cd", "lastState" : "intro-state", "visits" : 8, "_id" : ObjectId("633c32a32d0e6c069b88f5d1") }, { "characterId" : "6310201f1be218cecb1cc639", "lastState" : "intro-state", "visits" : 1, "_id" : ObjectId("633c32a32d0e6c069b88f5d2") } ], "onSay" : { "_id" : ObjectId("633079567097830dfdd2806d"), "state" : "intro-state" },

I think think this is actually working:
Adventurer's Guild Hall of Tests
You are standing in a small hallway. The names of adventurer's line the wall in small coppper plaques, denoting those who have achieved fame or notoriety - or both - as a result of their deeds. If you so choose, you could add your name to that wall.
Exits: southwest, [north] (door)
Characters:
  Pia Kung
  Amonsul
You say, "hi pia kung"
Pia Kung says "Hello Hrothgar, it's good to see you again. If you're interested in learning more about the [guild], I can tell you more about the guild rankings. I can also tell you what [quests] are currently available."


store date of wallet creation (USD)

Description
It appears that there are no kept records of the creation date of a wallet (BTC or USD). As the BTC wallet is created at the same time as the user account (we believe), it is trivial to get this info for that wallet. However, we do not know when a user got access to the USD/stablesats feature, and thus when its USD wallet was created. Furthermore, if more currencies / saving accounts or else are later offered, it would be great to know when a user got access to it/those.
Right now, a good proxy is to use the date of the first USD transaction. It would however be valuable to know the lag between the enabling of the stablesats feature on a wallet and the first USD transaction. We think it would be interesting to know what impact enabling the USD wallet has on users' activity, for that we need to know when they had access to it.
Proposed solution

add a created_at field to wallet collection (so that it is specific to each wallet, USD, BTC, ...)
For the BTC wallets: fill in new created_at field in wallets collection with the created_at field in the users collection
Set created_at to null for users who already have a USD wallet (we will change it to first USD transaction then on our side)

will mostly be relevant when the API to add new wallet is available

@nicolasburtey i would like to work on it

@nicolasburtey Can I work on this? Could u assign me this issue?

Go ahead @vr-varad

@nicolasburtey Just for confirmation, is @galoy/core/api/src/app/wallets the place i should be working on?

any idea @nicolasburtey it would be very helpful.

Hello @nicolasburtey, That looks like quick changes, I opened a PR for it at https://github.com/GaloyMoney/galoy/pull/4270


"Something went wrong. Please try again some time." when create event

Hi team, we cannot create event after deploy the app, and prompted error "Something went wrong. Please try again some time."
Please kindly advise how can I fix the error, thanks :)

The same here !
Thanks for advise on fixing this...

Is this an intermittent issue?

Hi Madhan,
No, the issue is permanent. We still have the same problem. We also experienced the same issue on  a client installation yesterday. We replicate the issue in every installation.

The issue is not intermittent.

We replicate this issue in different environments and are unable to proceed. Please advise how to mitigate.

We replicate this issue in different environments and are unable to proceed. Please advise how to mitigate.

Having this same issue.

Hi All
Enabled Application Insights for the app under app services, everything started to work
fixed:

able to add categories
able to add events

Trying this now,

Same issue.  Tried the app insights but still getting the same.

Same, didn't fix for mine

Exact same issue here. Not able to solve with enabling Insights.

Same issue here

Anyone in this thread was successful in resolving the issue of adding new categories?

Enabled app insights and it worked!

I have redeployed numerous times, enabled insights , disabled and then re-enabled insights, but this is still not working for me ? Please share a solution to this


Add "sa" alias to make it easy to search aliases

I've had this alias in my own .zshrc for awhile to remind me of my own aliases when I can't remember.  There are many new aliases as a new convert to Prezto, and having this alias has really sped up my ability to learn all the things I get with Prezto.
Don't remember how to do a git reset --hard HEAD?    Easy!

This is pretty clever


Specify port syntax

The page should present how to specify a port other than the default to connect.
It could, for example, in the "Server name" row of the table says something like "Enter the name of the target Linux SQL Server machine or its IP address and port, in the format IP,port."

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

ID: 44db5687-5102-dea4-b7b3-f088cdf57457
Version Independent ID: b8d4cdad-8b18-2eea-415d-97f6048535af
Content: Use SSMS to Manage SQL Server on Linux - SQL Server
Content Source: docs/linux/sql-server-linux-manage-ssms.md
Product: sql
Technology: linux
GitHub Login: @VanMSFT
Microsoft Alias: vanto

@SheepRock -- thank you for your feedback.  I am looking into this article.

@VanMSFT -- please review private PR 15457.


Failing tests on Linux

Hi there! — I recently installed dockstring, however when running tests on my machine I get that several of them fail.
I have not seen this documented, and on the main branch the badge shows passing, so I thought it'd be worth bringing it up.
Also, I think some of the errors resembled the ones in this issue on OSX(#141).
Test summary info here—I added only the summaries. Happy to share the full log here :)
============================================================================================== test session starts ===============================================================================================
platform linux -- Python 3.7.10, pytest-7.2.0, pluggy-1.0.0
rootdir: /home/arctoris/dockstring, configfile: pytest.ini
collected 79 items

tests/test_benchmarks.py ..F......                                                                                [ 11%]
tests/test_dataset_matching.py .F.FFFF...FF.....F.F....                                                                                [ 41%]
tests/test_targets.py ........................FFFFF.....F.F.........                                                                                [100%]

==================================================================================================== FAILURES ====================================================================================================
...
============================================================================================= short test summary info ==============================================================================================
FAILED tests/test_benchmarks.py::TestOriginalBenchmarks::test_benchmark_values[promiscuous_PPAR-O=C1C=CC2=CC=C3C=C(Nc4cccc(C5C=c6cc7c(cc6=C5)CC=C7)c4)N=C3C12-expected_obj_parts1--11.59705] - assert False
FAILED tests/test_dataset_matching.py::test_value_matches[HSD11B1-C=1(C=CC(C[C@H](N)C(=O)N2CSCC2)=CC1)C3=C(C=C(C=C3)F)F--9.1] - assert False
FAILED tests/test_dataset_matching.py::test_value_matches[SRC-C1(=C(C(Cl)=CC(=C1)Cl)OCC(CC(CC(=O)O)O)O)C(C2=CC=C(C=C2)F)C3=CC=C(C=C3)F--9.2] - assert False
FAILED tests/test_dataset_matching.py::test_value_matches[DRD2-N(C([C@H](CCC(=O)O)NC([C@H](CC(=O)O)NC([C@H](C)NC([C@H](CC(=O)O)N)=O)=O)=O)=O)[C@H](CC1=CC=CC(C(P(=O)(O)O)(F)F)=C1)C(N[C@H](C(N)=O)CC(C)C)=O--8.9] - assert False
FAILED tests/test_dataset_matching.py::test_value_matches[ESR1-O=C1C(NC2=CC=C(N)C=C2)=C(NC(=O)CC)C(=O)C3=C1C=CC=C3--8.6] - assert False
FAILED tests/test_dataset_matching.py::test_value_matches[ADORA2A-IC1=CC(F)=C(NC2=C(C(OC3=CC=4NC(OC4C=C3)=O)=CC(F)=C2)C(=O)N)C=C1--10.5] - assert False
FAILED tests/test_dataset_matching.py::test_value_matches[AKT2-N(C)(C(C1=CNC2=CC=C(C=C21)Br)C=3C=CC(=CC3)OC)C=4C=CC=CC4--8.3] - assert False
FAILED tests/test_dataset_matching.py::test_value_matches[MMP13-BrC12CC3(CC(C1)CC(C3)C2)CC(=O)NCC4=CC=CC=C4--9.1] - assert False
FAILED tests/test_dataset_matching.py::test_value_matches[MMP13-S(=O)(=O)(N(C)C)C=1C=C(NC(=O)COC(=O)CCC2CCCCC2)C(=CC1)C--8.9] - assert False
FAILED tests/test_dataset_matching.py::test_value_matches[PGR-C(C=1C=C(N2CCOCC2)C=C(C(NC=3C=C(NC(C=4C=CC(OCC=5N=CC=CC5)=CC4)=O)C(=CC3)C)=O)C1)(F)(F)F--9.0] - assert False
FAILED tests/test_targets.py::TestDocking_Slow::test_charged[C(CCN)C[C@@H](C(=O)O)N] - assert (-4.4 is not None and False)
FAILED tests/test_targets.py::TestDocking_Slow::test_charged[NCCCC[C@H](N)C(=O)O] - assert (-4.4 is not None and False)
FAILED tests/test_targets.py::TestDocking_Slow::test_seeds[0--4.6] - assert (-4.7 is not None and False)
FAILED tests/test_targets.py::TestDocking_Slow::test_seeds[1--4.6] - assert (-4.3 is not None and False)
FAILED tests/test_targets.py::TestDocking_Slow::test_seeds[2--4.7] - assert (-4.6 is not None and False)
FAILED tests/test_targets.py::TestDocking_Slow::test_positive_score - assert (-6.6 is not None and -6.6 >= 0.0)
FAILED tests/test_targets.py::TestDocking_Slow::test_pdbqt_to_pdb_error - assert False
==================================================================================== 17 failed, 62 passed in 772.86s (0:12:52) =====================================================================================

Environment — installed from the repo's environment.yaml:
Python 3.7.10

conda list
# packages in environment at /home/arctoris/miniconda3/envs/dockstring:
#
# Name                    Version                   Build  Channel
_libgcc_mutex             0.1                 conda_forge    conda-forge
_openmp_mutex             4.5                       2_gnu    conda-forge
attrs                     22.2.0                   pypi_0    pypi
boost                     1.74.0           py37h796e4cb_5    conda-forge
boost-cpp                 1.74.0               h75c5d50_8    conda-forge
brotli                    1.0.9                h166bdaf_8    conda-forge
brotli-bin                1.0.9                h166bdaf_8    conda-forge
bzip2                     1.0.8                h7f98852_4    conda-forge
ca-certificates           2022.12.7            ha878542_0    conda-forge
cairo                     1.16.0            ha61ee94_1014    conda-forge
certifi                   2022.12.7          pyhd8ed1ab_0    conda-forge
cycler                    0.11.0             pyhd8ed1ab_0    conda-forge
dockstring                0.2.0                    pypi_0    pypi
exceptiongroup            1.1.0                    pypi_0    pypi
expat                     2.5.0                h27087fc_0    conda-forge
font-ttf-dejavu-sans-mono 2.37                 hab24e00_0    conda-forge
font-ttf-inconsolata      3.000                h77eed37_0    conda-forge
font-ttf-source-code-pro  2.038                h77eed37_0    conda-forge
font-ttf-ubuntu           0.83                 hab24e00_0    conda-forge
fontconfig                2.14.1               hc2a2eb6_0    conda-forge
fonts-conda-ecosystem     1                             0    conda-forge
fonts-conda-forge         1                             0    conda-forge
fonttools                 4.38.0           py37h540881e_0    conda-forge
freetype                  2.12.1               hca18f0e_1    conda-forge
gettext                   0.21.1               h27087fc_0    conda-forge
greenlet                  1.1.3            py37hd23a5d3_0    conda-forge
icu                       70.1                 h27087fc_0    conda-forge
importlib-metadata        4.11.4           py37h89c1867_0    conda-forge
iniconfig                 2.0.0                    pypi_0    pypi
jpeg                      9e                   h166bdaf_2    conda-forge
kiwisolver                1.4.4            py37h7cecad7_0    conda-forge
lcms2                     2.14                 h6ed2654_0    conda-forge
ld_impl_linux-64          2.39                 hcc3a1bd_1    conda-forge
lerc                      4.0.0                h27087fc_0    conda-forge
libblas                   3.9.0           16_linux64_openblas    conda-forge
libbrotlicommon           1.0.9                h166bdaf_8    conda-forge
libbrotlidec              1.0.9                h166bdaf_8    conda-forge
libbrotlienc              1.0.9                h166bdaf_8    conda-forge
libcblas                  3.9.0           16_linux64_openblas    conda-forge
libdeflate                1.14                 h166bdaf_0    conda-forge
libffi                    3.4.2                h7f98852_5    conda-forge
libgcc-ng                 12.2.0              h65d4601_19    conda-forge
libgfortran-ng            12.2.0              h69a702a_19    conda-forge
libgfortran5              12.2.0              h337968e_19    conda-forge
libglib                   2.74.1               h606061b_1    conda-forge
libgomp                   12.2.0              h65d4601_19    conda-forge
libiconv                  1.17                 h166bdaf_0    conda-forge
liblapack                 3.9.0           16_linux64_openblas    conda-forge
libnsl                    2.0.0                h7f98852_0    conda-forge
libopenblas               0.3.21          pthreads_h78a6416_3    conda-forge
libpng                    1.6.39               h753d276_0    conda-forge
libsqlite                 3.40.0               h753d276_0    conda-forge
libstdcxx-ng              12.2.0              h46fd767_19    conda-forge
libtiff                   4.4.0                h82bc61c_5    conda-forge
libuuid                   2.32.1            h7f98852_1000    conda-forge
libwebp-base              1.2.4                h166bdaf_0    conda-forge
libxcb                    1.13              h7f98852_1004    conda-forge
libxml2                   2.10.3               hca2bb57_1    conda-forge
libzlib                   1.2.13               h166bdaf_4    conda-forge
matplotlib-base           3.5.3            py37hf395dca_2    conda-forge
munkres                   1.1.4              pyh9f0ad1d_0    conda-forge
ncurses                   6.3                  h27087fc_1    conda-forge
numpy                     1.21.6           py37h976b520_0    conda-forge
openbabel                 3.1.1            py37ha011765_4    conda-forge
openjpeg                  2.5.0                h7d73246_1    conda-forge
openssl                   3.0.7                h0b41bf4_1    conda-forge
packaging                 23.0               pyhd8ed1ab_0    conda-forge
pandas                    1.3.5            py37he8f5f7f_0    conda-forge
pcre2                     10.40                hc3806b6_0    conda-forge
pillow                    9.2.0            py37h850a105_2    conda-forge
pip                       22.3.1             pyhd8ed1ab_0    conda-forge
pixman                    0.40.0               h36c2ea0_0    conda-forge
pluggy                    1.0.0                    pypi_0    pypi
pthread-stubs             0.4               h36c2ea0_1001    conda-forge
pycairo                   1.21.0           py37h0afab05_1    conda-forge
pyparsing                 3.0.9              pyhd8ed1ab_0    conda-forge
pytest                    7.2.0                    pypi_0    pypi
python                    3.7.10          hf930737_104_cpython    conda-forge
python-dateutil           2.8.2              pyhd8ed1ab_0    conda-forge
python_abi                3.7                     3_cp37m    conda-forge
pytz                      2022.7             pyhd8ed1ab_0    conda-forge
rdkit                     2021.03.3        py37haf5a968_0    conda-forge
readline                  8.1.2                h0f457ee_0    conda-forge
reportlab                 3.5.68           py37h69800bb_1    conda-forge
setuptools                59.8.0           py37h89c1867_1    conda-forge
six                       1.16.0             pyh6c4a22f_0    conda-forge
sqlalchemy                1.4.42           py37h540881e_0    conda-forge
sqlite                    3.40.0               h4ff8645_0    conda-forge
tk                        8.6.12               h27826a3_0    conda-forge
tomli                     2.0.1                    pypi_0    pypi
typing-extensions         4.4.0                hd8ed1ab_0    conda-forge
typing_extensions         4.4.0              pyha770c72_0    conda-forge
unicodedata2              14.0.0           py37h540881e_1    conda-forge
wheel                     0.38.4             pyhd8ed1ab_0    conda-forge
xorg-kbproto              1.0.7             h7f98852_1002    conda-forge
xorg-libice               1.0.10               h7f98852_0    conda-forge
xorg-libsm                1.2.3             hd9c2040_1000    conda-forge
xorg-libx11               1.7.2                h7f98852_0    conda-forge
xorg-libxau               1.0.9                h7f98852_0    conda-forge
xorg-libxdmcp             1.1.3                h7f98852_0    conda-forge
xorg-libxext              1.3.4                h7f98852_1    conda-forge
xorg-libxrender           0.9.10            h7f98852_1003    conda-forge
xorg-renderproto          0.11.1            h7f98852_1002    conda-forge
xorg-xextproto            7.3.0             h7f98852_1002    conda-forge
xorg-xproto               7.0.31            h7f98852_1007    conda-forge
xz                        5.2.6                h166bdaf_0    conda-forge
zipp                      3.11.0             pyhd8ed1ab_0    conda-forge
zlib                      1.2.13               h166bdaf_4    conda-forge
zstd                      1.5.2                h6239696_4    conda-forge

Platform:
Linux 5.15.0-57-generic #63-Ubuntu SMP Thu Nov 24 13:43:17 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Hi @niladell , thanks for your interest in dockstring! @mgarort and I tried to replicate this on two machines. On one machine (running Ubuntu 18.04 which was used to develop dockstring), and on another machine running a later version of Ubuntu we did find that some tests do not pass. We suspect that this is due to a difference in which random numbers are generated for a given random seed.
To help us figure out exactly where the problem is, would you be willing to do the following?

Re-run tests but with extra verbosity so that we can see exactly why the tests do not pass (i.e. python -m pytest -vvv tests/)
Export your environment so that we can replicate it more easily (conda env export > environment-tests-failing.yml). This might help us isolate the issue to a particular package.

We hope that this issue could be solved by pinning more specific versions of packages, but in the worst case if it is an OS issue it might just not be resolvable and we will add a warning to the package if it is not running on a supported OS.

Definitively! These are the outputs for both the tests (verbose) and the environment export.

tests_230118.log
environment-tests-failing.yaml.txt

If it's an OS problem, I wonder where the variability across comes from. Vina seems to be using a Mersenne Twister generator (boost::mt19937), but I don't know enough to be able to say whether—given a fixed seed—it should be influenced by other elements in the install/OS. Maybe it's worth checking with the developers from Vina if the bug ends up being something non-trivial.

Definitively! These are the outputs for both the tests (verbose) and the environment export.
* [tests_230118.log](https://github.com/dockstring/dockstring/files/10451849/tests_230118.log)

* [environment-tests-failing.yaml.txt](https://github.com/dockstring/dockstring/files/10451852/environment-tests-failing.yaml.txt)

If it's an OS problem, I wonder where the variability across comes from. Vina seems to be using a Mersenne Twister generator (boost::mt19937), but I don't know enough to be able to say whether—given a fixed seed—it should be influenced by other elements in the install/OS. Maybe it's worth checking with the developers from Vina if the bug ends up being something non-trivial.

Thanks for sending. We may not be able to look at this in detail until next week, but we will look at it as soon as we can.

Definitively! These are the outputs for both the tests (verbose) and the environment export.
* [tests_230118.log](https://github.com/dockstring/dockstring/files/10451849/tests_230118.log)

* [environment-tests-failing.yaml.txt](https://github.com/dockstring/dockstring/files/10451852/environment-tests-failing.yaml.txt)

If it's an OS problem, I wonder where the variability across comes from. Vina seems to be using a Mersenne Twister generator (boost::mt19937), but I don't know enough to be able to say whether—given a fixed seed—it should be influenced by other elements in the install/OS. Maybe it's worth checking with the developers from Vina if the bug ends up being something non-trivial.

Hi @niladell I installed this exact environment on another linux machine (with a different OS though) and all the tests seem to pass. I'm not sure what else to try.
If the tests don't pass then you can still use dockstring, the outputs just might not match the pre-computed dataset. You could also try using it on a virtual machine with an older linux kernel and see if that works?
@mgarort any suggestions on how to proceed with this?

Hi, for @niladell and anybody else who is interested, we looked into this but ultimately could not figure out why the scores match on some linux systems but not others. Our best guess is the random number generators from different linux versions, which is not something we can change...
Because we don't think this is fixable, instead we added a series of tests to check what fraction of docking scores don't match the dataset and by how much they deviate (this was PR #159). Our current recommendation is to run the test, and if only a small fraction of molecules do not match then you can just ignore the mismatch, otherwise unfortunately you probably need to use a different computer. However, in all cases we tried (even Mac) most deviations were small, and on all linux systems we tested we got an r^2 of approximately 0.99.


Dockerfiles

Let's all try to create dockerfiles. I'll try to create one w/ a python base but we should also try with an R base.

I can try with a R base!

Dockerfile created see #64


correlationId validation schema error when upgrading from 1.68.0 to 1.76.0

We haven't changed anything in the code, it's a dependabot provider update where we see this on all of our confluent_schema objects.
│   with module.material-tech.module.abc.confluent_schema.main["test"],
│   on modules/topic/main.tf line 144, in resource "confluent_schema" "main":
│  144: resource "confluent_schema" "main" {
│
╵
╷
│ Error: error validating Schema: error validating a schema: [{errorType:'READER_FIELD_MISSING_DEFAULT_VALUE', description:'The field 'correlationId' at path '/fields/0' in the new schema has no default value and is missing in the old schema', additionalInfo:'correlationId'} {oldSchemaVersion: 2} {oldSchema: '{"type":"record","name":"CommonFctV1Avsc","namespace":"com.bestseller.schema.materialtech.common.v1","fields":[{"name":"result","type":{"type":"string","avro.java.string":"String"}},{"name":"details","type":{"type":"array","items":{"type":"record","name":"CommonFctV1DetailAvsc","fields":[{"name":"errorCode","type":{"type":"string","avro.java.string":"String"}},{"name":"message","type":{"type":"string","avro.java.string":"String"}},{"name":"payload","type":{"type":"record","name":"CommonFctV1PayloadAvsc","fields":[{"name":"key","type":{"type":"string","avro.java.string":"String"}},{"name":"value","type":{"type":"string","avro.java.string":"String"}}]}}]}}}]}'} {validateFields: 'true', compatibility: 'BACKWARD'}]

@Andrei-Predoiu seems the issue has already been reported #378

I'm closing this one as it's a duplicate of #378.


SQS Dead letter

Hi, Is there a way to creare a dead letter que in Terraform?

yes - you would need to setup a 2nd queue to handle this and update your upstream queue's redrive_policy attribute
redrive_policy = jsonencode({
    deadLetterTargetArn = aws_sqs_queue.terraform_queue_deadletter.arn
    maxReceiveCount     = 4
  })

resource "aws_sqs_queue" "terraform_queue_deadletter" {
name = "terraform-example-queue-deadletter"
delay_seconds = 90
max_message_size = 2048
message_retention_seconds = 86400
receive_wait_time_seconds = 10
}


Improve instructions for "React 27: Use State to Toggle an Element"

The last part of the hint uses the term "fat arrow function". This should probably be changed as JS doesn't have have multiple kinds of arrow functions.
It would also simplify the instructions a tiny, tiny bit.
Refer:
-or use a fat arrow function
+or use an arrow function

Changed it to "an ES6 arrow function" — thanks!


[FEAT] after tailscale up, set_fact tailscale_ip

Is your feature request related to a problem? Please describe.
Using the tailscale ip later in a playbook run currently makes it necessary to pause/finish the play, set a variable with the tailscale ip, then resume or run another
Describe the solution you'd like
as soon as tailscale up succeeds and a tailscale ip is assigned to the device, it should be dynamically added to the ansible_facts, probably via set_fact. then it should be available in later tasks.

Great idea

How do these look to you? https://github.com/artis3n/ansible-role-tailscale/pull/464/files#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5R68

ah, you beat me to it :D
that looks very thorough and adds a bunch of other useful info.
i'm wondering about the scope of this role and adding additional features. it's a nice working unit, and feature creep is the plague.
when thinking about a unit of responsibility of an ansible role, i think i like the idea that assigning facts to a host that sort of programmatically document the outcome of a play run make a lot of sense as the final bracket of the functionality. you could so to speak pipe this output into the next play, very unix-y approach.
this is all just to make sure the additional feature  is justified, and i think your implementation is well in the boundaries of that. so: cool! and thank you for the work you are putting into all this.


docs: fixed url for licence hyperlink

Description

Closing this old PR due to inactivity. The license link has been excluded since PR-4634.


[kmac] lc_escalation signal value that is not On or Off

Hi Michael and Eunchan,
I think for other IPs, when lc_escalate_en != Off, it will trigger escalation.
But in kmac, we will trigger escalation only when lc_escalate_en == On
I believe the related code is here:
https://github.com/lowRISC/opentitan/blob/master/hw/ip/kmac/rtl/kmac.sv#L1296
Should that be:
  assign lc_escalate_en = (alerts_q[1] || (lc_escalate_en_sync == lc_ctrl_pkg::Off))
                          ? lc_ctrl_pkg::Off : lc_ctrl_pkg::On;

Other IPs:
https://github.com/lowRISC/opentitan/blob/master/hw/ip/sram_ctrl/rtl/sram_ctrl.sv#L161
Thanks @weicaiyang https://github.com/lowRISC/opentitan/pull/10810/files#r806194105 for reviewing and finding the issue.
CC @msfschaffner
Thanks,
Cindy

This has just changed slightly with #10814 landing. Now a malformed lc_escalate_en_sync will propagate. I assume we've got a well-formedness check in whatever consumes it eventually? If not, we probably should have :-D

Oh thank you for pointing that out. I did not rebase the code. Let me double check with the latest codebase.

No more error with #10814. Thanks Rupert.


Merge 6-18 updates to live

Docs Build status updates of commit e5b4520:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

api/TOC.md
:white_check_mark:Succeeded
View

api/Visio.AccelItem.md
:white_check_mark:Succeeded
View

api/Visio.AccelItems.md
:white_check_mark:Succeeded
View

api/Visio.AccelTable.md
:white_check_mark:Succeeded
View

api/Visio.AccelTables.md
:white_check_mark:Succeeded
View

api/Visio.Addon.md
:white_check_mark:Succeeded
View

api/Visio.Addons.md
:white_check_mark:Succeeded
View

api/Visio.Application.ActiveDocument.md
:white_check_mark:Succeeded
View

api/Visio.Application.ActivePage.md
:white_check_mark:Succeeded
View

api/Visio.Application.ActiveWindow.md
:white_check_mark:Succeeded
View

api/Visio.Application.BeforeDocumentClose.md
:white_check_mark:Succeeded
View

api/Visio.Application.BeginUndoScope.md
:white_check_mark:Succeeded
View

api/Visio.Application.Documents.md
:white_check_mark:Succeeded
View

api/Visio.Application.EndUndoScope.md
:white_check_mark:Succeeded
View

api/Visio.Application.SaveAsWebObject.md
:white_check_mark:Succeeded
View

api/Visio.Application.ShowChanges.md
:white_check_mark:Succeeded
View

api/Visio.Application.Window.md
:white_check_mark:Succeeded
View

api/Visio.Application.WindowActivated.md
:white_check_mark:Succeeded
View

api/Visio.Application.WindowHandle32.md
:white_check_mark:Succeeded
View

api/Visio.Application.WindowTurnedToPage.md
:white_check_mark:Succeeded
View

api/Visio.Application.md
:white_check_mark:Succeeded
View

api/Visio.ApplicationSettings.md
:white_check_mark:Succeeded
View

api/Visio.Cell.FormulaU.md
:white_check_mark:Succeeded
View

api/Visio.Cell.md
:white_check_mark:Succeeded
View

api/Visio.Characters.Begin.md
:white_check_mark:Succeeded
View

api/Visio.Characters.CharProps.md
:white_check_mark:Succeeded
View

api/Visio.Characters.End.md
:white_check_mark:Succeeded
View

api/Visio.Characters.ParaProps.md
:white_check_mark:Succeeded
View

api/Visio.Characters.Text.md
:white_check_mark:Succeeded
View

api/Visio.Characters.md
:white_check_mark:Succeeded
View

api/Visio.Color.md
:white_check_mark:Succeeded
View

api/Visio.Colors.md
:white_check_mark:Succeeded
View

api/Visio.Connect.md
:white_check_mark:Succeeded
View

api/Visio.Connects.md
:white_check_mark:Succeeded
View

api/Visio.ContainerProperties.md
:white_check_mark:Succeeded
View

api/Visio.Curve.md
:white_check_mark:Succeeded
View

api/Visio.DataColumn.md
:white_check_mark:Succeeded
View

api/Visio.DataColumns.md
:white_check_mark:Succeeded
View

api/Visio.DataConnection.md
:white_check_mark:Succeeded
View

api/Visio.DataRecordset.md
:white_check_mark:Succeeded
View

api/Visio.DataRecordsetChangedEvent.md
:white_check_mark:Succeeded
View

api/Visio.DataRecordsets.md
:white_check_mark:Succeeded
View

api/Visio.Document.Application.md
:white_check_mark:Succeeded
View

api/Visio.Document.Masters.md
:white_check_mark:Succeeded
View

api/Visio.Document.Pages.md
:white_check_mark:Succeeded
View

api/Visio.Document.PaperSize.md
:white_check_mark:Succeeded
View

api/Visio.Document.SaveAs.md
:white_check_mark:Succeeded
View

api/Visio.Document.md
:white_check_mark:Succeeded
View

api/Visio.Documents.OpenEx.md
:white_check_mark:Succeeded
View

api/Visio.Documents.md
:white_check_mark:Succeeded
View

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


Making CIF metrics usable

We recently switched from PDB > CIF with two main motivations:

store metrics (like pLDDT) without abusing b-factor, and hopefully store pairwise interaction metrics as well (PAE etc)
better compatibility with current/future software pipelines (but see #49)

We followed recommendation to use  modelcif, and specifically _ma_qa_metric, but I don't see a way to color by this field in pymol; and don't see pairwise metrics in pymol either.
I need help figuring out what's the right pipeline for users.

@aozalevsky  @brindakv  recommendations are very welcome

afaik, direct support of _ma_qa_metric is implemented in Mol* (which you already know since you're using it in your web service) and ChimeraX. In Mol* pLDDT is automatically recognized as one of the Validation attributes and colored according to pLDDT Confidence colorscheme. In ChimeraX you can color a model using the following command:
color by pLDDT_score atoms palette alphafold

where pLDDT comes from a _ma_qa_metric and _score is added later in the code as a label.
All scripts for pLDDT coloring for PyMOL rely on the  _atom_site.B_iso_or_equiv (or simply B-factors) field since it's been a common (though hacky) practice. DeepMind is also populating both _ma_qa_metric and  _atom_site.B_iso_or_equiv for backwards compatibility. Seems that you also opted for a similar strategy.
As for PyMOL, seems like only the minimal useful information from PDBx/mmCIF and  BinaryCIF is extracted.  I wonder if @JarrettSJohnson would be willing to chime in. Would be really nice to have at least per-residue (local) scores from _ma_qa_metric supported in all major visualization packages.

Showing _ma_qa_metric_local_pairwise in ChimeraX is not related to the capability added by @e-pettersen in April 2023 to show per-residue attributes from _ma_qa_metric since a residue-pair score would be handled entirely differently than a score on individual residues.  But I have used the AlphaFold PAE plot to show residue-residue distances as shown here
 https://rbvi.github.io/chimerax-recipes/rrdist/rrdist.html

That code just rewrote the distances in AlphaFold PAE JSON file format and read the file.  I could possibly try some Python code in ChimeraX that reads the _ma_qa_metric_local_pairwise table from a ModelCIF entry and show it with the AlphaFold PAE plot in ChimeraX.  Could you point me to a ModelCIF file that has that table?  The dictionary description of the table suggests it has all the information needed to display like PAE data.

@arogozhnikov @tomgoddard i took one of the examples from the Chai-1 webserver and generated a CIF file with embedded PAEs.
There are a few comments, though:

my example has only protein-protein PAEs. The reason is that models.qa_metric.LocalPairwise is defined on the per-residue level, but as @arogozhnikov pointed out, they use per-atom PAEs for ligands and non-canonical amino acids/nucleotides. I've opened the issue  https://github.com/ihmwg/python-modelcif/issues/38

there are no dictionary requirements/definitions related to the format of PAEs. Technically, a PAE matrix should be a symmetric square matrix. Still, at the moment, there are no guidelines on whether the full matrix or only the upper triangular part has to be populated. It also seems that only selected scores could populated (as in my example - i ignored protein-ligand PAEs). To continue the discussion I've created https://github.com/ihmwg/python-modelcif/issues/39

I

The ChimeraX PAE plotting for AlphaFold 2 and AlphaFold 3 assumes that the matrix rows and columns include all residues in order and for AlphaFold 3 all atoms for all non-standard residues.  I believe in AlphaFold 3 the PAE files contain residues numbers, chain ids, not sure about atom names, for each PAE row, but ChimeraX is not using those because the ChimeraX code was written for early AlphaFold 2 PAE files that had none of that information labeling the matrix rows.   Also the PAE matrix is not symmetric in AlphaFold since the PAE value is defined by aligning the row residue/atom and then giving an error for the placement of the column residue/atom, so it is by definition not symmetric.  So ChimeraX has no provision to handle just one triangle of a symmetric matrix.  All these ChimeraX PAE limitations could be fixed for ModelCIF.  My purpose in this comment is just to explain how ChimeraX PAE plotting is currently based entirely on AlphaFold (and ESMFold) PAE conventions.

First of all let me state that it is great to see the interest in properly storing the quality metrics using ModelCIF. Given my involvement in ModelCIF and ModelArchive (MA), I can hopefully provide some useful input here.

Here are two somewhat representative examples for the use of ma_qa_metric_local_pairwise in MA: ma-bak-cepc-0944, ma-dm-hisrep-003. In all cases in MA, the local pairwise scores are extracted into a separate file to keep the main ModelCIF file at a manageable size. The ModelCIF categories ma_associated_archive_file_details and ma_entry_associated_files cleanly define the location of that extra file (via item file_content == "local pairwise QA scores"). The python-modelcif library can automatically split ModelCIF files with pairwise scores when dumping them (see e.g. the code used to create the ma-dm-hisrep ModelCIF files).
In terms of providing data, mmCIF generally does not guarantee that data is provided for each atom, each residue, each residue-pair or anything else (unless it's mandatory data according to the dictionary definition). Similarly, there are no requirements on the order of the data. So ma_qa_metric_local_pairwise can definitely contain only a subset of the PAE matrix and we had such cases in ModelArchive. The two examples provided above cover both cases with ma-bak-cepc-0944 only storing inter-chain pairwise scores and ma-dm-hisrep-003 storing the full PAE matrix.
In terms of ensuring that ModelCIF files are valid (which is unfortunately not always the case with AlphaFold output), we have a validation tool based on RCSB's CifCheck tool which we highly recommend to use.
In terms of supporting ModelCIF and MA PAE data in ChimeraX I wanted to write a long time ago to suggest this as an improvement but somehow forgot to do it. My bad. I will write to<EMAIL_ADDRESS>with further info asap.
To support the new quality estimates introduced with AF3, we will need to extend ModelCIF first (as was already observed in earlier comments). I will make a suggestion for it in https://github.com/ihmwg/ModelCIF/issues. In a nutshell, I believe that it will require new allowed values in _ma_qa_metric.type and new categories for per-chain, per-chain-pair, per-atom, and per-atom-pair scores. For the latter, I am uncertain how to best handle per-residue tokens and would be happy for your input. My suggestion would be to simply only use the "token centre atom" (as in 2.6 of Supplementary information for AlphaFold 3; CA for standard amino acids, C1' for standard nucleotides) for per-residue tokens and hence only sparsely populate the per-atom-pair scores table. The alternative would require a mix of per-atom-pair and per-residue-pair data which I think would be more confusing I think.

ChimeraX plots the AlphaFold 3 PAE scores and handles its combination of residue and atom level values (one PAE value per residue for standard amino and nucleic acids, and one PAE value per atom for all other atoms).  Specifically it knows that the per-residue score is a residue score, not just a score for the C-alpha atom.  If you treat it as a C-alpha atom score you lose some knowledge about the meaning of the score.  I agree it is messy to handle though.

I made an example ChimeraX command to plot pairwise residue scores included directly in ModelCIF structure files described here
https://rbvi.github.io/chimerax-recipes/modelcif_pae/modelcif_pae.html

Yeah the "meaning of AlphaFold 3 PAE scores" is a tricky one here. In terms of what is being predicted, it relates only to the CA/C1' atoms for standard amino and nucleic acids. But: I could make the same argument about per-residue pLDDT and PAE in AF2. In terms of interpretation of the score (i.e. making it useful), I of course agree that PAE values for standard amino and nucleic acids relate to the whole residue and not just to CA/C1' atoms.
Anyway I updated my suggested update of ModelCIF (https://github.com/ihmwg/ModelCIF/issues/21) with an idea how one could represent QE metrics which are listed in separate ModelCIF tables. I.e. the same PAE metric would then have values in _ma_qa_metric_per_atom_pairwise and _ma_qa_metric_local_pairwise. From the perspective of the PAE writers and parsers this option would then also mean that data needs to be written in separate tables in separate ways for per-residue-pair and per-atom-pair PAEs.

A simple idea for making the mmCIF tables handle pairwise scores between atoms and residues is to add two atom name fields to the _ma_qa_metric_local_pairwise table
https://mmcif.wwpdb.org/dictionaries/mmcif_ma.dic/Categories/ma_qa_metric_local_pairwise.html

If the atom name was given as "." then that would mean the score applies to the whole residue, while if an atom is named e.g. "CA" then the score is associated with that atom.  This allows a pair score to be between an atom and a residue as it is done in AlphaFold 3.  I think it will be important to handle AlphaFold 3 PAE scores.  They will probably be the most heavily used pairwise scores in the next few years.

If the atom name was given as "." then that would mean the score applies to the whole residue, while if an atom is named e.g. "CA" then the score is associated with that atom. This allows a pair score to be between an atom and a residue as it is done in AlphaFold 3. I think it will be important to handle AlphaFold 3 PAE scores. They will probably be the most heavily used pairwise scores in the next few years.

we have a somewhat similar concept in ihm for crosslinks (which are also, typically, are pairwise restraints) _ihm_cross_link_restraint.model_granularity. Theoretically, similar modifiers could be applied for both ends of a restraint/score. However, maintaining the by-feature level (basically any custom selection other than standard things like an atom, full residue, or a full asym_unit) is tricky and requires multiple additional tables.

Agree with the above. Supporting AF3 PAE will be important and we need to make sure that whatever we implement can handle pairs between single atoms and full residues. I will update the suggestion in https://github.com/ihmwg/ModelCIF/issues/21 accordingly. One worry of adding more columns to ma_qa_metric_local_pairwise is that it makes it more bulky while a pure per-atom table could be linked to atom_site.id instead. Additionally the current per-residue identification would not be suitable to handle QE for water molecules (unless we deviate from PDB standards and give each water molecule a separate label_asym_id) which are relevant for physics-based docking tools.


Dribbblish(for example): how to make song timer working.

I would love to know if it possible to custom themes to show the timers of a song: (e.g)

Thank you for advance.

It's only hidden by CSS. Find their class name and search in user.css file.
You need to find a place to put them tho, it's not gonna be easy.

I am asking if it you know the class name cuz in Dribbblish's user.css isn't something like 'timer' or 'time'.

@mlunax enable and use dev-tools

Dev-tools not working here.

spicetify enable-devtool

I know, it doesn't working.


Simplified flag value access

What type of PR is this?

feature

What this PR does / why we need it:
This PR implements convenience accessors to access flag values in a context.
Instead of writing ctx.Int(f.Name) or ctx.Value(f.Name).(int) one can write f.Get(ctx).
Thus, you don’t have to use the correct type method or the appropriate type assertion. The flag picks the correct name and gives you the correct type.
Which issue(s) this PR fixes:
Fixes #1316
Special notes for your reviewer:
~I’m happy to give the accessor a shorter name if one comes up with a good idea :).~ (done! ~ @meatballhat)
Release Notes
All built-in flags now have a convenience method to access a flag’s value within a `Context`.
With `f.Get(ctx)` you don’t have to provide the flag’s name or its value’s actual type.

@toaster What do you think of claiming Get? This would be similarly as terse as flag.Getter.Get and future (v3+) versions could similarly define an interface method with return signature of any once we're beyond supporting go < 1.18.

@toaster What do you think of claiming Get? This would be similarly as terse as flag.Getter.Get ~and future (v3+) versions could similarly define an interface method with return signature of any once we're beyond supporting go < 1.18~.

I like the idea and added a respective commit.
However, I’m not deep enough into the project to assess whether this fits the API.

@dearchap when you get time, I'd appreciate your thoughts on this 🙇🏼

@meatballhat I have no problem with the new interface. This API is not within most people's workflow wherein they get the flag value from context but if users wants to use flag.GetFromContext thats fine with me.

Is there a minimal example on how to use it? On a minimal example from the docs, how could the new approach be used to access the value of the lang flag from the example below?
app := &cli.App{
    Flags: []cli.Flag{
      &cli.StringFlag{
        Name:    "lang",
        Aliases: []string{"l"},
        Value:   "english",
        Usage:   "language for the greeting",
        EnvVars: []string{"LEGACY_COMPAT_LANG", "APP_LANG", "LANG"},
      },
    },
  }

@xoxys You will need a reference to the flag in order to use this type of access. For example, to take your code and put it into an example app to show the typical way of using *cli.Context, but with a modification demonstrating the source of bugs that's alleviated via direct flag access:
package main

import (
    "log"
    "os"

    "github.com/urfave/cli/v2"
)

func main() {
    app := &cli.App{
        Flags: []cli.Flag{
            &cli.StringFlag{
                Name:    "lang",
                Aliases: []string{"l"},
                Value:   "english",
                Usage:   "language for the greeting",
                EnvVars: []string{"LEGACY_COMPAT_LANG", "APP_LANG", "LANG"},
            },
        },
        Action: func(cCtx *cli.Context) error {
            notLang := cCtx.String("1ang")
            log.Println("is this lang?:", notLang)

            lang := cCtx.String("lang")
            log.Println("is this lang?:", lang)

            return nil
        },
    }

    if err := app.Run(os.Args); err != nil {
        log.Fatal(err)
    }
}

and then modify it to use the access provided via the flag's Get method:
package main

import (
    "log"
    "os"

    "github.com/urfave/cli/v2"
)

func main() {
    langFlag := &cli.StringFlag{
        Name:    "lang",
        Aliases: []string{"l"},
        Value:   "english",
        Usage:   "language for the greeting",
        EnvVars: []string{"LEGACY_COMPAT_LANG", "APP_LANG", "LANG"},
    }

    app := &cli.App{
        Flags: []cli.Flag{langFlag},
        Action: func(cCtx *cli.Context) error {
            notLang := langFlag.Get(cCtx)
            log.Println("is this lang?:", notLang)

            lang := langFlag.Get(cCtx)
            log.Println("is this lang?:", lang)

            return nil
        },
    }

    if err := app.Run(os.Args); err != nil {
        log.Fatal(err)
    }
}

Here's the diff, if helpful:
--- a/1367.go
+++ b/1367.go
@@ -8,21 +8,21 @@
 )

 func main() {
+       langFlag := &cli.StringFlag{
+               Name:    "lang",
+               Aliases: []string{"l"},
+               Value:   "english",
+               Usage:   "language for the greeting",
+               EnvVars: []string{"LEGACY_COMPAT_LANG", "APP_LANG", "LANG"},
+       }
+
        app := &cli.App{
-               Flags: []cli.Flag{
-                       &cli.StringFlag{
-                               Name:    "lang",
-                               Aliases: []string{"l"},
-                               Value:   "english",
-                               Usage:   "language for the greeting",
-                               EnvVars: []string{"LEGACY_COMPAT_LANG", "APP_LANG", "LANG"},
-                       },
-               },
+               Flags: []cli.Flag{langFlag},
                Action: func(cCtx *cli.Context) error {
-                       notLang := cCtx.String("1ang")
+                       notLang := langFlag.Get(cCtx)
                        log.Println("is this lang?:", notLang)

-                       lang := cCtx.String("lang")
+                       lang := langFlag.Get(cCtx)
                        log.Println("is this lang?:", lang)

                        return nil

I hope this is helpful 😁

I hope this is helpful grin

That helps, thanks a lot!


Questions on if Flyway has any support for integrating with Data Catalogues tools ?

This is a question.
Were there any prior integration between Flyway and Data Catalogue tools ? We are being asked to find a mechanism to have tables created report into Data Catalogue tools like Alation so that Enterprise has insight into Data managed across all the data stores.
I am trying to see if anyone has solved this puzzle before and want to learn from them.

I'm closing this as I think StackOverflow might be more suitable for this kind of question (it will probably have more visibility as well).


TFRS - Rebase January Release Branch with Latest Release Branch

Description:
The goal of this task is to rebase the January 2024 release branch of TFRS with the latest release branch. This is needed to ensure the branch contains all the most recent features, optimizations, and bug fixes. This will enhance our ability to debug, maintain, and develop on top of the most recent and stable codebase.

Acceptance Criteria:

Ensure a full backup of the current January release branch is available before proceeding.
The January release branch is successfully rebased onto the latest release branch without any conflicts.
All the tests pass successfully after the rebase.
The rebased branch is pushed to the remote repository and a Pull Request (PR) is created for peer review.

Notes:

Please ensure all conflicts (if any) are resolved correctly and the branch integrity is maintained.
Follow the standard code rebase and conflict resolution best practices.

Nothing for PO to test


Simplify Artifacts Release

I'm eager to see if we can adopt what @fwbrasil is doing for https://github.com/traneio/arrows (and perhaps other projects). The idea of being able to trigger a release via git commit to version.sbt seems quite appealing to me.
As of now, it takes about 10 mins in total for me to cut a release (no including writing release notes) -that's like 2h/year (12 releases) that I could have spent playing with my dog or, at least, wasting my time in Overwatch.
This commit seems to enable the magic for Trane Arrows: https://github.com/traneio/arrows/commit/310b1862fbe62579af1081107540358a997e4dce

I think the benefit not only the time you save but also the fact that it enables other contributors to make releases. That's something essential to build a maintainers community that doesn't depend on you :)
Most of the changes were based on https://www.theguardian.com/info/developer-blog/2014/sep/16/shipping-from-github-to-maven-central-and-s3-using-travis-ci

@vkostyukov i've started working on this.
I will need your help when it comes to adding the encrypted GPG files required to perform the auto-release

@arron-green Glad to hear that and would be happy to assist you with anything!

I think it's done as of #1000. We'll follow up with any fixes/improvements.


XCOPA bug

@amirrezamirzaei  In task1179_xcopa_commonsense_cause_effect_th, everything is mapped to effect.

yes, I looked at the data it seems that they have been labeled incorrectly in the source database. I will try to label them correctly myself.

I see. If it's something that will take more than 30 mins, don't waste your time on it (It might be easier to drop/replace the task.)

I think we can close this issue.


docs

papier, bitte

Added documentation on branch "docs".
Added readthedocs page: https://materials.readthedocs.io/en/latest/


Refactor & deprecate OrderImportShortened class

This PR refactors the OrderImportShortened class (creating a new OrderImport class) which extract the ApiService, LookupTable, and Marc subfield methods into separtate classes.

the application is failing because an application.properties file with valid values doesn't exist.   The application requires either creating a .env or application.properties file to set up api credentials as well as other properties.   I don' t know if docker-compose can run such that it ignores unit tests, but the tests that exist are primarily fo developer debugging and not true unit tests.  There were no tests at all in the original Lehigh code and it would require a lot more refactoring to implement junit tests at this point.

I don' t know if docker-compose can run such that it ignores unit tests, but the tests that exist are primarily fo developer debugging and not true unit tests.

docker-compose is simply using the Dockerfile to build the image. We could modify the following line
https://github.com/cul-it/order-import-poc/blob/d16bc8438acefaea7c8ab0597ef32ce81522b127/Dockerfile#L7
to:
RUN mvn package -DskipTests

Long term, this is probably not the best idea, but if you're saying the existing tests have no value for ci/cd, then perhaps it's acceptable for now?

turned off junit tests in Dockerfile because they were not created for ci/cd
Added test in LookupUtil to test for .env


Ambiguous/confusing grammar syntax

In the syntax definitions for INF file entries, brackets are being used to distinguish tokens from literal strings and to designate parameters as optional.
reg-root, [subkey],[value-entry-name],[flags],[value][,[value]]

Perhaps another pair of characters can be used to enclose tokens besides brackets? Also, since leading/trailing spaces are ignored, why not use them to further improve readability?
reg-root, <subkey>, <value-entry-name>, <flags>, <value>[, <value>]
reg-root, {subkey}, {value-entry-name}, {flags}, {value}[, {value}]

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

ID: acdc91cd-c89e-684c-c48b-5d66d098fa9c
Version Independent ID: 4865d5a4-df22-1c26-f993-a661882194a7
Content: INF AddReg Directive - Windows drivers
Content Source: windows-driver-docs-pr/install/inf-addreg-directive.md
Product: windows-hardware
Technology: windows-devices
GitHub Login: @tedhudek
Microsoft Alias: tedhudek

Hi @mr-intj, square brackets always means optional in these.  The second value in your example is for multi-sz and binary ones where you may need to specify multiple values to fully describe the value.

Ah, I see. I was expecting something more like this:
reg-root[, (subkey | )[, (value-entry-name | )[, (flags | )[, (value | )[, (value | ) ...]]]]]

Thanks.


Rx for Geofire

Is there a Rx library for Geofire?
I'd like to be able to concurrently listen to my firebase data and my geofire locations. Would wrapping Geofire in Rx help or is there an alternative?

@ahaverty there is not an Rx library for GeoFire.  I think some people may find it useful for sure, but I don't think we'd ever make it part of the core library.
For that reason going to close this issue, but if you release something of your own please comment here since I'd love to see it.

Thanks @samtstern will do 👍


Refactor handling of custom relative URLs

See discussion about #65 for more details.

Coverage increased (+0.3%) to 92.216% when pulling 9111ce0df83b2f09dc58d80542ad9353f67226ad on edgarmueller:master into fd17a918ae65a9c5ce192d3d2e522f2e96c5c96e on eclipsesource:master.

Coverage increased (+0.3%) to 92.216% when pulling fb44f6e1326447609414c67edef676bba220aa11 on edgarmueller:master into fd17a918ae65a9c5ce192d3d2e522f2e96c5c96e on eclipsesource:master.

Coverage increased (+0.2%) to 92.045% when pulling e77e04c91217964bbde8ae86983a90acb423d052 on edgarmueller:master into fd17a918ae65a9c5ce192d3d2e522f2e96c5c96e on eclipsesource:master.


docs: update troubleshooting details for v3 migration

When I was migrating from Docusaurus v2 to v3 today, I ran into a React "invalid hook call" error, which was caused by two different versions of React being pulled in as dependencies. Even after deleting my node_modules directory and re-running npm install, I was still getting the issue. It turns out my package-lock.json file still had a reference to React 17 somewhere, because the issue got resolved after I tried deleting both node_modules and package-lock.json, and then re-running npm install.
I wanted to make a documentation update to the troubleshooting steps to help prevent others who run into this from getting stuck.
I also thought it would be good to rename the "Ask For Help" section here to "Troubleshooting", as I feel that name more accurately reflects the content of the section. I didn't initially read that section when I ran into trouble, because I assumed it was only about how to ask someone else for help, and I wasn't ready to do that yet.

Thanks
That seems like a reasonable change, although removing your lockfile won't always solve deduplication, and can also introduce problems in some cases.


Fix rollback context first

:tada: This PR is included in version 7.0.0-beta.15 :tada:
The release is available on:

v7.0.0-beta.15
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 7.0.0-rc.1 :tada:
The release is available on:

v7.0.0-rc.1
GitHub release

Your semantic-release bot :package::rocket:

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

v7.0.0
GitHub release

Your semantic-release bot :package::rocket:


Upgrade fails when VMSS extensions are present.

When attempting to migrate a VMSS with extensions present in the Extensions Profile of the VMSS (such as Service Fabric Node), the Json Serializer fails to serialize the extensions as they are a type of "system.object".
log : 2023-04-24T11:24:11-04 [Error]:[BackupVmss] An error occured while exporting the VMSS '' for backup purposes. Error: Exception calling "Serialize" with "3" argument(s): "The
collection type 'System.Object' on 'Microsoft.Azure.Commands.Compute.Automation.Models.PSVirtualMachineScaleSetExtension.Settings' is not supported."
At C:\Program Files\WindowsPowerShell\Modules\AzureBasicLoadBalancerUpgrade\2.0.4\modules\BackupBasicLoadBalancer\BackupBasicLoadBalancer.psm1:119 char:13

        log -Severity Error -Message $message -terminateOnError

        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,log

I manually copied the lines out of the BackupBasicLoadBalancer.psm1 file to test the serialization manually without the extensions and was able to serialize the rest of the VMSS.

$vmss = Get-AzVmss -ResourceGroupName  -VMScaleSetName
$options = [System.Text.Json.JsonSerializerOptions]::new()
$options.WriteIndented = $true
$options.IgnoreReadOnlyProperties = $true
$vmss.VirtualMachineProfile.ExtensionProfile.Extensions = $null
[System.Text.Json.JsonSerializer]::Serialize($vmss, [Microsoft.Azure.Commands.Compute.Automation.Models.PSVirtualMachineScaleSet], $options)

The Service Fabric Node Extension snippet copied from Resource Explorer (resources.azure.com):
{
"name": "ServiceFabricNode",
"properties": {
"autoUpgradeMinorVersion": true,
"publisher": "Microsoft.Azure.ServiceFabric",
"type": "ServiceFabricNode",
"typeHandlerVersion": "1.1",
"settings": {
"clusterEndpoint": "https://eastus.servicefabric.azure.com/runtime/clusters/my-guid",
"nodeTypeRef": "primary",
"dataPath": "D:\\SvcFab",
"durabilityLevel": "Bronze",
"enableParallelJobs": true,
"nicPrefixOverride": "<IP_ADDRESS>/24",
"certificate": {
"thumbprint": "my cert thumbprint",
"x509StoreName": "My"
}
}
}
}

PS C:\WINDOWS\system32> $PSVersionTable
Name                           Value

PSVersion                      5.1.22621.963
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.22621.963
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

I'll give PS Core a go.

Matthew, thank you for such a quick response. This has addressed the issue.


Unable to compile the dec-auto-home branch (git pull date: 08-10-22)

Just a FYI, unable to compile the dec-auto-home branch (git pull date: 08-10-22).
Board: MKS_GENL_V2.1
OS: Ubuntu 22.04.1 LTS
root@odroid:/home/OAT_GitHub/dec-auto-home/OpenAstroTracker-Firmware# git branch -a | head -2
*dec-auto-home
remotes/origin/Alt-Az-local-config
root@odroid:/home/OAT_GitHub/dec-auto-home# arduino-cli compile --fqbn arduino:avr:mega ./OpenAstroTracker-Firmware
/home/OAT_GitHub/dec-auto-home/OpenAstroTracker-Firmware/src/Mount.cpp: In member function 'bool Mount::isAxisRunning(StepperAxis)':
/home/OAT_GitHub/dec-auto-home/OpenAstroTracker-Firmware/src/Mount.cpp:1665:20: error: '_stepperALT' was not declared in this scope
             return _stepperALT->isRunning();
                    ^~~~~~~~~~~
/home/OAT_GitHub/dec-auto-home/OpenAstroTracker-Firmware/src/Mount.cpp:1665:20: note: suggested alternative: '_stepperRA'
             return _stepperALT->isRunning();
                    ^~~~~~~~~~~
                    _stepperRA
/home/OAT_GitHub/dec-auto-home/OpenAstroTracker-Firmware/src/Mount.cpp:1669:20: error: '_stepperAZ' was not declared in this scope
             return _stepperAZ->isRunning();
                    ^~~~~~~~~~
/home/OAT_GitHub/dec-auto-home/OpenAstroTracker-Firmware/src/Mount.cpp:1669:20: note: suggested alternative: '_stepperRA'
             return _stepperAZ->isRunning();
                    ^~~~~~~~~~
                    _stepperRA
/home/OAT_GitHub/dec-auto-home/OpenAstroTracker-Firmware/src/Mount.cpp:1673:20: error: '_stepperFocus' was not declared in this scope
             return _stepperFocus->isRunning();
                    ^~~~~~~~~~~~~
/home/OAT_GitHub/dec-auto-home/OpenAstroTracker-Firmware/src/Mount.cpp:1673:20: note: suggested alternative: '_stepperRA'
             return _stepperFocus->isRunning();
                    ^~~~~~~~~~~~~
                    _stepperRA
/home/OAT_GitHub/dec-auto-home/OpenAstroTracker-Firmware/src/Mount.cpp: In member function 'void Mount::stopSlewing(StepperAxis)':
/home/OAT_GitHub/dec-auto-home/OpenAstroTracker-Firmware/src/Mount.cpp:2285:9: error: '_stepperAZ' was not declared in this scope
         _stepperAZ->stop();
         ^~~~~~~~~~
/home/OAT_GitHub/dec-auto-home/OpenAstroTracker-Firmware/src/Mount.cpp:2285:9: note: suggested alternative: '_stepperRA'
         _stepperAZ->stop();
         ^~~~~~~~~~
         _stepperRA
/home/OAT_GitHub/dec-auto-home/OpenAstroTracker-Firmware/src/Mount.cpp:2291:9: error: '_stepperALT' was not declared in this scope
         _stepperALT->stop();
         ^~~~~~~~~~~
/home/OAT_GitHub/dec-auto-home/OpenAstroTracker-Firmware/src/Mount.cpp:2291:9: note: suggested alternative: '_stepperRA'
         _stepperALT->stop();
         ^~~~~~~~~~~
         _stepperRA
/home/OAT_GitHub/dec-auto-home/OpenAstroTracker-Firmware/src/Mount.cpp: In member function 'long int Mount::getCurrentStepperPosition(StepperAxis)':
/home/OAT_GitHub/dec-auto-home/OpenAstroTracker-Firmware/src/Mount.cpp:2363:16: error: '_stepperALT' was not declared in this scope
         return _stepperALT->currentPosition();
                ^~~~~~~~~~~
/home/OAT_GitHub/dec-auto-home/OpenAstroTracker-Firmware/src/Mount.cpp:2363:16: note: suggested alternative: '_stepperRA'
         return _stepperALT->currentPosition();
                ^~~~~~~~~~~
                _stepperRA
/home/OAT_GitHub/dec-auto-home/OpenAstroTracker-Firmware/src/Mount.cpp:2369:16: error: '_stepperAZ' was not declared in this scope
         return _stepperAZ->currentPosition();
                ^~~~~~~~~~
/home/OAT_GitHub/dec-auto-home/OpenAstroTracker-Firmware/src/Mount.cpp:2369:16: note: suggested alternative: '_stepperRA'
         return _stepperAZ->currentPosition();
                ^~~~~~~~~~
                _stepperRA

Used library   Version Path
AccelStepper   1.61    /root/Arduino/libraries/AccelStepper
TMCStepper     0.7.3   /root/Arduino/libraries/TMCStepper
SPI            1.0     /root/.arduino15/packages/arduino/hardware/avr/1.8.5/libraries/SPI
SoftwareSerial 1.0     /root/.arduino15/packages/arduino/hardware/avr/1.8.5/libraries/SoftwareSerial
LiquidCrystal  1.0.7   /root/Arduino/libraries/LiquidCrystal
EEPROM         2.0     /root/.arduino15/packages/arduino/hardware/avr/1.8.5/libraries/EEPROM

Used platform Version Path
arduino:avr   1.8.5   /root/.arduino15/packages/arduino/hardware/avr/1.8.5

Error during build: exit status 1

Yeah, these branches are for devs to work out stuff and collaborate. There is absolutely no guarantee that they will even compile, much less work correctly. Also there is no support for any of the dev branches. If you want live on the edge, you're on your own :-)