Add guest post: ribbon/catchup trick

Let me know if everything is OK with it! :-)

nags @qrush gently ;-)

I'll take a look today...been really busy, moving this weekend. Sorry :(

Hey Nick, just wanted to check if you were going to merge this -- if not, I'd go ahead post it on my own blog.
(I'm also on XMPP at<EMAIL_ADDRESS>if there's any issues to be ironed out.)

I'm really sorry, but I dropped the ball here. Just merged/deployed/etc. I'll add you as a contributor if you want to write more :)

Haha, don't worry -- thanks for merging! And thanks for adding me as a contributor. :)
Happy holidays :)


[Cloud-Masthead]: add services endpoint to determine auth status for Cloud Console - DPO Consulting

Engineering info:

Innovation Team engineer: @proeung
Innovation Team JIRA Ticket: https://jsw.ibm.com/browse/HC-2377
DPO consulting engineer: @annawen1

The problem

It was brought to our attention that the Cloud console team has completed a feature to detect and personalize based on if a person was authenticated/logged-on on via the cloud.ibm.com console.
This detection method was based on a request to personalize /cloud pages with users' live login state, which can now be accomplished.
@kjwhitla Can you let me know if this is correct from a business requirement perspective?

The solution
Steps to verify the personalization functionality:

Goto an IBM.com marketing page, like https://ibm.com/cloud
Open the developer console
type _dl.ddo.user.segment.isCloudLoggedOn (previously made a typo and omitted the _ in this command)
The console output should read true or false
Either log in or log out of cloud.ibm.com (change your state)
Reload the https://ibm.com/cloud page
Repeat step 3 and see the status updated

We’ll need to adjust our CloudAccountAuth script within the Services package of the Carbon for ibm.com.
Application/website
AEM, Drupal
Business priority
Medium Priority = upcoming release but is not pressing
What time frame would this ideally be needed by (if applicable)
The timeframe of this work has not been determined yet.
Examples
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate issues

Reopening this ticket as the solution added to this PR doesn't seem to be working on PROD. https://github.com/carbon-design-system/carbon-for-ibm-dotcom/pull/8149
PR to revert the changes - https://github.com/carbon-design-system/carbon-for-ibm-dotcom/pull/8792

@annawen1 Just wanted to revisit this issue. Do you have any recommendations on how to best test this change (see above).

@proeung Yeah, it seems so far the only way to test if it really works or not is to test in a Drupal environment. We might have to try pushing changes to canary for Drupal test pages to consume.

@annawen1 We can certainly try that, however, ideally, I'd like to get these changes tested before the PR is merged down so that we don't have to create follow-up PRs to address any issues that might pop up. I wonder if there's a way to generate a CDN reference per PR with some sort of GH label. This obviously will be a new Jenkins job I would assume.


Max character limit for authors and towns and should be 10 instead of 9.

For some reason, this is 9? My name on AC is 'Jacqueline' so I can't fit it into the author field in the pattern details.

That's because the QR codes are from ACNL (the previous, 3DS game) and that had a 9 character limit on the names. The format of the codes only has room for 9 characters; there's nothing we can do about that. :-(
It doesn't really matter, because no matter what author information you put there, ACNH will never let you edit patterns imported by QR (the game actively blocks it for imported patterns, regardless of author).


Polygon grid features shifting with --coalesce-fraction-as-needed

I'm trying to coalesce a grid of hexagons. My issue is that some of the coalesced polygons are shifting vertically. I confirmed this by checking feature ids before and after coalescing. I read in the docs that "the polygons to which nested polygons are coalesced may not necessarily be the immediately enclosing features." I'm not sure if this is what I'm observing, or if there is a way to control this. Any help is appreciated!
This is the command that resulted in the screenshots below:
tippecanoe -o file.mbtiles filenotnull.json --force --maximum-zoom=8 --coalesce-fraction-as-needed
Other things I tried:
--include=_solar_1_mean
--accumulate-attribute=_solar_1_mean:mean
--accumulate-attribute=_solar_1_mean:max
Last zoom level before coalescing occurs:

First zoom level where coalescing occurs:

Further zoomed out:

Thanks for the report. The --coalesce-fraction-as-needed coalescing coalesces features by quadkey or Hilbert curve adjacency rather than actual two-dimensional adjacency, which I think probably explains the problem you are seeing. Please try the --hilbert option, which should generally be a better approximation to actual adjacency. If that isn't enough, I can try to look into how to improve it further.

Thank you. Using --hilbert improves it significantly for my use case. Here is a before and after:


No module error

Im getting the following error while trying to run your code from src folder. I ran like python demo.py
Traceback (most recent call last):
  File "C:/Users/Downloads/Compressed/squeezeDet-master/squeezeDet-master/src/demo.py", line 23, in <module>
    from config import *
  File "C:\Users\Downloads\Compressed\squeezeDet-master\squeezeDet-master\src\config\__init__.py", line 1, in <module>
    from kitti_model_config import kitti_model_config
ImportError: No module named 'kitti_model_config'

Replace from kitti_model_config import kitti_model_config with from .kitti_model_config import kitti_model_config .
You will get some new errors similar to above and all of them can be resolved by keeping '.'

I have the same error, and i tried to add . but the python said syntax error, i use windows 8 and python 3.5 to run it. how to solve it

check the pull request, "Fix for python3"


Light Version FeatBit

Should we provide a simple arch FeatBit version, just use MongoDB in the infrastructure ?

Added this enhancement issue to FeatBit project's draft list

Added to FeatBit's project / Backlog


Move inline flag to start of regex

3.11 requires global flags at the start (bpo-47066). See https://github.com/python/cpython/issues/91222
Fixes issue #199 on python 3.11

thanks for opening the PR, I will prepare release tonight

changes was released in version 0.31.0, thanks for opening the PR!

Thanks for the super useful package and my first code contribution on GitHub!


[feat] Add Swedish translation. 🇸🇪

Started work on a Swedish translation, so far only the landing page has been translated. 🤘
Quick demo 📷

The dashboard translation is pretty big so I'll continue this work tomorrow. 👍

Finished the Swedish translation. 🎉
Might change some phrases after viewed in action but, it's good to push to production.

Lovely, thank you for the contribution!! 🎉


Figma Component to match new features

General Support Request
We need to update our figma component based off the the features in this issue #141 and this pr #142

The Figma component will not be able to have adjustable sizing for the menu due to restraints in Figma components. By default it will match the width of the dropdown. However, I can add the sizing options to the blueprint.

https://www.figma.com/file/nyXRAgG4YzZaGdIVmPwARP/Select?node-id=1313%3A1430
Added behavior specs to blueprint. @jason-capsule42 please review.


Can't find variable: __fbBatchedBridge in android release

Our app is in release mode and published on play store we are receiving a lot of crash reports mentioning:
java.lang.RuntimeException: ReferenceError: Can't find variable: __fbBatchedBridge (<unknown file>:1)
	at com.facebook.react.bridge.queue.NativeRunnable.run(Native Method)
	at android.os.Handler.handleCallback(Handler.java:739)
	at android.os.Handler.dispatchMessage(Handler.java:95)
	at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:31)
	at android.os.Looper.loop(Looper.java:158)
	at com.facebook.react.bridge.queue.MessageQueueThreadImpl$3.run(MessageQueueThreadImpl.java:187)
	at java.lang.Thread.run(Thread.java:818)

Can you please mention if we are missing something while making final build.

Run this code in your project route：
react-native bundle --platform android --entry-file index.android.js --bundle-output android/app/index.android.bundle --dev false
and then copy the file "index.android.bundle" in your project folder.
Your problem will be solved！

@Victor880829 No need to copy the file manually with this command:
react-native bundle \
   --assets-dest ./android/app/src/main/res/ \
   --entry-file ./index.android.js \
   --bundle-output ./android/app/src/main/assets/index.android.bundle \
   --platform android \
   --dev true

@sreejithr Do we need to run this command every time we build our release? Maybe this should be in the docs?

@xvalentino
No, this command is to generate bundle file in the project, but if your js files have changed you should generate the bundle file again.

@facebook-github-bot answered

Closing this issue as @christopherdro says the question asked has been answered. Please help us by asking questions on StackOverflow. StackOverflow is amazing for Q&A: it has a reputation system, voting, the ability to mark a question as answered. Because of the reputation system it is likely the community will see and answer your question there. This also helps us use the GitHub bug tracker for bugs only.


Fixup: em-dash rule

A style guide tells to use an em dash as an emphasis inside a sentence. A corresponding rule should deny the use of hyphen or en dash in these places. But, a rule in question was errorneously denying the use of hyphen or em dash.
This little fix was verified when running vale on a text using em dash.

@kprosise do you want to merge this?

I will have to update the package and the doc vale config before it takes effect, but thank you for this fix!


Emit TestStepStarted event on @BeforeAll and @AfterAll hooks

Is your feature request related to a problem? Please describe.
It look like @BeforeAll and @AfterAll hooks do not fire any events, at least I don't see it in the code explicitly.
This makes impossible to report them in third-party report systems. At least in a straightforward way, without hacking that with AspectJ.
Describe the solution you'd like
Fire TestStepStarted event as you do for all other hooks.

This came up recently when looking at BeforeAll/AfterAll hooks in cucumber-js. Because these hooks and their results aren't represented in messages, there's no way for a formatter to know what happens with them, resulting in things like the formatter saying everything went fine when in fact an AfterAll hook errored and caused the test run to fail.
I tend to agree with @mattwynne's earlier comment that these global hooks are a different beast then scenario-level ones. It would be good to have the different types of hooks represented in a consistent way in the schema, but I don't think it's worth making a breaking change for (especially now the community is building tools around this stuff). I'd vote for new GlobalHookStarted and GlobalHookFinished messages as a way to solve this.

I'd vote for new GlobalHookStarted and GlobalHookFinished messages as a way to solve this.

Sounds good to me.

I have only just parsed, and do like @mpkorstanje's suggestion earlier that:

The equivalent of a special test step for before hooks would be a special test case for before all hooks.
And a failure of a before all hook would be equivalent to failing the test run (same as with failure of a test case, worst result wins).

We could model a BeforeAll hook by creating an additional TestCase and TestStep for it in the message stream. I like this because it would keep the protocol simple and backwards-compatible. I have a niggling concern about whether the semantics would be clear enough, but it seems like it would be the least disruptive thing to try first.

I don't see that as being backwards-compatible, because TestCase requires a pickleId, which we won't have if it's a synthetic test case.

I don't see that as being backwards-compatible, because TestCase requires a pickleId, which we won't have if it's a synthetic test case.

True, I didn't spot that.


Rework landing

Rework the doc overview page to be a little more welcoming and start from the beginning instead of assuming that users know what to do with decentralized computing.
Preview: https://docs-staging-git-rework-landing-trili-tech.vercel.app/overview/

@NicNomadic Sorry, I forgot about this item. Would you please re-review? I'll fix conflicts in other PRs after this is merged.


Change torch launcher recipe & add refuel mechanic

I have a suggestion to change the 'Torch launcher' to 'Rechargeable Torch Launcher'(RTL).  With this I propose the following recipe changes, to make it more in line with vanilla: (coal or charcoal, the block doesn't matter)

Also, I propose adding a refuel mechanic to the torch, the player can add charges by craft a piece of wood, plank, stick, or (char)coal in a crafting grid with the RTL.
Here is my proposed amount of torches you get:
Stick - 1
Plank - 2
Wood - 8
(Char)coal - 8
The idea is being able to store my torch charges then a single stack of torches.  Maybe a limit of 256?  You could also make it slightly less efficient by tweaking the refuel amount, maybe removing sticks and reducing others.
I think this is a good idea, let me know.

Yeah a refuel would make sense.  Have it not completely break at zero and add some reload mechanic.

its not exactly as you imagined it, but it is repairable in an anvil https://minecraft.curseforge.com/projects/cyclic/files/2457419


Traffic Light FSM

RTL_Schematic and Design Program (No Simulation Program in this commit) for Traffic Light with Cow on Farm Road Mealy FSM

!bounty 600


don't break journaling if CREATED exists at file level #383

The existence of a CREATED entry in the file-level property drawer causes
=org-journal-new-entry= to fail. Ignore all file-level properties when
searching through the file for the correct timestamp to start a new entry.

Wonderful! Thank you!
Could you restrict the pull request to just the code changes and remove the whitespace changes, please?

Sorry, lost this in my email. Didn't mean to do any reformatting. New PR coming.


[webapi] Sync 2dtransforms tests to latest W3C

Impacted TCs num(approved): New 0, Update 2, Delete 0
Unit test Platform: Crosswalk Project for Android 16.44.396.0
Unit test result summary: Pass 2, Fail 0, Blocked 0
BUG=https://crosswalk-project.org/jira/browse/XWALK-4566
BUG=https://crosswalk-project.org/jira/browse/XWALK-4567

Thank, please also apply to Crosswalk 15 branch.


[BEAM-434] Control the number of output shards in the Direct Runner

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[ ] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[ ] Make sure tests pass via mvn clean verify. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).
[ ] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[ ] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

Add a Write Override Factory that limits the number of shards is
unspecified. This ensures that we will not write an output file per-key
due to bundling.

R: @dhalperi
CC: @amitsela @francesperry

This particlar change seems to break Spark.

I'll take a look

@tgroh checkout https://github.com/tgroh/incubator-beam/pull/1, hope this works..

While this fix solves the problem, I'm wondering about this solution.. Is it OK to have the default sharding of the direct runner random (within range) ? to the best of my knowledge, sharding is related to the nature (and volume)  of the data, so for a word count example of 2 words, you might end-up having 7 output files...
I guess this depends on how we see the DirectRunner, if it's for examples and testing, it's fair enough, but if it's also an out-of-the-box in-memory runner to get started with (until your business grows, and you actually start having Big Data) I'm not sure that's a good fit.
WDYT ?

I've added a Dynamic Sharding override instead of the random number of fixed shards. This uses the log base 10 of the number of records to determine the number of shards, with a minimum of three shards (with the exception of 1 or 2 records).

LGTM, but can you rebase in order to set the commit message you want? I'm not sure the right way to squash.

Done
On Mon, Jul 18, 2016 at 10:00 AM, Daniel Halperin<EMAIL_ADDRESS>wrote:

LGTM, but can you rebase in order to set the commit message you want? I'm
not sure the right way to squash.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-beam/pull/651#issuecomment-233390564,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAaPKm_xmTglLB3g-g2dBJza9aYNPHKrks5qW7EigaJpZM4JL9tR
.

Does not build:
ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:testCompile (default-testCompile) on project beam-runners-direct-java: Compilation failure: Compilation failure:
[ERROR] /Users/travis/build/apache/incubator-beam/runners/direct-java/src/test/java/org/apache/beam/runners/direct/WriteWithShardingFactoryTest.java:[147,66] incompatible types
[ERROR] required: org.apache.beam.sdk.transforms.DoFnTester<java.lang.String,org.apache.beam.sdk.values.KV<java.lang.Long,java.lang.String>>
[ERROR] found:    org.apache.beam.sdk.transforms.DoFnTester<java.lang.String,org.apache.beam.sdk.values.KV<java.lang.Integer,java.lang.String>>
[ERROR] /Users/travis/build/apache/incubator-beam/runners/direct-java/src/test/java/org/apache/beam/runners/direct/WriteWithShardingFactoryTest.java:[162,66] incompatible types
[ERROR] required: org.apache.beam.sdk.transforms.DoFnTester<java.lang.String,org.apache.beam.sdk.values.KV<java.lang.Long,java.lang.String>>
[ERROR] found:    org.apache.beam.sdk.transforms.DoFnTester<java.lang.String,org.apache.beam.sdk.values.KV<java.lang.Integer,java.lang.String>>
[ERROR] /Users/travis/build/apache/incubator-beam/runners/direct-java/src/test/java/org/apache/beam/runners/direct/WriteWithShardingFactoryTest.java:[180,66] incompatible types
[ERROR] required: org.apache.beam.sdk.transforms.DoFnTester<java.lang.String,org.apache.beam.sdk.values.KV<java.lang.Long,java.lang.String>>
[ERROR] found:    org.apache.beam.sdk.transforms.DoFnTester<java.lang.String,org.apache.beam.sdk.values.KV<java.lang.Integer,java.lang.String>>
[ERROR] /Users/travis/build/apache/incubator-beam/runners/direct-java/src/test/java/org/apache/beam/runners/direct/WriteWithShardingFactoryTest.java:[204,66] incompatible types
[ERROR] required: org.apache.beam.sdk.transforms.DoFnTester<java.lang.String,org.apache.beam.sdk.values.KV<java.lang.Long,java.lang.String>>
[ERROR] found:    org.apache.beam.sdk.transforms.DoFnTester<java.lang.String,org.apache.beam.sdk.values.KV<java.lang.Integer,java.lang.String>>
[ERROR] -> [Help 1]

Since the build is currently broken, may be worth waiting for Luke's fix to get in and then rebase/fix.

I believe that the previous build failure is flakiness due to a TOCTU bug in FileIOChannelFactory#create - namely, we check to see if a directory exists and then if not call mkdirs, and fail if the mkdirs returns false; however, if the directory has been created between the two calls, mkdirs returns false but the file exists.
I've added a second check to ensure that we don't fail improperly.

LGTM


Adjust update strategy for nnf-dm worker pods

From @behlendorf:

It took a significant amount of time for it to kill and restart all the pods when I added in the merced filesystem since it ran through it sequentially.  Thankfully that's a one time thing, but it seems it will make redeploying slow.

When you add/remove a lustrefilesystem resource, the nnf-dm-manager-controller sees that and then adds/removes a Volume and VolumeMount to the nnf-dm-worker DaemonSet.  Kubernetes then handles it from there and restarts the nnf-dm-worker pods on each rabbit to mount/umount that filesystem change. The DaemonSet defines this for the updateStrategy:
 updateStrategy:
    rollingUpdate:
      maxSurge: 0
      maxUnavailable: 1
    type: RollingUpdate

That maxUnavailable: 1 is what is causing the sequential behavior. We'll need to tweak this.

@behlendorf, I'm making changes to set this to a sane default for our 3 daemonsets:

nnf-dm-worker
lustre-csi-node
nnf-node-manager

maxUnavailable can be set to a number of nodes/pods or a percentage. Setting it to 100% would cause it to attempt a restart on all the nodes at the same time, 50% would do half, 25% a quarter, etc. Do you have a preference on what percentage (or hard number) should be?
This value will be adjustable for each system.

@bdevcich as an initial swag how about 25%.  This seems like it may be a reasonable compromise between propagating the changes rapidly and potentially overwhelming the system / container repository / other.  Then we can tune on a per system basis, and revisit the default as needed.

@bdevcich as an initial swag how about 25%. This seems like it may be a reasonable compromise between propagating the changes rapidly and potentially overwhelming the system / container repository / other. Then we can tune on a per system basis, and revisit the default as needed.

Perfect, that's the percentage that I've been playing around with in my testing.

PRs here to default these all to 25%:

https://github.com/HewlettPackard/lustre-csi-driver/pull/62
https://github.com/NearNodeFlash/nnf-sos/pull/262
https://github.com/NearNodeFlash/nnf-dm/pull/155

For nnf-dm, the NnfDataMovementManager resource is edited rather than the DaemonSet directly. The manager is responsibe for managing the DaemonSet.

@behlendorf I am comfortable closing this issue after we implemented this manually today on El Cap. Do you agree?

Yup, things are looking much better after these changes.


Dco draft

- What this PR does and why is it needed

- Special notes for reviewers

- How to verify it

- Description for the changelog

/retest


GIDSignIn.sharedInstance.signIn does not return a callback sometimes

Describe the bug
The issue is, the GIDSignIn.sharedInstance.signIn method does not return a callback sometimes. This bug is a very inconsistent to reproduce. But here are the steps:
To Reproduce
Steps to reproduce the behavior:

Call the signIn method in swift code like so:

GIDSignIn.sharedInstance.signIn(
    with: configuration,
    presenting: rootViewController,
    hint: nil,
    additionalScopes: ["https://www.googleapis.com/auth/gmail.readonly"]
) { result, error in
    // Inside the closure
}

Observe that closure (callback) never gets executed sometimes, but the google sign in sheet is dismissed.

Usually, this occurs the first time during an app-run and the second time, it works as expected. As a result, the implementation has been flaky in our application, leading to users having to sign-in twice each time (most of the times, since it occurs randomly, there are times when the first sign in attempt works as expected)
Expected behavior
The GIDSignIn.sharedInstance.signIn method to work properly and execute the callback consistently, even if there is some error.
Screenshots
N/A
Environment

Device: On several iOS devices, was able to reproduce on iPhone 14 pro, iPhone 13 pro max and iPhone XR.
OS: iOS 17.3.1 (but also on different versions of iOS 17)
Browser: N/A

Additional context
Seems like this has already been mentioned here: https://github.com/google/GoogleSignIn-iOS/issues/360 but without much context. I have added enough context, hoping to help debug this better.

