[Request deployment] New Hub: agu.2i2c.cloud

The GitHub handle of the community representative
@jmunroe
Hub important dates
Monday, Dec 11 -Dec 15
Hub Authentication Type
Other (may not be possible, please specify in comments)
First Hub Administrators
@jmunroe
[GitHub Auth only] How would you like to manage your users?
None
[GitHub Teams Auth only] Profile restriction based on team membership
No response
Hub logo image URL
2i2c logo
Hub logo website URL
2i2c.org
Hub user image GitHub repository
No response
Hub user image tag and name
n/a
Extra features you would like to enable

[ ] Dedicated Kubernetes cluster
[ ] Scalable Dask Cluster

(Optional) Preferred cloud provider
None
(Optional) Preferred cloud region
No response
(Optional) Billing and Cloud account
None
Other relevant information to the features above
Spin up a binder instance to be available during AGU.
Tasks to deploy the hub

[ ] 1. Deploy information filled in above
[ ] 2. Engineer who will deploy the hub is assigned
[ ] 3. If using GitHub Orgs/Teams Auth, Engineer is given Owner rights to the org to set this up.
[ ] 4. Initial Hub deployment PR
[ ] 5. Administrators able to log on -> Hub now in steady-state

Flowing out of a chat with @yuvipanda in preparation for AGU next week.
Open for AGU, but to be shutdown after the conference.

@jmunroe With https://github.com/2i2c-org/infrastructure/pull/3540, agu-binder is gone. Did you get any use out of it during the conference?

One thing I've learnt is that we can run these binders without immediately being taken over by crypto miners :)

Closing this one, feel free to re-open if needed to provide further feedback, @jmunroe.


No more announcement banner

With PST 15.3rc1, no more announcement banner despite:
html_theme_options = {
    ...
    "announcement": "Nouvelle version de la FAQ LaTeX GUTenberg !",
    ...
}

in conf.py.

It used to work, e.g. with PST 0.14.4.

OOps - probably my fault in #1703 ? I'll take a look

Actually it's some new javascript that was only added to the remote option of the announcement banner, I'll submit a PR soon for a fix. Thanks @dbitouze !


[Android 13] saveNetworkInDevice error not triggered if already saved

Testing with Android 13, when calling saveNetworkInDevice (when the  local network was already successfully saved using that same function) doesn't trigger/throw the error ERR_NETWORK_SAVED  specified in the documentation.
How can I make sure to get that error in order to fallback into the regular connectToLocalNetwork if it's already saved?
Thanks in advance again for your help!

Could you please do some debugging on saveNetworkInDevice at native side? I think it's related to Android 13 version maybe another error being thrown

@aboozaid I'll debug it and let you know.. can you share any useful guidance from the native module? Otherwise I'll add a bunch of break points and let you know hopefully soon.


how to create an AccAddress from a given private key

I searched the repository but could not find any example. Where can I find the steps:

generate a private key
derive public from private key
derive address from public key
Thanks

What exactly are you trying to do?
You can see the steps that the Cosmos SDK uses for 2 and 3 here:  https://github.com/osmosis-labs/cosmos-sdk/blob/osmosis-main/crypto/keys/secp256k1/secp256k1_test.go#L37
For #1, you can use the this function:
https://github.com/osmosis-labs/cosmos-sdk/blob/osmosis-main/crypto/keys/secp256k1/secp256k1.go#L82

closing this.


Add inputs validation

Currently duplicate usernames are allowed to be stored in DB when the OnSignup() method in api.go is called.
Kindly assist to validate that a username is in use, and throw an error if so.
Update the response in swagger.yml too as you go along.

Can I work on it?

May I take this one?

Sure!

Thanks!


Properties menu item does not exist for storage account, is now endpoints.

In the section "How to determine the scope for a resource" it says "In the Azure portal, open the resource and then look at the properties.".
The "properties" menu item does not exist anymore and is now visible under settings->endpoints. Also the screenshot is not current anymore, still shows properties.

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

ID: cab99d26-210a-4354-1abe-50ec096a775e
Version Independent ID: d7d74122-eb72-7f1f-34d2-dcad7ed290b8
Content: Understand scope for Azure RBAC
Content Source: articles/role-based-access-control/scope-overview.md
Service: role-based-access-control
GitHub Login: @rolyon
Microsoft Alias: rolyon

@gerbendv
Thanks for your feedback! We will investigate and update as appropriate.

@gerbendv
I'm going to assign this to the document author so they can take a look at it accordingly.
@rolyon
Can you please check and add your comments on this doc update request as applicable.

Hi @gerbendv
Thanks for your feedback. We've updated the screenshot
https://learn.microsoft.com/en-us/azure/role-based-access-control/scope-overview#how-to-determine-the-scope-for-a-resource
Let us know if you have additional feedback.
thanks

#please-close


Accept host:port for client instead of only URL

Is your feature request related to a problem? Please describe.
All other SDKs use host:port, we should too
Describe the solution you'd like

