DynamoDB Local HTTPS Error

I keep getting the following error when trying to run DynamoDB locally. Looks like the tests Dynamoose run just fine and run DynamoDB locally as well. So I'm not sure why it would be giving me this error here. Any ideas?
dynamoose:table error describing table +26s { NetworkingError: Protocol "http:" not supported. Expected "https:"
  at new ClientRequest (_http_client.js:55:11)
  at Object.exports.request (http.js:31:10)
  at handleRequest (/Code/node_modules/aws-sdk/lib/http/node.js:43:23)
  at executeSend (/Code/node_modules/aws-sdk/lib/event_listeners.js:241:29)
  at Request.SEND (/Code/node_modules/aws-sdk/lib/event_listeners.js:256:9)
  at Request.callListeners (/Code/node_modules/aws-sdk/lib/sequential_executor.js:101:18)
  at Request.emit (/Code/node_modules/aws-sdk/lib/sequential_executor.js:77:10)
  at Request.emit (/Code/node_modules/aws-sdk/lib/request.js:661:14)
  at Request.transition (/Code/node_modules/aws-sdk/lib/request.js:22:10)
  at AcceptorStateMachine.runTo (/Code/node_modules/aws-sdk/lib/state_machine.js:14:12)
  at /Code/node_modules/aws-sdk/lib/state_machine.js:26:10
  at Request.<anonymous> (/Code/node_modules/aws-sdk/lib/request.js:38:9)
  at Request.<anonymous> (/Code/node_modules/aws-sdk/lib/request.js:663:12)
  at Request.callListeners (/Code/node_modules/aws-sdk/lib/sequential_executor.js:115:18)
  at callNextListener (/Code/node_modules/aws-sdk/lib/sequential_executor.js:95:12)
  at /Code/node_modules/aws-sdk/lib/event_listeners.js:167:9
message: 'Protocol "http:" not supported. Expected "https:"',
code: 'NetworkingError',
region: 'us-west-2',
hostname: 'localhost',
retryable: true,
time: 2016-09-12T04:47:32.910Z }

Got the same error here. How do you fix it?

I got the very same issue and it turns out it was my httpOptions used to resolve https://github.com/aws/aws-sdk-js/issues/862 that caused the problems. These options set up an HTTPS agent with TLSv1, and as a side-effect apparently disables HTTP.
Details:
This does NOT work (gives the "http not supported" message):
new AWS.DynamoDB({
  endpoint: new AWS.Endpoint('http://localhost:8000'),
  httpOptions: {
    agent: new https.Agent({
      secureProtocol: "TLSv1_method",
      ciphers: "ALL"
    })
  }
});

but this works:
new AWS.DynamoDB({
  endpoint: new AWS.Endpoint('http://localhost:8000')
});

The sneaky thing was I had the httpOptions injected as default options in one central place to eliminate the 862 issue and didn't immediately realize what was happening - when setting up a DynamoDB object from a stand-alone node console everything was working fine! :)


Add Python hexagonal architecture example

hey @mehdihadeli - let me know if you're interested in merging this. There's also a blog post (linked from the repo) with a more in-depth explanation if that would be a better fit. No worries either way, but if this isn't a desired addition I can close the PR.

@alex-grover Hi alex,
Thanks for your contribution.
There are some other samples currently out here that has better quality.
Sorry about that  :)

sounds good, thanks!


[PROJECT] Contribution Flow Update

Overview
One year ago, we worked on an update for the contribution flow that included a new header, clearer contribution selection, and the platform tips section. At that time, we updated the existing components only (Header, contribution form, and FAQ sidebar) without modifying the layout:

Old version
After the first update