Hi @doctorsaway this isn't reproducible on our end. Please take a look at our example apps to see how you might use this functionality. If there is something that is different, or something that you believe we can address, please reply with more exact reproduction steps (for example, providing context on how your call to -[GIDSignIn signIn...] is made would be helpful).

@mdmathias
We are experiencing the same thing, except that it is not intermittent has overnight stopped working altogether.
We've had no change to the same code that was working yesterday, but suddenly today there is no callback firing anymore.
Neither the success nor Cancel scenarios fire the callback anymore.
NOTE: We tried both async and callback APIs and neither are continuing past the initial invocation.
Invocation code:
func initiateGoogleAuth_async() async throws -> User {
	do {
		let result:GIDSignInResult = try await GIDSignIn.sharedInstance.signIn( withPresenting: self )

		// authenticate
		let user:User = try await self.accountService.authenticate( googleUser: result.user ) //  <--- never gets here

	} catch let error {
		print( "ERROR: \(error)" ) // <--- never gets here
		...
	}
}

func initiateGoogleAuth_callback( onSuccess:@escaping(User) -> (), onError:@escaping(any Error) -> () ){
	GIDSignIn.sharedInstance.signIn( withPresenting: self ){ (result:GIDSignInResult?, error:(any Error)?) in
		guard let result else {
			print( "ERROR: \(error)" ) // <--- never gets here
			...
			return
		}

		// authenticate
		let user:User = try await self.accountService.authenticate( googleUser: result.user ) //  <--- never gets here
	}
}

Could this have anything to do with some security/configuration for the project not being correctly set?

UPDATE: The callbacks started working again after over an hour of observed downtime.
This is quite concerning as it seems there might be Google back-end issues that the library is not handling. If there are errors they should be surfaced up through the error callback not swallowed and app left in an undetermined state (ie: neither succeeded or failed)
ASK: Could the team investigate if any back-end issues were experienced on Apr 11, 2014 prior to 3:30pm UTC (time of my prior post). By 5pm UTC the callbacks started resuming again.
Please keep us posted on this as it is a total blocker to user sign-up / acquisition if this happens intermittently, and we'd like to understand how pervasive this is (ie: % of SLA to expect)

Chased this further down and it seems that within GIDSignIn::addCompletionCallback(..) (line 859) the self->_currentOptions.completion line fails the nil check (in fact _currentOptions itself if nil), so it somehow loses reference to the callback passed into the initial SDK by the time the full auth sequence finishes.

I've confirmed there are no underlying errors and the actual user object is successfully fetched as can be seen in the screenshot above.
Happy to schedule a call and walk the team through any debugging needed to reproduce this on your guys end.

Hi @marchy. Thanks for the posts and your analysis. Sorry that you're having trouble.
First, let me confirm that I understand your issue. From what I gather, it seems like you're experiencing a kind of race condition due to simultaneous calls to restorePreviousSignIn() and signIn(), where the restore call is setting _currentOptions to nil prior to the sign in call's use of _currentOptions.completion to add the completion callback. Therefore, the sign in flow in your app will occasionally not issue a callback due to this race condition. Seems like this line would not pass in this scenario, which would lead to no callback. Is that right?
If my understanding is correct, then it is unfortunately an error to simultaneously call signIn() and restorePreviousSignIn(). From the library's point of view, it doesn't make sense to restore and sign in at the same time.
Even if we made changes to GSI to protect against this error [1], apps would still have to implement some logic to choose which response to handle. For example, which response is the truth? The sign in or the restore? The completions will not have the same information.
The practical solution on your end is to make sure that you are signing in and restoring at different points in your app's lifecycle. Ultimately, it's up to apps to manage this. You can take a look at our Swift sample and ObjC sample for inspiration.
[1] I haven't fully thought through the feasibility of your request, but I believe it may require significant refactoring of the library. We'd have to (potentially re-) consider GIDSignIn's singleton status, manage multiple async callback queues on behalf of clients wishing to issue simultaneous and duplicative requests, etc. While I can see ways that this would be useful to callers like yourself (given the scenario you outline above), I have to admit that this sort of change is not feasible at the moment. Of course, since the repo is open source, if you believe you have a simple fix to resolve this, then please send us a PR and we would love to review it!

Hi @mdmathias
I have the same issue and I didn't simultaneously call signIn() and restorePreviousSignIn(). I call signIn() only after restorePreviousSignIn() doesn't succeed, not in parallel, but the callback from signIn() is never called. I use v. 8.0

If anyone needs a workaround for this issue for v.8.0 SDK, you can use this. Works like a charm for me.
It essentially monitors Google Auth controller disappearing. You don't get the error, but you can get the fact that it was presented and dismissed and check the currentUser after the dismissal is complete.
Also, you can make the completion be called only only once by putting it into a separate optional property and making it nil after the first call. But for my use case it's not needed.
    private weak var presentingController: UIViewController?
    private var dismissalTimer: Timer?
    private var googleAuthWasPresented = false

    private func signInAndRequestCalendarPermission(presenting: UIViewController, completion: @escaping (GIDGoogleUser?, Error?) -> Void) {
        let scopes = [kGTLRAuthScopeCalendar]

        // It's a workaround, because signIn() doesn't return a callback in most cases
        self.presentingController = presenting
        startMonitoringDismissal(completion: completion)

        GIDSignIn.sharedInstance.signIn(withPresenting: presenting,
                                        hint: nil,
                                        additionalScopes: scopes) { result, error in
            completion(result?.user, error)
        }
    }

    private func startMonitoringDismissal(completion: @escaping (GIDGoogleUser?, Error?) -> Void) {
        dismissalTimer?.invalidate()
        dismissalTimer = Timer.scheduledTimer(withTimeInterval: 0.1,
                                              repeats: true) { [weak self] _ in
            guard let self = self else { return }

            if self.presentingController?.presentedViewController != nil {
                self.googleAuthWasPresented = true
            } else if self.googleAuthWasPresented {
                print("Presented view controller has been dismissed.")
                completion(GIDSignIn.sharedInstance.currentUser, nil)

                self.googleAuthWasPresented = false
                self.presentingController = nil
                self.dismissalTimer?.invalidate()
                self.dismissalTimer = nil
            }
        }
    }


rad app delete should cleanup resources in case of app deployment failure

Description
We do not track the outputResources in the event of deplyment failure, but might have created some, potentially with errors.
If the deployment of outResource errors, we should still be able to cleanup these gracefully using rad app delete command.
Type of change

This pull request fixes a bug in Radius and has an approved issue (issue link required).

Fixes: #7052

changing to draft status since this is going through a design discussion for API change.

closing due to low priority of issue


How to download the Electron Microscopy Dataset dataset to run the "227_mito_segm_using_models_from_Keras_Unet_collection.py"?"

I followed the clip and "227_mito_segm_using_models_from_Keras_Unet_collection.py"
We must to have data in images folder and masks folder:

And, I download the data at the link (https://www.epfl.ch/labs/cvlab/data/data-em/). But I only can open it with Fiji software, not have the masks folder and images folder.

I downloaded and had, as following:

Please help me have the data to run the file. Thank you @bnsreenu .

Did you solve it?


Problem with using sum on timespan

I just upgrade to EF 3 and one of my queries that used to work, gives an exception now
 ProductionRecords = _context.ProductionRecords
          .Where(r => r.DataCriacao.Date == DateTime.Now.Date)
            .Select(pr => new ProductionRecordViewModel
            {
                Id = pr.Id,
                Operador = pr.Operador,
                DataCriacao = pr.DataCriacao,
                Celula = pr.Celula.Name,
                Turno = pr.Turno.Name,
                TotalPecasSemDefeito = pr.ReferenceRecords.Sum(c => c.Quantity),
                TotalPecasComDefeito = pr.DefectRecords.Sum(c => c.Quantidade),
                TotalTempoParado = pr.StopRecords.Sum(c => Convert.ToInt32(c.Duration.TotalMinutes)),
            })
          .AsNoTracking()
          .ToList();

One of the solutions was to add AsEnumerable before select but that will reduce performance a lot. How can i return the sum of timespan minutes without evaluating on client side?

@jfcaldeira - Can you also post error message & stack trace and your model classes?

@jfcaldeira - Can you also post error message & stack trace and your model classes?

Hi i have edited with the error message and the models

Looking into this. I want to write a test that essentially just reproduces this bug so that we can make sure it stays fixed. I believe that to reproduce we just need to try to sum TimeSpan.totalMinutes values of a nested collection on an entity, and make sure this returns the correct result. I'm new to the codebase and am having trouble locating where such a test would fit in the test code. I was looking into the BuiltinDataTypesTestBase class, but this class seems to only have implementations relevant to Cosmos and SqlServer. However, I have confirmed this bug is happening in Sqlite as well. Any help would be greatly appreciated!


fix!(command-parser/arguments): lifetime issue

Could you write a little bit about what this fixes?

It ties the lifetime to Arguments: thus this could will now work: (previously arg would not live long enough)
enum Command<'a> {
    Info,
    Prefix(Option<&'a str>),
}

fn command_type<'a>(cmd: Command<'a>) -> Option<Command<'a>> {
    use Command::*;
    let arg = Some(cmd.arguments.as_str()).filter(|x| !x.is_empty());
    Some(match cmd.name {
        "info" => Info,
        "prefix" => Prefix(arg),
        _ => return None,
    })
}

Thanks


fix(FX-3586): Keep recent searches if log in to the same account

The type of this PR is: Bugfix
This PR resolves FX-3586
Description
Currently if user is logged out and back into the app they can't see their recent searches.
This PR keeps recent searches in async storage after log out and only removes them if previous user and newly logged in one are not the same.
PR Checklist (tick all before merging)

[ ] I have included screenshots or videos to illustrate my changes, or I have not changed anything that impacts the UI.
[ ] I have tested my changes on iOS and Android.
[ ] I have added tests/stories for my changes, or my changes don't require testing/stories, or I have included a link to a separate Jira ticket covering the tests.
[ ] I have added a feature flag, or my changes don't require a feature flag. (How do I add one?)
[ ] I have documented any follow-up work that this PR will require, or it does not require any.
[ ] I have added an app state migration, or my changes do not require one. (What are migrations?)
[ ] I have added a changelog entry below or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

keep recent searches after log out - anastasiapyzhik

This PR contains the following changes:

Cross-platform user-facing changes (keep recent searches after log out - anastasiapyzhik)

  Generated by :no_entry_sign: dangerJS against c7c13f320a91e94a44657329fd75f0fd795848d8

Sorry for the late review, this looks good to me


Update description of lab 5.

Fixed two typo's. I've merged the PR, because more and more students want to get started with lab 5.


tls: reject certificate without either a subject CN or altnames

Description:
A server certificate must have either a subject CN or supported subject
alternative names. Certificates that have neither are a configuration
error, not an assertion, so check for this condition and throw an
exception rather than asserting.
Fix up the TLS certificate assertions to log the last libcrypto error
when we do actually assert, so that we can have get hint as to the
underlying problem. Add release assertion messages to describe other
assertion cases.
Risk Level: Low
Testing: Unit tests
Docs Changes: None
Release Notes: None
Fixes: #9182

As per Slack discussion, this should be 3 PRs:
(1) reject certificate without SAN or Subject
(2) lastCryptoError
(3) SessionContextID refactor


[Bug] Install-PSResource fails in Windows Powershell 5.1

https://github.com/PowerShell/PowerShellGet/blob/98aadd21b741c69ad782c6438663b18a309ff9e3/src/InstallPSResource.cs#L304
This type is supposed to shim to the mscorlib version, but doesn't. I suspect it's because Powershell isn't running on net framework 4.6.1+ and you're using net standard 2.0?
$psversiontable

Name                           Value
----                           -----
PSVersion                      5.1.19041.1
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.19041.1
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

install-psresource pester -Prerelease -Reinstall -Scope CurrentUser
install-psresource : Could not load file or assembly 'System.Security.Principal.Windows, Version=<IP_ADDRESS>,
Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file
specified.
At line:1 char:1
+ install-psresource pester -Prerelease -Reinstall -Scope CurrentUser
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Install-PSResource], FileNotFoundException
    + FullyQualifiedErrorId : System.IO.FileNotFoundException,Microsoft.PowerShell.PowerShellGet.Cmdlets.InstallPSRes
   ource

[system.security.principal.windowsidentity].assembly

GAC    Version        Location
---    -------        --------
True   v4.0.30319     C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscorlib.dll

Testing Notes: If you target net472 instead of netstandard2.0 it works fine on both pwsh and powershell

This should be resolved now.


[Issue] Picture-in-Picture doesn't stay on top

Picture-in-Picture is a Chrome browser extension that allows you to watch videos in a floating window (always on top of other windows) so you can keep an eye on what you’re watching while interacting with other sites, or applications.
Issue: currently Minecraft covers it if it's in fullscreen and this mod doesn't fix it, I found that Bordless gaming software solves it but that requires to be ran every single time.

This mod is just supposed to remove the Border of the normal windowed client and not to be a borderless full screen window, you could try Borderless Mining for this application type.


Introduce a class to represent a local VCS working directory

Previously, the call to fromDirectory() and e.g. to a succeeding call to
getRemoteUrl() both needed to get the workingDir passed. With the
intermediate WorkingDirectory class this is not needed anymore as it
stores the workingDir internally.

This change is

Reviewed 11 of 11 files at r1.
Review status: all files reviewed at latest revision, 3 unresolved discussions.

analyzer/src/main/kotlin/managers/Maven.kt, line 128 at r1 (raw file):

                        vcsDir?.getRemoteUrl() ?: "",
                        vcsDir?.getRevision() ?: ""
                )

Could use let:
VersionControlSystem.fromDirectory(projectDir).let {
VcsInfo(...)
}

downloader/src/main/kotlin/VersionControlSystem.kt, line 52 at r1 (raw file):

         * Return the applicable VCS for the given [vcsDirectory], or null if none is applicable.
         */
        fun fromDirectory(vcsDirectory: File) =

Somewhat unrelated to this change, but to me "forDirectory" sounds better, especially for the way it is used now in the files above.

downloader/src/main/kotlin/vcs/Git.kt, line 52 at r1 (raw file):

                    val rootDir = File(revParse.stdout().trimEnd())

                    revParse = runGitCommand(rootDir, "-C", controlledPath.absolutePath, "rev-parse", "--show-prefix")

Can't we just use workingDir instead of rootDir? It seems to always return the same result, no matter in what subfolder of rootDir I am.

Comments from Reviewable

Review status: all files reviewed at latest revision, 3 unresolved discussions, some commit checks failed.

analyzer/src/main/kotlin/managers/Maven.kt, line 128 at r1 (raw file):
Previously, mnonnenmacher (Martin Nonnenmacher) wrote…
Could use let:
VersionControlSystem.fromDirectory(projectDir).let {
VcsInfo(...)
}

Done.

downloader/src/main/kotlin/VersionControlSystem.kt, line 52 at r1 (raw file):
Previously, mnonnenmacher (Martin Nonnenmacher) wrote…
Somewhat unrelated to this change, but to me "forDirectory" sounds better, especially for the way it is used now in the files above.

I'll do this in a follow-up commit then, also for the related functions.

downloader/src/main/kotlin/vcs/Git.kt, line 52 at r1 (raw file):
Previously, mnonnenmacher (Martin Nonnenmacher) wrote…
Can't we just use workingDir instead of rootDir? It seems to always return the same result, no matter in what subfolder of rootDir I am.

The idea was to support cases where the workingDir that was passed to create the WorkingDir is not the VCS root directory. I should have separated this change out, and will do so now.

Comments from Reviewable

Reviewed 4 of 4 files at r2, 10 of 10 files at r3, 2 of 2 files at r4.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


[Docs] documentation on deployment via gcloud #317

#317 [Docs] documentation on deployment via gcloud.

Thanks so much for this, @Wahaj26 !


Find typos and fix them

here is a fun (some may say boring) issue :) find the typos in the repository and fix them! (I know one at leat! if interested, ask for hints)

hi @j-soule
sure, feel free to open a PR with any typos you spot


changed defaults to 4/4 in schedule.py and hyperparameters_config.py

Thanks @katherinethai! Could you also change the default datasets for lit_analysis_left and lit_analysis_right to be 4/0 and 0/4 respectively?

@martiansideofthemoon Changed!


Just export a file with it's real name please...

I would like to export files as they are named. If I have a file named "octopus.do/sitemap/pricing" just WHY it is exported as "octopus.do_sitemap_pricing"?
Between Figma creating subfolder and this pluging doing also something strange, it is not possible to just export a file the way it should ? 😠

Hello. @Demandrel Thank you for the issue!
This problem appears to have occurred in the logic of replacing characters prohibited on Android and iOS when using the "Variant" function in a Figma project merged through a previous PR(#2).
To resolve this issue, we are planning to provide an option to replace the text, but this may take some time.
If you want a quick solution, you can run the plugin locally and disable only the function. (Refer to issue#7 branch)


Valid access token, but every call throws invalid access token

I have been encountering a very weird situation where every call throws an invalid access token exception. I have double-checked the call manually (both with an outgoing sniffer and Postman calls) and it returns expected results.
This has been causing my error log to grow insanely fast. This is the relevant section from the logs:
[2016-05-04 19:08:22] 2020filmproject.ERROR: Larabros\Elogram\Exceptions\OAuthAccessTokenException: The access_token provided is invalid. in /var/www/filmproject/vendor/larabros/elogram/src/Http/Clients/AbstractAdapter.php:69

Stack trace:
#0 /var/www/filmproject/vendor/larabros/elogram/src/Http/Clients/GuzzleAdapter.php(49): Larabros\Elogram\Http\Clients\AbstractAdapter->resolveExceptionClass(Object(GuzzleHttp\Exception\ClientException))
#1 /var/www/filmproject/vendor/larabros/elogram/src/Repositories/UsersRepository.php(53): Larabros\Elogram\Http\Clients\GuzzleAdapter->request('GET', 'users/self/medi...', Array)
#2 /var/www/filmproject/app/Helpers/Gatherer/InstagramGatherer.php(88): Larabros\Elogram\Repositories\UsersRepository->getMedia('self', 50)

Is it possible your access token has expired?

This issue is indeed occurring even with a brand new access token attained by authorization.

Thanks for the reply, I'll look into it later tonight :)

Just a quick update - when I am running a console command, the call always succeeds on the first try and subsequently always fails (basically refreshing the feed/search) in the same process. Restarting the command always results in the same issue.

Would it be possible to some sort of a code sample? I'm not having much luck reproducing...

Actually, I am encountering some more problems with this.
Imagine a scenario where I am running calls for multiple users in a single script, each using the user's access_token stored in a database after they gave authorization to the app.
Here is a very simplistic snippet from my console command. I believe I have narrowed down the cause to be in $client->setAccessToken($access_token);.
$client = new Client(env('INSTAGRAM_CLIENT_ID'), env('INSTAGRAM_CLIENT_SECRET'));

for ($i = 0; $i < 5; $i++) {
    $this->info('Running count ' . $i);

    $access_token = new AccessToken(['access_token' => '{ "access_token": "' . $user_access_token . '" }']);
    $client->setAccessToken($access_token);
    $result = $client->tags()->getRecentMedia('nike');

    $this->info(' - ' . count($result->get()->all()) . ' results to process.');

    sleep(2);
}

If we intercept and print the access_token in AuthMiddleware, this is the result:
> php artisan marsd:sample --token="___replaced___"
Running count 0
Access Token: ___replaced___
 - 20 results to process.

Running count 1
Access Token: { "access_token": "{ "access_token": "___replaced___" }" }

  [Larabros\Elogram\Exceptions\OAuthAccessTokenException]
  The access_token provided is invalid.

I have found a solution to this in the meantime, that is to declare a new Client with an access_token everytime in the constructor like so:
$access_token = new AccessToken(['access_token' => '{ "access_token": "' . $user->instagram_access_token . '" }']);
$client       = new Client(env('INSTAGRAM_CLIENT_ID'), env('INSTAGRAM_CLIENT_SECRET'), $access_token);

I'm not sure if this issue is worth exploring further, but this could be a nice-to-know for other users who may have similar use cases.

Thank you so much for your detailed reply, using multiple access tokens was never something I actually got round to testing. I agree with your assessment of setAccessToken(), I'll try and take a look at it today (sorry, never got time yesterday)

I've just tagged 1.2.2 which should solve the issue, please let me know if it hasn't.

Any luck, @marsd?

I'm facing the same problem and the last version has not solved the problem for me.
Any other ideas? I've seen the suggestion of using the access token wrapped of a JSON, but that did not work to me aswell.
Thanks


Load balancing simulation and visualization

It is often challenging to fully grok the interaction of Envoy's sophisticated load balancing schemes, priorities, localities, failover, overprovisioning, health, panic mode, etc. We have some documentation describing this at https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/upstream/load_balancing/load_balancing, but there is still a significant gap between this and truly understanding e2e the resulting LB behavior from a given configuration.
I think some tooling here would be quite amazing. Two ideas:

A CLI tool that takes a Cluster configuration, as well as endpoint health and registration status (e.g. in a ClusterLoadAssignment) and produces a distribution of expected traffic across endpoints.

A web UX similar to (1) that allows the visual construction of the LB topology and other inputs. This would then be able to use some sort of visual representation of load distributions across hosts (even just proportionally sized circles would be neat as a starting point). As a bonus, the real Envoy LB implementation could be used in the browser via WebAsm and fakes/mocks.

This is not high priority but would be an amazing documentation and user education feature for someone with the right skillset for (1) and (2).

A CLI tool that takes a Cluster configuration, as well as endpoint health and registration status (e.g. in a ClusterLoadAssignment) and produces a distribution of expected traffic across endpoints.

I implemented the first plan: ynqa/envoy-lb-simulator. This is still a prototype that has not considered DNS resolution and health checking. It iterates chooseHost given times against clusters field in config file.

A CLI tool that takes a Cluster configuration, as well as endpoint health and registration status (e.g. in a ClusterLoadAssignment) and produces a distribution of expected traffic across endpoints.

I implemented the first plan: ynqa/envoy-lb-simulator. This is still a prototype that has not considered DNS resolution and health checking. It iterates chooseHost given times against clusters field in config file.

Awesome!! cc @tonya11en who might be interested in checking out ^.

Awesome!! cc @tonya11en who might be interested in checking out ^.

To count the assignments for endpoints can understand the simple load balancing algorithm such as random, round-robin, but others are difficult to grasp the behaviors.

To count the assignments for endpoints can understand the simple load balancing algorithm such as random, round-robin, but others are difficult to grasp the behaviors.


bumped deploy version for SNAPSHOTs

Coverage remained the same at 80.108% when pulling 60dcc667a5e8ad5af0e7a589c6a1623655b878d2 on akmorrow13:fix_npm_buildgoal into 6b4399a30b9fb1db6a5f29b827c62eeb67bc381e on bigdatagenomics:master.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/mango-prb/860/
Test PASSed.


excluding non-lausd users from the user table

I talked to Brent this morning and he said that he got confused when looking at the user table on the monitoring tool since the number of users is different from what's reported on the class setup.
If it is the Mobilize deployment, can we filter out non-lausd users with 0 responses? Of course, those that have responses should be there so # of responses will be consistent somewhere else.

Sorry just noticed this now. This is actually already done, see the code here: https://github.com/mobilizingcs/monitor/blob/master/index.js#L502-L513
I tested it as well just now and the user count matches the count found in the teacher tool. Could I have an example of this if it's happening somewhere I'm missing..?


Eliminate unnecessary rebuilds in build script

Our various test and benchmark artifacts are created repeatedly on every build. While not a noticeable slowdown at this point, it's unnecessary work and, over time, the cause of wear for SSDs, for example.
The problem seems to be that the generated files' mtimes are after those of Cargo's output file that they are compared against to determine staleness. This behavior is counter-intuitive: it is the build script that emits those outputs to stdout while also generating those files. Hence, the build script's outputs can only be available completely after said script has run (that is, after the files have been generated as well). Alas, this behavior seems to be fully intentional from the Cargo side [0].
With this change we work around this problem, by adjusting generated files' time stamps to those of said output file after generation. It's not perfect (the output file is more or less an implementation detail and could potentially change at some point; also, because we rely on the existence of this output file we need two builds before the mtimes are correct), but should be good enough. We also add a CI job that makes checks that we don't re-generate files for the default generate-test-files feature.
[0] https://github.com/rust-lang/cargo/blob/4a60ff78a5f03e7c9ed2399754efb62c80a8ecc8/src/cargo/core/compiler/fingerprint/mod.rs?L249#L249-L256
Fixes: #91

LGTM. Just curious why shelling out to touch instead of doing this from Rust code (seems like a pretty straightforward operation, there must be some crate for this, right?)

Indeed, ideally we would use Rust code. However, I didn't want to add a build dependency, because internal consumers are dependency-averse at this point (and we just managed to get down to only a single dependency: libc). Hopefully said consumers will sort things out and that won't be a blocker down the road. We could use the respective libc calls ourselves, though when I looked at doing that a while back the plumbing seemed rather...intricate. I don't think the shelling out part is an issue, to be honest, but my worry is that some touch binaries won't support all the options used and will just error out...


[PIP-163][Txn]Add lowWaterMark check before appending entry to TB

Master Issue: #15423
Motivation & Modification
Details can be found at https://github.com/apache/pulsar/issues/15423.
Verifying this change

[ ] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API: (yes / no)
The schema: (yes / no / don't know)
The default values of configurations: (yes / no)
The wire protocol: (yes / no)
The rest endpoints: (yes / no)
The admin cli options: (yes / no)
Anything that affects deployment: (yes / no / don't know)

Documentation
Check the box below or label this PR directly.
Need to update docs?

[ ] doc-required
(Your PR needs to update docs and you will update later)

[x] no-need-doc
(Please explain why)

[ ] doc
(Your PR contains doc changes)

[ ] doc-added
(Docs have been already added)

/pulsarbot run-failure-checks


feat: Add a mechanism to set additional attributes on generated swift libraries.

In order to merge my example using grpc-swift from RSPM I need to be able to add the alwayslink = True tag to the generated build file for SwiftAtomics. The tests will crash on Ubuntu if this is unset.
If we have a tag class to customize attributes for packages in MODULE.bazel, that would allow me to fix this issue.
From this thread: https://github.com/cgrindel/rules_swift_package_manager/issues/1214

It was specifically the ManagedAtomic type in swift atomics that was failing on ubuntu.
I think the flag was not necessary on apple platforms because their linker has different default behavior.
The flag controls whether the linker should ignore object files that are unreferenced elsewhere in the program.
In Swift, you can extend types to conform to a protocol outside of their defining file / module. I believe in this case an extension was "falling off" and the program was crashing at runtime.
There was some discussion around whether this should just be the default for swift_library.
As for RSPM, I think a tag class that allows this to be configured on a per-dependency basis sounds good. If you add that, I'm happy to rebase the PR and get it working again.
https://stackoverflow.com/questions/48653517/what-does-bazel-alwayslink-true-mean

Ideally we wouldn't need to customize this and we can get all the information about if we need this or not from the information that SPM provides? If SPM is able to compile this with that info, we should be able to as well.

@brentleyjones How do you think we should determine when we need to apply the alwayslink = True flag?
These deps work as expected on linux when building with SPM but they fail at runtime with Bazel.

Does SPM always link as well, e.g. when doing something like swift build

@luispadron I did not see any specific configuration for the module, but it's possible this is a default behavior in swift build
https://github.com/apple/swift-atomics/blob/main/Package.swift
A swift_binary built from this package with Bazel crashed on Ubuntu but the same executable built with SPM worked.
Keith suggested the alwayslink flag and that fixed it, which is why I added that to swift atomics in rules swift.
I traced it back to the ManagedAtomic type and an extension in another file adding a conformance to a protocol.
It's possible that Apple configures the linker differently than bazel when running swift build.

This feels like we need to adjust our default behavior to mimic what SPM does.

@brentleyjones @cgrindel this is the minimal example project I created to reproduce the issue with Bazel and show that it works with SPM:
https://github.com/AttilaTheFun/swift_atomics_test
I used a Ubuntu VM that matched the version used by RSPM / rules_swift CI.
These are the instructions I wrote for myself to install the VM and instead Bazel and Swift on it too:
Installing a Multipass Ubuntu VM with Bazel and Swift
Install Ubuntu VM with Multipass
Install multipass:
brew install multipass

Check that it was successful:
multipass version

List the available VMs:
multipass find

Install a Ubuntu 20.04 (aka focal) with the default config:
multipass launch jammy

If you want a different config:
multipass launch jammy -n jammy -c 2 -m 4G -d 20G

To ssh into the running machine:
multipass shell jammy

To start the VM:
multipass start jammy

To copy files to / from the VM:
multipass transfer jammy:file.txt .

Install Bazelisk
Change directory into the user binaries directory:
cd /usr/bin

Download the bazelisk binary to this directory:
sudo wget https://github.com/bazelbuild/bazelisk/releases/download/v1.19.0/bazelisk-linux-arm64

Change this URL for a newer bazelisk.
Rename the binary file:
sudo mv bazelisk-linux-arm64 bazelisk

Make it executable:
sudo chmod +x bazelisk

Check that it was installed correctly:
bazelisk version

Install swift
Instructions from: https://www.swift.org/install/linux/
Change into the home directory:
cd ~/

Update the package registry:
sudo apt-get update

Install the package dependencies:
apt-get install \
          binutils \
          git \
          gnupg2 \
          libc6-dev \
          libcurl4-openssl-dev \
          libedit2 \
          libgcc-9-dev \
          libpython3.8 \
          libsqlite3-0 \
          libstdc++-9-dev \
          libxml2-dev \
          libz3-dev \
          pkg-config \
          tzdata \
          unzip \
          zlib1g-dev

Download the tar file:
wget https://download.swift.org/swift-5.9-release/ubuntu2004-aarch64/swift-5.9-RELEASE/swift-5.9-RELEASE-ubuntu20.04-aarch64.tar.gz

Uncompressed the tar file:
tar xzf swift-5.9-RELEASE-ubuntu20.04-aarch64.tar.gz

Delete the tar file:
rm -rf swift-5.9-RELEASE-ubuntu20.04-aarch64.tar.gz

Add the swift binaries to the PATH:
export PATH=/home/ubuntu/swift-5.9-RELEASE-ubuntu20.04-aarch64/usr/bin:"${PATH}"

Verify Swift was installed successfully:
swift --version

Use clang instead of gcc:
export CC=clang

Based on https://github.com/bazelbuild/rules_swift/commit/2cc542ab55335dff09da8af42e4c69d7f005699d, we should probably unconditionally set it?

Yeah @brentleyjones I'd be in favor of matching the SPM behavior in swift_library. Then this wouldn't be necessary.
It could be gated behind a config  if this is considered a breaking change.

Since we are pre-1.0, I think we should just make the change.

https://github.com/cgrindel/rules_swift_package_manager/pull/1385


Register

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/107453
Tip: Release Notes
Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.
@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.
Tagging
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" ff0ea4882e91111e49ab5d6c5272ae24a19ba6e2
git push origin v0.1.0


Check to avoid join replacement in recursive-joined models, #1617

Check issue #1617 or feel free to contact me for details.

I tried this locally, and added a test for it (310fe4abee9a65f325a989322ea0d2ee622806f4). But your fix isn't solving the issue. The filter on the related model column isn't working as expected.


Problem with upload annotation  - landscape/portrait

Hello,
Maybe my problem is similar like in issue #733 but I will tell you about my case.
When we have photos, some of them can have bad orientation to make bboxes on them (1bokiem.jpg).

So we have two ways:

Rotate 90 degrees in any program to correct orientation (like photo 1ok.jpg) and import to CVAT's task.
Use a build in functionality to rotate photo.

And here is a bit problem with with second way.

I see bad orientation photo, I can't work on them so I use rotation in CVAT menu.
Now I can work, make BBoxes on rotated photo.
When I finished I saved changes, dump annotation  and closed task's window.
When I open again this task, the photo is again rotated on bad orientation, but BBoxes are rotated too, so ok. Here we don't have problem yet.
When I will now make new task, with the same photos, and I will use Upload annotation then everything works, I see rotated photo with rotated BBoxes so still everything is OK.
But now finally we have problem: When I will use way nr 1 (rotate photo to correct orientation - useful to make BBoxes on them) make a task from these photos and try to upload my annotation from the same photo but with bad-orientation, then I have error:

which means that rotating function in CVAT's window work only optically on this session, and it not saving the new orientation in photo data.

Is this works correct?

Hi @sbanori ,
Basically it does work correctly. For the tool you changed photos (at least dimensions) and try to upload old annotations for new photos. It will not work. Even you are lucky and you don't have the error you will have incorrect annotations on these new photos (they are new just because you did some transformation with them out of the tool).
You have to update annotations as well (rotate bounding boxes as you did for images). It should be trivial but we don't have scripts which will do such transformation for you.
What can be done here?

Save your preferences per task and load the task as you did in the past (we don't have the feature yet)
If all photos are in the same "bad" orientation you can use option "rotate images on all frames" in settings (F2).
We can provide a module which can do some transformation for you (we don't have the feature yet)

I will close the question for now. Don't hesitate to summit a feature request

@sbanori From what I figured out CVAT reads in the image in the original 'rotation', meaning that it doesn't apply any rotation stored in the EXIF metadata. Sometimes pictures include an EXIF Orientation Value, and when you open them, based on the software you are using and this value they can be rotated or not. See for example scikit-image/scikit-image #3150.
For example if you use skimage.io.imread to open your images, you can open them ignoring the EXIF Orientation Value by using the option skimage.io.imread(filename, plugin='pil'), this will open the image in the same way as CVAT does.

@dzanaga , do you think we should have an option to use EXIF metadata for images in settings?

@nmanovic I believe it would be enough to document the behavior in the User's Guide, so that users are aware or can easily find out about this detail if needed for their images.
The EXIF orientation is a metadata value that can be changed quite easily by viewing software or can also be lost during intermediate processing steps. I wouldn't rely on it, I think it would introduce more confusion.
e.g. imagine that you have that option activated and you label an image. Then an user opens that image on the file system to check it and rotates it (etc). The orientation metadata value changes, but the label in cvat db wouldn't be aware of it. When the user dumps the annotation he would end up with something rotated, and unless you add also another field in the annotations to keep track of the original orientation value at the time of the creation this can only be found out later by manual inspection. Most of the time it would go unnoticed creating wrong labels.
The current behavior enforce more consistency.

@sbanori From what I figured out CVAT reads in the image in the original 'rotation', meaning that it doesn't apply any rotation stored in the EXIF metadata. Sometimes pictures include an EXIF Orientation Value, and when you open them, based on the software you are using and this value they can be rotated or not. See for example scikit-image/scikit-image #3150.
For example if you use skimage.io.imread to open your images, you can open them ignoring the EXIF Orientation Value by using the option skimage.io.imread(filename, plugin='pil'), this will open the image in the same way as CVAT does.

For opencv for example you can use
cv2.imread(path,  cv2.IMREAD_IGNORE_ORIENTATION | cv2.IMREAD_COLOR)

as highligted in https://stackoverflow.com/questions/44537075/image-orientation-pythonopencv


[Bug] crash if truncated is used but without i:jd

@emilleishida noticed that if you specify columns to transfer (as opposed to transferring all columns), but without specifying the time, the client will crash. This is due to the fact that internally the code tries to sort results from the HBase query against i:jd without checking it exists...
Action: check if i:jd exists before sorting results.

Done @emilleishida -- You should be able to transfer any columns you want :-)


Utilize cached Python on GitHub-hosted runners

Note: I considered opening this issue under the uv repository, where it might be solved, but I think the context here is more suitable.
GitHub-hosted runners have multiple versions of Python installed. For example, consider the ubuntu-latest image:

Python

3.7.17
3.8.18
3.9.19
3.10.14
3.11.9
3.12.5

Another Python version is the default - 3.10.12, but all of them are installed.
Therefore, when I run the following step in a GitHub workflow:
      - name: Install Python 3.12.5
        run: uv python install 3.12.5 --offline

I expect it to work, and identify the runner's tool cache, which in this case is:
$RUNNER_TOOL_CACHE/Python/3.12.5/x64/bin/python
This is especially relevant after I use the astral-sh/setup-uv action in the step preceding:
      - uses<EMAIL_ADDRESS>        with:
          version: "0.4.8"

The actions/setup-python action does use the cached tools:
https://github.com/actions/setup-python/blob/main/docs/advanced-usage.md#hosted-tool-cache
And astral-sh/setup-uv intends to replace it, so I expect it to follow suit.
I've opened a test repository with one workflow to test this:
https://github.com/jond01/uv-python-cache

Our Python distributions are different than the ones GitHub provides. You may use the GitHub ones, but you may also want to use the same Python distributions everywhere in which case you'll want to install ours. Hopefully I clarified the intended behavior of uv python install over in https://github.com/astral-sh/uv/issues/7340

I see, thanks.
I think it can be helpful to document this here:
https://github.com/astral-sh/setup-uv?tab=readme-ov-file#do-i-still-need-actionssetup-python-alongside-setup-uv
Since actions/setup-python supports cached Python without any download.
However, uv downloads the required Python in uv python install so fast, making it a non-issue in most cases.


I am slightly concerned about the proposal at the end for a null-aware spread. I think it's important to support something like that, but the syntax ...?foo seems more line-noisy than idiomatic Dart.
Not sure what else to suggest, though. I agree that ...? is a logical way to express this.

Yeah, I agree it's pretty punctuation-heavy, but it's probably the natural-est solution.

Part of my concern is that I think this will be pretty common (unlike some of the other punctuationy things in Dart), and I fear Dart turning into Perl. :-)
The other part of my concern is that usually the question mark is after the thing that you're null-checking, not before:
foo ?? bar is about foo being null
foo ??= bar is about foo being null
foo?.bar is about foo being null
...?bar is about bar being null
Maybe if it was more like ...bar? it would be clearer? But it would be harder to parse.
Maybe the ... should be on the rhs in general?
var args = [
  testArgs...,
  '--packages=${PackageMap.globalPackagesPath}',
  '-rexpanded',
  filePaths...
];

Widget build(BuildContext context) {
  return new CupertinoPageScaffold(
    child: new ListView(
      children: <Widget>[
        new Tab2Header(),
        buildTab2Conversation()...,
      ],
    ),
  );
}

var params = {
  "userId": 123,
  "timeout": 300,
  uri.queryParameters...
};

[1, "234".runes..., 5]

var first = {"key": "value"};
var second = {"a": "b", first..., "c": "d"};

var command = [
  engineDartPath,
  '--target=flutter',
  extraFrontEndOptions...?,
  mainPath
];

I kinda like that better in general, actually. It reads more like English. Would it be sufficiently unambiguous to parse?

those seem equally confusing to me... ..., whether as prefix or suffix, looks like it binds more tightly than +. (That's a problem we run into with .., where it looks like it binds more tightly than it does, which makes the code a bit confusing to read sometimes... to the point where sometimes I encourage people to add more parens than strictly necessary.)
If we make ... bind tightly, it would end up being one of these:
var command = [
  engineDartPath,
  ...(stuff + moreStuff),
  another,
  (stuff + moreStuff)...,
  more
];

Both work ok here, but I think I prefer the latter. What about something more elaborate:
  var arguments = <String, Object>{
    'foo': bar,
    ...?tabStops?.map<String, Object>(
      (String int, Direction direction) => new MapEntry('--tab$int', direction.toString()),
    ),
    'baz': quux,
  };

  var arguments = <String, Object>{
    'foo': bar,
    tabStops?.map<String, Object>(
      (String int, Direction direction) => new MapEntry('--tab$int', direction.toString())
    )...?,
    'baz': quux,
  };

I think the suffix form has a (very) slight edge, mostly because it's not actually necessary to understand the code (obviously if it's valid code, and you have a random expression in the middle of the literal, it's going to be adding that value to the map -- the ... is only really required to disambiguate between adding the list itself or expanding the list, in the case of a list literal where the list itself would be a valid value). Since it's not strictly necessary for readability, the prefix form is IMHO slightly hurt by the in-your-face-ness of its leading ? coming before an alphabetic character and it being before the thing you're null-checking instead. (Especially egregious in the example above where there's a question mark before and after the first identifier.)

Closing since this syntax is locked down now.


chore: Add console statements log to JS_RUN event

Description
This PR adds consoleStatements field to JS_OBJECT_FUNCTION_RUN analytics event
Fixes #25532
Type of change

Chore (housekeeping or task changes that don't impact user perception)

Testing
Nil
Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

/ok-to-test

/ok-to-test

@ohansFavour - Please add reason for skip-TestPlan to PR.

@ohansFavour - Please add reason for skip-TestPlan to PR.

@Aishwarya-U-R  This is an instrumentation change


Raise OnTrackChange event for "other" tracks as well

I was trying out the local APIs with some podcasts and noticed that the OnTrackChange event was never raised, except when switching from a normal track to a podcast or vice versa.
I found out that podcasts don't seem to be currently supported by the APIs (neither by the local ones nor by the official web APIs), so when a podcast is playing the track object's fields are all null except for TrackType and Length.

Looks good! Gonna test this and merge it soon :+1:


Update solana.tokenlist.json

update SAIL & gSAIL with serumV3Usdc field
I agree to not ping anybody on Discord/Twitter/email about this pull request. Instead I will inquire by posting a new comment in the pull request if needed.

PRs are reviewed in bulk and and can take up to two weeks to be merged.
Please provide the following information for your token.
Please include change to the src/tokens/solana.tokenlist.json file in the PR.
DON'T modify any other token on the list.
At minimum each entry should have

Token Address:
Token Name:
Token Symbol:
Logo: (logo should be uploaded under assets/mainnet//*.<png/svg>)
Link to the official homepage of token:
Coingecko ID if available (https://www.coingecko.com/api/documentations/v3#/coins/get_coins__id_):

Hi @oJshua
nothing urgent, but appreciate if you can merge this PR ;-)
Thanks

Hi again @oJshua
Was not urgent 9 days ago, but we really need this merge to continue our next steps in our project 😉
Appreciate 👍


Updated rotation apis and parameters to support both an isith and nsith for current and next thresholds

New rotation rules will require that current signing threshold isith is not the same as the prior next signing threshold nsith
so rotations must support both independently. The default is for isith to be the prior next when not provided so mostly backwards compatible.

Codecov Report

Merging #323 (3e2d863) into development (2748af4) will increase coverage by 0.05%.
The diff coverage is 98.79%.

@@               Coverage Diff               @@
##           development     #323      +/-   ##
===============================================
+ Coverage        92.69%   92.74%   +0.05%
===============================================
  Files              116      116
  Lines            35975    35990      +15
===============================================
+ Hits             33346    33380      +34
+ Misses            2629     2610      -19

Impacted Files
Coverage Δ

src/keri/vdr/credentialing.py
82.90% <0.00%> (ø)

src/keri/app/grouping.py
84.67% <100.00%> (ø)

src/keri/app/habbing.py
82.72% <100.00%> (+0.11%)
:arrow_up:

src/keri/app/keeping.py
88.30% <100.00%> (+3.08%)
:arrow_up:

src/keri/app/kiwiing.py
76.51% <100.00%> (ø)

src/keri/db/basing.py
93.37% <100.00%> (+0.01%)
:arrow_up:

tests/app/cli/test_kli_commands.py
100.00% <100.00%> (ø)

tests/app/test_grouping.py
100.00% <100.00%> (ø)

tests/app/test_keeping.py
99.32% <100.00%> (+0.01%)
:arrow_up:

tests/core/test_escrow.py
99.87% <100.00%> (ø)

... and 1 more

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Fix 0.6.0 bugs.

Thank you a lot for contributing to Cosmos Voyager!

Issue

closes: #720
Screenshots

❤ Thank you!

I fixed the reconnection bug in #726 while shutting down the lcd process. If this is acceptable let's use that fix.


multi-stage-frontend Dockerfile is broken

contrib/docker/multi-stage-frontend/Dockerfile is broken
Expected Behavior
Building the multi-stage-frontend should result in a fully working image.
Current Behavior
Building the multi-stage-frontend results in an almost working image. Going to http://localhost:/ works, navigating from
there to any sections such as /api-docs, /catalog, etc works. However, if you enter http://localhost:/catalog directly into the browser or simply reload the page nginx returns a 404. The logs report that the /path/to/nginx/dir/catalog does not exist.
The above is caused by the Dockerfile failing to pull in docker/default.conf.template. The Dockerfile also fails to pull in docker/run.sh. This is due to the docker folder missing from contrib/docker/frontend-with-nginx/docker.
Possible Solution
This mostly fixes it:
 cp -a contrib/docker/frontend-with-nginx/docker contrib/docker/multi-stage-frontend/

However, the COPY commands' source paths to these files are relative:
COPY docker/default.conf.template /etc/nginx/conf.d/default.conf.template
COPY docker/run.sh /usr/local/bin/run.sh

Attempting to build the image inside contrib/docker/multi-stage-frontend/ to get around this does not work. Building from the root of the repo works if you update the paths in  contrib/docker/multi-stage-frontend/Dockerfile to:
COPY contrib/docker/multi-stage-frontend/docker/default.conf.template /etc/nginx/conf.d/default.conf.template
COPY contrib/docker/multi-stage-frontend/docker/run.sh /usr/local/bin/run.sh

But is this what we want to do? Perhaps these paths and/or contrib/docker/multi-stage-frontend/README.md need to be updated to reflect the correct build instructions.
Once we're able to copy in default.conf.template and run.sh, the issues described are resolved.
Steps to Reproduce
The build completes if run from the root, but has the aforementioned issues:
docker build -t backstage-frontend -f contrib/docker/multi-stage-frontend/Dockerfile .
The following fails with error Cannot find the root of your workspace - are you sure you're currently in a workspace?:
cd contrib/docker/multi-stage-frontend/
docker build -t backstage-frontend -f Dockerfile .

What does work:
Updating the COPYcommands in contrib/docker/multi-stage-frontend/Dockerfile to:
COPY contrib/docker/multi-stage-frontend/docker/default.conf.template /etc/nginx/conf.d/default.conf.template
COPY contrib/docker/multi-stage-frontend/docker/run.sh /usr/local/bin/run.sh

And then running docker build -t backstage-frontend -f contrib/docker/multi-stage-frontend/Dockerfile . will result in a working image!

I believe that this is no longer the case; the Dockerfile has been iterated on since. Closing, and please do reopen if the problem manifests itself still

for posterity - we actually went ahead and cleaned up this to make it work https://github.com/backstage/backstage/pull/5391


test: Replace mocking in test_execute_missing_schema

Codecov Report

Merging #480 into master will decrease coverage by 0.31%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #480      +/-   ##
==========================================
- Coverage   99.89%   99.57%   -0.32%
==========================================
  Files          30       30
  Lines        1896     1886      -10
  Branches      300      300
==========================================
- Hits         1894     1878      -16
- Misses          1        4       +3
- Partials        1        4       +3

Flag
Coverage Δ

#unittests
99.57% <ø> (-0.32%)
:arrow_down:

Impacted Files
Coverage Δ

src/schemathesis/extra/pytest_plugin.py
92.85% <0.00%> (-7.15%)
:arrow_down:

src/schemathesis/lazy.py
100.00% <0.00%> (ø)

src/schemathesis/models.py
100.00% <0.00%> (ø)

src/schemathesis/cli/context.py
100.00% <0.00%> (ø)

src/schemathesis/runner/events.py
100.00% <0.00%> (ø)

src/schemathesis/runner/impl/core.py
100.00% <0.00%> (ø)

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 a5613fd...157a577. Read the comment docs.


moment.js missing from setup

Just a small change to suggest, add:
src="https://cdnjs.cloudflare.com/ajax/libs/moment.js/2.8.4/moment.min.js">
to your setup readme

want to send a PR?

nvm :)


Node module resolution for SCSS files

A failing test for #78894 - fix coming later

Added here: https://github.com/microsoft/vscode-css-languageservice/blob/61ed31a6083a6f61f28433d71c188f375d586f0b/src/test/scss/scssNavigation.test.ts#L205


Fix issue causing the response callback to be invoked with the invalid requestCode

In addition, this deprecates support for forwarding callbacks from Godot's parent activity.
Fixes #47073

Thanks!


Fix new typing errors

This PR adds some type: ignore to ignore the typing problems that appear in the up.model.delta_stn.py file after the usage of an updated version of mypy in the CI

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 85.13%. Comparing base (b6f716b) to head (bd60179).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #580   +/-   ##
=======================================
  Coverage   85.13%   85.13%
=======================================
  Files         201      201
  Lines       26989    26989
=======================================
  Hits        22977    22977
  Misses       4012     4012

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

I found a simpler solution in #582


Multiple select (checkboxes and/or toggleStates)

Is there any intention to incorporate a standard multiple select drop down with checkboxes / toggle states at any point? - Specifically like this -> http://www.erichynds.com/jquery/jquery-ui-multiselect-widget/
It would be nice to have as a core option without hacking around the formatting with injected checkboxes and custom event handlers to catch the behaviours needed with the current select2 library.
Cheers,

D

Has this enhancement been implemented? I'm looking at Version 4.0.0-beta.3 and I don't see it.

This is possible to do now by either styling selected options ([aria-selected=true]) or overriding the resultsAdapter and adding some more logic when rendering the results.

Has this enhancement been implemented? Can anyone tell how to use this enhancement.

Hi, take a look into this: http://jsfiddle.net/wasikuss/cg1zr4zd/
I know that functions called from onSelect won't work properly, but it is ok for simple usage :)
I'm going to finish this and make fully compatible plugin that adds new functions without altering default behaviour.

@kevin-brown are there any examples of overriding the resultsAdapter? I've looked in the Docs and the Forum but i can't see anything.

If this is still a thing, can this issue get reopened? And if not, can you clearly say so?

Looks like you can get half way there without a custom adapter by just overriding the template for results.
http://jsbin.com/wezudobake/1/

Nice, but it would be great if we could get some extra features as

grouping (category1 with some sub-elements, category2 with some sub-elements, etc..)
selecting multiple sub-elements with a single click on their parent (group)
(un)expanding groups (show/hide all sub-elements in a group)

Basically, something like this

@kevin-brown, in your example of overriding the template, if CloseOnSelect is set to false, clicking outside of the checkbox will select the item but not check the checkbox.
http://jsbin.com/tifuzikimo/edit?html,js,output
Also, the templateSelection is still tag based. That is fine for a few items, but when dozens of items are selected it could be too much. Showing a summary instead would be nice, like "21 of 100 selected".
erichynds jquery-ui-multiselect-widget takes this idea a step further by showing either the selected items or the summary based on the number of item selected: "Alabama, Florida, Georgia" or "48 of 50 selected"
Anyway, I think @wasikuss's example is the kind of functionality were looking for.

@homer2 the example from @wasikuss is a nice example but is not going to work on multiple select boxes on the page selected by a class. The code needs some alteration for multiple select boxes.

@PlippiePlop,
It also work on class-selected elements
http://jsfiddle.net/wasikuss/gx93rwnk/

@wasikuss  ah I see what I did wrong. Thank you for the insight ;)

+1

+1

+1
Any news on this?

+1
Please integrate the checkboxes into main version, the tags are useless with lots of elements selected

+1

+1

For anyone coming here from google and/or interested, check https://github.com/alexandernst/angular-multi-select for a good multi select.

For anyone that would want a simple CSS solution to this :
http://codepen.io/stephenbe/pen/zBrzYP
Just change the background color to a background image of a checkbox.
Cheers

@wasikuss did you ever make a plugin for this?

Ok, I see more and more ppl need that plugin. I will post link to plugin when it's done ( 2 - 3days ).

+1, tags are not needed in every case. Moreover, fast group selection is desired too.

+1

https://github.com/wasikuss/select2-multi-checkboxes
Please try and feel free to report any bugs/features.
Cheers

+1

I tried copying the fiddle from https://jsfiddle.net/wasikuss/gx93rwnk/ but it did not work because my fiddle account was using jQuery 1.9.1, once I added jQuery 1.10.1 as an external resource it worked fine.

Is it possible to have the search facility with multiple selection?

The select2 that I'm converting to multi-select includes an up/down arrow on the far right, a magnifying glass search icon on the far right in the search input box, and a scrollbar on the right of the dropdown.

Is it possible to incorporate these three styles into the third 'select2-original' option please?

just remove line 44 in select2.multi-checkboxes.js ;)

Setting minimumResultsForSearch: 0 shows the search box for the first 2 dropdowns which is nice, thank you. However it doesn't change the 3rd option where the selected names appear at the top. There seems to be a search box there without border, it would be great if the border, magnifying glass image, up/down arrow, and vertical scroll could be incorporated into the 3rd layout option.

Hi @wasikuss , was checking your plugin and it's almost what I need but i see it's working with select2 3.5.2. Did your ever upgrade the code to v4?
Thanks in advance,

This issue is closed- has it been implemented already?

Great,
This was what I was looking for also.
@zakamik Yes, repo is here:
https://github.com/wasikuss/select2-multi-checkboxes

For those who are still looking for a solution, have a look at my fiddle.
I have used a couple of fiddles posted about the question and combined it all into 1
Not perfect, but it works.
https://jsfiddle.net/Lkkm2L48/7/

@WillemOpperman  works great, but only issue that it does not work when you have multiple selects on the screen. it should work with multiple selects on class or id base. See https://jsfiddle.net/nzfhkfuk/2

@WillemOpperman looks good except it always jumps to first selection each time you select.

sorry for late response but it is already done. This time properly - less ugly hacks that previously broke partially select2 API.
https://github.com/wasikuss/select2-multi-checkboxes/tree/amd

so the feature was requested but the  case was close to use select2?

+1 !

That's how I solved this problem.
https://jsfiddle.net/akwud47t/1/


128x128 Level only loads at 64x64

I created a custom level with the size of 128x128, saved it, and opened it. The size is incorrect when opening. I'm not sure if I am doing something wrong but replicating the issue is just creating a custom level that is bigger than default, saving it, then opening it.

After further investigation, this happens when saving as a .editor, .nw, or .graal. However, saving this as a .lvl correctly loads the custom size. Cannot find a way tor restore work from the .editor file though.

Yeah those formats don't support anything other than 64x64. That's for graal only. You can create a gmap though and load the gmap.
.lvl is a custom format to support anything the editor supports. LevelFormatLVL.cpp has code to show how to load it if you want to use it in your game.

Okay, got it. Not really using this for any dev work just for nostalgic fun. Thanks for responding!


CMake: Support building as shared library / QML module.

@benlau Hi! I am currently packaging this project for Debian as it is needed to bring to Ubuntu Touch apps to Debian: telePORTS (a Telegram chat client) and Dekko2 (an email client).
For this, I need to be able to build quickflux as a shared library / QML module (rather then linking it into the application statically at build-time).
In this PR find a patch, that should achieve this (note: I haven't tested it yet, will do so soon).


Could you provide SciTSR-trained model?

Hi, thanks for uploading the code.
Do you have any plan to open the checkpoint trained on SciTSR?

Thanks for your attention. We are planning to do a update version of LGPMA recently, we will release the model on several different datasets including SciTSR after the updation (~2023Q1).


Update LibXC to New Version

Hi PySCF devs :smiley:
I think the libxc dependency could be upgraded to new version 5.0.0.
https://github.com/pyscf/pyscf/blob/c7ea840b012a59fce5fa4114ef3274a7cf00165e/pyscf/lib/CMakeLists.txt#L174
Motivation of this issue, is that LibXC's LYP fxc part (3rd derivative) is flaw in version 4.3.4 in my testing. This is probably resolved by new version 5.0.0. Well, the following issue is not LYP but PBE:
https://gitlab.com/libxc/libxc/-/issues/72
I think maybe simply change the URL to https://gitlab.com/libxc/libxc/-/archive/5.0.0/libxc-5.0.0.tar and then recompile PySCF's lib module could resolve the problem.

It has already updated to v5.1.2 in current version of pyscf :smiley:


chore: Add semantic-release configuration and workflow

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


PhantomJS not found on PATH

when installing using npm I see the following error
PhantomJS not found on PATH
Downloading https://github.com/Medium/phantomjs/releases/download/v2.1.1//phantomjs-2.1.1-linux-x86_64.tar.bz2

There is an extra slash after the v2.1.1

PhantomJS not found on PATH
That's not really a problem. Because you don't have phantomjs locally, it tries to download the phantomjs.
Do you get another error after the download log? Maybe it's just a formatting bug.
That issue would belong to https://github.com/medium/phantomjs/issues

oh ok thanks. Yeah it's not a blocker. The module works perfectly. Thanks so much


Show your pride with badges

When you integrate witht he varoius cloud (software quality) services, you should show your pride with badges in the README.

Duplicate to #4

Closing as duplicate of #4.


update start_time_metric_regex example

This addresses a comment made in https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/32993

Opened PR by accident, closing


Shouldn't fail on CSS mistake

React-native-css should be more forgiving.

+1

@wbashir will be released this weekend.


plugin no longer compatible with runelite

A runelite update was released and this plugin is no longer compatible

#31 Should fix this

#31 Should fix this

Thanks


Infer dependencies based on what's imported into namespace

@pankajroark just need some feedback on initial approach. Will revisit tests and dead code if I'm along the right path here


Fix #2600: Turn on docker build

Also, set the yarn version to the current stable in docker.

Still getting some errors:
jsbuild_1   | ✘ [ERROR] Could not resolve "jquery-ujs"
jsbuild_1   |
jsbuild_1   |     app/javascript/application.js:4:15:
jsbuild_1   |       4 │ import {} from 'jquery-ujs'
jsbuild_1   |         ╵                ~~~~~~~~~~~~
jsbuild_1   |
jsbuild_1   |   You can mark the path "jquery-ujs" as external to exclude it from the bundle, which will remove this error.
jsbuild_1   |
jsbuild_1   | ✘ [ERROR] Could not resolve "bootstrap"
jsbuild_1   |
jsbuild_1   |     app/javascript/application.js:7:27:
jsbuild_1   |       7 │ import * as bootstrap from "bootstrap";
jsbuild_1   |         ╵                            ~~~~~~~~~~~
jsbuild_1   |
jsbuild_1   |   You can mark the path "bootstrap" as external to exclude it from the bundle, which will remove this error.
jsbuild_1   |
jsbuild_1   | ✘ [ERROR] Could not resolve "jquery"
jsbuild_1   |
jsbuild_1   |     app/javascript/src/jquery.js:1:19:
jsbuild_1   |       1 │ import jquery from 'jquery';
jsbuild_1   |         │                    ~~~~~~~~
jsbuild_1   |         ╵                    "./jquery"
jsbuild_1   |
jsbuild_1   |   Use the relative path "./jquery" to reference the file "app/javascript/src/jquery.js". Without the leading "./", the path "jquery" is being interpreted as a package path instead.
jsbuild_1   |
jsbuild_1   | ✘ [ERROR] Could not resolve "@fortawesome/fontawesome-free/js/all"
jsbuild_1   |
jsbuild_1   |     app/javascript/src/fontawesome.js:2:7:
jsbuild_1   |       2 │ import '@fortawesome/fontawesome-free/js/all';
jsbuild_1   |         ╵        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
jsbuild_1   |
jsbuild_1   |   You can mark the path "@fortawesome/fontawesome-free/js/all" as external to exclude it from the bundle, which will remove this error.
jsbuild_1   |
jsbuild_1   | ✘ [ERROR] Could not resolve "turbolinks"
jsbuild_1   |
jsbuild_1   |     app/javascript/src/turbolinks.js:3:23:
jsbuild_1   |       3 │ import Turbolinks from 'turbolinks';
jsbuild_1   |         │                        ~~~~~~~~~~~~
jsbuild_1   |         ╵                        "./turbolinks"
jsbuild_1   |
jsbuild_1   |   Use the relative path "./turbolinks" to reference the file "app/javascript/src/turbolinks.js". Without the leading "./", the path "turbolinks" is being interpreted as a package path instead.
jsbuild_1   |
jsbuild_1   | ✘ [ERROR] Could not resolve "stupid-table-plugin"
jsbuild_1   |
jsbuild_1   |     app/javascript/src/table_sorting.js:2:7:
jsbuild_1   |       2 │ import 'stupid-table-plugin';
jsbuild_1   |         ╵        ~~~~~~~~~~~~~~~~~~~~~
jsbuild_1   |
jsbuild_1   |   You can mark the path "stupid-table-plugin" as external to exclude it from the bundle, which will remove this error.
jsbuild_1   |
jsbuild_1   | 6 errors
jsbuild_1   | [watch] build finished, watching for changes...
cssbuild_1  | Error: Can't find stylesheet to import.
cssbuild_1  |   ╷
cssbuild_1  | 1 │ @import 'bootstrap/scss/bootstrap';
cssbuild_1  |   │         ^^^^^^^^^^^^^^^^^^^^^^^^^^
cssbuild_1  |   ╵
cssbuild_1  |   app/javascript/styles/bootstrap.scss 1:9               @import
cssbuild_1  |   app/assets/stylesheets/application.bootstrap.scss 2:9  root stylesheet
cssbuild_1  |
cssbuild_1  | Sass is watching for changes. Press Ctrl-C to stop.
cssbuild_1  |


Generics generate impractical entities

When translating C# generic new(), this will generate conditions impossible to satisfy
export class Company<TAddress extends Address & { new(): TAddress }> extends
    BaseEntity<number> {
         Income: number;
         Name: string;
         EmployeeCount: number;
         Address: Array<TAddress>;
  }

This is making the claim that TAddress is and Address and a constructor which returns TAddress.  Constructors don't return values.
Additionally, if you were to declare that TAddress has a parameterless constructor, you the generator should generate the Address entity compatible with the Company, but if you were to try to create a new Company().   This will fail.

Sorry for the late reply.
You're right, because we don't have a type system we can't easily add parameterless ctor constraint. Example you provided is my mistake, I believe I didn't think it through.
I'm removing new() constraint for now.

Published 1.3.12 NuGet.


Change serde_json::from_value to use pass-by-reference

If the function needs ownership, you should pass by value. If the function only needs a reference, you should pass by reference.
-- https://stackoverflow.com/a/64814149/342293
from_value doesn't need to own its parameter, so it should use pass-by-reference.

Is this not an obvious breaking change that would require a serde_json 2.0?

Is this not an obvious breaking change that would require a serde_json 2.0?

Hmm yes, any other parts that should also been updated? (Apologies if these should be obvious, still learning)

@GnomedDev Redone the fix so now from_value accepts both &Value and Value (maybe the latter can be deprecated?). New test for the &Value is on doctest (should I add more?)


How can i put images? on the buttons

You can put the images in the resource pack
example)

textures/items/apple
textures/items/apple_golden
textures/blocks/stone

You can put the images in the resource pack
example)

textures/items/apple
textures/items/apple_golden
textures/blocks/stone