Change tls_config: Optional[TLSConfig] = None to tls_config: Union[bool, TLSConfig] = False
If a scheme is not present (meaning we're backwards compatible here), before sending to core, set it as http if tls_config is false or https otherwise

Maybe I should rename tls_config to tls? I think I will... (that's backwards incompat but who cares)


Fixed GIS tests

Patch from https://github.com/django/django/commit/0a899157836cc4c3d3980ab6a70b2f37bbb7ba97#commitcomment-11550904 .

Fixed already in 7abf418eb12471c86e97f68d58f966598d9fc86b


Default now is to run from the project’s folder

Per your request, this is now the defaults behavior and there is a workspace option that allows you to go back to the previous behavior and run from the source file’s folder.

Any chance of getting this looked at and maybe merged? Thanks!


How to deal with 16-bit vs 8-bit audio and frame_size may be incorrectly named

Firstly, thanks for this library. I'm encountering some issues, particularly with 16-bit audio.  The examples and documentation don't specify how to deal with each case. Also, a single frame of stereo 16-bit audio is 4 bytes long but in your documentation, you are using a frame_size of 480. Is that supposed to be the number of samples to process?

I'm archiving the repository for lack of interest in maintaining it. Sorry I never got to deal with this issue. Please see @discordjs/opus for an alternative implementation that is based this project but uses more stable Node.js module technology that should break less between Node.js versions.


[Question] Switching oauth2 clients without logout

Hey @okrad , First of all, Thank you for this helper class. It's awesome!
Secondly, I have a question:
The app which I am developing has a multiple clients. All clients are custom oAuth2 clients with PKCE flow. Now the requirement is switching between clients without logout. At present if an app user wants to switch client, he has to logout from one client and login again to another client. Is there any way to achieve this switching functionality without logout? Please guide me.
(Example: The way Gmail and Instagram have the option to switch between multiple accounts without repeating login.)
Thank you once again for your hard work.

I realised that I could able to achieve this if I do not call the disconnect method during logout.
Thank you once again @okrad.
I am closing this question.


Scaffold tests in generated SDK

We recently introduced simple test scaffolding in fern-python. We should do something similar here, potentially with jest.

Working on it.

closing as this would be part of a generator parity project


ISPN-1342 Near caching for Java Hot Rod client

https://issues.jboss.org/browse/ISPN-1342

Add near cache functionality to Java Hot Rod client.
Two modes implemented, lazy and eager.
Near caches can optionally be configured to keep a maximum number of entries.
Refactored Hot Rod client testing utilities.
Upon near cache failover, near caches are cleared.

FAILURE - TeamCity Infinispan :: Pull requests monitor Build 8182/galderz:t_1342_x for a93e3c0b59cedfa6464047f04ca8651919646240
Tests: 8788, 0 failed (0 new), 6 ignored. Build time: 00:20:36
Error message is logged
Process exited with code 1
Compilation failure

Compilation error with recently added test, fixing...

Compilation error fixed

FAILURE - TeamCity Infinispan :: Pull requests monitor Build 8185/galderz:t_1342_x for d1a8258b4d9b74eecc130c67b4df492d0ae5d5fb
Tests: 8788, 0 failed (0 new), 6 ignored. Build time: 00:31:39
Error message is logged
Process exited with code 1
Compilation failure

Two minor comments, but this looks excellent.

FAILURE - TeamCity Infinispan :: Pull requests monitor Build 8186/galderz:t_1342_x for d1a8258b4d9b74eecc130c67b4df492d0ae5d5fb
Tests: 11229, 1 failed (1 new), 23 ignored. Build time: 02:48:10
Failed tests detected

(new) TestSuite: org.infinispan.statetransfer.ClusterTopologyManagerTest.testClusterRecoveryWithRebalance

Error message is logged
Build duration (secs) is too large: 10049

FAILURE - TeamCity Infinispan :: Pull requests monitor Build 8199/galderz:t_1342_x for b44dafa4a099b9ff3c0ec840b00648e754d8aacb
Tests: 11228, 4 failed (4 new), 23 ignored. Build time: 01:40:40
Failed tests detected

(new) TestSuite: org.infinispan.distribution.DistSyncTxL1RepeatableReadFuncTest.testBackupOwnerInvalidatesL1WhenPrimaryIsUnaware

(new) TestSuite: org.infinispan.interceptors.ConcurrentInterceptorVisibilityTest.testSizeVisibility

(new) TestSuite: org.infinispan.client.hotrod.near.EvictEagerNearCacheTest.testEvictAfterReachingMax

(new) TestSuite: org.infinispan.client.hotrod.near.ClusterEagerNearCacheTest.testNearCacheUpdatesSeenByAllClients

SUCCESS - TeamCity Infinispan :: Pull requests monitor Build 8222/galderz:t_1342_x for b44dafa4a099b9ff3c0ec840b00648e754d8aacb
Tests: 11230, 0 failed (0 new), 23 ignored. Build time: 01:41:40

FAILURE - TeamCity Infinispan :: Pull requests monitor Build 8242/galderz:t_1342_x for b44dafa4a099b9ff3c0ec840b00648e754d8aacb
Tests: 11231, 2 failed (2 new), 23 ignored. Build time: 02:00:41
Failed tests detected

(new) TestSuite: org.infinispan.distexec.mapreduce.DistributedFourNodesMapReduceTest.testInvokeMapReduceOnAllKeysWithCollator

(new) org.infinispan.server.test.query.ManualIndexingIT.testManualIndexing

Error message is logged
Build duration (secs) is too large: 6800

@tristantarrant Updated PR fixing those two things.

FAILURE - TeamCity Infinispan :: Pull requests monitor Build 8251/galderz:t_1342_x for 335857b7e78ab7426e05dd78d0d9edc2f45e2e45
Tests: 11231, 1 failed (1 new), 23 ignored. Build time: 01:41:20
Failed tests detected

(new) TestSuite: org.infinispan.interceptors.ConcurrentInterceptorVisibilityTest.testSizeVisibility

Nice one Galder, it's in.

FAILURE - TeamCity Infinispan :: Pull requests monitor Build 8256/galderz:t_1342_x for 335857b7e78ab7426e05dd78d0d9edc2f45e2e45
Tests: 11230, 1 failed (1 new), 23 ignored. Build time: 02:10:38
Failed tests detected

(new) TestSuite: org.infinispan.client.hotrod.near.ClusterLazyNearCacheTest.testNearCacheUpdatesSeenByAllClients

Error message is logged
Build duration (secs) is too large: 7822


Clear prepared statement cache in case of schema change table event

Fixes: #261

I see that this type of change was previously added and then removed from upstream, not sure why

Instead of this we should disable skipping metadata optimization for SELECT * queries as it is broken and print additional warning that there might be a performance impact when running SELECT * queries


Make rest of the website discoverable

The documentation outside the manual page is hard to find, should have a link on the title bar to find the other pages, and reference it more through the manual.

Current thought is just rename FAQ in the titlebar to More... and add more side links in the manual doc.


Installer error

When running the curl get.pimoroni.com/piglow | bash command as instructed, it says
sh: line 274: dt_check: command not found

But it then carries on as normal, so I guess it's not quite a fatal error?

I can't see a reference to dt_check in the installer script, so perhaps this has been fixed since? https://github.com/pimoroni/get/blob/master/installers/piglow
Probably best to open an issue against the get repo if not!
Cheers.

Yeah, fixed in https://github.com/pimoroni/get/commit/404522371d942f510eabf35885d8d332b4f8db98
(ironically just 3 days after I opened this issue!)


Invalid HTTP port

Invalid HTTP port: tcp://<IP_ADDRESS>:9000 when upgrade from 0.8.5 to 0.9.0.

Could you elaborate a bit more on this?
Not sure if related but we introduced these changes regarding the port:

#438
https://github.com/lmenezes/cerebro-docker/pull/5

Server:Docker
Env:none
Image:lmenezes/cerebro:0.9.0

Container Stdout

Pod yaml
apiVersion: v1
kind: Pod
metadata:
  labels:
    app: cerebro
    pod-template-hash: "6954484579"
  name: cerebro-6954484579-kdnhj
spec:
  containers:
  - image: lmenezes/cerebro:0.9.0
    imagePullPolicy: Always
    livenessProbe:
      failureThreshold: 3
      httpGet:
        path: /
        port: 9000
        scheme: HTTP
      initialDelaySeconds: 10
      periodSeconds: 5
      successThreshold: 1
      timeoutSeconds: 2
    name: cerebro
    ports:
    - containerPort: 9000
      name: http
      protocol: TCP
    readinessProbe:
      failureThreshold: 3
      httpGet:
        path: /
        port: 9000
        scheme: HTTP
      initialDelaySeconds: 10
      periodSeconds: 5
      successThreshold: 2
      timeoutSeconds: 2
    resources:
      limits:
        cpu: 500m
        memory: 800Mi
      requests:
        cpu: 100m
        memory: 800Mi
    securityContext:
      capabilities: {}
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
      name: default-token-b4655
      readOnly: true
  dnsPolicy: ClusterFirst
  enableServiceLinks: true
  priority: 0
  restartPolicy: Always
  schedulerName: default-scheduler
  securityContext: {}
  serviceAccount: default
  serviceAccountName: default
  terminationGracePeriodSeconds: 30

Can also confirm that 0.8.5 works, while 0.9.1 is giving the Invalid HTTP Port error.
Also running on Kubernetes.

We experienced similar issue during upgrade to Cerebro 9.0
We identified the root cause with a workaround.
Root cause:
Cerebro 9.0 introduced CEREBRO_PORT environment variable to set the daemon port (See https://github.com/lmenezes/cerebro/commit/04b5ca8935cdf49e11aa125aeab6121e5bdd466a).
This variable could conflicts with Kubernetes deployment.
Kubernetes generates (by default) environment variables for services deployed in same namespace (see https://kubernetes.io/docs/concepts/services-networking/service/#environment-variables).
If you deploy Cerebro with a Kubernetes service called cerebro, the CEREBRO_PORT environment variable will be automatically defined to tcp://<pod_id_address>:9000.
When Cerebro starts, it execute server.http.port = tcp://<pod_id_address>:9000 and crash with the following error:
Invalid HTTP port: tcp://<pod_id_address>:9000

Work-around
We identified 2 workarounds:

Override CEREBRO_PORT to force Cerebro port. You may add the following lines to your container:env:
- name: "CEREBRO_PORT"
  value: "9000"

Set enableServiceLinks=false in your pod deployment (See https://kubernetes.io/docs/concepts/services-networking/connect-applications-service/#accessing-the-service) to avoid environment variables conflicts

@vmercierfr - tried it with work-around #2 and can confirm this works fine with the 0.9.1 image.
Thanks! 👍

We experienced similar issue during upgrade to Cerebro 9.0
We identified the root cause with a workaround.
Root cause:
Cerebro 9.0 introduced CEREBRO_PORT environment variable to set the daemon port (See 04b5ca8).
This variable could conflicts with Kubernetes deployment.
Kubernetes generates (by default) environment variables for services deployed in same namespace (see https://kubernetes.io/docs/concepts/services-networking/service/#environment-variables).
If you deploy Cerebro with a Kubernetes service called cerebro, the CEREBRO_PORT environment variable will be automatically defined to tcp://<pod_id_address>:9000.
When Cerebro starts, it execute server.http.port = tcp://<pod_id_address>:9000 and crash with the following error:
Invalid HTTP port: tcp://<pod_id_address>:9000

Work-around
We identified 2 workarounds:

Override CEREBRO_PORT to force Cerebro port. You may add the following lines to your container:env:
- name: "CEREBRO_PORT"
  value: "9000"

Set enableServiceLinks=false in your pod deployment (See https://kubernetes.io/docs/concepts/services-networking/connect-applications-service/#accessing-the-service) to avoid environment variables conflicts

Thx,it works.

Thank you very much for the investigation @vmercierfr


Possible issue around caching on apnews.com

When attempting to use the new configuration in the following PR: https://github.com/html2rss/html2rss-configs/pull/176 I seem to have hit an issue around the caching of dynamic config files. I have yet to figure out a good set of steps to reproduce, or find the root cause of where exactly it goes wrong. But what i have done is this:
Try to load section=trending-news then shortly after attempt to load another, for example section=ukraine. It will either mix the stories from both trending-news and ukraine. Or only load the previous trending-news news stories under ukraine.
My feeling is that it might have to do with these pages taking a bit to load, and there are errors seeming to be around timeouts. But this might be the wrong path to go down. You can see the logs below:
[1] Puma starting in cluster mode...
[1] * Puma version: 5.6.2 (ruby 3.1.1-p18) ("Birdie's Version")
[1] *  Min threads: 5
[1] *  Max threads: 5
[1] *  Environment: production
[1] *   Master PID: 1
[1] *      Workers: 2
[1] *     Restarts: (✔) hot (✖) phased
[1] * Preloading application
[1] * Listening on http://<IP_ADDRESS>:3000
[1] Use Ctrl-C to stop
[1] - Worker 0 (PID: 3) booted in 0.0s, phase: 0
[1] - Worker 1 (PID: 4) booted in 0.0s, phase: 0
source=rack-timeout id=0894f721-5348-4ba2-9fac-0fffcabb1078 timeout=15000ms state=ready at=info
/usr/local/bundle/bundler/gems/html2rss-a898923f92b2/lib/html2rss/item_extractors/href.rb:26: warning: redefining constant Struct::Options
/usr/local/bundle/bundler/gems/html2rss-a898923f92b2/lib/html2rss/item_extractors/html.rb:25: warning: redefining constant Struct::Options
/usr/local/bundle/bundler/gems/html2rss-a898923f92b2/lib/html2rss/item_extractors/static.rb:16: warning: redefining constant Struct::Options
/usr/local/bundle/bundler/gems/html2rss-a898923f92b2/lib/html2rss/item_extractors/text.rb:23: warning: redefining constant Struct::Options
source=rack-timeout id=0894f721-5348-4ba2-9fac-0fffcabb1078 timeout=15000ms service=1462ms state=completed at=info
source=rack-timeout id=45b4009a-7b73-4652-b7d2-fc2e84178fe1 timeout=15000ms state=ready at=info
source=rack-timeout id=45b4009a-7b73-4652-b7d2-fc2e84178fe1 timeout=15000ms service=1ms state=completed at=info
source=rack-timeout id=a2bd4d83-a7b9-420e-b131-668b5394abc3 timeout=15000ms state=ready at=info
source=rack-timeout id=a2bd4d83-a7b9-420e-b131-668b5394abc3 timeout=15000ms service=1ms state=completed at=info
source=rack-timeout id=1e97365c-5228-4d84-a3b2-c3b401cd06d5 timeout=15000ms state=ready at=info
source=rack-timeout id=1e97365c-5228-4d84-a3b2-c3b401cd06d5 timeout=15000ms service=4ms state=completed at=info
source=rack-timeout id=a2720804-beca-41de-9003-194396ef1a69 timeout=15000ms state=ready at=info
source=rack-timeout id=9f3a171e-3956-47fc-8eed-cd3fe10a51a0 timeout=15000ms state=ready at=info
source=rack-timeout id=a2720804-beca-41de-9003-194396ef1a69 timeout=15000ms service=2ms state=completed at=info
source=rack-timeout id=9f3a171e-3956-47fc-8eed-cd3fe10a51a0 timeout=15000ms service=1ms state=completed at=info
source=rack-timeout id=ad960dbb-d315-4752-8229-fc42159466d8 timeout=15000ms state=ready at=info
source=rack-timeout id=ad960dbb-d315-4752-8229-fc42159466d8 timeout=15000ms service=1ms state=completed at=info
source=rack-timeout id=806abc6b-43c8-4479-ba37-0ad93475f3a3 timeout=15000ms state=ready at=info
/usr/local/bundle/bundler/gems/html2rss-a898923f92b2/lib/html2rss/item_extractors/href.rb:26: warning: redefining constant Struct::Options
/usr/local/bundle/bundler/gems/html2rss-a898923f92b2/lib/html2rss/item_extractors/html.rb:25: warning: redefining constant Struct::Options
/usr/local/bundle/bundler/gems/html2rss-a898923f92b2/lib/html2rss/item_extractors/static.rb:16: warning: redefining constant Struct::Options
/usr/local/bundle/bundler/gems/html2rss-a898923f92b2/lib/html2rss/item_extractors/text.rb:23: warning: redefining constant Struct::Options
source=rack-timeout id=806abc6b-43c8-4479-ba37-0ad93475f3a3 timeout=15000ms service=4094ms state=completed at=info
source=rack-timeout id=2c4a2607-64e9-44ca-9732-bbaace89398b timeout=15000ms state=ready at=info
source=rack-timeout id=2c4a2607-64e9-44ca-9732-bbaace89398b timeout=15000ms service=634ms state=completed at=info
source=rack-timeout id=de17384a-22f5-4aac-8295-f79e2c6c5204 timeout=15000ms state=ready at=info
source=rack-timeout id=de17384a-22f5-4aac-8295-f79e2c6c5204 timeout=15000ms service=364ms state=completed at=info

Okay so after some digging into what i was doing a month ago i figured it out. The currently shipped apnews config works flawlessly. I failed however to say that i was extending apnews using my own custom feeds.yml file with my own apnews.com scraper:
# config/feeds.yml
stylesheets:
  - href: '/rss.xsl'
    media: 'all'
    type: 'text/xsl'
headers:
  "User-Agent": "Mozilla/5.0 (Windows NT 10.0; rv:68.0) Gecko/20100101 Firefox/68.0"
feeds:
  apnewshub:
    channel:
      url: https://apnews.com/hub/%<section>s
      language: en
      ttl: 120
      time_zone: UTC
    selectors:
      items:
        selector: ".FeedCard"
      title:
        selector: h2
      link:
        selector: a:first
        extractor: href
      description:
        selector: p
        post_process:
          name: gsub
          pattern: '^COPENHAGEN, Denmark \(AP\) \— '
          replacement: ''
      updated:
        selector: ".Timestamp"
        extractor: attribute
        attribute: data-source
        post_process:
          name: "parse_time"
      author:
        selector: 'span[class^="Component-bylines"]'
        post_process:
          - name: gsub
            pattern: '^By '
            replacement: ''
          - name: gsub
            pattern: '^$'
            replacement: 'APNEWS'

This configuration does fail if you go to http://localhost:3000/apnewshub.rss?section=denmark then quickly thereafter http://localhost:3000/apnewshub.rss?section=ukraine. However, this works properly when using curl and the ruby comparison you provided, but it does load wrongly under chromium, see attached pictures below.

Okay i found some even more oddity with whatever is going on, i stopped and deleted the container, edited some settings in feeds.yml, restarted a brand new container with new and changed settings. Then going to http://localhost:3000/apnewshub.rss?section=norway under chromium, a section i have never loaded before, and somehow got returned what the previous http://localhost:3000/apnewshub.rss?section=ukraine should have looked like.
And again testing against curl gives me the correct and new ukraine, and the correct and new norway section. But with chromium it is somehow pulling the last generation of the config file's ukraine response on the newly never before fetched norway section.
I have a strong feeling this is some really absurd caching issue with chromium rather than an issue with html2rss-web, but i have no clue how this is even possible.

Forced refreshes (SHIFT+F5) does not seem to help either. It may sometimes give me the correct result where a previous one was wrong. But i have also had the behavior where section=denmark went from Hub Denmark to Hub Norway when i ran a SHIFT+F5 force refresh.

Wow, thank you for the detailed response. Love it! That's something to work with :-)
Sadly, I can't free up the required time currently to properly address this issue.
If anyone wants to take over, feel free and maybe give me a little ping. Otherwise, I'll gladly take on this issue as soon as I find the time.

Hello @imsofi ,
Can you check if the error appears after applying  the patch I propose in #589 ?
Maybe #587 is a duplicated and/or particular case of this issue.
regards,

With #587 being closed and a bugfix merged, I have the feeling this issue likely is also fixed by that. Can you please give it a try with the updated docker image, @imsofi, and report back? Thank you! :)

I no longer use html2rss, so I am afraid I will be unable to test this. But if it does work for others, I would say this issue could be closed. Thank you for your work @mabeett and @gildesmarais! :smile:


Set SOURCE_EEPROM_IMAGE using rpi-eeprom-update logic

Additionally, default to 'default' rather than 'latest' eeprom image.

This isn't quite ready-to-go yet as it seems we have some difficulty re-provisioning an already provisioned device if we change the eeprom image. There is some commented-out code @tdewey-rpi regarding "a partial signing situation". Do you have any idea if this has suffered from bit-rot or if it's possible to autodetect that situation?


ABI-2 Time_lock can be set to 0

ABI-2 Time_lock can be set to 0
Auditor: Movebit
Code: Atomic Bridge
Level: Critical
Code Location: protocol-units/bridge/contracts/src/AtomicBridgeInitiator.sol#47

protocol-units/bridge/move-modules/sources/atomic_bridge_initiator.move#83

Timelocks are now set during initialisation of the contract and remain constant


Transactions are not to be added to the mempool if they already exist

We will receive a block from the network where transactions already exist in the mempool. Transactions are fungible so we will simply leave them in the mempool and not add them unless we can add the block to our current chain. #232 will delete transactions when we add a block.

@lucafavatella Make sure this is so and we'll close the ticket.

https://www.pivotaltracker.com/story/show/152481717


Include adviser name in subscriber-list endpoint

This adds the name field to the response body of the subscriber-list endpoint.

Codecov Report

Merging #385 into develop will increase coverage by <.01%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##           develop     #385      +/-   ##
===========================================
+ Coverage    95.85%   95.85%   +<.01%
===========================================
  Files           70       70
  Lines         2703     2704       +1
  Branches       243      243
===========================================
+ Hits          2591     2592       +1
  Misses          79       79
  Partials        33       33

Impacted Files
Coverage Δ

datahub/omis/order/serializers.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


verify doesn't fail the test

I noticed that verify doesn't fail the test when the call count doesn't match. I eventually figured out that there's a global closure variable, testFailureReport,  that verify calls to report a test failure. But the testFailureReport closure by default doesn't do anything. What's the reason for this? I also haven't found this mentioned in the documentation, that one needs to set testFailureReport to something useful.

Hi, thanks for the question. The target with the library is linked to the target being developed because mocks are currently being generated in it. Therefore, it is impossible to link the XCTest library to it.
I will cover this point in the documentation and in the future I plan to make a separate target that can be connected to a target with tests, which will have a function that allows you to configure the engine to work.

#56

I see. How about using a plain Swift assert in the default implementation of testFailureReport that says it should be replaced with XCTFail or something similar? That will make it extra visible if someone has not read the documentation.

Nice idea, thank you very much.

Expecting changes:

Change default implementation of testFailureReport to assertion.

That should help user setup engine correctly.
That should prevert user from fake success tests without correct setup the engine.


Add driven loop mux

Add LcmDrivenLoop class which has MUX feature
Update the scripts of cassie osc controllers and dispatchers to use LcmDrivenLoop
Add ControllerChannelSender to publish lcm message that contains channel name

@mposa The PR is ready for review

@mposa The PR is ready for review


Update SUPPORT.md - Social Platform added

Social Media Platform Links of Ark is added to Support.md
Signed-off-by: Midhun Biju<EMAIL_ADDRESS>

Is this a duplicate of #1017?

@nrb it's a replacement, targeting master.

@nrb  #1017  was done by me as part of digitalocean hacktoberfest but it was made on release-0.9 branch . and I got a mail saying that if I'm still interested in getting this merged, it should be made against the master branch. So that I done the same in the master branch.

Instead of having 1 section that only mentions the mailing list aka google group, and another section that mentions twitter and slack, how about if we have a single section for how to get in touch with us, and list all of them in 1 place?


Train Machine Learning Model Cross Validation How-To

Train Machine Learning Model Cross Validation How-To
Internal Review Link
AB#1463694

Duplicate of https://github.com/dotnet/docs/pull/12159


Illegal instruction (core dumped) on Rust implementation

Hi!
Today I cloned the rust implementation repo and pushed it to a raspberry pi zero w application on resin cloud. When it started and when i run ./resin_wifi-connection, I got this error:
Illegal instruction (core dumped)
It's because it can't be run on ARMv6?

Hi,
Please use https://github.com/majorz/resin-wifi-connect for now. We will be merging the project into this repo at some point in the coming week.

Hi @josephroberts
I did that yesterday, I cloned that repo to my machine, and, without any modifications, pushed it to the resin cloud. After running the Rust executable, I got the above error: "Illegal instruction (core dumped)".
But no rush. I will developing another parts of the application and at the same time, debugging with the serial tool as you advised.

@josephroberts @majorz why is project code being kept in a personal
account? This is an anti-pattern we should avoid. Please bring the code
into the main repo asap. Cc @petrosagg
On Sep 5, 2017 2:14 PM, "Arthur Moisés"<EMAIL_ADDRESS>wrote:

Hi @josephroberts https://github.com/josephroberts
I did that yesterday, I cloned that repo to my machine, and, without any
modifications, pushed it to the resin cloud. After running the Rust
executable, I got the above error: "Illegal instruction (core dumped)".
But no rush. I will developing another parts of the application and at the
same time, debugging with the serial tool as you advised.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/resin-io/resin-wifi-connect/issues/111#issuecomment-327157326,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABLUCHwKIiLPNwYqqzE0KOrs-x2LGmBDks5sfTsVgaJpZM4PMKua
.

@arthurmoises, following up on this issue-- the newly released version of resin-wifi-connect v3.0.0 is now working on Raspberry Pi 1 and Zero / ARMv6. The error was because we used the debian toolchains for cross-compiling for ARMv6, instead of the raspbian fork, which produces proper ARMv6 hard-float binaries.


Docker build for Production

I would like to be able to run docker in production.

You still have debug = True for the API in production.

Good catch. There is an env var that should be setting this. I'll take a look.

Fixed with #67. When python evaluates a string to a bool value. The actual value doesn't matter, as long as there is something True will always be returned. Aka bool('False') == True.


Integration with ApiComparer

Crazy idea :)
We're contemplating an api for ApiComparer. Does paket have any integration points where it would make sense to list api changes, warn about breaking changes etc?
paket outdated with a potential --show-diffs looks interesting. I guess it could be just a generated link eg. http://apicomparer.particular.net/compare/rabbitmq.client/3.4.3...3.5.0 or some deeper integration where semver compliance is checked and updates with breaking changes are flagged in the output of the command in some way.
Thoughts?

Yes I guess that could make sense. Opening a website would be a valid way
to do this.
On Aug 24, 2015 8:31 PM, "Andreas Öhlund"<EMAIL_ADDRESS>wrote:

Crazy idea :)
We're contemplating
https://github.com/ParticularLabs/APIComparer/issues/46 an api for
ApiComparer https://github.com/ParticularLabs/APIComparer. Does paket
have any integration points where it would make sense to list api changes,
warn about breaking changes etc?
paket outdated with a potential --show-diffs looks interesting. I guess
it could be just a generated link eg.
http://apicomparer.particular.net/compare/rabbitmq.client/3.4.3...3.5.0
or some deeper integration where semver compliance is checked and updates
with breaking changes are flagged in the output of the command in some way.
Thoughts?
—
Reply to this email directly or view it on GitHub
https://github.com/fsprojects/Paket/issues/1012.


Update UI to include link for viewing contributor contributions

enhance UI for contributor profile and previous contributions link
- Updated the UI to make the contributor profile link more visible and accessible.
- Improved styling and layout for better user experience when viewing previous contributions.
- Adjusted design elements to align with the overall theme and enhance the interface’s aesthetics.
- Ensured that the new UI elements are responsive and user-friendly.
Fixes #72

s


[Bug]: Ecuador boundary files are too big (too precise)

What happened?
Boundary files for Ecuador are way too big relative to country size, resulting in about 40mb of boundary files...

Which country / deployment are you running?
Ecuador
Add a screenshot (if relevant)
No response

List of top countries with large data files:
119M	./public/data/rbd
53M	./public/data/ecuador
51M	./public/data/rbd/ch
37M	./public/data/mozambique
36M	./public/data/cambodia
33M	./public/data/cameroon
32M	./public/data/nepal
31M	./public/data/ukraine
24M	./public/data/cuba
23M	./public/data/tanzania
19M	./public/data/nigeria

https://mapshaper.org/ is a neat too to simplify geojson and see the results live


help with downloading

im using a guest pc with no admin privileges

this happens when i try to open this file using anaconda prompt
im veery new to github scripts and im confused on what to do
ive heard something about path variable but it needs admin privileges
is there any way to do without admin privileges

ah yes, the problem is clearly bc of admin privileges

There is no way you forgot an argument, for example install, pffft, who runs python setup.py install?
all my homies run python setup.py.

i cant make head or tail of what u said lmfao
srsly tho can u help? in a simplified way?

nvm looking at it now i see that the command is install and i forgot install
in my defense other anime download scripts dint need the install command

ay

how to launch the script now?

also is there any way to launch only the script in its own windows as if the script fails i have to type setup.py and the commands all over again

looking through the docs i noticed a gui command i downloaded the dependencies but how to actually run it?

also animepahe doesnt seem to be working even though its mentioned it works in the documentation
also how to do a re-search as sometimes all the results dont show
the one im searching for is nanatsu no taizai fundo no shinpan

im getting this issue now D:

also animepahe doesnt seem to be working even though its mentioned it works in the documentation
also how to do a re-search as sometimes all the results dont show
the one im searching for is nanatsu no taizai fundo no shinpan

AnimePahe will start to work again once https://github.com/anime-dl/anime-downloader/pull/674 gets merged.

You can install that fork for now if you desperately want animepahe.
To do so download https://github.com/nate-moo/anime-downloader/archive/refs/heads/KwikFix.zip
Then install it in the same way you installed anime-dl (previously).
animepahe should be working after that
oh yeah, even if it is going to work, it will only download m3u8 (playlist files) not mp4, so its only good for streaming for now

You can install that fork for now if you desperately want animepahe.
To do so download https://github.com/nate-moo/anime-downloader/archive/refs/heads/KwikFix.zip
Then install it in the same way you installed anime-dl (previously).
animepahe should be working after that
oh yeah, even if it is going to work, it will only download m3u8 (playlist files) not mp4, so its only good for streaming for now

will there ever be downloads supported for animepahe
many scripts ive used dont work anymore for animepahe
ig its bcz of the added captcha
ive tried using monkey-dl but it requires 2captcha which is paid which kinda beats the purpose even if its a few cents

Closing as the original issue appears to be resolved.


Apogee

We are not adding noise here, just applying our techniques and seeing how it goes.

How can we characterize distribution of this data?
Let's do a kernel density plot over anomalousness scores.


feat: Introduce Transaction and Hub.start_transaction

This aligns the tracing implementation with the current JS tracing implementation, up to a certain extent.
Hub.start_transaction or start_transaction are meant to be used when starting transactions, replacing most uses of Hub.start_span / start_span.
Spans are typically created from their parent transactions via transaction.start_child, or start_span relying on the transaction being in the current scope.
It is okay to start a transaction without a name and set it later.
Sometimes the proper name is not known until after the transaction has started.
We could fail the transaction if it has no name when calling the finish method. Instead, set a default name that will prompt users to give a name to their transactions. This is the same behavior as implemented in JS.

I don't know what's wrong with the docs generation job https://travis-ci.com/github/getsentry/sentry-python/jobs/354722815

I don't know what's wrong with the docs generation job https://travis-ci.com/github/getsentry/sentry-python/jobs/354722815

Circular imports.
Removed the SpanLike type, making the total diff smaller and solving the circular import.

diff --git a/sentry_sdk/_types.py b/sentry_sdk/_types.py
index 7c1aaa6..8e5427c 100644
--- a/sentry_sdk/_types.py
+++ b/sentry_sdk/_types.py
@@ -12,7 +12,7 @@ if MYPY:
     from typing import Optional
     from typing import Tuple
     from typing import Type
-    from typing import Union
+
     from typing_extensions import Literal

     ExcInfo = Tuple[
@@ -37,7 +37,3 @@ if MYPY:
     ]
     SessionStatus = Literal["ok", "exited", "crashed", "abnormal"]
     EndpointType = Literal["store", "envelope"]
-
-    from sentry_sdk.tracing import Span, Transaction  # noqa
-
-    SpanLike = Union[Span, Transaction]
diff --git a/sentry_sdk/scope.py b/sentry_sdk/scope.py
index 0c082c4..f928063 100644
--- a/sentry_sdk/scope.py
+++ b/sentry_sdk/scope.py
@@ -26,7 +26,7 @@ if MYPY:
         Type,
     )

-    from sentry_sdk.tracing import SpanLike
+    from sentry_sdk.tracing import Span
     from sentry_sdk.sessions import Session

     F = TypeVar("F", bound=Callable[..., Any])
@@ -114,7 +114,7 @@ class Scope(object):
         self.clear_breadcrumbs()
         self._should_capture = True

-        self._span = None  # type: Optional[SpanLike]
+        self._span = None  # type: Optional[Span]
         self._session = None  # type: Optional[Session]
         self._force_auto_session_tracking = None  # type: Optional[bool]

@@ -181,13 +181,13 @@ class Scope(object):

     @property
     def span(self):
-        # type: () -> Optional[SpanLike]
+        # type: () -> Optional[Span]
         """Get/set current tracing span or transaction."""
         return self._span

     @span.setter
     def span(self, span):
-        # type: (Optional[SpanLike]) -> None
+        # type: (Optional[Span]) -> None
         self._span = span
         # XXX: this differs from the implementation in JS, there Scope.setSpan
         # does not set Scope._transactionName.
diff --git a/sentry_sdk/tracing.py b/sentry_sdk/tracing.py
index 05abcf6..d390c6b 100644
--- a/sentry_sdk/tracing.py
+++ b/sentry_sdk/tracing.py
@@ -25,9 +25,6 @@ if MYPY:
     from typing import Dict
     from typing import List
     from typing import Tuple
-    from typing import Type
-
-    from sentry_sdk._types import SpanLike

 _traceparent_header_format_re = re.compile(
     "^[ \t]*"  # whitespace
@@ -225,7 +222,7 @@ class Span(object):

     @classmethod
     def continue_from_environ(
-        cls,  # type: Type[SpanLike]
+        cls,
         environ,  # type: typing.Mapping[str, str]
         **kwargs  # type: Any
     ):
@@ -239,7 +236,7 @@ class Span(object):

     @classmethod
     def continue_from_headers(
-        cls,  # type: Type[SpanLike]
+        cls,
         headers,  # type: typing.Mapping[str, str]
         **kwargs  # type: Any
     ):
@@ -261,7 +258,7 @@ class Span(object):

     @classmethod
     def from_traceparent(
-        cls,  # type: Type[SpanLike]
+        cls,
         traceparent,  # type: Optional[str]
         **kwargs  # type: Any
     ):

Removed some commentary, will move the discussion into new issues where appropriate.


Control Camera Speed

I added a simple slider that allows to control the camera speed. Currently it is by default set to 5m/s and it can be set between 0.1 and 30 m/s.
However, I found a bug that happens when moving forward through the scene origin. By doing that, the camera turns around and looks back to the origin. Up and Down arrows now switched directions. https://github.com/playcanvas/supersplat/issues/286

I have made those changes. However, I wish I could make the slider-control transparent for key-up/down events. Any idea how to accomplish that?

Might be possible, but quite fiddly.
How about hooking + and - keys to speed camera up and down?

I've merged the changes from yesterday's lint update into your branch.

I also added the missing localisations.
Please check you're happy before I merge.

I think you changed every single line of code :)
All good


primaryAxisPosition is ineffective

Currently working on it. Will post the fix as soon as I figure it out.

dupe of #81


[BUG] UI - Upgrade menu option is not enabled on Longhorn UI.

Describe the bug
Upgrade option is not enabled on Longhorn UI on upgrade.
To Reproduce
Steps to reproduce the behavior:

Deploy Longhorn v1.1.0 using kubectl command in a cluster of 4 nodes (1 etcd/control plane, 3 worker)
Create some volumes and attach them to pods.
Upgrade Longhorn to master.
Neither live upgrade nor offline upgrade option is not available on the Longhorn UI.

Environment:

Longhorn version: Longhorn - master 03/09/2021

Note
Concurrent Automatic Engine Upgrade Per Node Limit is set to 0.

We can close this one in favor of https://github.com/longhorn/longhorn/issues/2311


Update pyo3 to 0.22

This removes the Clone impl from Py<T> which we can work around by keeping the GIL a bit longer in log. I believe that this has little to no implication (or maybe a positive one actually due to the switch to clone_ref).
However, this means that we have to remove Clone impl from Logger.
All of this is still compatible with 0.21 but still a breaking change.

What do we do about old Python versions no longer building on newer MacOs ?

What do we do about old Python versions no longer building on newer MacOs ?

Probably disable them there. I've been ignoring it for a lack of time for a while…

Published. Thank you.


Merge events when adding existing notified user

Coverage decreased (-0.03%) to 65.68% when pulling 2adaec3a2b0ef91fa360ad0a3a9610985b328fac on guidow:merge_notification_events into e34c3c705f5448549a89adc04bc82af4771cd423 on pyfarm:master.

Looks good, merging.


getting error while deploying cdk stack

10:39:24 AM | CREATE_FAILED        | Custom::AWSCDK-EKS-KubernetesResource       | ssmAgentdeployment/Resource/Default
Received response status [FAILED] from custom resource. Message returned: AccessDeniedException: Resource is not in the state functionActive
at Object.extractError (/var/runtime/node_modules/aws-sdk/lib/protocol/json.js:61:27)
at Request.extractError (/var/runtime/node_modules/aws-sdk/lib/protocol/rest_json.js:61:8)
at Request.callListeners (/var/runtime/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
at Request.emit (/var/runtime/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
at Request.emit (/var/runtime/node_modules/aws-sdk/lib/request.js:686:14)
at Request.transition (/var/runtime/node_modules/aws-sdk/lib/request.js:22:10)
at AcceptorStateMachine.runTo (/var/runtime/node_modules/aws-sdk/lib/state_machine.js:14:12)
at /var/runtime/node_modules/aws-sdk/lib/state_machine.js:26:10
at Request. (/var/runtime/node_modules/aws-sdk/lib/request.js:38:9)
at Request. (/var/runtime/node_modules/aws-sdk/lib/request.js:688:12) (RequestId: 13bbd8c8-b697-4661-be52-97a9b7589069)
10:39:24 AM | CREATE_FAILED        | Custom::AWSCDK-EKS-KubernetesResource       | loadBalancerCRD/Resource/Default
Received response status [FAILED] from custom resource. Message returned: AccessDeniedException: Resource is not in the state functionActive
at Object.extractError (/var/runtime/node_modules/aws-sdk/lib/protocol/json.js:61:27)
at Request.extractError (/var/runtime/node_modules/aws-sdk/lib/protocol/rest_json.js:61:8)
at Request.callListeners (/var/runtime/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
at Request.emit (/var/runtime/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
at Request.emit (/var/runtime/node_modules/aws-sdk/lib/request.js:686:14)
at Request.transition (/var/runtime/node_modules/aws-sdk/lib/request.js:22:10)
at AcceptorStateMachine.runTo (/var/runtime/node_modules/aws-sdk/lib/state_machine.js:14:12)
at /var/runtime/node_modules/aws-sdk/lib/state_machine.js:26:10
at Request. (/var/runtime/node_modules/aws-sdk/lib/request.js:38:9)
at Request. (/var/runtime/node_modules/aws-sdk/lib/request.js:688:12) (RequestId: 2414184d-fba4-4d93-a591-4635521c97da)
10:39:27 AM | ROLLBACK_IN_PROGRESS | AWS::CloudFormation::Stack                  | Services
The following resource(s) failed to create: [LBServiceAccount67A900BC, loadBalancerServiceAccount1D19AD3A, ssmAgentdeployment3666D473, xraydeployment7059A3EB, petsiteAwsAuth
manifest576F9E03, k8sdashboardrbac66807D7E, loadBalancerCRDEF35F65C, cloudwatcheployment7FE6A515]. Rollback requested by user.
10:39:27 AM | ROLLBACK_IN_PROGRESS | AWS::CloudFormation::Stack                  | Services
The following resource(s) failed to create: [LBServiceAccount67A900BC, loadBalancerServiceAccount1D19AD3A, ssmAgentdeployment3666D473, xraydeployment7059A3EB, petsiteAwsAuth
manifest576F9E03, k8sdashboardrbac66807D7E, loadBalancerCRDEF35F65C, cloudwatcheployment7FE6A515]. Rollback requested by user.

how to resolve this error

Any update on this

Any update on this

Hello @vikasj003,
Thank you for your patience. I have recently on-boarded to the team and I'm following up with issues for this project.
I was able to deploy the current code successfully.
Could you confirm if you still receive the same error?


Some 14.0 based ISOs: kp on guz_zstd_decompress

With some 14.0-CURRENT based experimental ISOs, we get a kernel panic:
mdconfig -a -t vnode-o readonly -f /boot/rootfs.uzip
(...)
panic: guz_zstd_decompress: Expected 262144 bytes, got 163840
(...)
KDB: stack backtrace:
(...)

This is the FreeBSD source code in question:
https://github.com/freebsd/freebsd-src/blob/627f1555f571b5328637dbfbe441ed89c84db20c/sys/geom/uzip/g_uzip_zstd.c#L81

Build 0H55 does not panic
Build 0H56 panics (only change was to include a self-built pkg of drm-510-kmod which is not even loaded yet at the stage where the crash happens)
Build 0H59 (a mere re-run of 0H56 without any code changes) also panics in the exact same way
Build 0H59 (reverted to the same contents as 0H55) does not panic again

Conclusion: It seems like with some contents or with  some size of the contents, the mdconfig -a -t vnode-o readonly -f /boot/rootfs.uzip step fails at guz_zstd_decompress.

0H62 (same package set as 0H56 but built a day later) also panics in the exact same way

0H64 (same but with 2 MB of random data added) does not panic.

https://github.com/helloSystem/ISO/releases/tag/experimental-14.0-0.8.0_0H75 crashes
Rebuild with this change: uncomment dd if=/dev/random of="${uzip}"/random.data bs=1M count=2 in https://github.com/helloSystem/ISO/commit/c0f278e98fe49908ca7024c40ef2de357e7faf1b
...

This can also happen with, e.g., the Developer ISO.

can add normal Setup OS ? (like a Linux with Calamares ?)
and, add support Wi-Fi usb-adapter? - rtl8192eu ?
and.. why cannot run .appimage apps ?
i just double click on apps, and not run...
or, appimage not work here?? in bsd?
tested on SMplayer (mpv/mplayer)

hello-0.8.0_0H106-FreeBSD-14.0-amd64.iso crashes with guz_zstd_decompress

Reported upstream:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267082

Lately, more or less all helloSystem ISOs based on FreeBSD 14.0-CURRENT fail:

With makefs -R 16384 it did not crash but the resulting ISO was noticeably larger.


ComposerScriptの作成

#31

Coverage remained the same at 0.0% when pulling b9308a28c2773839714aaba204bab1f54d275d26 on 17 into 70512283de24e9fe0d028b8f050fd1c336a3ea3f on develop.


Typo "@runincluster"→"@runincluster"

Italic with escape characters
https://docs.microsoft.com/en-us/sql/sql-server/sql-server-2017-release-notes?view=sql-server-2017

@hyoshioka0128 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

LGTM. Thanks @hyoshioka0128


ui: refactor global createmenu

Description
Refactors global create menu code to make it visible only when any menu is accessible.
Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Enhancement (improves an existing feature and functionality)
[x] Cleanup (Code refactoring and cleanup, that may add test cases)
[ ] build/CI

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[ ] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[ ] Trivial

Screenshots (if appropriate):
Admin:

Read-only user:

Custom role user:

How Has This Been Tested?

How did you try to break this feature and the system with this change?

@blueorangutan ui

@shwstppr a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build failed: :heavy_multiplication_x:
(SL-JID-359)

@blueorangutan ui

@shwstppr a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: https://qa.cloudstack.cloud/simulator/pr/9139 (QA-JID-362)


Handle large context windows using Ollama's LLMs for evaluation purpose

[/ ] I checked the documentation and related resources and couldn't find an answer to my question.
I integrated Langfuse with Ragas for evaluation purposes. Referring to issue #53, it's mentioned that by default, "we are using 'gpt-3.5-16k', so you don't have to reduce document size when running the evals." However, when using different Ollama LLMs like llama3, mistral, phi3..., I noticed that Ragas limits the context window to between 500-700 tokens. I want it to handle larger document sizes, similar to 'gpt-3.5-16k'. Is this possible?
# setup ragas evaluation ----------------------------------------------------

# import metrics
from ragas.metrics import faithfulness, answer_relevancy, context_precision
from ragas.metrics.critique import SUPPORTED_ASPECTS, harmfulness
from ragas.run_config import RunConfig
from ragas.metrics.base import MetricWithLLM, MetricWithEmbeddings
from langchain_openai.chat_models import ChatOpenAI
from langchain_openai.embeddings import OpenAIEmbeddings

# wrappers
from ragas.llms import LangchainLLMWrapper
from ragas.embeddings import LangchainEmbeddingsWrapper

from langchain_community.chat_models import ChatOllama
from ragas import evaluate
from langchain_community.embeddings import OllamaEmbeddings
# information found here: https://docs.ragas.io/en/latest/howtos/customisations/bring-your-own-llm-or-embs.html

# metrics you chose
metrics = [answer_relevancy]

# util function to init Ragas Metrics
def init_ragas_metrics(metrics, llm, embedding):
    for metric in metrics:
        if isinstance(metric, MetricWithLLM):
            metric.llm = llm
        if isinstance(metric, MetricWithEmbeddings):
            metric.embeddings = embedding
        run_config = RunConfig()
        metric.init(run_config)

llm = ChatOllama(model="deepseek-coder-v2:latest")
emb = OllamaEmbeddings(model="nomic-embed-text")

# llm = ChatOpenAI(model="gpt-3.5-turbo-16k")
# emb = OpenAIEmbeddings()

init_ragas_metrics(
    metrics,
    llm=LangchainLLMWrapper(llm),
    embedding=LangchainEmbeddingsWrapper(emb),
)

async def score_with_ragas(query, chunks, answer):
    scores = {}
    for m in metrics:
        print(f"calculating {m.name}")
        scores[m.name] = await m.ascore(   # call each metric's ascore, pass dict with question, context, and answer(calculation here)
            row={"question": query, "contexts": chunks, "answer": answer}  # result stored in 'scores' dict with the metric's name as key
        )
    return scores

from langchain_core.runnables import RunnableLambda

# Define a global variable to store the context
context_retrieved = None

def inspect(state):
    """Print the state passed between Runnables in a langchain and pass it on"""
    global context_retrieved
    context_retrieved = state.get("context")
    print(state)
    return state

chain = (
    RunnableParallel(
        {
            "context": _search_query | retriever,
            "question": RunnablePassthrough(),
        }
    )
    | RunnableLambda(inspect)
    | prompt
    | llm2
    | StrOutputParser()
)

import pprint

user_question = "What happened to Alice after she ate the cake?"
answer = chain.invoke({"question": user_question})
pprint.pprint(answer)

context_retrieved = '''
She ate a little bit, and said anxiously to herself, “Which way? Which
way?”, holding her hand on the top of her head to feel which way it was
growing, and she was quite surprised to find that she remained the same
size: to be sure, this generally happens when one eats cake, but Alice
had got so much into the way of expecting nothing but out-of-the-way
things to happen, that it seemed quite dull and stupid for life to go
on in the common way.
'''

context_red_retrieved = context_retrieved[:700]
question, contexts, answer = user_question, context_red_retrieved, answer
eval_ans = await score_with_ragas(question, contexts, answer)
print(eval_ans)

@dosu
I tried your solution, but it still doesn't work. Perhaps it's due to the model's context window limitation or because Ragas only allows 'gpt-3.5-16k' to handle larger document sizes without reduction. When I exceed Ragas' context window limit, it keeps showing 'nan'.

It still appeared the same error

@TM02 this could be an issue with the models context length but it is recommended to use a better model for eval so that you can trust the model graded results


IndirectClient (re)generating state token for ajax requests

I have an application here that performs a lot of AJAX requests in parallel for a few reasons, and what is happening is that I get state check errors every now and then, which are pretty hard to debug.
I took a look at org.pac4j.core.client.IndirectClient#getRedirectAction, it has:
        if (ajaxRequestResolver.isAjax(context)) {
            logger.info("AJAX request detected -> returning the appropriate action");
            RedirectAction action = redirectActionBuilder.redirect(context);
            cleanRequestedUrl(context);
            return ajaxRequestResolver.buildAjaxResponse(action.getLocation(), context);
        }

What is very weird for me is that it calls redirectActionBuilder.redirect(context) even when it is an AJAX method, probably just to calculate the location, but it doesn't actually redirect.
So far, so good, but it causes an issue: if redirectActionBuilder.redirect(context) is called, a new State is put in the session store. If I had already started my authentication redirection by a previous request (and this is just an AJAX call being performed by an iframe, for example, which I believe is the case here), by the time my SSO solution returns the result for the first process we have another state token in the session store (put by the AJAX request that happened in parallel), so my auth fails with a "State parameter is different from the one sent in authentication request. Session expired or possible threat of cross-site request forgery" message.
I tried to extend OidcRedirectActionBuilder so we don't overwrite the state for AJAX requests, but at that point, there is no way to check if the request is an AJAX or not (unless I do some ugly stuff), so that's why I'm creating this issue.
I believe that, if it is an AJAX, we should not call redirectActionBuilder.redirect(context) at all. Probably separating the logic to create the location from the actual redirect, but I'm not so sure about that.
Can you help, please?

Started a PR with just a failing test case for now:
https://github.com/pac4j/pac4j/pull/1259
Please, let me know what you think.

The redirection URL is computed to be added as a header to the 401 HTTP response. I don't think it is used in most cases.
So I'm in line that it should be better not to compute it, although it should be possible.
So the redirectActionBuilder.redirect(context) should certainly happen in the AjaxRequestResolver.buildAjaxResponse method if it is necessary. Controlled by some addRedirectionUrlAsHeader property which is false by default.
We can do that in v4 (master branch) as it's a breaking change.
In your case (v3.x), I think the easiest is to override the OidcRedirectActionBuilder with a new class using the AjaxRequestResolver to know if it should do something.
Does it make sense?

@leleuj, please evaluate my proposed solution. The test is now passing and I can confirm the problem is gone in my app as well.

So the redirectActionBuilder.redirect(context) should certainly happen in the AjaxRequestResolver.buildAjaxResponse method if it is necessary

By this phrase I understood that AjaxRequestResolver.buildAjaxResponse  should now be the one deciding if the redirect needs to be calculated or not, so that's what I did.
I also kept the original signature of the org.pac4j.core.http.ajax.DefaultAjaxRequestResolver#buildAjaxResponse(org.pac4j.core.exception.http.RedirectionAction, org.pac4j.core.context.WebContext) is case someone is extending DefaultAjaxRequestResolver, so it should be just a matter of setting the new boolean to restore the old behaviour.

I'm in line with your proposal. See my proposal on the source code refactoring...


[UIImage g8_grayScale]: unrecognized selector sent to instance 0x1c00ad860'

I've reproduced the app WhichFont using Tesseract Without CocoaPods. The problem is it goes in crash in CameraViewControler File
if let rec = recognition {     switch rec {         case .grayscale:              img = img.g8_grayScale() //<-- here goes in crash an there is a warning that say this method is deprecated         case .blackwhite:               img = img.g8_blackAndWhite() //here too      } }
how Can I fix it?

For first you can look into this page https://www.raywenderlich.com/93276/implementing-tesseract-ocr-ios
Also, that methods are removed so you can use GPUImage that is more fast.
Follow this wiki page https://github.com/gali8/Tesseract-OCR-iOS/wiki/Tips-for-Improving-OCR-Results
Daniele Galiotto | www.nexor.it
Inviato da iPhone

Il giorno 16 ago 2017, alle ore 19:43, Rufy86<EMAIL_ADDRESS>ha scritto:
I've reproduced the app WhichFont using Tesseract Without CocoaPods. The problem is it goes in crash in CameraViewControler File
`if let rec = recognition {
switch rec {
case .grayscale:
                img = img.g8_grayScale() <---here and there is a warning:'g8_grayScale()' is deprecated: This method is no longer supported as a part of Tesseract-OCR-iOS
            case .blackwhite:
                img = img.g8_blackAndWhite() <--- here too warning 'g8_blackAndWhite()' is deprecated: This method is no longer supported as a part of Tesseract-OCR-iOS
            }
        }`

how Can I fix it?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Thank you for the reference, but I need to see how it work and if work, before to read other documentation. raywenderlich it's great but old. So, when can you fix this bug?
(Grazie mille per la documentazione, ma vorrei prima vedere come funzione e , soprattutto, se funziona la tua app e l'integrazione  tra Vision di Apple e Tesseract, prima di leggere altra documentazione. Perciò, quando avrai modo di correggere il bug?)
Thank you

You can replace the img.g8_grayScale() method with https://github.com/gali8/Tesseract-OCR-iOS/wiki/Tips-for-Improving-OCR-Results#using-gpuimages-adaptive-threshold-filter

I hate cocoa pods because insert files without control. but now I've installed cocoapods and I don't know why this method work without problem. maybe is because you create the framework, this don't contains some headers that I find in the framework made by cocoaPods.

Yep => https://github.com/gali8/Tesseract-OCR-iOS/issues/225

however, please make a versione or a way to use updated tesseract without cocoapods, thanks


Fix #1120 - Improve batch writer throughput

I try to make some new allowances for improved networking speeds and higher main memory since this code was last modified.  I also remove a possible cause of deadlock on line 249.  Permanently waiting on if 'somethingFailed' will cause a thread to get stuck.  I also start to wait before the memory gets exhausted.  Just trying some simple steps to fix #1120

I improved my pull request for this issue.  I think it will take advantage of faster networking speeds and greater RAM and virtual memory in newer equipment.

@ctubbsii,  I tested my changes by running the ReadWriteIT last week and I saw some 5% speedup compared to master branch in the interleaved, sunnyLG, and sunnyDay tests on one occasion.  I re-ran the tests again a few times and the running times went up and down a little from run to run so I really can't say that I have improved anything here.  The maximum memory of the batch writer and maximum latency are configurable like you say so that is probably the best way to approach the modifying those parameters.
I will look at the TabletServerBatchWriter class a little more deeply to see if I can come up with any better ideas on how to improve throughput.  I will comment on issue #1120 in the issue thread instead of the pull request from now on.

@ctubbsii, I tested my changes by running the ReadWriteIT last week and I saw some 5% speedup compared to master branch in the interleaved, sunnyLG, and sunnyDay tests on one occasion.

That IT is designed to be a basic smoke test to ensure we can put data into Accumulo and it subsequently view it. It's not designed or well-suited for performance testing or experimentation.

I re-ran the tests again a few times and the running times went up and down a little from run to run so I really can't say that I have improved anything here.

Variance is pretty normal. If you want to see if this code changed things in a meaningful way, you'll probably need to do some controlled experiments with various sizes and settings to demonstrate (or disprove) improved throughput with the change(s). A good experiment will also eliminate the JVM startup times as a variable by avoiding using MiniAccumuloInstance (used by ReadWriteIT), and would run with several tservers (to ensure the binning part of the batch writer is exercised, since that's a relevant code path for the question of throughput).

I will look at the TabletServerBatchWriter class a little more deeply to see if I can come up with any better ideas on how to improve throughput. I will comment on issue #1120 in the issue thread instead of the pull request from now on.

The ideas in this PR don't seem to be very similar to the 2-layer queuing strategy described in the old JIRA issue linked on #1120. Have you attempted to implement that design proposed in that ticket at all? It could be implemented alongside the existing BatchWriter, as a new API, instead of modifying the current one. And, if it turns out to be higher performance, we can either swap in the new implementation, or deprecate the old API in favor of the new one.


Want to add new game "Drum_And_Kit"

Describe the project you want to add with tech stack

Drum and Kit Game is a rhythm-based game where players simulate playing a virtual drum kit using input devices such as a keyboard or controller.
Technology used: Html, Css, Javascript
Expected behavior

The game provides visual feedback in the form of on-screen prompts or notes that indicate when and which drum element to hit.
With increasing difficulty levels and varying music tracks, Drum and Kit Game offers an engaging and immersive experience for rhythm game enthusiasts.
Screenshots (optional)

Additional context (optional )

I would like to work on this issue please assign me this.

Hey! I'm GSSoC 2023 contributor,I would like to work on this issue please assign me this.

I have already assigned inder issue 185

Assign me this task under GSSOC

Already present


Destroying a girder with bullets crashes the server.

Steps to reproduce:

Shoot a wall with a projectile weapon until the girder is exposed.
Shoot the girder.

After few tests I came to conclusion it's because of weird interaction between wreckage spawn code and physics system. If wreckage has Physics component, it gonna crash on spawn.
https://github.com/space-wizards/space-station-14/blob/master/Content.Server/GameObjects/Components/Damage/DestructibleComponent.cs#L57
causes server to crash
trying
if (Owner.EntityManager.TrySpawnEntityAt(spawnOnDestroy, Owner.Transform.GridPosition, out var wreck)

returns false
trying
Owner.EntityManager.ForceSpawnEntityAt(spawnOnDestroy, Owner.Transform.GridPosition);

crashes the server
calling var wreck = Owner.EntityManager.SpawnEntity(spawnOnDestroy); without changing wreckage position works, but wreckage obviously spawns at origin point

Fixed by space-wizards/RobustToolbox/pull/821


chore(main): release 0.0.7

:robot: I have created a release beep boop
0.0.7 (2024-06-29)
Bug Fixes

Add protobufjs dependency. (c609191)

Miscellaneous Chores

Prepare 0.0.7 release (cdbb186)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.0.7
:sunflower:


payload_test and streaming_test failing

I've built on a Raspberry Pi 2, with the Raspbian OS: Linux 4.14.79-v7+ #1159 SMP Sun Nov 4 17:50:20 GMT 2018 armv7l GNU/Linux
This is with commit: add10b87a588acfeb5ef5e64ac2e4402467d741b
I have not tried other commits.
On Ubuntu, x86_64, there are no failed tests.
16/22 Test: payload_test
Command: "/home/russ/test/pistache/build/tests/run_payload_test"
Directory: /home/russ/test/pistache/build/tests
"payload_test" start time: Mar 01 17:18 CST
Output:
----------------------------------------------------------
Running main() from gtest_main.cc
[==========] Running 2 tests from 1 test case.
[----------] Global test environment set-up.
[----------] 2 tests from payload
[ RUN      ] payload.from_description
[       OK ] payload.from_description (167 ms)
[ RUN      ] payload.manual_construction
terminate called after throwing an instance of 'Pistache::Async::Error'
  what():  Attempt to reject a fulfilled promise
<end of output>
Test time =   0.42 sec
----------------------------------------------------------
Test Failed.
"payload_test" end time: Mar 01 17:18 CST
"payload_test" time elapsed: 00:00:00
----------------------------------------------------------

17/22 Testing: streaming_test
17/22 Test: streaming_test
Command: "/home/russ/test/pistache/build/tests/run_streaming_test"
Directory: /home/russ/test/pistache/build/tests
"streaming_test" start time: Mar 01 17:18 CST
Output:
----------------------------------------------------------
Running main() from gtest_main.cc
[==========] Running 1 test from 1 test case.
[----------] Global test environment set-up.
[----------] 1 test from streaming
[ RUN      ] streaming.from_description
terminate called without an active exception
<end of output>
Test time =   0.19 sec
----------------------------------------------------------
Test Failed.
"streaming_test" end time: Mar 01 17:18 CST
"streaming_test" time elapsed: 00:00:00
----------------------------------------------------------

The async tests are somewhat flakey (sadly).  If you re-run it many times, does it fail 100% of the time on your platform, or less than 100% of the time?

Have not seen them pass yet, but I've only run it about 15 times. Is it safe to ignore these failures and assume the build is successful? Is it just the test itself that's flaky, and not the actual build?

Generally, on x86, yes.  Do you plan to use the async features?
I recommend that you build and test your app (as much as possible) on x86 as well.
For my own app, I use an custom-build python black-box test suite.  It uses one of the python unit-test frameworks and 'Requests', and spins up my pistache app (new one for each test), sends GET/POST/DELETE/PUT requests and validates the results.  If you did something like that, you could test your app's behavior on both x86 and whatever is in the PI.

@rkubes Do you have these test fails on latest sources (including this commit)

@knowledge4igor I just tried the latest sources a72d6b868771f51150f7b44b04c79a9144313b99 and the payload_test passes now, but the streaming_test still fails.
@dennisjenkins75 I'm not sure yet if I plan to use the async features. I may try to stay away from them if I can't get the tests to be stable.

After further debugging, I have found the issue is just that the test creates too many threads for the Raspberry Pi to handle.
I threw in exception handling to see where it was failing, and it's in the loop at the line where the thread object 'job' is created. Once it tries to create the 228th thread, an exception is thrown "Resource temporarily unavailable"
If I reduce stack size: "ulimit -s 4096" then the test passes without issue or modification (SET_REPEATS = 10)
I'm not sure if we want to leave this issue open or not. I think one could say the test is "broken" because it's failing due to a hardware limitation, as opposed to actual failure of the build/software. I think it comes down to a question of if it's a valid test to expect a pistache implementation to need >200 threads, or should logic be added to limit the number of concurrent threads in the test?

@rkubes  Hello, please, take a look at this change and can you check this fix in your environment.

All tests pass now. Thanks. This can be closed from my point of view.


Commit

just  for fun

Thanks for the PR.
Hope to see more contribution from you in this organization in future.
We will like have you onboard.
Feel free to contact me in case of any doubt.


Support uploading bundle from staged s3 bucket to DSS

Now supports the command hca upload s3://my-remote-bucket/fastqs/bundle.
All files within the bundle must have all required checksums precomputed. These are:

sha1
sha256
crc32c
s3_etag
content-type

Codecov Report

Merging #16 into master will increase coverage by 5.5%.
The diff coverage is 39.62%.

@@            Coverage Diff            @@
##           master      #16     +/-   ##
=========================================
+ Coverage   68.25%   73.76%   +5.5%
=========================================
  Files           7        7
  Lines         482      606    +124
=========================================
+ Hits          329      447    +118
- Misses        153      159      +6

Impacted Files
Coverage Δ

hca/upload_to_cloud.py
64.81% <61.29%> (+23.63%)
:arrow_up:

hca/full_upload.py
27.77% <9.09%> (+0.39%)
:arrow_up:

hca/constants.py
100% <0%> (ø)
:arrow_up:

hca/parser.py
97.35% <0%> (+0.74%)
:arrow_up:

hca/define_api.py
85.88% <0%> (+3.13%)
:arrow_up:

Continue to review full report at Codecov.

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

Ignoring codecov complaints, merging, and packaging new PyPi release.


download from raiplay

Checklist

[x ] I'm asking a question
[ ] I've looked through the README and FAQ for similar questions
[ ] I've searched the bugtracker for similar questions including closed ones

Question

WRITE QUESTION HERE
i've tried to download the video from link:
https://www.raiplay.it/video/2021/01/Che-Dio-ci-aiuti-S6E1-E-tu-sei-pronto-b4b77f3a-0496-4c99-95ab-097034450b02.html
but the result is without audio
the only stream downloaded is video
my config parameters are:
-o "I:\downloads\youtube-dl%(title)s-%(id)s.%(ext)s"
where i'm wrong?
thanks

in some tv shows the audio and video streams are separated so do
-f "bestvideo+bestaudio"

in some tv shows the audio and video streams are separated so do
-f "bestvideo+bestaudio"

not working...

not working...


In API resource, ConditionallyLoadsAttributes::attributes() improperly converts Carbon objects to strings

Laravel Version: 5.7.3
PHP Version: 7.2.10

Description:
When using $this->attributes() in an API resource, it calls $this->resource->toArray() which converts Carbon objects to strings using the model's serializeDate method instead of Carbon's native serializeJson method.  This is not the expected behaviour.  The date serialization format (e.g. for MySQL) is not necessarily what one would want to use for an API response (ISO8601).
Example Resource:
public function toArray($request)
{
    return [
        $this->attributes([
            'created_at',
        ]),
    ];
}

This returns {"created_at":"2018-10-02 05:59:58"} by default, which doesn't include the timezone so is not suitable for an API response.
public function toArray($request)
{
    return [
        'created_at' => $this->created_at,
    ];
}

This returns the correct response: {"created_at":"2018-10-02T05:59:58Z"}.
The work-around is easy, but it took me some time debugging to figure out what was going on.
attributes is convenient for keeping the resource code clean and not repetitive.  I believe it should return Carbon objects, so that their underlying serializeJson methods can be called instead of making assumptions about the desired format.

This is not the expected behaviour.

This is expected design bug, and there are many closed issue about...

Closing this issue because it's already solved, old or not relevant anymore. Feel free to reply if you're still experiencing this issue.

The issue is still very much relevant.  The only solution is to not use the resource attributes method at all.
In case it wasn't clear, the attributes method takes an array of field names, so there's no way to customize the format while using it.  With a date field like like 'created_at', instead of returning the Carbon object, it behaves as if you were going to insert it into a database, and returns the Eloquent-serialized date (as defined in the model, defaults to MySQL format without timezone).  That's not the purpose of Resource classes, however.  If it didn't do any conversion and simply returned the Carbon object, Carbon's own jsonSerialize method would be called to correctly convert it to a JSON string.

Hi @hackel it's the expected behavior and the most relevant way to convert a date in JSON since if you do: new Date("2018-10-02T05:59:58Z") you get the equivalent object in JS.
It's not the Eloquent-serialized (no T or Z to insert into the database).
You can choose you own way to convert Carbon object into any JSON-compatible value using serializeUsing or settings.
See the documentation, it's explained: https://carbon.nesbot.com/docs/#api-json
But I don't understand what you expect.  I guess you realize that the Carbon object cannot be returned in a JSON. JSON can only have plain objects, or primitives, it does not support instances of classes and mostly not PHP classes.

Hi @hackel I guess ->attributes() method is not dedicated to JSON output. There is no particular reason for the method ->toArray to output JSON-compatible values. You should use ->toJson instead. And it's what says the doc: https://laravel.com/docs/5.7/eloquent-serialization#serializing-to-json

You should use ->toJson instead

    public function toJson($options = 0)
    {
        $json = json_encode($this->jsonSerialize(), $options);

        if (JSON_ERROR_NONE !== json_last_error()) {
            throw JsonEncodingException::forModel($this, json_last_error_msg());
        }

        return $json;
    }

    /**
     * Convert the object into something JSON serializable.
     *
     * @return array
     */
    public function jsonSerialize()
    {
        return $this->toArray();
    }

🤣

@LastDragon-ru I understand your reaction but it's not because jsonSerialize calls toArray that you can override one or the other indifferently. toArray, jsonSerialize and toJson can all be used in different places, that's why you should override the higher level. Override toJson if you want a JSON override not toArray because it has a wider impact.
The native toArray is:
public function toArray()
{
  return $this->attributes;
}

By default, there is no change at all to attributes properties. So @hackel what you should do may simply be:
public function toArray()
{
  return array_only($this->attributes, [
    'created_at',
  ]);
}

But if your only concern is about JSON, override jsonSerialize instead with this code and let toArray unchanged.

This is not a bug. You have to code what you would want to be returned as API response if you are not satisfied with the default. For example, on one of the app my company produces, all the clients accept the "2018-10-02 05:59:58" happily and the app is designed to work in a single geographical location only so time zone is not my concern.

I agree this is not a bug. Still it can be a considered as a feature request. As both jsonSerialize and toArray exist, they could both try to guess for each type the best conversion. toArray would be a string cast (strval so __toString called on classes), and jsonSerialize should try first to detect if the type implement JsonSerializable, if so, call jsonSerialize on it, else fallback to the string cast, this seems to me like a smarter behavior that could be implemented in a future version of Laravel.
I made a deeper study here: https://github.com/laravel/framework/issues/21703#issuecomment-446921134
I plan to submit this on https://github.com/laravel/ideas soon.

I'm re-opening this to give this some more thought at a later time. I feel like we should get to the bottom of this but currently don't have the time to check into it.

Great, please take a look at this other (but very related) topic: https://github.com/laravel/framework/issues/21703#issuecomment-446921134
And this: https://github.com/laravel/ideas/issues/1481
I could make a PR, but I do not want to spend a lot of time if we're not first OK about what to do.
Main expectations to meet IMO:

By default a Carbon object sent inside a JSON string should be the same as json_encode($thisCarbonDate) (means call the ->toJSON method of Carbon).
Dy default, a Carbon object dump as string (in SQL query for example) should be the same as strval($thisCarbonDate) (->__toString())
We should be able to customize separately the dateJsonFormat (so ->format($dateJsonFormat) would be called instead of ->toJSON) and the dateStringFormat (so ->format($dateStringFormat ) would be called instead of ->__toString)

In Laravel 7, a new default for date serialization will be used: https://github.com/laravel/framework/pull/30715


Add eopsin builtins for UPLC verify signature builtins

UPLC features (by now 3) builtin functions to verify signatures. Since it is nontrivial to call them from python code, I suggest to add functions to eopsin.builtins, a python file that hosts python functions that simulate these builtins. They would not be actually compiled though but just replaced with raw UPLC at compile time.
Usage example
from eopsin.builtins import verify_schnorr

def validator(msg: bytes) -> bool:
   return verify_schnorr(msg, b"pubkey", b"sig")

This is a description of what needs to be updated for this to become "real".

Bump the required version of the uplc package to 0.5.4 in setup.py
Add a new rewrite module that rewrites imports from eopsin.builtins

something in similar spirit was written for imports from hashlib
the raw pluthon functions injected can more or less directly forward to the new builtin functions but must adhere to the eopsin ABI

Add an actual module builtins that implements the builtin functions in proper python. This can also just delegate to their implementation in the uplc package found here: https://github.com/ImperatorLang/uplc/blob/master/uplc/ast.py#L527
Add a short description to the README on how to properly install libsecp256k1 if one wants to use the new verification primitives similar to the description in uplc

covered as part of #134


Contract

updates item editing to match the new server code
edited items will now be considered the same item

note that this update will mean listings created before this cannot be deleted. They may still be editable.


Avoid redundant std::move

I added this move initially because I believed the NVRO optimization didn't apply here (return type differs from variable type being returned). However, upon closer inspection this is not necessary: see "Automatic move from local variables and parameters" on https://en.cppreference.com/w/cpp/language/return, which states that even if the type differs, move-returning will be done if available.

My understanding is that automatic moving will happen here. As you've noted, move-returning can be done even if the id-expression in the return statement is not of the same type as the function return type.
However, note that C++17 mandatory move elision cannot happen - for that the id-expression in the return statement does have to match the return type. See https://en.cppreference.com/w/cpp/language/copy_elision:

In a return statement, when the operand is a prvalue of the same class type (ignoring cv-qualification) as the function return type

Therefore, the compiler won't initialize directly into the storage for the return object to elide copy and move.
The main reason not to use std::move in the return operand is in cases where doing so might prevent move elision (eg the object can't be moved so will have to be constructed and copied rather than just constructed into the storage for the return object). That isn't relevant here since the move elision isn't possible.
In summary, I don't think this makes any difference. I have no strong preference either way, but there's no harm in doing it so if you think it's clearer then ACK 235217895c2d507ec4498a50351ce0e570eadadf.

Example copy/move elision code
Partially copied from https://stackoverflow.com/questions/51402731/why-does-returning-a-stdoptional-sometimes-move-and-sometimes-copy / http://coliru.stacked-crooked.com/a/6bf853750b38d110
#include <optional>
#include <iostream>
#include <string>

class UserName
{
public:
    explicit UserName() : mName("Default")
    {
        std::cout << "UserName::UserName(\'";
        std::cout << mName << "\')\n";
    }

    explicit UserName(const std::string& str) : mName(str)
    {
        std::cout << "UserName::UserName(\'";
        std::cout << mName << "\')\n";
    }
    ~UserName()
    {
        std::cout << "UserName::~UserName(\'";
        std::cout << mName << "\')\n";
    }
    UserName(const UserName& u) : mName(u.mName)
    {
        std::cout << "UserName::UserName(copy \'";
        std::cout << mName << "\')\n";
    }
    UserName(UserName&& u) : mName(std::move(u.mName))
    {
        std::cout << "UserName::UserName(move \'";
        std::cout << mName << "\')\n";
    }
    UserName& operator=(const UserName& u) // copy assignment
    {
        mName = u.mName;

        std::cout << "UserName::=(copy \'";
        std::cout << mName << "\')\n";

        return *this;
    }
    UserName& operator=(UserName&& u) // move assignment
    {
        mName = std::move(u.mName);

        std::cout << "UserName::=(move \'";
        std::cout << mName << "\')\n";

        return *this;
    }

private:
    std::string mName;
};

std::optional<UserName> CreateUserElideCopyMove()
{
    std::optional<UserName> u = std::make_optional<UserName>("ElideCopyMove");
    return u; // u is of the return type - construct directly into return storage
}

std::optional<UserName> CreateUserAutomaticMove()
{
    UserName u("AutoMove");
    return u; // u is not of the return type - copy can be elided but not move
}

std::optional<UserName> CreateUserExplicitMove()
{
    UserName u("ExplicitMove");
    return std::move(u); // std::move(u) is an rvalue - move ctor is used
}

int main()
{
    {
        auto a = CreateUserElideCopyMove();
    }
    {
        auto b = CreateUserAutomaticMove();
    }
    {
        auto c = CreateUserExplicitMove();
    }
}

Program returned: 0
UserName::UserName('ElideCopyMove')
UserName::~UserName('ElideCopyMove')
UserName::UserName('AutoMove')
UserName::UserName(move 'AutoMove')
UserName::~UserName('')
UserName::~UserName('AutoMove')
UserName::UserName('ExplicitMove')
UserName::UserName(move 'ExplicitMove')
UserName::~UserName('')
UserName::~UserName('ExplicitMove')

I don't believe any ellision will happen here. As I see it, the return value is not guaranteed to be unique at compile-time because of the if branch above.  Because of that, this could be returning a named object or a temporary. So I don't think the compiler could ellide it?
Even in that case, though, move still wouldn't be needed because "In a return statement or a throw-expression, if the compiler cannot perform copy elision but the conditions for copy elision are met or would be met, except that the source is a function parameter, the compiler will attempt to use the move constructor even if the object is designated by an lvalue;"

Yes, to be clear: it's obvious elision cannot happen here. I'm just trying to make sure the object isn't copied unnecesarily.

Also, my motivation for this change is that gcc 10.3 warns about a redundant move here.

ACK 235217895c2d507ec4498a50351ce0e570eadadf
There's a good description of the redundant move warning here in the -Wredundant-move section of https://developers.redhat.com/blog/2019/04/12/understanding-when-not-to-stdmove-in-c/

ACK 235217895c2d507ec4498a50351ce0e570eadadf

@jnewbery Thanks for your explanation, I had wondered if there was any downside to the move other than noise in the code.


🐛 Flashing Label /Tooltip

Describe the bug
When a label/tooltip is at the end of the screen,it keeps on appearing/disappearing automatically.
To Reproduce
Steps to reproduce the behavior:

Go to  https://bdlukaa.github.io/fluent_ui/
Click on 'command bar'
Scroll down to 'carded complex command bar with many items (horizontal scrolling)
add tool tip to 'refresh' button
bring mouse cursor on refresh button such that the cursor is on top of label.
you should see flashing label.

Expected behavior
label/ tool tip should not flash. Instead re-position if it has no available place.
Screenshots

Additional context
The label might not be visible in ss, but it appears below cursor and has screen end on right. So no space for label to be drawn from pointer's current position to it's natural size. So kinda flashes. Re-draws again and again to start from cursor position. But may be fails due to screen (context / size) constraints.

Sorry, but I can't reproduce it :/

Can you share a reproducible snippet?

I guess this was fixed in dev version. I was using stable version.
Thanks for your time.


Need to split a types module out from notify-listen-beam

The HasNotification and HasChangeNotification classes need to be accessible to GHCJS so they should be decoupled from the backend-specific beam code.

Wait, why do they need to be accessible to the frontend? I can't see a reason.

They don't, but you want them to be in the common code so you don't have orphans when defining your schema.


Save engine configuration

Currently the engine config is created at creation time and used.
Best would be to

[ ] Save the config of the engine as .ron file
[ ] Create a seperate graphics configuration
[ ] use the graphics configuration at renderer creation time

This should be done first: https://github.com/SiebenCorgie/jakar-engine/issues/16


[Bug]: Error [ERR_REQUIRE_ESM]: require() of ES Module

What happened?
When I run my Node script using Style Dictionary and sd-tranforms, I get this error:
./Tokens/node_modules/@tokens-studio/sd-transforms/dist/src/parsers/add-font-styles.cjs:3
var utils = require('style-dictionary/utils');
            ^

Error [ERR_REQUIRE_ESM]: require() of ES Module<EMAIL_ADDRESS>from<EMAIL_ADDRESS>not supported.
Instead change the require of index.js in<EMAIL_ADDRESS>to a dynamic import() which is available in all CommonJS modules.
    at Object.<anonymous> (./Tokens/node_modules/@tokens-studio/sd-transforms/dist/src/parsers/add-font-styles.cjs:3:13)
    at Object.<anonymous> (./Tokens/node_modules/@tokens-studio/sd-transforms/dist/src/parsers/parse-tokens.cjs:4:21)
    at Object.<anonymous> (./Tokens/node_modules/@tokens-studio/sd-transforms/dist/src/registerTransforms.cjs:16:19)
    at Object.<anonymous> (./Tokens/node_modules/@tokens-studio/sd-transforms/dist/src/index.cjs:3:26)
    at Object.<anonymous> (./Tokens/build-from-figma.js:5:5) {
  code: 'ERR_REQUIRE_ESM'
}

Node.js v20.9.0

I get the same error with Style Dictionary latest 3.x and 4.x versions, and both sd-transform 0.13.1 and 0.13.2.
Reproduction
No response
Expected output
No response
Version
0.13.2

Hi, you're probably using style-dictionary v4 which is ESM only. If you use sd-transforms in CJS context, it will use CJS and try to use style-dictionary as CJS as well.
There's a lot of articles (e.g. https://blog.logrocket.com/commonjs-vs-es-modules-node-js/) about CommonJS versus ES Modules, but the summary is that ES Modules is a standardized format for Javascript, including for browsers, and since style-dictionary v4 is written to be browser-compatible out of the box, we've switched to this modern format of writing Javascript modules, rather than using the old Node default format (CommonJS).
If you want to upgrade to style-dictionary v4, your code must be upgraded to ESM format everywhere (recommended, not too much work usually), or use a build-time tool that allows you to execute javascript with mixed formats (not recommended, as it introduces build-time complexity that is in my experience tough to get rid of later down the line)

@jorenbroekema I know ESM/CJS.
As I mentioned in my issue, I get the error with both style-dictionary v3.x and v4.x
As I plan to move to Style Dictionary 4 anyway, I'll change my code to be ESM, and check again.

I changed my code to ESM, and I get a new error:
file:///…/Tokens/build-from-figma.js:6
import { StyleDictionary } from 'style-dictionary';
         ^^^^^^^^^^^^^^^
SyntaxError: The requested module 'style-dictionary' does not provide an export named 'StyleDictionary'
    at ModuleJob._instantiate (node:internal/modules/esm/module_job:131:21)
    at async ModuleJob.run (node:internal/modules/esm/module_job:213:5)
    at async ModuleLoader.import (node:internal/modules/esm/loader:316:24)
    at async loadESM (node:internal/process/esm_loader:34:7)
    at async handleMainPromise (node:internal/modules/run_main:66:12)

Node.js v20.9.0

I see import { StyleDictionary } from 'style-dictionary'; in a lot of code of the https://github.com/amzn/style-dictionary/tree/v4 branch, so I don't understand.

import StyleDictionary from 'style-dictionary'; without the curly braces works.
Now I get a new error: TypeError: StyleDictionary.extend is not a function
I'm following this example but with ESM code: https://github.com/tokens-studio/sd-transforms#multi-dimensional-theming

Right, so style-dictionary v4 is a new major version and comes with some breaking changes https://github.com/amzn/style-dictionary/blob/v4/CHANGELOG.md
Specifically the breaking change that's causing the error for you is this one https://github.com/amzn/style-dictionary/blob/v4/CHANGELOG.md#major-changes-1 :
/**
 * old:
 *   const sd = StyleDictionary.extend({ source: ['tokens.json'], platforms: {} });
 *   sd.buildAllPlatforms();
 */
const sd = new StyleDictionary({ source: ['tokens.json'], platforms: {} });
await sd.buildAllPlatforms();


Drop down field - missing text

Expected behavior:
Chosen question or answer type on the setting screen for tasks should be displayed in the drop down box.
Actual behavior:
The chosen question or answer types disappear after choosing them:
 <--- Text is missing

Done :-)


Ribbon positioning in canvas

We are building a force-direct diagram with chords diagrams at each node. We experienced a bug, chords are fixed at the origin of the canvas without any possibility of positioning.

This is not a bug; this is the documented behavior. As the README says, you must use context.translate or similar to change the origin of the ribbon.

Finally I translated (x,y) and translated back (-x,-y) for each ribbon, and it works fine.
You were right, thanks for helping.

I would recommend using context.save and context.restore, but either would work.


Make iputils-ping a package, not dev, dependency (FW8 branch)

If ping is not present at runtime, Chorus fails to send anything. In some Docker deployments, the iputils-ping package is not installed by default, so we need lfmerge to depend in iputils-ping so that it will install correct dependencies in Docker/Kubernetes environments.
This is https://github.com/sillsdev/LfMerge/pull/120 applied against fieldworks8-master. Both PRs should be merged together.

This change is

#120 was approved by @ermshiperete so I'm merging both.


Support Scala Native

It would be nice if Magnolia worked on Scala Native. Anyone familiar with setting up Scala Native in SBT could probably tackle this.

scala-native does not support sbt 1.x

https://github.com/scala-native/scala-native/pull/1039
https://github.com/propensive/magnolia/blob/eb53a6df0/project/build.properties

Aha, knowing that is going to same me some time, @xuwei-k -- thanks. I've been planning to build Scala Native programs directly from the command line (without SBT), but couldn't find enough documentation. Maybe I'll try a bit harder to find out, and I can do it this way.

also scala native doesn't support scala 2.12

https://github.com/scala-native/scala-native/issues/233

We're still supporting 2.11.x, so at least that shouldn't be too big a problem. :)


swigwin download path changed

Tried to install ORTools from source and got an error in swigwin
The new path is:
https://newcontinuum.dl.sourceforge.net/project/swig/swigwin/swigwin-4.0.1/swigwin-4.0.1.zip
Changed Makefile.third_party.win.mk to solve the problem

did you use master or default branch ?

Hi Mizux, I used the default  (stable) branch.
Best regards,

This is fixed on master.
Thanks
Laurent Perron | Operations Research |<EMAIL_ADDRESS>| (33) 1 42 68 53
00
Le mar. 31 mars 2020 à 18:26, davidhdezf<EMAIL_ADDRESS>a
écrit :

Hi Mizux, I used the default (stable) branch.
Best regards,
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/1943#issuecomment-606733816,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACUPL3JZVG75TORM2Y3ZF7LRKIKU7ANCNFSM4LXIRDFQ
.


Update standard_library_numerics.rst

Fix wrong function name in requirements from To_Decibel to To_Factor.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Good catch! Thanks for the correction!


Investigate CircleCI failures

E.g. https://circleci.com/gh/snowdrop/spring-cloud-stream-binder-artemis/68?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link

I'll try replacing CircleCI with GitHub action because I cannot reproduce the test failure locally and historically there were such issues on CircleCi on other projects too.


github webhook: For release events show actions and tag name.

The github webhook release event comes in several defined actions (e.g. created or deleted). The current webhook always says published even if the event got deleted. The new implementation takes the action and puts it 1:1 into the message (as it fits gramatically).
Furthermore instead of the release it now says release for tag xyz. (I am rather showing tag names than release names, as release names are often null).
Testing Plan:
The existing test got updated. I could also add payload of all action types, but that seems unnecessary overhead as it is passed 1:1.
GIFs or Screenshots:
No UI change.

Great, merged, thanks @Brutus5000!