Now we have enough feedback and plans to bring this design to the next level, making sure we are communicating the breakdown of each transaction transparently, including the communication and behavior for the platform tips, and including some other improvements we have wanted to tackle recently (ex. #4169)
Owner
@Memo-Es
Secondary Developer on the project:
It will be decided after the kick-off call
Prioritization

Does this serve our mission
Totally, this flow is probably the most important we have in our platform. To be financially healthy and thrive, we must ensure we nail down how this checkout process works for our specific context and goals. As we advance, allowing projects to use the contribution flow as a tool for them to be successful in more and more flexible ways sounds like something we should maintain with the highest quality criteria.

Will this help to make us financially sustainable within a year?
Yes, it is essential to have the best flow possible to improve the money flowing in the platform.

Can this make us move faster?
If it has the success we need, it will allow us to have more resources and have faster feedback loops and release cycles.

Does this increase quality?
Yes, this project's main focus is to increase the quality of contributing using the platform capabilities.

Does this add technical debt?
I'm not sure

Is it feasible to build and maintain with our current team and runway?
Yes

What insight or research is this project based on?
#4268 #4169 #3897 https://github.com/opencollective/opencollective/issues/3438

Is this problem already solved elsewhere?
Yes, a couple of references have been popping out in previous discussions, some of the main beings:

Hello Asso - Reference
Gofundme
Donorbox

How will we measure our success? Do we have a baseline today that we can compare this against?
Ummm, amount of money being contributed? 🙂

How well do we understand the complexity of the problem, feature to be added, or user needs to be addressed?
We have been gathering feedback to improve our contribution flow along this time, which makes us confident to propose a new series of improvements.

What is the estimated timeframe for delivering this project?
I foresee three main chunks of work under this project:

Platform tips Design how we handle the communication for platform tips
Contribution form Redesign the contribution form to be more versatile and adaptative, including the issue to connect the contribution flow to a tier or project and, probably, including in the process the question of how it can be embedded in third-party websites to add to the white-labeling efforts
Layout How we display the summary and FAQs

Roadmap & Timeframe

[x] First discussion and scoping
[x] Design proposal for platform tips #4268
[x] Design proposal for tier redesign https://github.com/opencollective/opencollective/issues/4346
[x] Design proposal for new layout
[x] Ask for feedback and improve the design
[x] Wrap up final proposal

Release planning

[ ] TBD

Estimated delivery date

The final proposal should be up by the end of this sprint (Late June), we could spend a week of the next sprint to nail down production details and mobile versions.

Next steps

[x] Open up any appropriate project issues
[ ] Open a documentation issue, link it to this one
[ ] Open a release issue, link it to this one
[ ] Create a project board, add this issue to the description, add any issues created above

Project Closure

Close all relevant project issues
Open up issues for improvements
Post comm's according to comm's plan (most likely in release issue)
Post project screencast on documentation slack channel
Post project closure in newsletter slack channel
Celebrate!!

Prioritisation notes: looking to improve the design to better communicate platform tips, and the possiblity to connect a contribution with a tier or event. Small design update. Get to a design to implement either at the end of the sprint or following sprint.

@opencollective/design : Just a small suggestion; maybe we should include https://github.com/opencollective/opencollective/issues/4314 to the design as well since we are redesigning the contribution flow. 😄

Definition and follow-up document

Production-ready files

Components
Check-out page
Success

Link to figma file →

@Memo-Es From the design above, is my understanding correct that we're getting rid of the steps in the contribution flow to instead offer a single, one-page form? Do we have a design that includes the summary step (used for taxes) like in https://staging.opencollective.com/captainfact_io/contribute/tshirt-10355/checkout/summary?

Also @Memo-Es, can you confirm that this background on the success page is to be removed entirely?

The work for this issue is now separated into these smaller issues:

https://github.com/opencollective/opencollective/issues/4692
https://github.com/opencollective/opencollective/issues/4895
https://github.com/opencollective/opencollective/issues/4896
https://github.com/opencollective/opencollective/issues/4897
https://github.com/opencollective/opencollective/issues/4898

Waiting for the feedback in https://github.com/opencollective/opencollective/issues/4299#issuecomment-957503602 and https://github.com/opencollective/opencollective/issues/4299#issuecomment-957535716 two eventually create two others:

Revisit the layout of the success page (+ remove background)
Make the contribution flow a single-step process

@Betree

From the design above, is my understanding correct that we're getting rid of the steps in the contribution flow to instead offering a single, one-page form? Do we have a design that includes the summary step (used for taxes) like in https://staging.opencollective.com/captainfact_io/contribute/tshirt-10355/checkout/summary?

Do you think we can integrate the summary step you mention into the live summary featured on the check-out page?

You are correct to assume we're getting rid of the steps from the current flow for a single check-out page instead.

can you confirm that this background on the success page is to be removed entirely?

Yes, I confirm. I know we all love the watercolor texture backgrounds everywhere but

We will most likely see it as the default tier card hero image:

And 2. If the collective changed the hero image, it would be closer to 'their' brand, which is something I think we want for groups to be closer to their communities.

Do you think we can integrate the summary step you mention into the live summary featured on the check-out page?

@Memo-Es It's tricky because there are form fields in there; mostly for people to type in the tax id number (VAT number). I'm afraid they could miss it if we move it two the right, especially since the right column is pretty much hidden on mobile

It's tricky because there are form fields in there; mostly for people to type in the tax id number (VAT number). I'm afraid they could miss it if we move it two the right, especially since the right column is pretty much hidden on mobile

After doing some analysis today, we think this deserves further work, especially for mobile. So we are leaving it as a priority for next sprint
@Betree


Format .roc files with roc format

This is just the result of running roc format (Dec 4 version) in the repo root.

Let's hold off on this until https://github.com/roc-lang/basic-cli/pull/257 is merged because it may create a lot of conflicts

Yay, #257 seems to have run roc format, as there are now zero formatting discrepancies on main.


Feat: Favorite Devices

Please check if the PR fulfills these requirements

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Feat

What is the current behavior? (You can also link to an open issue here)
dojot/dojot#2412

What is the new behavior (if this is a feature change)?

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

Is there any issue related to this PR in other repository? (such as dojot/dojot)

Other information:

@LeonamMoura We might limit the amount of favorite devices, to avoid performance problems. Ex: max 50 favorite devices per user. What do you think?
I think that 50+ favorite devices does not make any sense.


[SMALLFIX] Add OutStreamBase

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

Please add unit tests to ensure that the number of bytes written is updated even when mShouldCacheCurrentBlock is false

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

@aaudiber  unit tests added. Please take another look.
Thanks

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

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

LGTM, thanks for the improvement!


Async Upload

Enhancement includes:

Fixed: Remote folder pre-cleanup.
Added: Upload files async to reduce locking of Visual Studio
Added: Removal of launch.json if it previously existed
Added: More output logging.
Update: Enhanced Output
Updated: Output Window drop-down title to "Linux Debugger" from "Remote Debugger"

Reference Links:

#2
#7
#14

Updated to v1.8.1


No services in advertisement

I've commented all Kotlin dependencies (not sure why it was there, there is no Kotlin code in the project) and managed to build the app for API 32.
I run it in my Pixel 4. I can see the pixel device, but no services advertised.
Could you please take a look?

yes, the project needed some updates to make it work on Android 10.....
I updated the project and everything seems to work as far as I can tell.
Let me know if it works for you

Hi Weliem,
I've re-cloned the project, it compiles without issues now.
However the problem still there.
in bluetoothctl (I am on Linux) I can see the device of my Android -  "Pixel 4a". But there are no services. I tried another Time Server example project before. It works.
But this one does not work though I see it calls bluetoothLeAdvertiser.startAdvertising(...
and enters into BluetoothServer.onAdvertisingStarted(...) callback.

When I try to connect to the server it enters BluetoothServer.onCentralConnected()
and then right away into BluetoothServer.onCentralDisconnected()

Please check it using apps like nrfConnect or LightBlue. When I run the example I definitely see an advertised service.

nrfConnect does not work in my Ubuntu. I see the Current Time Service advertised in LightBlue.
I am trying to figure out ....

There is a difference in what is advertised and what it 'has' as services.
The example app advertises the Heart Rate Service:
"0000180D-0000-1000-8000-00805f9b34fb"
But it also has the Device Information Service and Current Time service.
But those are not in the advertisement. The max size of the advertisement
is 31 bytes.
On Linux this is hard to distinguish because bluetoothctl doesn't show you
the 'raw' advertisement. It only shows what it has learned about the
device, either from the advertisement or from connecting to it and doing a
full service discovery.
What you could do in bluetoothctl is to set a discovery filter on the
HeartRate service UUID and then do a discovery. The device should then be
found.
On Sat, Jul 9, 2022 at 11:13 PM Mark Malakanov @.***>
wrote:

nrfConnect does not work in my Ubuntu. I see the Current Time Service
advertised in LightBlue.
I am trying to figure out ....
—
Reply to this email directly, view it on GitHub
https://github.com/weliem/bluetooth-server-example/issues/3#issuecomment-1179607498,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACT7HZZZAYV4UEYBGX3P5ALVTHTODANCNFSM53DUQEIA
.
You are receiving this because you commented.Message ID:
@.***>

I've made Current Time service advertised. But linux does not see it advertised. When I connect it can see it.
My watch (Nordic nRF52840 based) does not see advertised service too.
When it connects it can subscribe for notifications. But cannot receive notifications. The Blessed issues 2 notifications then it stucks.
This is weird. I've tried another code, made from this https://github.com/androidthings/sample-bluetooth-le-gattserver. It is simpler, it does not have queueing. But it works.
My watch sees advertised service and receives notifications.
I am completely puzzled. :(

Sounds weird....I use 2 Android phones and everything works totally fine.
try using 'sudo btmon' to monitor what is really going on on Linux. You can see the actual advertisement there....

This is what a raw advertisement looks like in btmon output:
> HCI Event: LE Meta Event (0x3e) plen 21                                                                #51 [hci0] 11.652482
      LE Advertising Report (0x02)
        Num reports: 1
        Event type: Connectable undirected - ADV_IND (0x00)
        Address type: Public (0x00)
        Address: C0:26:DA:13:38:FE (OUI C0-26-DA)
        Data length: 9
        Flags: 0x06
          LE General Discoverable Mode
          BR/EDR Not Supported
        16-bit Service UUIDs (partial): 2 entries
          Health Thermometer (0x1809)
          Device Information (0x180a)
        RSSI: -66 dBm (0xbe)

mine report shows:

HCI Event: LE Meta Event (0x3e) plen 28                                                                                #50 [hci0] 11.725181
LE Advertising Report (0x02)
Num reports: 1
Event type: Connectable undirected - ADV_IND (0x00)
Address type: Random (0x01)
Address: 4B:62:4D:EE:DE:8B (Resolvable)
Data length: 16
Flags: 0x02
LE General Discoverable Mode
Name (complete): Pixel 4a MM
RSSI: -74 dBm (0xb6)

HCI Event: LE Meta Event (0x3e) plen 19                                                                                #51 [hci0] 11.727175
LE Advertising Report (0x02)
Num reports: 1
Event type: Scan response - SCAN_RSP (0x04)
Address type: Random (0x01)
Address: 4B:62:4D:EE:DE:8B (Resolvable)
Data length: 7
TX power: -11 dBm
16-bit Service UUIDs (complete): 1 entry
Current Time Service (0x1805)
RSSI: -73 dBm (0xb7)

when I run android example time server it shows:

HCI Event: LE Meta Event (0x3e) plen 32                                                                                #62 [hci0] 14.770011
LE Advertising Report (0x02)
Num reports: 1
Event type: Connectable undirected - ADV_IND (0x00)
Address type: Random (0x01)
Address: 69:C0:11:E8:9A:28 (Resolvable)
Data length: 20
Flags: 0x02
LE General Discoverable Mode
Name (complete): Pixel 4a MM
16-bit Service UUIDs (complete): 1 entry
Current Time Service (0x1805)
RSSI: -77 dBm (0xb3)

HCI Event: LE Meta Event (0x3e) plen 12                                                                                #63 [hci0] 14.770995
LE Advertising Report (0x02)
Num reports: 1
Event type: Scan response - SCAN_RSP (0x04)
Address type: Random (0x01)
Address: 69:C0:11:E8:9A:28 (Resolvable)
Data length: 0
RSSI: -77 dBm (0xb3)

Ok, so that looks fine actually. Bluez combines the advertisement and scan response into 'one'.
I noticed in my code that I had actually swapped the advertisement and scanresponse. The correct order is:
peripheralManager.startAdvertising(advertiseSettings, advertiseData, scanResponse);
... that at least explains why you see the Service UUID in the scan response rather than the advertisement. So if you swap those 2 parameters you will get the same as your other example.

Good catch! It how shows service in ads. But now Name is in the scan.

HCI Event: LE Meta Event (0x3e) plen 22                                                                                #3 [hci0] 1.020584
LE Advertising Report (0x02)
Num reports: 1
Event type: Connectable undirected - ADV_IND (0x00)
Address type: Random (0x01)
Address: 7F:CE:F3:4E:E3:09 (Resolvable)
Data length: 10
Flags: 0x02
LE General Discoverable Mode
TX power: -11 dBm
16-bit Service UUIDs (complete): 1 entry
Current Time Service (0x1805)
RSSI: -71 dBm (0xb9)

HCI Event: LE Meta Event (0x3e) plen 25                                                                                #4 [hci0] 1.022571
LE Advertising Report (0x02)
Num reports: 1
Event type: Scan response - SCAN_RSP (0x04)
Address type: Random (0x01)
Address: 7F:CE:F3:4E:E3:09 (Resolvable)
Data length: 13
Name (complete): Pixel 4a MM
RSSI: -70 dBm (0xba)

Ok, mystery solved then?

Regarding why it is in the scan response: because the code puts it there!
        AdvertiseData advertiseData = new AdvertiseData.Builder()
                .setIncludeTxPowerLevel(true)
                .addServiceUuid(new ParcelUuid(serviceUUID))
                .build();

        AdvertiseData scanResponse = new AdvertiseData.Builder()
                .setIncludeDeviceName(true)
                .build();

You can move it to the advertiseData if you want....
Regarding why your watch can subscribe for notifications but is not receiving them......I don't know. Looks like a problem with your watch. Have a look at the logs to learn more...

#1. Yes! I've found how to add Name.
#2. :) The watch works well with other programs including the original example code from Android developers.

Hmm. In the code it all named 'notifications'.
Ok. I'll check the watch.
If there any way to set up the Blessed to send 'notifications', not  'indications', just in case.

According to the GATT standard, the Current Time Service should send indications. But if you really want to change that to notifications, then modify this line:
   private @NotNull final BluetoothGattCharacteristic currentTime = new BluetoothGattCharacteristic(CURRENT_TIME_CHARACTERISTIC_UUID, PROPERTY_READ | PROPERTY_INDICATE, PERMISSION_READ);

Yes! I've replaced PROPERTY_INDICATE with PROPERTY_NOTIFY and it works!
I am looking into the watch code now. (It is open programmable watch Bangle.js 2)

100% watch problem then....

Actually it is not. I've fixed "my" program (that is derived from the Android devs program) by adding processing for ENABLE_INDICATION_VALUE in AdvertiseCallback.onDescriptorWriteRequest
and it works!
    public void onDescriptorWriteRequest(BluetoothDevice device, int requestId,
                                         BluetoothGattDescriptor descriptor,
                                         boolean preparedWrite, boolean responseNeeded,
                                         int offset, byte[] value) {
      if (TimeProfile.CLIENT_CONFIG.equals(descriptor.getUuid())) {
        if (Arrays.equals(BluetoothGattDescriptor.ENABLE_NOTIFICATION_VALUE, value)) {
          Log.i(TAG, "Subscribe device to notifications: " + device);
          mRegisteredDevices.add(device);
        } else if (Arrays.equals(BluetoothGattDescriptor.ENABLE_INDICATION_VALUE, value)) {
          Log.i(TAG, "Subscribe device to indications: " + device);
          mRegisteredDevices.add(device);
        } else if (Arrays.equals(BluetoothGattDescriptor.DISABLE_NOTIFICATION_VALUE, value)) {
          Log.i(TAG, "Unsubscribe device from notifications: " + device);
          mRegisteredDevices.remove(device);
        }

        if (Arrays.equals(BluetoothGattDescriptor.ENABLE_INDICATION_VALUE, value)) {
          Log.i(TAG, "Subscribe device to notifications: " + device);
          mRegisteredDevices.add(device);
        } else if (Arrays.equals(BluetoothGattDescriptor.DISABLE_NOTIFICATION_VALUE, value)) {
          Log.i(TAG, "Unsubscribe device from notifications: " + device);
          mRegisteredDevices.remove(device);
        }

        if (responseNeeded) {
          mBluetoothGattServer.sendResponse(device,
            requestId,
            BluetoothGatt.GATT_SUCCESS,
            0,
            null);
        }
      } else {
        Log.w(TAG, "Unknown descriptor write request");
        if (responseNeeded) {
          mBluetoothGattServer.sendResponse(device,
            requestId,
            BluetoothGatt.GATT_FAILURE,
            0,
            null);
        }
      }

That doesn't make any difference, your still sending notifications...

No, that all doesn't matter...
The actual sending of a notification/indication is done by this call:
https://developer.android.com/reference/android/bluetooth/BluetoothGattServer#notifyCharacteristicChanged(android.bluetooth.BluetoothDevice, android.bluetooth.BluetoothGattCharacteristic, boolean)
...and you didn't change the code that makes that call. Hence you are still sending notifications.

I need to check the actual call, but first I've replaced PROPERTY_NOTIFY with PROPERTY_INDICATE and the program stopped working.
Then I've added
else if (Arrays.equals(BluetoothGattDescriptor.ENABLE_INDICATION_VALUE, value)) {           Log.i(TAG, "Subscribe device to indications: " + device);           mRegisteredDevices.add(device);         }
And it started working. But I will check the call.

Yep....it looks like the Bangle watch doesn't send the confirmations that are mandatory for indications.

You were right. The notifyCharacteristicChanged call had hardcoded confirmation=false .
I've changed that to be True when ENABLE_INDICATION_VALUE received in onDescriptorWriteRequest.
And the watch does not work now. I'll contact Bangle people...
Also, I've looked at GATT standard, Current Time should send notifications.
https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=292957
3.1.2 Characteristic Behavior – Notification
BLUETOOTH SERVICE SPECIFICATION Page 10 of 17
Current Time Service
3.1 Current Time
In this section, the term “local date and time” refers to the internal representation of date
and time which is maintained by the server device. During read or notify GATT
operations, the fields of the Current Time characteristic are set to values derived from
the local date and time. During write GATT operation, the local date and time is
optionally set to values derived from the fields of the Current Time characteristic.
3.1.1 Characteristic Behavior – Read
The Current Time characteristic returns the current date and time in the server device
when read by a client device using the GATT Read Characteristic Value sub-procedure. ...

seems you are correct! ....but you will sooner or later encounter Indications when using other services.

Yes, I know. The Current Time is just a test service for me. Actually I am working on "Location and Navigation" one.
THANKS for your help!

Hi Weliem,
Do you know an answer to my question?
Currently what happens - After connection established, Android calls notifyCharacteristicChanged and it returns True. The Watch receives the indication but does not respond with confirmation. BLE does not send next indications. However notifyCharacteristicChanged keeps returning True at each following call.
How to detect this situation?

What could be a strategy in such situation? Something like count issued indications and received confirmations. And after some difference reached, like 5 or 10 to disconnect the silent Central device?

In my opinion, not confirming indications means you are not implementing a basic mechanism of the Bluetooth spec. Not worth a workaround...

Hi Weliem, do you have an example how to process Write to a characteristic?

Not yet....I could expand the current time service with a 'write' option.
Basically:

When a write is requested, the callback onCharacteristicWrite is called. There you validate the payload and either reject or accept it.
Then the write is completed and onCharacteristicWriteCompleted is called.

updated the CurrentTimeService to support Write....


ActionBar hides first few lines

The ActionBar on the latest version of Bakareader Ex hides the first few lines of content, even when scrolled all the way up. Picture (this is on Nexus 5, Android Lollipop 5.1.1.):

Try to enable fullscreen for the time being.

https://github.com/calvinaquino/LNReader-Android/releases/tag/1.1.34-beta1

The main issue is fixed (assuming the bar on top is just a debug thing). However, when I toggle fullscreen and then tap to bring up the actionbar, the actionbar hides the first few lines again.

The greybox is debug thing, as for full screen mode, it will hide the first few line when the action bar shown (by design). It should be OK as the action bar will auto hide after few seconds.
For normal mode, it will not hide the first few lines (always below action bar).


"loaded" doesn't stop loading

v2.1.3 - for some reason the "loaded" emit isn't stopping it from continuing to load results down the page. I'm pretty sure this was working before, but I can't figure out why this is happening.
So, basically even though I haven't scrolled down, it keeps hitting my server and loading more results.  Here's my onInfinite function:
onInfinite () {
        api.tracks.get(PAGE_AMOUNT, this.tracks.length, tr => {
          console.log(`TRACKS: ${this.tracks.length}`)

          if (tr.length > 0) {
            this.tracks = this.tracks.concat(tr)
            if (tr.length < PAGE_AMOUNT) {
              this.$refs.infiniteLoading.$emit('$InfiniteLoading:complete')
            } else {
              this.$refs.infiniteLoading.$emit('$InfiniteLoading:loaded')
            }
          } else {
            this.$refs.infiniteLoading.$emit('$InfiniteLoading:complete')
          }
        })
      }

My template:
<template>

    <TrackItem v-for='(track, index) in tracks' :track='track' :index="index" :key='track.id'/>
    <infinite-loading :on-infinite="onInfinite" ref="infiniteLoading" spinner="waveDots"></infinite-loading>

</template>

I did put console logs in and it IS hitting that else where it sends the loaded emit.  I also changed it to :complete and it stopped calling at that point in the code.  So it is emitting, it just seems like its not caring - or for some reason it thinks that its scrolled down.
Anything I'm doing wrong? Or any ideas on how to debug it further?

Simplified the onInfinite, but same result:
 onInfinite () {
        api.tracks.get(PAGE_AMOUNT, this.tracks.length, tr => {
          if (tr.length > 0) {
            this.tracks = this.tracks.concat(tr)
            console.log(`TRACKS: ${this.tracks.length}`)
            this.$refs.infiniteLoading.$emit('$InfiniteLoading:loaded')
          } else {
            this.$refs.infiniteLoading.$emit('$InfiniteLoading:complete')
          }
        })
      }

I have changed the distance calculation method since v2.1.2, perhaps there has something wrong in the latest version if you previously using version earlier than v2.1.2, could you reproduce this problem on JSFiddle or other website like it?

When I use in nested component, I have same issue.

I'm sorry it was my misunderstanding. I used vue within Laravel, so it may be caused by laravel blade tempalte in my case :)

I currently experiencing this kind of issue, it creates multiple request during page loading I'm using Laravel 5.4 and axois. Below is my JS code
axios.get(config.NBLAPI + config.API.PLAYERSLEADERBOARD, {
    params: {
        splits: self.splits,
        playingPosition: self.playingPosition,
        competitionId: self.competitionId,
        page: self.pagination,
        sort: self.sort,
        order: self.order,
        limit: self.limit,
    }
}).then( (response) => {
    let data = response.data.data;
    let lastpage = response.data.last_page;

    if ( data.length ) {
        self.leagueLeaders = self.leagueLeaders.concat(data);
        self.$refs.infiniteLoading.$emit('$InfiniteLoading:loaded');
        self.pagination += 1;
        if(self.pagination == lastpage){
            self.$refs.infiniteLoading.$emit('$InfiniteLoading:complete');
            console.log(123);
        }
    }
    else {
        self.$refs.infiniteLoading.$emit('$InfiniteLoading:complete');
        if( url.includes('orderby') ) {
            let order = url.split('/').pop();
            let highlight = document.getElementsByClassName(order);
            _.forEach(highlight, (elem, key) => {
                elem.className += ' hightlight';
            });
        }
        else {
            let highlight = document.getElementsByClassName('points');
            _.forEach(highlight, (elem, key) => {
                elem.className += ' hightlight';
            });
        }
    }
});

I am also experiencing this issue. The event keeps on firing even if I am not scrolling. Its weird because I just followed the guide. I am using elementUI's table

@PenAndPapers @rodwin which version of Vue.js and this component do you use? If it is possible, please reproduce your problem on (JSFiddle)[https://jsfiddle.net], thanks!

I'm using "vue": "^2.0.1" and "axios": "^0.15.2".

I thought it was not compatible with axios so I tried to use "vue-resource": "^1.2.1", but still no luck

@PenAndPapers I think it was not caused by ajax lib, if you are using vue-router and enable the keep-alive feature, I recommend you to try to use the Vue.js v2.2.0 and later, refer issue.

I'm seeing this issue as well with VueJS 2.3.4. I'm also seeing it send out two events each time.

@PeachScript I've tried Vue.js v2.2.6 still not working, im not using vue router on my project

@mcmillion @PenAndPapers I need your help to find the real reason, could you reproduce this problem on JSFiddle? You can use setTimeout instead of ajax requests, thanks!

I have same issue (Vue 2.3) and  vue-infinite-loading sends event all time. Similar case to @DaveSanders.
I tried to create jsFiddle but I could not reproduce https://jsfiddle.net/vbabenko/fb6r82eb/1/
@PeachScript Could issue be related to css? I am using flexbox

To make matters worse (at least for finding the bug) its stopped doing it for me, and seems to be working fine now. I'm really not sure what I've changed.  I'm guessing its related to page structure, and I did move some things around when we redesigned the screen. I was going to go back to look at old commits to see if I can find the difference, but I've been slammed with crunch time here.

@DaveSanders
yeah, it's my assumption too, I am using  vue-infinite-loading on several projects and only one has such behavior. Looks like it sensitive to html/css structure.

@DaveSanders Ive run into the same problem when I nest 'infinite-loading' in divs while using window as the scroll parent. What I've noticed in the infiniteLoading.vue file is that the getCurrentDistance function does not account for the infinite-loading component to be further down the page then it is.
When i change the function to the following everything is resolved.
  function getCurrentDistance(elm, dir) {
    let distance;
    const scrollTop = isNaN(elm.scrollTop) ? elm.pageYOffset : elm.scrollTop;
    if (dir === 'top') {
      distance = scrollTop;
    } else {
      let scrollElmHeight;
      if (elm === window) {
        scrollElmHeight = window.innerHeight;
        distance = this.$el.getBoundingClientRect().top - scrollTop - scrollElmHeight - (elm.offsetTop || 0);
      } else {
        scrollElmHeight = elm.getBoundingClientRect().height;
        distance = this.$el.offsetTop - scrollTop - scrollElmHeight - (elm.offsetTop || 0);
      }
    }
    return distance;
  }

@vbabenko I'm not sure how this issue is caused, maybe related to CSS/HTML. The tricky place is, we have no way to reproduce it, so it is difficult to find the real reason...

@DaveSanders waiting for your good news, thank you very much!

@vbabenko is there has some specials in your problem project? Such as the different scroll container, the different front-end router, the different nested HTML structure, etc.

I'm having this issue again today too. In my case I think its because the component that have infiniteLoading init and running is hidden and it keeps loading till I open it.
Here is my setup: I have a toolbar tab component (using Bootstrap for HTML&CSS):

                 <tab-layout></tab-layout>                 <tab-bkgrnd></tab-bkgrnd>

The  component is hidden by default and that is where I have infiniteLoading setup and running. When I first access the page infiniteLoading keeps loading forever until I click on tab-bkgrnd. If I change  to open by default then its only load once and working as expected when scrolling down.

@duyhung85 yep, because the getBoundingClientRect method will all return 0 if the element was hidden, so this plugin cannot calculate correct distance if it was hidden, perhaps you can try v-if to solve it.

@PeachScript I think the issue appear when styles wrote in bad manner, like this
https://jsfiddle.net/vbabenko/fb6r82eb/7/
css class 'top' has overflow-x: hidden
css class 'deploy' has overflow: auto
when you comment overflow: auto in last class - everything will work. When I have time I will try debug source file

@vbabenko it's a very useful information, thank you very much!

@DaveSanders @PenAndPapers @rodwin @vbabenko @adamyarger @mcmillion hi everyone, sorry to bother, could you tell me does your scroll container has a fixed height?

@PeachScript, it's okay, thank you for your library, it's awesome.
In my case - no (everything positioning by flexbox), my scroll container has flex-grow: 1; overflow: auto;

@PeachScript, no im using the window to scroll.  I believe i may have been using an older version of the component before when when offsetTop was being used to measure the distance, it now looks like getBoundingClientRect().top is being used. So everything works as expected now.

@vbabenko thanks for your appreciation! This plugin will calculate distance through the getBoundingClientRect().top of infinite-loading element and the getBoundingClientRect().bottom of scroll container, the distance is expected when the top - bottom <= the passing distance, but if the scroll container has automatic height, the distance will always be expected...
So I think should to add a additional condition to process it, I will as soon as possible.

@adamyarger got it, thanks for your feedback!
Best regards.

@vbabenko @Akari1987 I have encountered a thorny problem. For now, this plugin will find the closest parent node that has overflow-y: auto CSS style as the scroll container, but in the example that provided by @vbabenko , the closest overflow-y: auto parent node is not the real scroll container, so I have planed to check the height property at the same time, if the element has overflow-y: auto, and it's height property not be auto or it's max-height property not be none, auto or 0px, it should be the real scroll container. The problem is, I did not found a better way to detect whether a element's height property is auto, do you have any idea?

@PeachScript yeah, it's not easy solution. I will think about other ideas. But for now, I cannot suggest better option. @PeachScript what do you think if you add extra properties like settings where user can manually provide css selector to scroll container? By default it will work with your approach and in rare case when something goes wrong a user can provide container selector

@PeachScript ｍｍｍ... I do not have any idea at the moment. If I hit on good idea, I'll write here.

@vbabenko for the manual scroll container, we can easily do it now:
mounted() {
  this.$refs.infiniteLoading.scrollParent = this.$refs.yourManuallyContainer;
}

But the key point is, how the users know the scroll container is wrong 😞

@Akari1987 thanks, waiting for your good news!

Hi all participants @DaveSanders @Akari1987 @PenAndPapers @rodwin @mcmillion @vbabenko @adamyarger @duyhung85 , I have no idea about how to find the real scroll parent, but this issue has been created for 2 months, so I plan to add a special property to solve it, looks like this:

    <infinite-loading force-use-infinite-wrapper="true"></infinite-loading>

The special property called force-use-infinite-wrapper, it will find the closest parent node which has infinite-wrapper attribute, and it will ignore other parent node, even if some parents has overflow-y: auto|scroll CSS styles.
What do you think about the solution? And how about the attribute name force-use-infinite-wrapper?
Best regards.

Sounds good. It would be nice to update documentation, this property is not obvious for those who doesn't aware about this issue

@vbabenko perhaps we can observe the number of times when this component be trigger, and we can throw a warning if it was triggered many times in a short time, do you think it is feasible?

I dunno but I have been testing around, what i have noticed is that first you have to set the height of your body to auto then this listen will do a great work:
window.onscroll = function(ev) {
    if ((window.innerHeight + window.pageYOffset) >= document.body.offsetHeight) {
        // scroll hits the floor, then you can call the function
    }
};

Sorry, I don't know what do you want to solve...Is your solution related to this issue?

yes it is, when ever I scroll down once the loading never stops and keeps calling my function to the infinite, so I had to change the function on the scroll listener and it worked now.

@JefferyHus thanks for your reply! Perhaps there are many reasons for this issue, I need your help, could you reproduce your problem on JSFiddle?

@PeachScript emmm, I will try even tho im not sure if it will reproduce again but will also put the solution I did, once im free

Hi everyone, v2.2.0 has been released, include the force-use-infinite-wrapper feature, you can try it now, please feedback to here if you find any question, thanks :D

@PeachScript thanks a lot for force-use-infinite-wrapper! My current problem with it though is that I cannot chance this property during runtime. I have a responsive design in which I only want this behavior in portrait mode. What I'm trying is :force-use-infinite-wrapper="!landscape"

@junpls this component will only search scroll wrapper when it is initialized, what is the situation that you need to change scroll wrapper during runtime?

@PeachScript this is what I'm trying:
(It should say "infinite" on the left site as well)

@junpls I see, thanks for your explanation, I will add responsive support the force-use-infinite-wrapper property in the next version.

This works for me:
      ```

const scrollY = window.scrollY
const visible = document.documentElement.clientHeight
const pageHeight = document.documentElement.scrollHeight
const bottomOfPage = visible + scrollY >= pageHeight
      if (bottomOfPage || pageHeight < visible) {
        this.fetchPosts()
        console.log('At the bottom');
      }

Ref: https://scotch.io/tutorials/simple-asynchronous-infinite-scroll-with-vue-watchers

v2.1.3 - for some reason the "loaded" emit isn't stopping it from continuing to load results down the page. I'm pretty sure this was working before, but I can't figure out why this is happening.
So, basically even though I haven't scrolled down, it keeps hitting my server and loading more results. Here's my onInfinite function:
onInfinite () {
        api.tracks.get(PAGE_AMOUNT, this.tracks.length, tr => {
          console.log(`TRACKS: ${this.tracks.length}`)

          if (tr.length > 0) {
            this.tracks = this.tracks.concat(tr)
            if (tr.length < PAGE_AMOUNT) {
              this.$refs.infiniteLoading.$emit('$InfiniteLoading:complete')
            } else {
              this.$refs.infiniteLoading.$emit('$InfiniteLoading:loaded')
            }
          } else {
            this.$refs.infiniteLoading.$emit('$InfiniteLoading:complete')
          }
        })
      }

My template:
<template>

    <TrackItem v-for='(track, index) in tracks' :track='track' :index="index" :key='track.id'/>
    <infinite-loading :on-infinite="onInfinite" ref="infiniteLoading" spinner="waveDots"></infinite-loading>

</template>

I did put console logs in and it IS hitting that else where it sends the loaded emit. I also changed it to :complete and it stopped calling at that point in the code. So it is emitting, it just seems like its not caring - or for some reason it thinks that its scrolled down.
Anything I'm doing wrong? Or any ideas on how to debug it further?

please add
infinite-wrapper attriubte
and         :force-use-infinite-wrapper="true"
<infinite-loading
@infinite="infiniteHandler"
:identifier="indetifyId"
:force-use-infinite-wrapper="true"
spinner="circles">

<TrackItem v-for='(track, index) in tracks' :track='track' :index="index" :key='track.id'

infinite-wrapper
/>

v2.1.3 - for some reason the "loaded" emit isn't stopping it from continuing to load results down the page. I'm pretty sure this was working before, but I can't figure out why this is happening.
So, basically even though I haven't scrolled down, it keeps hitting my server and loading more results. Here's my onInfinite function:
onInfinite () {
        api.tracks.get(PAGE_AMOUNT, this.tracks.length, tr => {
          console.log(`TRACKS: ${this.tracks.length}`)

          if (tr.length > 0) {
            this.tracks = this.tracks.concat(tr)
            if (tr.length < PAGE_AMOUNT) {
              this.$refs.infiniteLoading.$emit('$InfiniteLoading:complete')
            } else {
              this.$refs.infiniteLoading.$emit('$InfiniteLoading:loaded')
            }
          } else {
            this.$refs.infiniteLoading.$emit('$InfiniteLoading:complete')
          }
        })
      }

My template:
<template>

    <TrackItem v-for='(track, index) in tracks' :track='track' :index="index" :key='track.id'/>
    <infinite-loading :on-infinite="onInfinite" ref="infiniteLoading" spinner="waveDots"></infinite-loading>

</template>

I did put console logs in and it IS hitting that else where it sends the loaded emit. I also changed it to :complete and it stopped calling at that point in the code. So it is emitting, it just seems like its not caring - or for some reason it thinks that its scrolled down.
Anything I'm doing wrong? Or any ideas on how to debug it further?

please add
infinite-wrapper attriubte
and         :force-use-infinite-wrapper="true"
<infinite-loading
@infinite="infiniteHandler"
:identifier="indetifyId"
:force-use-infinite-wrapper="true"
spinner="circles">

<TrackItem v-for='(track, index) in tracks' :track='track' :index="index" :key='track.id'

infinite-wrapper
/>

I also experiencing this issue, but not about CSS/html ,it was coursed by the array increase method, when i increase array like this
Array.prototype.push.apply(this.infiniteArticles.content, newArticles)
i get uncontrol infinite loading, and it work well like this
this.infiniteArticles.content = this.infiniteArticles.content.concat(newArticles.content)

There will be one more case that causes calling handler multiple time.
Here is my handler. I've added a filter statement to make sure there are no duplicated records.
infiniteHandler($state) {
  axios.get(api, {
    params: {
      page: this.page,
    },
  }).then(({ data }) => {
    if (data.hits.length) {
      this.page += 1;
      const newHits = data.hits.filter((hit) =>
        this.list.every((item) => item.id !== hit.id)
      );
      this.list.push(...newHits);
      $state.loaded();
    } else {
      $state.complete();
    }
  });
}

The problem comes when the data.hits.length > 0 and newHits = [], so the loaded() method never calls.


linuxPackages<=4.9: mark broken on aarch64

Motivation for this change
closes: #122281
ZHF: #122042
https://hydra.nixos.org/eval/1668552?filter=cryptodev&compare=1668435&full=#tabs-still-fail
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

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

been a few days, merging


[FLINK-17805][networ] Fix ArrayIndexOutOfBound for rotated input gate indexes

It's possible that indexes of passed InputGates are not monotonic - that left input has higher input gate index. This commit fixes an ArrayIndexOutOfBound caused by this.
Verifying this change
This PR adds a dedicated unit test.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

Test failure is unrelated and fixed on more recent master by some commit (don't know which)


ng-toolkit/universal installation issues

When i run command 'ng add @ng-toolkit/universal', following error occurs
Installing packages for tooling via npm.
ERROR: Path "/local.js" already exist.
ERROR: If you think that this error shouldn't occur, please fill up bug report here: https://github.com/maciejtreder/ng-toolkit/issues/new
INFO: stacktrace has been sent to tracking system.
Nothing to be done.

@BoDaly Which version of CLI are you using?

@maciejtreder
Angular CLI: 6.1.2
Node: 10.7.0
OS: win32 x64
Angular: 6.1.1

Closing now for housekeeping purposes.


no enviroment are shown in the lazyvim config

Hi I am still new to NeoVim sorry if I asked sth very stupid
here are my setting plugin inside lazyvim on mac
this config are copy from official docs
return {
  "linux-cultist/venv-selector.nvim",
  cmd = "VenvSelect",
  opts = function(_, opts)
    if LazyVim.has("nvim-dap-python") then
      opts.dap_enabled = true
    end
    return vim.tbl_deep_extend("force", opts, {
      -- name = {
      --   "venv",
      --   ".venv",
      --   "env",
      --   ".env",
      -- },
      anaconda_base_path = "/opt/homebrew/Caskroom/miniconda/base",
      anaconda_envs_path = "/opt/homebrew/Caskroom/miniconda/base/envs",
      auto_refresh = true,
    })
  end,
  keys = { { "<leader>cv", "<cmd>:VenvSelect<cr>", desc = "Select VirtualEnv" } },
}

i have fd install on my machine with
brew install fd
I tried many different config but still end up with nothing

even if I create .venv directly under the current dir, still there is nothing showing up.
Please help me with my config or is there more example.

VenvSelect:
{
  anaconda = {},
  anaconda_base_path = "/opt/homebrew/Caskroom/miniconda/base",
  anaconda_envs_path = "/opt/homebrew/Caskroom/miniconda/base/envs",
  auto_refresh = true,
  cache_dir = "/Users/polo/.cache/venv-selector/",
  cache_file = "/Users/polo/.cache/venv-selector/venvs.json",
  changed_venv_hooks = { <function 1>, <function 2>, <function 3>, <function 4> },
  dap_enabled = false,
  enable_debug_output = true,
  hatch_path = "~/Library/Application/Support/hatch/env/virtual",
  name = "venv",
  notify_user_on_activate = true,
  parents = 2,
  pdm_path = "~/.local/share/pdm/venvs",
  pipenv_path = "~/.local/share/virtualenvs",
  poetry_path = "~/Library/Caches/pypoetry/virtualenvs",
  pyenv_path = "~/.pyenv/versions",
  search = true,
  search_venv_managers = true,
  search_workspace = true,
  venvwrapper_path = "~/.virtualenvs"
}
VenvSelect: Setting fd_binary_name to 'fd' since it was found on system.
VenvSelect: Telescope path: /Users/polo
VenvSelect: Looking for parent venvs in '/' using the following parameters:
VenvSelect:
{ "--absolute-path", "--color", "never", "-E", "/proc", "-HItd", "^venv$", "/" }
VenvSelect: Found venv in parent search: /opt/homebrew/Caskroom/miniforge/base/lib/python3.10/venv/
VenvSelect: Found venv in parent search: /opt/homebrew/Caskroom/miniforge/base/envs/ultron/lib/python3.12/venv/
VenvSelect: Found venv in parent search: /usr/local/mysql-shell-8.0.33-macos13-arm64/lib/mysqlsh/lib/python3.10/venv/
VenvSelect: Found venv in parent search<EMAIL_ADDRESS>VenvSelect: Found venv in parent search: /opt/homebrew/Caskroom/miniforge/base/pkgs/python-3.12.3-h4a7b5fc_0_cpython/lib/python3.12/venv/
VenvSelect: Found venv in parent search: /opt/homebrew/Caskroom/miniforge/base/pkgs/python-3.10.14-h2469fbe_0_cpython/lib/python3.10/venv/
VenvSelect: Found venv in parent search<EMAIL_ADDRESS>VenvSelect: Found venv in parent search: /System/Volumes/Data/Library/Developer/CommandLineTools/Library/Frameworks/Python3.framework/Versions/3.9/lib/python3.9/venv/
VenvSelect: Found venv in parent search: /System/Volumes/Data/usr/local/mysql-shell-8.0.33-macos13-arm64/lib/mysqlsh/lib/python3.10/venv/
VenvSelect: Found venv in parent search<EMAIL_ADDRESS>...

Seems like it does found the env, but does now show in the result?

@linux-cultist  I think it's because of my telescope config
Also my conda env are listing the wrong path (which not even exist) /opt/homebrew/Caskroom/miniforge/base/lib/python3.10/venv/
I think i will start by only using poetry and only create .venv in the project dir, that will be a easy fix for me, thanks!

You can try the regexp branch of the plugin I'm working on too. The current code has grown quite complicated because it was never intended to support all those venv managers from the start, so there is a lot of conditional statements and complicated logic in the current code base. And bugs too.
The rewrite in the regexp branch is quite different since it's designed from the start to support your own queries if the built in ones are not finding things. And it's a lot simpler code because it doesn't try to guess what you want. :)
You can try that branch if you want. It's using a different much simpler config too.

Here is an example if you want to try the regexp branch:
Configuration for lazy.nvim:
return {
  "linux-cultist/venv-selector.nvim",
    dependencies = {
      "neovim/nvim-lspconfig",
      "mfussenegger/nvim-dap", "mfussenegger/nvim-dap-python", --optional
      { "nvim-telescope/telescope.nvim", branch = "0.1.x", dependencies = { "nvim-lua/plenary.nvim" } },
    },
  lazy = false,
  branch = "regexp", -- This is the regexp branch, use this until its merged with the main branch later
  config = function()
      require("venv-selector").setup()
    end,
    keys = {
      { ",v", "<cmd>VenvSelect<cr>" },
    },
},

The plugin will look in /opt/anaconda/bin and ~/.conda/envs for python venvs automatically but if you have them in another location, you can create two searches that replaces the build-in ones:
      require("venv-selector").setup {
        settings = {
          search = {
                anaconda_envs = {
                    command = "fd bin/python$ ~/.conda/envs --full-path --color never -E /proc" -- change path here to your anaconda envs
                },
                anaconda_base = {
                    command = "fd /python$ /opt/anaconda/bin --full-path --color never -E /proc", -- change path here to your anaconda base
                },
          },
        },
      }

Just run the fd commands on the command line first to make sure they list only your python venvs, otherwise you have to slightly change the regexp or alter the fd command to exclude paths. The end result needs to be absolute paths to pythons:
/home/cado/.conda/envs/conda1/bin/python
/opt/anaconda/bin/python

Im closing this since its probably a telescope configuration issue but hope you try the new version. It just works a lot better. :)

Hi, I am facing the same error here.
I am using Mac mini M2, installing miniconda with brew and using the LazyVim distro. Running cmd conda env list shows the following:
# conda environments:
#
base * /opt/homebrew/Caskroom/miniconda/base
rnn /opt/homebrew/Caskroom/miniconda/base/envs/rnn

Modifying the plugin spec as follows might fix this:
  {
    "linux-cultist/venv-selector.nvim,
    config = function(_, _)
      require("venv-selector").setup({
        settings = {
          search = {
            anaconda_envs = {
              command = "fd bin/python$ /opt/homebrew/Caskroom/miniconda/base --full-path --color never -E /proc", -- change path here to your anaconda envs
            },
            anaconda_base = {
              command = "fd /python$ /opt/homebrew/Caskroom/miniconda/base/envs --full-path --color never -E /proc", -- change path here to your anaconda base
            },
          },
        },
      })
    end,
  },

I leave this snippet to those who have faced the same error and seeking a solution.
BTY, thanks to the NICE plugin~

Thanks for adding it to the thread :)
Probably should add some section to the Readme with example configs for different platforms... Maybe in the future. :)


Add Tests

The purpose of each codemod is pretty opaque, so we can both test the modification and get some built-in examples if we're able to build out a test suite.

Yup - @cpojer was on my case about this as well. We should take the scaffolding from his codemod repos, then use the changes to our tests as fixtures.

I've had success running tests with the following structure: https://github.com/joshblack/codemods/tree/master/test just adding in folders for tests as developers makes issues on the repo. Any thoughts? Would love to help contribute to this repo and adding tests seems like a good start.

@joshblack Yeah, definitely! If you want to open a PR, that would be super duper helpful.

The setup from https://github.com/reactjs/react-codemod can literally be copy and pasted. A bunch of other forks use the same structure, it would be nice to keep some sort of consistency.

Sounds good, consistency is important.

Do we have example project files that the mods were ran against that I can start filling the test cases out with?

@joshblack The tests and examples on history and React Router, actually.

Perfect, thanks for the heads up!

Just wanted to give a heads up, currently working on this here: https://github.com/joshblack/rackt-codemod just have to add the history tests and I'll open up a PR.

Awesome!


NullPointerException thrown when AssetLoader.getDependencies returns null

Using latest nightlies, AssetManager now crashes with NullPointerException when attempting to load assets with no dependencies, using custom loaders.
The cause is here:
https://github.com/libgdx/libgdx/commit/491f2646309e3d71f41ca7dbc8e02b5e09ba98d3#diff-d0ba77a9cde8d11730d759b7be8e8df8R101
As you can see, dependencies == null. But then, in removeDuplicates, the code is trying to access array.ordered which causes the NPE.
The code probably shouldn't even be trying to do anything with dependencies since it's null.

Great catch, thanks!


board: acrn : config for the flash runner

Add config for acrn using sanitycheck automation.
For zephyr ACRN visualization testing, we need to add this file.
Signed-off-by: Enjiax Mai<EMAIL_ADDRESS>

Simply change. It looks good to me.

@andrewboie could you take look at it? We need it for testing ACRN platform.

@andrewboie @nashif  excuse me, could you please help to check this PR first, this blocks our automated zephyr + ACRN testing. And this modification is simply adding a ACRN board.cmake file . Thank you!


Default Dashboard: Google Ads Cost per Click (CPC)

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/1736
Originally created by @dmor on 2020-02-13 21:03:08

Definition of Cost per Click (CPC):

The average cost of each inline link click.

Data Label: CPC (Cost per Link Click)
Calculation: Amount Spent divided by Clicks, bounded by some time period
MVC Scope: This will only be at the account level.
https://developers.google.com/adwords/api/docs/appendix/reports/ad-performance-report#averagecpc

View 5 previous comments from the original issue on GitLab


Naive AES: Fix decryption mode

I wasn't trying to follow the OpenTitan version with this implementation, but you're right it makes sense to follow their decryption form, I'll update this PR.


Add Support for ARM64

Description

Fixes #570 Add ARM64 Support

Nuget packages updated to versions which support arm64
ARM64 configuration added

Motivation and Context

The current Xaml controls gallery doesnt support Arm64, which is inconvenient for arm device users and sends a poor message to developers.
Fixes #570 Add ARM64 Support
How Has This Been Tested?
This has been built for ARM64, and a test .msix package was built. This was then installed on an arm64 device (Surface Pro X) and ran correctly.
Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

@Samuel12321 if you are still interested in fixing this, please let me know and I'll leave this to you :)

@Samuel12321 if you are still interested in fixing this, please let me know and I'll leave this to you :)

Hi @chingucoding , happy to create a new pr provided it actually gets merged this time :)
new PR: https://github.com/microsoft/WinUI-Gallery/pull/1014


Nix, package manager migration. Defaults to nixpkgs as specified at nix installation.

The main reason about this migration is explained at 7891ace. It resumes to point out we need a way to provide a stable/maintained development environtment. In that commit, too, explains a tentative roadmap, if this PR gets merge.
At commit 52b06c8, added nix-related information to the README.md
Commits 7b10016 and aa022ad are the formatter and linting process. I would like to point out that biome has partial support to HTML and supersets, but that can be easily fix using dprint, a rust-based formatter with integrations; so we use biome just as linter.
Linter, formatter, and related tools will get managed in their own PR.
Setting up a task runner -- I'm debating wether to use make, as God intented, or just a rust-based make-inspired alternative, as the young lads out there do.

Hi Brayen!
I have these problems when running nix-shell:

I was testing on arch linux and debian

Hi, @IvanM9!, thank you for your input.
The problem is nix-shell is looking for  channel; that's, the registry of nix and nix-related packages -- this is like adding a repo in Debian -- but is not declared.
At cf4d5f8, I tagged the lastes stable  release at nix-shell, now this should work as expected.
Sure, this can be fixed at user side, adding channels using nix-channel command, but we intend for this to be a plug-and-play setting.
Let me know if this helps you!,
Brayen

This is a great resource on how to install nix in imperative distribution:
https://nix-community.github.io/nix-installers/
It supports deb, pacman and rpm. We should consider writing a script for this to be setup.

Works, but still sometimes there are problems with the daemon :(

Yes, that may be a problem with Debian installation.
As soon as I get to office, I'll troubleshoot it back.
Can you access to biome and related development tools?
Thank you!,
Brayen
El mar., 10 de diciembre de 2024 11:15 p. m., Iván Manzaba <
@.***> escribió:

Works, but still sometimes there are problems with the daemon :(
Screenshot.from.2024-12-10.21-12-44.png (view on web)
https://github.com/user-attachments/assets/cb63668c-dacc-458c-813f-92cfdc4e043d
—
Reply to this email directly, view it on GitHub
https://github.com/Ecuador-In-Tech/web/pull/20#issuecomment-2533466859,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A3YSTNCRXLPAJM7MSIYXQOL2E6N4VAVCNFSM6AAAAABTKE4MUCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZTGQ3DMOBVHE
.
You are receiving this because you were assigned.Message ID:
@.***>

Yes, works

I haven't troubleshot problem in debian installation -- I know Arch Linux and Void Linux repo install do okay, I've done it --
I'll update README and point out potential problems / solutions. And I don't like it, but I'll make more obvious that upstream install -- a curl into sh pipe X.X -- would be best bet for anyone not having native package manager support for nix.

I have thunk deeply about this. I'll dockerize -- throught podman! -- nix workflow, for best compatibility... But that'll get done in another PR.

I'm using distrobox to troubleshoot debian nix problem.
I haven't been able to reproduce problem with nix-daemon as @IvanM9  has pointed out.
(ins)📦[bjgavilanes@debian www]$ nix-shell
unpacking 'https://github.com/NixOS/nixpkgs/tarball/nixos-24.11' into the Git cache...
these 44 paths will be fetched (49.76 MiB download, 235.27 MiB unpacked):
  /nix/store/nrl5m466dwdscvavf1nqzdnqhszjyy9n-acl-2.3.2
  /nix/store/nmq6s9l9zlym3qjx76zzrqbp05a63y90-attr-2.5.2
  /nix/store/p6k7xp1lsfmbdd731mlglrdj2d66mr82-bash-5.2p37
  /nix/store/2bpqfzq78d0li8hn21flnpydnmkngw3k-biome-1.9.4
  /nix/store/hl3iw85v12gh9mwgvr9yfgjgy0rk81hb-bzip2-1.0.8

Altought, reading history log shows
  489  sudo apt-get update
# (...)
  495  sudo apt install nix-setup-systemd

That I did and apt-get and then apt invocation. I don't believe this is the problem, but will try to install nix as documented in the README.
For the record, I'm testing in debian-unstable
distrobox list
ID           | NAME                 | STATUS             | IMAGE
6c613be53703 | debian               | Up 35 minutes      | docker.io/library/debian:unstable

Using distrobox
distrobox --version
distrobox: 1.8.0

So, I remove nix-setup-systemd and then sudo apt autoremove
(ins)📦[bjgavilanes@debian ~]$ sudo apt remove nix-setup-systemd
The following packages were automatically installed and are no longer required:
  bash-static             libdbi-perl
  libarchive13t64         liblowdown1
  libboost-context1.83.0  libsodium23
  libcpuid17              libwww-curl-perl
  libdbd-sqlite3-perl     nix-bin
Use 'sudo apt autoremove' to remove them.

REMOVING:
  nix-setup-systemd

Summary:
  Upgrading: 0, Installing: 0, Removing: 1, Not Upgrading: 5
  Freed space: 36.9 kB

Continue? [Y/n]
(ins)📦[bjgavilanes@debian ~]$ sudo apt autoremove
REMOVING:
  bash-static      libboost-context1.83.0  libdbd-sqlite3-perl  liblowdown1  libwww-curl-perl
  libarchive13t64  libcpuid17              libdbi-perl          libsodium23
# (...)

And then perform apt-get as documented in README. I worked, as previously reported.
I began to think that maybe it did work because distrobox was communicating with my host-machine's nix-daemon.service, but no!
● nix-daemon.service - Nix Daemon
     Loaded: loaded (/etc/systemd/system/nix-daemon.service; linked; preset: ignored)
    Drop-In: /nix/store/qxahi9pkgfdanxj2bfswvn44cx9wk21v-system-units/nix-daemon.service.d
             └─overrides.conf
     Active: active (running) since Wed 2024-12-25 03:03:13 -03; 1 day 19h ago
 Invocation: 276ff05ef67b4ef7b77d94f1b9c202a6
TriggeredBy: ● nix-daemon.socket
       Docs: man:nix-daemon
             https://nixos.org/manual
   Main PID: 1726 (nix-daemon)
         IP: 330.3M in, 4.1M out
         IO: 358M read, 1.7G written
      Tasks: 2 (limit: 1048576)
     Memory: 607.9M (peak: 870.2M swap: 3.4M swap peak: 3.5M)
        CPU: 2min 5.834s
     CGroup: /system.slice/nix-daemon.service
             └─1726 nix-daemon --daemon

Dec 26 15:04:41 natja nix-daemon[1726]: accepted connection from pid 130001
# (...)
Dec 26 22:42:18 natja nix-daemon[1726]: accepted connection from pid 190377, user bjgavilanes (trusted)

As last resource, I can troubleshoot in a Debian VM... However, I would advise to reinstall nix. Preferably, using upstream method IF local package manager installation still doesn't work.

According to this thread you can fix problem with nix-daemon.socket by adding your user to the nix-users group. I added that e information to the README, too.

Still having problems :(
I tried again on Arch and Debian

On Mon Dec 30, 2024 at 2:14 PM -03, Iván Manzaba wrote:

Still having problems :(
I tried again on Arch and Debian

Thank you for your assistance. I'll troubleshoot in a VM ASAP.
I'll continue development for our tooling at #21 PR. I'll update README to globally install biome and dprint. Also, I'll began a make scheme from that PR.
Thanks!,
Brayen


Unable to compile app after upgrading to 1.7.2

I am getting the following error after running npx react-native run-ios --simulator 'iPhone 12'
The following build commands failed:
	CompileC /Users/dev/Library/Developer/Xcode/DerivedData/BrightID-eratlntujddnpaewlhvxbkufgvjj/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/RNCPushNotificationIOS.build/Objects-normal/x86_64/RNCPushNotificationIOS.o<EMAIL_ADDRESS>normal x86_64 objective-c com.apple.compilers.llvm.clang.1_0.compiler
(1 failure)

unable to compile and build my app with v1.7.2

I was also getting same issue in 1.7.2, Now I downgraded on 1.7.1 version and Now working fine.

I am getting the following error after running npx react-native run-ios --simulator 'iPhone 12'
The following build commands failed:
	CompileC /Users/dev/Library/Developer/Xcode/DerivedData/BrightID-eratlntujddnpaewlhvxbkufgvjj/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/RNCPushNotificationIOS.build/Objects-normal/x86_64/RNCPushNotificationIOS.o<EMAIL_ADDRESS>normal x86_64 objective-c com.apple.compilers.llvm.clang.1_0.compiler
(1 failure)

unable to compile and build my app with v1.7.2

Same issue

https://github.com/react-native-push-notification-ios/push-notification-ios/commit/ba6bc11f862ac79f78c8442b9d2965cc942aef26#comments
same for me

Can you remove the version, seems like this is an inner dep for other projects and its causing issues

Sorry for all the trouble caused. I've published v1.7.3 that will fix the issue.


workflow test

If the checks fail, then that means it's working

yay the github workflow works :D


Document size calculation for DynamoDb

Can someone point me to an explanation of exactly how document size is determined for DynamoDB?
In addition, it would be a great feature if Amazon.DyanmoDBv2.DocumentModel.Document could provide a property, or an extension method, that could do this calculation - allow us to determine whether or not the payload needs to be S3'd. If I fully understood the calculation, I would be happy to take a shot at a PR for this.
Thanks for your help and a terrific project.

The Limits page of the DynamoDB Developer Guide has information about this logic.


make audio sockets path configurable

pass xrdp socket path to user session (chansrv) via environment variable
respect XRDP_SOCKET_PATH environment variable
other minor changes

I confirmed this properly works with non-default socket directory. Compiled --with-socket-dir=/tmp/.xrdp2 option. If this is OK to merge, let's ship this to v0.9 branch too.

Any opinions? If no objections, I'll merge this in 24 hours.


How do I disable placeholders(?) on match arms filling and similar places

Currently when I have code like this
  match foo {}

RA will suggest to fill in match arms, which is a good behavior. But when it does so it will fill in something that looks like this:
  match foo {
      Event::Mouse(${0:_}) => todo!(),
      Event::Resize(_, _) => todo!(),
  }

How do I make it to fill in this instead, note _ instead of ${0:_}:
  match foo {
      Event::Mouse(_) => todo!(),
      Event::Resize(_, _) => todo!(),
  }

These placeholders should be replaced by the client. What LSP client / editor are you using?

These placeholders should be replaced by the client. What LSP client / editor are you using?

neovim with neovim/nvim-lspconfig and simrat39/rust-tools.nvim.

The client removes them now.


fix bug where missing built in slot config would break generation of the recognizer.json

resolved in 0.5.7


Closes softlayer/sl-ember-components#582

Implemented integration test suite for sl-date-range-picker and removed duplicate tests from unit test suite

Reviewed 2 of 2 files at r1.
Review status: all files reviewed at latest revision, 2 unresolved discussions, some commit checks failed.

tests/integration/components/sl-date-range-picker-test.js, line 23 [r1] (raw file):
Why is the [ 0 ] part needed?

tests/integration/components/sl-date-range-picker-test.js, line 321 [r1] (raw file):
Per discussion, let's remove the content of this function

Comments from the review on Reviewable.io

Review status: 1 of 2 files reviewed at latest revision, 2 unresolved discussions, some commit checks pending.

tests/integration/components/sl-date-range-picker-test.js, line 23 [r1] (raw file):
It is needed to isolate the element that we want to test against.

tests/integration/components/sl-date-range-picker-test.js, line 321 [r1] (raw file):
The body of this test has been removed.

Comments from the review on Reviewable.io

Reviewed 1 of 1 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved, some commit checks pending.

Comments from the review on Reviewable.io


Index swap

The goal of this issue is to make Meilisearch more production-ready by allowing the swap of indexes.
Indeed, this feature should remove the possible downtimes: the users will be able to index on a temporary index and then, swap the index names.
TODO

[ ] Work on PRD
[ ] Create a prototype if needed
[ ] Create the spec
[ ] Implement the final version in the code and merge it into main

⚠ Depends on scheduler refactoring https://github.com/meilisearch/meilisearch/issues/2725
Impacted teams
@meilisearch/docs-team @meilisearch/integration-team
Also pinging @meilisearch/cloud-team in case you would need it. Feel free to unsubscribe from this issue if I'm wrong.

To be precise, we don't know if it will be swapping or aliasing. There's a good chance it will be swapping, but I'd rather make that clear from the name of the issue 😇
I'll have more information next week.

I'll follow this topic. I'm waiting for this functionality for long time. :)

Hello @aaron5670
Glad to know this! We are working on it right now, should be release in v0.30.0 release

first RC at the beginning of November
official release is at the end of November!

Spec created and added to the issue description: https://github.com/meilisearch/specifications/pull/192


[Feature Request] Add Quick Settings tile

Thank you for this nice and clean app. It just does what I need.
Just one thing is missing IMHO, a tile for the Quick Settings.
This would come in handy because the scanner could be launched even from the lock screen.
It would be great if you could implement this.

Hello. Thank you for your feedback. It is actually a great idea, I think I will implement this feature in the near future.

Hello. Thank you for your feedback. It is actually a great idea, I think I will implement this feature in the near future.

Thank you! Looking forward to it. 😀

Implemented in v1.5


Remove --no-git-tag-version from alpha releases

Purpose
Unfortunately, using the --no-git-tag-version option for npm version during alpha releases leaves unstaged/uncommitted changes in source control, which causes grabthar-flatten -> grabthar-validate-git to fail prior to publishing. This PR removes --no-git-tag-version.
Another idea would be to keep --no-git-tag-version and run git stash, grabthar-flatten, then git stash apply for alpha releases: https://github.com/krakenjs/grabthar-release/pull/30

Closing this in favor of this: https://github.com/krakenjs/grabthar-release/pull/30


How to train the 20170512-110547 model by using MS-Celeb-1M

My goal is training the model(20170512-110547) provided from davidsandberg by using MS-Celeb-1M.
From now, I downloaded MS-Celeb-1M dataset(cropped and aligned) and knew that learning_rate_schedule_classifier_msceleb.txt and decode_msceleb_dataset.py were needed for preprocessing. Please give me a detailed explanation how to use the source code in facenet for training
Thank u in advance

one more thing!!
source code in decode_msceleb_dataset.py
file format is below
Column1: Freebase MID
Column2: Query/Name
Column3: ImageSearchRank
Column4: ImageURL
Column5: PageURL
Column6: ImageData_Base64Encoded
in http://www.msceleb.org/download/aligned
◦Column1: Freebase MID
◦Column2: ImageSearchRank
◦Column3: ImageURL
◦Column4: PageURL
◦Column5: FaceID
◦Column6: FaceRectangle_Base64Encoded (four floats, relative coordinates of UpperLeft and BottomRight corner)
◦Column7: FaceData_Base64Encoded d Data](https://msceleb.blob.core.windows.net/ms-celeb-v1-samples/MsCelebV1-Faces-Aligned.Samples.zip): 14 entities, 32MBceleb.blob.core.windows.net/ms-celeb-v1-samples/MsCelebV1-Faces-Aligned.Samples.zip): 14 entities, 32MB
is it okay to use this source code for decoding the db?

@davidsandberg

Hi，have you solved this problem? I  have the same problem now, can you give me some advice?
Thanks !

hello, have you solved this issue? I have the same problem with you and looking for some advice now, thank you~


error on Tesla V100S-PCIE-32GB cards

I am suing the same bindcraft version (1.2) and same bindcraft conda env on all our nodes. When I tried to start copies of the same run (same filter, advanced and target,json)  on multiple GPU nodes, the only node running with Tesla V100 cards gave the below error. The V100 node uses the same nvidia driver version and cuda version as the other nodes. something I can do to fix this? The v100s have 32gb of memory, which is you minimum amount of vram to run bindcraft on.
Stage 1: Test Logits
E1127 20:18:50.812097  150728 buffer_comparator.cc:157] Difference at 0: 96.2491, expected 96.2491
E1127 20:18:50.840553  150728 buffer_comparator.cc:157] Difference at 1: 97.6674, expected 97.6674
E1127 20:18:50.844962  150728 buffer_comparator.cc:157] Difference at 2: 94.0413, expected 94.0413
E1127 20:18:50.864918  150728 buffer_comparator.cc:157] Difference at 3: 97.4507, expected 97.4507
E1127 20:18:50.868603  150728 buffer_comparator.cc:157] Difference at 4: 94.7962, expected 94.7962
E1127 20:18:50.872160  150728 buffer_comparator.cc:157] Difference at 5: 98.3404, expected 98.3404
E1127 20:18:50.875985  150728 buffer_comparator.cc:157] Difference at 6: 101.752, expected 101.752
E1127 20:18:50.879264  150728 buffer_comparator.cc:157] Difference at 7: 97.9409, expected 97.9409
E1127 20:18:50.882718  150728 buffer_comparator.cc:157] Difference at 8: 105.633, expected 105.633
E1127 20:18:50.891108  150728 buffer_comparator.cc:157] Difference at 9: 97.9142, expected 97.9142
2024-11-27 20:18:50.899862: E external/xla/xla/service/gpu/autotuning/gemm_algorithm_picker.cc:348] Results mismatch between different GEMM algorithms. This is likely a bug/unexpected loss of precision.
E1127 20:18:50.907938  150728 buffer_comparator.cc:157] Difference at 0: 96.2491, expected 96.2491

-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 550.54.14              Driver Version: 550.54.14      CUDA Version: 12.4     |
|-----------------------------------------+------------------------+----------------------+
| GPU  Name                 Persistence-M | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  Tesla V100S-PCIE-32GB          On  |   00000000:3D:00.0 Off |                    0 |
| N/A   24C    P0             24W /  250W |       0MiB /  32768MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+
|   1  Tesla V100S-PCIE-32GB          On  |   00000000:3E:00.0 Off |                    0 |
| N/A   22C    P0             24W /  250W |       0MiB /  32768MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+
|   2  Tesla V100S-PCIE-32GB          On  |   00000000:88:00.0 Off |                    0 |
| N/A   24C    P0             24W /  250W |       0MiB /  32768MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+
|   3  Tesla V100S-PCIE-32GB          On  |   00000000:89:00.0 Off |                    0 |
| N/A   23C    P0             24W /  250W |       0MiB /  32768MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+
+-----------------------------------------------------------------------------------------+
| Processes:                                                                              |
|  GPU   GI   CI        PID   Type   Process name                              GPU Memory |
|        ID   ID                                                               Usage      |
|=========================================================================================|
|  No running processes found                                                             |
+-----------------------------------------------------------------------------------------
For the driver version cuda 12.x is recommended. I can try to module load cuda 11.8

We have had troubles running it on V100 and CUDA 11 recently, but I admit I did not spend much time debugging. If you find a solution, let us know!

pip uninstall -y jax jaxlib jax-cuda12-pjrt jax-cuda12-plugin
pip install jax[cuda]==0.4.30 jaxlib==0.4.30 -f https://storage.googleapis.com/jax-releases/jax_cuda_releases.html
pip list | grep jax
jax                       0.4.30
jax-cuda12-pjrt           0.4.30
jax-cuda12-plugin         0.4.30
jaxlib                    0.4.30
and then it works.
The other nodes have this:
pip list | grep jax
jax                       0.4.30
jax-cuda12-pjrt           0.4.33
jax-cuda12-plugin         0.4.33
jaxlib                    0.4.30
but they work.

that's great to know, thank you!!


Import Working Hours: Budget Planned values of old budgets are deleted

I had a project with two budgets filled with data of the last few months.
For testing purpose, I decided to add a third budget which should be assigned to a different contract.
I downloaded the example import files, manipulated them to have data for the last months of a new budget and uploaded them again.
Now the "Budget Planned"-values (seen in the Week and Month Overview) of the old two budgets are deleted in the time periods covered by the new budget.

I can reproduce the bug.
Two budgets:

After adding the third budget with dates that overlap:


switch headings to digitalmarketplace-govuk-frontend, add temp spacing override

https://trello.com/c/NwJZfDhf

Nice one.
I think you missed a file though; app/templates/auth/create-user-error.html?

Ah right yeah - I started with a simplistic grep on toolkit/page-heading

Cool.
Additionally we should now be able to remove this line @import "toolkit/_page-headings.scss";


Support pool ipam

Support pool ipam
Delete kube-vip chart

issue: https://github.com/harvester/harvester/issues/633

the kubevip states Service LoadBalancer address pools per namespace or global, does it means each namespace can have a range of IP pool config, I saw u have requested the user to config the ip_pool in the CCM but in which I reckon it's better to be configured on the harvester side per namespace(per guest k8s cluster since all VMs run in the same namespace)

Yes. The configurations are stored in the configmap. From my perspective, we can set it in UI.


Troop transport cart
~upvote=1|downvote=0

In PW/PK it was an annoyance for infantry to move itself, a simple suggestion is to implement carts that can carry a certain amount of soldiers. This might have some effects on the supply and demand of the horse economy, but it would be a great asset overall.

🏰 Discord Suggestion from Younes@9935

user Ryan@4214 voted +

user itsWilliam@2643 voted -

user ChrisTheJew@9908 voted +


Support for rollout restart of deployment/daemonset/statefulset when secret changes

Related to this closed issue https://github.com/external-secrets/external-secrets/issues/1865
Just taking a chance, we were looking at existing secrets controllers out there and specifically the vault secret operator and of course external secrets which seems to be the top contenders.
External secrets seems to tick all the boxes and is more versatile, but one very useful feature of the former is the ability to trigger rollout after secret changes (spec here )
I know, I know, we could install and managed yet another controller to do that, but since the Vault secret operator is fairly new and now supports it, I was wondering if this is a feature that should be reconsidered for external-secrets?
As I said taking a chance 😁
Thanks in advance for your answers!

It works like a charm with stakater reloader, just add metadata to secrets template.

It's true that the stakater reloader works like a charm. It's also true that this missing functionality of external-secrets was the sole reason for our decision to chose the Hashicorp VSO, mainly due to easy of deployment. We have many clusters, and any additional operator comes with additional operational cost (maintenance, testing).

Agreed. I just tried to help you until (and if) this function will be added.

Unfortunately, stakater reloader thinks that a Secret was changed every time it is updated (polled from AWS Secrets without actually changing the contents) by the external-secrets, and I get a rolling restart every refreshInterval.

I'd love to have this feature available in the ESO. It seems like the industry is leaning towards it being the secrets controllers's responsibility to rollout a restart if the underlying data have changed. I don't know if there would be a clever way of only doing a restart of a deployment/statefulset if the spec.template.spec.containers.envFrom.secretRef reference is managed by ESO.

Unfortunately, stakater reloader thinks that a Secret was changed every time it is updated (polled from AWS Secrets without actually changing the contents) by the external-secrets, and I get a rolling restart every refreshInterval.

@ait-maksymp it's likely that once https://github.com/external-secrets/external-secrets/pull/4086 is merged, your Kyverno/other systems won't constantly trigger restarts for secrets managed by ExternalSecret resources.
That is, unless the secret is actually changing, e.g. if you have two ExternalSecrets managing the same Secret, or are using a generator with refreshInterval > 0.

That is, unless the secret is actually changing, e.g. if you have two ExternalSecrets managing the same Secret

Oh, this is exactly what I am doing, I merge contents of two ExternalSecrets into one Secret 🤔
Thank you @thesuperzapper for food for thought.


Update PKGBUILD to 86.0.4240.111

well, I have no idea why that failed.

Yeah, that's just a problem from github actions.
Before merging, please add the xproto-fix-underflow-in-Fp1616ToDouble.patch like on my repo https://github.com/jstkdng/aur/commit/08809212e4d671b9feef973f5980c520afbe0955
I would have PR'd but you beat me to it.


Azure DevOps: No example on how to use PAT to access git repositories

Problem
There is beautiful documentation about the PATs in Azure DevOps and how nice and convenient they are.
However there is not even a single example on how to use them from the user perspective, i.e. there are examples on how to create them but not how to consume them. Not a single one.
Solution
It would be great to have at least a single example on how to consume the PATs to clone a git repo from Azure DevOps in the command line using the non-bloated raw git CLI NOT IN Windows.

@JoseFMP Can you provide the link you refer to?

Thank you.


Update Java's Buffer interface with GetBufferAsBuffer and GetBufferAsNativePointer methods

The previous developmental version of GetBufferAsType have been remove and replaced by these two methods which return a type derived from java.nio.Buffer or a long type for a native pointer.

@haesleinhuepf Per our discussions, I believe this is the interface that we converged at. Please take a look.

@blowekamp
That sounds great! Is there by chance a dll and a jar I can test? This is not part of the nightly build yet, right?
Thanks!

@haesleinhuepf Sorry for the massive delay on this forgotten PR. Lets get this merged into master so that the binaries can be tested before 2.1rc1.


named! with generics

Prerequisites
Here are a few things you should provide to help me understand the issue:

Rust version : 1.42
nom version : 5.1.1
nom compilation features used: None

Test case
I'm creating nom parser, but I'm not sure it's the best way. Also, I feel like named! could fit here, but it would require generics support (which it currently lacks). Here is my parser function, which I would like to rewrite:
#[macro_use]
extern crate nom;
use std::mem;

// functional style
pub fn take_struct<'a, S>() -> impl Fn(&'a [u8]) -> nom::IResult<&'a [u8], &'a S>
    where S: 'static
{
    // SAFETY: `take` ensures there is enough bytes in `s` slice to view it as an `S`.
    nom::combinator::map(
        nom::bytes::complete::take(mem::size_of::<S>()),
        |s: &[u8]| unsafe { (s.as_ptr() as *const S).as_ref().unwrap() })
}
// macro style
named!(protocol<&MyFfi>,
    preceded!(
        tag!(&b"prefix_"[..]),
        call!(take_struct::<MyFfi>())
    )
);
#[repr(C)]
#[derive(Debug, Eq, PartialEq)]
pub struct MyFfi {
    pub number: u32,
    pub payload: [u8; 4],
}
fn main() {
    let a = b"prefix_\x2a\0\0\01234_suffix";
    let res = MyFfi {
        number: 42,
        payload: ['1' as u8, '2' as u8, '3' as u8, '4' as u8],
    };
    assert_eq!(protocol(&a[..]), Ok((&b"_suffix"[..], &res)));
}

It feels like the signature of a take_struct is much more hustle than it should be. I would like to rewrite it in macro-style, if named! would support those <'a, S>.
Or maybe I should just shut up and accept the way it is 🤔

OK, this one seems a little bit more convenient:
// functional style
pub fn take_struct<S>(input: &[u8]) -> nom::IResult<&[u8], &S>
{
    // SAFETY: `take` ensures there is enough bytes in `s` slice to view it as an `S`.
    nom::combinator::map(
        nom::bytes::complete::take(mem::size_of::<S>()),
        |s: &[u8]| unsafe { (s.as_ptr() as *const S).as_ref().unwrap() }
    )(input)
}
// macro style
named!(protocol<&MyFfi>,
    preceded!(
        tag!(&b"prefix_"[..]),
        call!(take_struct::<MyFfi>)
    )
);


 THIS IS A TEST COMMENT, DO NOT COMMIT !!!!
    ```
    DO NOT COMMENT THIS CHANGE!


Warning: Cannot polyfill Path2D, rendering may be broken.

How can I fix this issue, I can't view the png file output.

Please try v3.3.0


there is any prepared chat for websdk?

If i want use the websdk i have a complete chat with all graphical things like the iOS and Android SDKs?
The method renderMyUI is effectively not defined...
Bests
Rocky

The WebSDK is a framework for integrating YOUR user interface with OUR servers and services.  It comes with bells and whistles like being able to tolerate periods of being offline.  But it is not itself a UI framework such Atlas which ships with our IOS and Android SDKs.
In any example you see from us, if the word "My" shows up in a function name, its intended to imply that its a function that you provide; its implicitly not defined, as the details of HOW its implemented will depend upon what UI framework you are building with.
If your looking for an easier starting point for building a UI, please see our https://github.com/layerhq/layer-js-sampleapps repository.


On IOS and Android no sound. On PC all is good.

Hello. In my video chat no sound on IOS and Android. I tested in https://rtcmulticonnection.herokuapp.com/demos/dashboard/  also not working sound on devices. I am uses RTCMultyCoccecntion 3.6.9. Help me please.

hello i same sence
author muaz say can be use the iceserver fix  in ther network on internet video/audio can'be connection problem.
you can build you turn&stun server and xirsys stun&turn service
two way i try . may i  use i build turn server 443/80 port server , it's work
but use the xirsys stun/turn service it's work


New Feature: #12686 SoftmaxCrossEntropyWithLogits gradient function

Committing in a new PR as the old PR has too many commit files

@suharshs This is the new PR taking over from the old one. Please let me know if there are any issues merging this.

Awesome ! Hey thank you everyone for helping me in pulling this together. I took an awfully long time to get this done. This is my first ever PR to Tensorflow so it means a lot ! Thanks again.


Auto generated GetResolver has constructor with wrong parameter order in Kotlin

Reproduction steps:

create class with more than two columns f.e.

@StorIOSQLiteType(table = "CreditCard")
data class CreditCard @StorIOSQLiteCreator constructor(
        @get:StorIOSQLiteColumn(name = "id", key = true) val cardId: Long,
        @get:StorIOSQLiteColumn(name = "name") val name: String,
        @get:StorIOSQLiteColumn(name = "expireYear") val expireYear: Int,
        @get:StorIOSQLiteColumn(name = "expireMonth") val expireMonth: Int,
        @get:StorIOSQLiteColumn(name = "type") val type: String,
        @get:StorIOSQLiteColumn(name = "isDefault") val isDefault: Boolean)

build project (couple of times if needed).

The reason for that is kapt (kotlins annotation processor, don't know about apt) does not process annotations in creation order.

Did you check it with kapt or kapt2?

kapt1 I guess (I'm using '1.0.5-2' version of Kotlin)
the one with
kapt {
    generateStubs = true
}

just checked with the new kapt (the one described here: https://blog.jetbrains.com/kotlin/2016/09/kotlin-1-0-4-is-here/) and the problem is still occurring.

Looks like I was very (un)fortunate with my Kotlin test case, but it's still my fault because I haven't tested it properly and was more concentrated on AutoValue case. I asked a question in Kotlin slack if it is expected behaviour or not. If it works as expected then I'll add an ordering parameter to column annotations and will sort fields according to it.
Thank you, very much for filing this issue! And sorry for inconvenience =(

maybe some reflection can be used to avoid parameter numbering?

JetBrains guys said that kapt should behave in the same way as apt.
So here is an issue: https://youtrack.jetbrains.com/issue/KT-15202.
Since we don't know when it will be fixed and current version doesn't work I think we still need to do something even if the problem is on kapt side.

@artem-zinnatullin Kotlin support is broken atm. Shall we wait more answers and fixes from Kotlin team or shall we start acting upon it by ourselves?

Do you think it's possible to give a fix from our side? Without reflection.
On Fri, Dec 16, 2016, 14:35 Ilya Zorin<EMAIL_ADDRESS>wrote:

@artem-zinnatullin https://github.com/artem-zinnatullin Kotlin support
is broken atm. Shall we wait more answers and fixes from Kotlin team or
shall we start acting upon it by ourselves?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pushtorefresh/storio/issues/735#issuecomment-267575840,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA7B3Mh7nBqWWj8RxcwJslSqMs_jqIu-ks5rIneDgaJpZM4LKbL8
.

I've just read some documentation, so I might be wrong but probably you can cast element annotated with @Creator annotation into ExecutableElement and it has getParameters() method. (see here: https://docs.oracle.com/javase/7/docs/api/javax/lang/model/element/ExecutableElement.html)

We can introduce new parameter order to StorIOSqliteColumn and sort parameters according to it before building parameters list

That looks like too much manual work :(
On Fri, Dec 16, 2016, 15:03 Ilya Zorin<EMAIL_ADDRESS>wrote:

We can introduce new parameter order to StorIOSqliteColumn and sort
parameters according to it before building parameters list
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pushtorefresh/storio/issues/735#issuecomment-267580309,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA7B3NEktTbvhdMad57jrEg7hdsVsSFwks5rIn4LgaJpZM4LKbL8
.

@pbochenski you can't get variables name from there :(
@artem-zinnatullin not that much, but adding  more manual work for users is always bad, I agree.

I just checked that @pbochenski is actually right and you can get actual parameters names from getParameters() on ExecutableElement. So it should be possible to map columns with parameters relying just on their names.

Nice!

@pbochenski please verify that the issue is fixed in the latest version.

sorry but no. testing using this: https://github.com/pbochenski/kaptstoriobug
the error is
error: Problem occurred with StorIOProcessor: -1
e: /Users/bochen/Documents/kod/testy/kaptstoriobug/app/src/main/java/geraltencore/kaptstoriobug/CreditCardKotlin.kt: (1, 1): Some error(s) occurred while processing annotations. Please see the error messages above.

Sorry if I wasn't clear. I've changed implementation in StorIO for using parameters names instead of relying on fields order. So I was asking you to test this issue with version 1.12.1. Kapt behaviour remains unchanged that's why test repo still doesn't work.

@geralt-encore yes I know, I've forked your repo since it is nicely isolated problem and updated StorIO libraries as well as added kotlin-apt plugin.

That's a bummer 😔
I tested it properly before making PR with the fix and it worked. Need to investigate it further...


Get path length on the server

What does this change?
Get path length on the server, using the SVG Path Commander
Why?
Follow-up on #135

You might want to actually lift the SVG Path Commander even higher up the chain, at the SVG processing level, to calculate the length at build time and prevent shipping the whole library to client unnecessarily, but I took the easy approach of only touching leaf nodes 😁

I think you have to merge pull requests for all external contributors: