text:
Getting onConnectionChange FAILED error from the flutter's janus_client.

Hey.
I've installed the Janus server https://185.87.194.121:8189/janus/info with default configs according to the readme's guide and it works properly for the Javascript client. But it doesn't work with this fluter client, I get D/FlutterWebRTCPlugin(11066): onConnectionChange FAILED and can't creat a room, for example.
Does anyone face this problem?
Thank you.

What exactly is the issue you are facing, if you could give brief information with example code i would be able to assist better

Thank you very much.
First of all, i've ensured that my Janus server is establised:
const WebSocket = require('ws');

const ws = new WebSocket('wss://112-24.ru:8198/', 'janus-protocol');

ws.on('open', function open() {
    ws.send('{"janus" : "create", "transaction" : "123"}');
});

and received success:
received: {
   "janus": "success",
   "transaction": "123",
   "data": {
      "id": 6620688758132739
   }
}

Then I ran the text_room example https://github.com/flutterjanus/flutter_janus_client/blob/master/example/lib/typed_examples/text_room.dart with these servers in the conf.dart
Map<String, String> servermap = {
  'janus_ws': 'wss://112-24.ru:8198/',
  'janus_rest': 'http://112-24.ru:8288/janus',
};

Here is my init method
  initializeClient() async {
    rest = RestJanusTransport(url: servermap['janus_rest']);
    ws = WebSocketJanusTransport(url: servermap['janus_ws']);
    janusClient =
        JanusClient(withCredentials: false, transport: ws, iceServers: [
      RTCIceServer(
          urls: "stun:stun1.l.google.com:19302", username: "", credential: "")
    ]);
    session = await janusClient.createSession();
    textRoom = await session.attach<JanusTextRoomPlugin>();
    var foo = await textRoom.createRoom(
        roomId: "1111111",
        permanent: true,
        isPrivate: false,
        description: "test_room_with_description",
        history: 100);
    debugPrint("textRoom.createRoom");
    debugPrint(foo);
    debugPrint("textRoom.listRooms");
    debugPrint(await textRoom.listRooms());
  }

where I want to see the create room json payload to the server, but I see this:
I/flutter ( 6689): textRoom.createRoom
I/flutter ( 6689): null
I/flutter ( 6689): textRoom.listRooms
I/flutter ( 6689): null

The full log:
I/flutter ( 6689): [INFO] JanusClient: Creating Session
I/flutter ( 6689): [FINE] JanusClient: fine message
I/flutter ( 6689): [INFO] JanusClient: Session Created
I/flutter ( 6689): [FINE] JanusClient: {janus: attach, transaction: 1a4c0039-58c9-4a55-9a7f-e6d8e58f3280, token: null, apisecret: null, session_id: 5886030759655815, plugin: janus.plugin.textroom}
I/flutter ( 6689): [INFO] JanusClient: using web socket transport for creating plugin handle
I/flutter ( 6689): [FINE] JanusClient: {janus: success, session_id: 5886030759655815, transaction: 1a4c0039-58c9-4a55-9a7f-e6d8e58f3280, data: {id: 6947476528710540}}
I/flutter ( 6689): [INFO] JanusClient: Plugin Initialized
I/flutter ( 6689): [FINE] JanusClient: peer connection configuration
I/flutter ( 6689): [FINE] JanusClient: {iceServers: [{username: , credential: , urls: stun:stun1.l.google.com:19302}], sdpSemantics: unified-plan}
I/flutter ( 6689): [FINE] JanusClient: webRTC stack intialized
I/org.webrtc.Logging( 6689): NativeLibrary: Loading native library: jingle_peerconnection_so
I/org.webrtc.Logging( 6689): NativeLibrary: Loading library: jingle_peerconnection_so
I/org.webrtc.Logging( 6689): PeerConnectionFactory: PeerConnectionFactory was initialized without an injected Loggable. Any existing Loggable will be deleted.
I/org.webrtc.Logging( 6689): EglBase14Impl: SDK version: 32. isEGL14Supported: true
I/org.webrtc.Logging( 6689): EglBase14Impl: Using OpenGL ES version 2
D/EGL_emulation( 6689): eglCreateContext: 0xb400007be9fe4390: maj 3 min 0 rcv 3
I/org.webrtc.Logging( 6689): WebRtcAudioManagerExternal: Sample rate is set to 44100 Hz
I/org.webrtc.Logging( 6689): WebRtcAudioManagerExternal: Sample rate is set to 44100 Hz
E/org.webrtc.Logging( 6689): JavaAudioDeviceModule: HW AEC not supported
E/org.webrtc.Logging( 6689): JavaAudioDeviceModule: HW NS not supported
I/org.webrtc.Logging( 6689): JavaAudioDeviceModule: createAudioDeviceModule
I/org.webrtc.Logging( 6689): JavaAudioDeviceModule: HW NS will not be used.
I/org.webrtc.Logging( 6689): JavaAudioDeviceModule: HW AEC will not be used.
I/org.webrtc.Logging( 6689): WebRtcAudioEffectsExternal: ctor@[name=main, id=2]
I/org.webrtc.Logging( 6689): WebRtcAudioRecordExternal: ctor@[name=main, id=2]
I/org.webrtc.Logging( 6689): WebRtcAudioTrackExternal: ctor@[name=main, id=2]
I/org.webrtc.Logging( 6689): PeerConnectionFactory: onNetworkThreadReady
I/org.webrtc.Logging( 6689): PeerConnectionFactory: onSignalingThreadReady
I/org.webrtc.Logging( 6689): PeerConnectionFactory: onWorkerThreadReady
I/flutter ( 6689): textRoom.createRoom
I/flutter ( 6689): null
I/flutter ( 6689): textRoom.listRooms
I/flutter ( 6689): null
D/CompatibilityChangeReporter( 6689): Compat change id reported: 78294732; UID 10149; state: DISABLED
D/EGL_emulation( 6689): app_time_stats: avg=125.62ms min=7.43ms max=484.29ms count=11
I/flutter ( 6689): using transrecievers in prepare transrecievers
D/MediaConstraintsUtils( 6689): mandatory constraints are not a map
D/MediaConstraintsUtils( 6689): optional constraints are not an array
I/org.webrtc.Logging( 6689): NetworkMonitor: Start monitoring with native observer -5476376614138694608
W/org.webrtc.Logging( 6689): NetworkMonitorAutoDetect: Unable to obtain permission to request a cellular network.
I/org.webrtc.Logging( 6689): NetworkMonitorAutoDetect: Network becomes available: 101
I/org.webrtc.Logging( 6689): NetworkMonitorAutoDetect: capabilities changed: [ Transports: WIFI Capabilities: NOT_METERED&INTERNET&NOT_RESTRICTED&TRUSTED&NOT_VPN&VALIDATED&NOT_ROAMING&FOREGROUND&NOT_CONGESTED&NOT_SUSPENDED&NOT_VCN_MANAGED LinkUpBandwidth>=12000Kbps LinkDnBandwidth>=30000Kbps TransportInfo: <SSID: <unknown ssid>, BSSID: 02:00:00:00:00:00, MAC: 02:00:00:00:00:00, Security type: 0, Supplicant state: COMPLETED, Wi-Fi standard: 1, RSSI: -50, Link speed: 1Mbps, Tx Link speed: 1Mbps, Max Supported Tx Link speed: 11Mbps, Rx Link speed: 2Mbps, Max Supported Rx Link speed: 11Mbps, Frequency: 2447MHz, Net ID: -1, Metered hint: false, score: 60, CarrierMerged: false, SubscriptionId: -1, IsPrimary: -1> SignalStrength: -50]
D/FlutterWebRTCPlugin( 6689): onIceGatheringChangeGATHERING
D/FlutterWebRTCPlugin( 6689): onConnectionChangeCONNECTING
D/FlutterWebRTCPlugin( 6689): onIceCandidate
D/FlutterWebRTCPlugin( 6689): onIceCandidate
D/FlutterWebRTCPlugin( 6689): onIceCandidate
D/FlutterWebRTCPlugin( 6689): onIceCandidate
I/flutter ( 6689): [FINE] JanusClient: sending jsep
I/flutter ( 6689): [FINE] JanusClient: {sdp: v=0
I/flutter ( 6689): o=- 2872195025229597058 2 IN IP4 127.0.0.1
I/flutter ( 6689): s=-
I/flutter ( 6689): t=0 0
I/flutter ( 6689): a=group:BUNDLE 0
I/flutter ( 6689): a=extmap-allow-mixed
I/flutter ( 6689): a=msid-semantic: WMS
I/flutter ( 6689): m=application 9 UDP/DTLS/SCTP webrtc-datachannel
I/flutter ( 6689): c=IN IP4 0.0.0.0
I/flutter ( 6689): a=ice-ufrag:gsKm
I/flutter ( 6689): a=ice-pwd:qIUXSYbt6PKWUY/Ihmda8o3P
I/flutter ( 6689): a=ice-options:trickle renomination
I/flutter ( 6689): a=fingerprint:sha-256 1F:81:1B:4E:54:AF:31:C9:09:5D:1F:57:E2:FF:D4:34:68:89:B1:98:EF:08:37:DD:32:18:6B:62:CE:E0:36:01
I/flutter ( 6689): a=setup:active
I/flutter ( 6689): a=mid:0
I/flutter ( 6689): a=sctp-port:5000
I/flutter ( 6689): , type: answer}
I/org.webrtc.Logging( 6689): NetworkMonitorAutoDetect: link properties changed
D/FlutterWebRTCPlugin( 6689): onIceCandidate
D/FlutterWebRTCPlugin( 6689): onIceCandidate
D/FlutterWebRTCPlugin( 6689): onIceCandidate
D/FlutterWebRTCPlugin( 6689): onIceCandidate
D/FlutterWebRTCPlugin( 6689): onIceCandidate
D/InputMethodManager( 6689): showSoftInput() view=io.flutter.embedding.android.FlutterView{e4c2d04 VFE...... .F....ID 0,0-1080,2176 #1 aid=1073741824} flags=0 reason=SHOW_SOFT_INPUT
D/EGL_emulation( 6689): app_time_stats: avg=3491.18ms min=2090.06ms max=4892.29ms count=2
D/EGL_emulation( 6689): app_time_stats: avg=316.73ms min=13.14ms max=4151.98ms count=14
D/InsetsController( 6689): show(ime(), fromIme=true)
D/EGL_emulation( 6689): app_time_stats: avg=89.43ms min=10.98ms max=498.26ms count=16
D/InputMethodManager( 6689): showSoftInput() view=io.flutter.embedding.android.FlutterView{e4c2d04 VFE...... .F...... 0,0-1080,2176 #1 aid=1073741824} flags=0 reason=SHOW_SOFT_INPUT
D/InsetsController( 6689): show(ime(), fromIme=true)
D/InputMethodManager( 6689): showSoftInput() view=io.flutter.embedding.android.FlutterView{e4c2d04 VFE...... .F...... 0,0-1080,2176 #1 aid=1073741824} flags=0 reason=SHOW_SOFT_INPUT
D/InsetsController( 6689): show(ime(), fromIme=true)
D/EGL_emulation( 6689): app_time_stats: avg=86.72ms min=12.75ms max=492.25ms count=15
I/flutter ( 6689): [FINE] JanusClient: sending text message to room:1234 with payload:{transaction: fxyU($BMp*20143870513, textroom: message, room: 1234, text: gh}
I/flutter ( 6689): before send RTCDataChannelMessage
I/TextInputPlugin( 6689): Composing region changed by the framework. Restarting the input method.
W/IInputConnectionWrapper( 6689): beginBatchEdit on inactive InputConnection
W/IInputConnectionWrapper( 6689): getTextBeforeCursor on inactive InputConnection
W/IInputConnectionWrapper( 6689): getTextAfterCursor on inactive InputConnection
W/IInputConnectionWrapper( 6689): getSelectedText on inactive InputConnection
W/IInputConnectionWrapper( 6689): endBatchEdit on inactive InputConnection
D/InsetsController( 6689): show(ime(), fromIme=true)
D/EGL_emulation( 6689): app_time_stats: avg=39.05ms min=10.35ms max=450.74ms count=26
D/EGL_emulation( 6689): app_time_stats: avg=67.43ms min=7.93ms max=504.98ms count=22
D/EGL_emulation( 6689): app_time_stats: avg=499.89ms min=498.22ms max=500.96ms count=3
D/EGL_emulation( 6689): app_time_stats: avg=499.99ms min=499.17ms max=501.00ms count=3
D/EGL_emulation( 6689): app_time_stats: avg=500.25ms min=498.42ms max=502.09ms count=2
D/EGL_emulation( 6689): app_time_stats: avg=499.66ms min=498.85ms max=501.18ms count=3
D/FlutterWebRTCPlugin( 6689): onConnectionChangeFAILED
D/EGL_emulation( 6689): app_time_stats: avg=500.16ms min=498.75ms max=501.50ms count=3
D/EGL_emulation( 6689): app_time_stats: avg=499.22ms min=491.79ms max=506.89ms count=3
...

the client has its session

and also

could you please help me with this? thank you a lot!

Yes you are right and this is happening because i forgot to send payload to janus server will fix it asap and you can test it in next release

@shivanshtalwar0 thank you a lot! But why the issue doesn't appear with https://janus.conf.meetecho.com/janus then?

Can you try now and let me know if the issue is fixed for you in latest commit

works. thank you a lot!


text:
HelmRelease Values wrongly merged when there's a TargetPath Array reference

Hi,
When using the valuesFrom.targetPath property with an array index on HelmReleases, helm-controller is not merging correctly the content of the values <> valuesFrom properties.
In this scenario:
apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
  name: kube-prometheus-stack
spec:
...
  values:
    prometheus:
      prometheusSpec:
        remoteWrite:
        - basicAuth:
            username:
              name: prometheus-secret
              key: username
            password:
              name: prometheus-secret
              key: password
  valuesFrom:
  - kind: ConfigMap
    name: prometheus-secret
    valuesKey: url
    targetPath: prometheus.prometheusSpec.remoteWrite[0].url
    optional: false

When HelmRelease Values are merged the remoteWrite[0].url doesn't get merged into the remoteWrite[0] property.
After further investigation I've concluded that there is an issue in the composeValues function within the helm-controller.
The desired scenario would be to correctly merge the values and the url property to get the correct content.

This behaves as it is documented in https://fluxcd.io/docs/components/helm/helmreleases/#values-overrides where it states that spec.values is the last to be merged, and it overwrites anything that was merged in before it.
I would suggest just placing your spec.values content into another ConfigMap, and merging it ahead of your url secret. The documented behavior is that spec.values always gets merged last, and this seems to be unlikely to change. Since your spec.values has prometheus.prometheusSpec.remoteWrite defined in it, I believe this will overwrite the array data that was present (rather than merge arrays, or appending).
I think you want url to be set in the existing array entry at the 0 index, which will happen if you write the merges in the opposite order. This data in your spec.values actually looks like a secret anyway, you don't want it to be written unencrypted in your HelmRelease body IMHO. Secrets should go in secrets, and if their lifecycle allows that they can be loaded from git, they should use SOPS encryption.

@kingdonb thanks for giving even more detailed information than what I shared in https://github.com/fluxcd/helm-controller/pull/280#issuecomment-866147618. Assuming there is very little more to be shared, I am going to go ahead and close this issue.

Thanks for your awesome explanation :)

source: gharchive/issue

authors: hiddeco kingdonb samueltorres

repo: fluxcd/helm-controller

license_type: permissive

license_source: github-api


text:
Update process fails and delete all installed app via FluxCD

Hello everyone 👋🏼,
I've tried to upgrade terraform-provider-flux from 0.2.1 to 0.7.3 and as far as  I know  starting  from 0.18 kustomize.toolkit.fluxcd.io was bumped to v1beta2.
So, the problems what I faced are next:

During running apply, we can see that old Kustomization manifest going to deleted

# module.flux.kubectl_manifest.sync["kustomize.toolkit.fluxcd.io/v1beta1/kustomization/flux-system/flux-system"] will be destroyed
  - resource "kubectl_manifest" "sync" {
      - api_version             = "kustomize.toolkit.fluxcd.io/v1beta1" -> null
      - force_new               = false -> null
      - id                      = "/apis/kustomize.toolkit.fluxcd.io/v1beta1/namespaces/flux-system/kustomizations/flux-system" -> null
      - kind                    = "Kustomization" -> null
      - live_manifest_incluster = (sensitive value)
      - live_uid                = "ec741eeb-5ef5-420f-8527-5c7a4a9b8afb" -> null
      - name                    = "flux-system" -> null
      - namespace               = "flux-system" -> null
      - uid                     = "ec741eeb-5ef5-420f-8527-5c7a4a9b8afb" -> null
      - validate_schema         = true -> null
      - wait_for_rollout        = true -> null
      - yaml_body               = (sensitive value)
      - yaml_body_parsed        = <<-EOT
            apiVersion: kustomize.toolkit.fluxcd.io/v1beta1
            kind: Kustomization
            metadata:
              name: flux-system
              namespace: flux-system
            spec:
              interval: 10m0s
              path: ./clusters/dev-beta-sandbox
              prune: true
              sourceRef:
                kind: GitRepository
                name: flux-system
              validation: client
        EOT -> null
      - yaml_incluster          = (sensitive value)
    }

And new one will be created :
# module.flux.kubectl_manifest.sync["kustomize.toolkit.fluxcd.io/v1beta2/kustomization/flux-system/flux-system"] will be created
  + resource "kubectl_manifest" "sync" {
      + api_version             = "kustomize.toolkit.fluxcd.io/v1beta2"
      + force_new               = false
      + id                      = (known after apply)
      + kind                    = "Kustomization"
      + live_manifest_incluster = (sensitive value)
      + live_uid                = (known after apply)
      + name                    = "flux-system"
      + namespace               = "flux-system"
      + server_side_apply       = false
      + uid                     = (known after apply)
      + validate_schema         = true
      + wait_for_rollout        = true
      + yaml_body               = (sensitive value)
      + yaml_body_parsed        = <<-EOT
            apiVersion: kustomize.toolkit.fluxcd.io/v1beta2
            kind: Kustomization
            metadata:
              name: flux-system
              namespace: flux-system
            spec:
              interval: 10m0s
              path: ./clusters/dev-beta-sandbox
              prune: true
              sourceRef:
                kind: GitRepository
                name: flux-system
        EOT
      + yaml_incluster          = (sensitive value)
    }

That's fine, but after deleting Kustomization , all apps what were installed via FluxCD  deleted  too, everything stuck and terraform apply failed.
Examples:
# stuck namespaces
cert-manager       Terminating   12h
confluent          Terminating   12h
default            Active        14h
external-secrets   Terminating   12h
flux-system        Active        14h
ingress-nginx      Terminating   13m
...

# terrafom output

Error: Provider produced inconsistent result after apply

When applying changes to
module.flux.kubectl_manifest.install["rbac.authorization.k8s.io/v1/clusterrole/crd-controller-flux-system"],
provider "provider[\"registry.terraform.io/gavinbunney/kubectl\"]" produced
an unexpected new value: Root resource was present, but now absent.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

Error: Deployment exceeded its progress deadline: &DeploymentCondition{Type:Progressing,Status:False,Reason:ProgressDeadlineExceeded,Message:ReplicaSet "source-controller-5bd4cb998" has timed out progressing.,LastUpdateTime:2021-11-19 09:57:28 +0000 UTC,LastTransitionTime:2021-11-19 09:57:28 +0000 UTC,}

  with module.flux.kubectl_manifest.install["apps/v1/deployment/flux-system/source-controller"],
  on .terraform/modules/flux/modules/flux/main.tf line 74, in resource "kubectl_manifest" "install":
  74: resource "kubectl_manifest" "install" {

Error: flux-system/flux-system failed to run apply: error when creating "/tmp/460057381kubectl_manifest.yaml": create not allowed while custom resource definition is terminating

  with module.flux.kubectl_manifest.sync["kustomize.toolkit.fluxcd.io/v1beta2/kustomization/flux-system/flux-system"],
  on .terraform/modules/flux/modules/flux/main.tf line 80, in resource "kubectl_manifest" "sync":
  80: resource "kubectl_manifest" "sync" {
...

Please , could you  provide some fix or step-by-step procedure how to do upgrade more smoothly and without impacting other apps.
Thank you.

Please see https://github.com/fluxcd/terraform-provider-flux/blob/main/CHANGELOG.md#040

Hi @stefanprodan, thanks for quick reply.

authors: ozcb stefanprodan

repo: fluxcd/terraform-provider-flux


text:
Bump Golang to 1.20

Description of change
This bumps Golang to the latest 1.20 version.
Also, it unifies all Docker builder images to golang:1.20-bullseye and final images from alpine to debian:bullseye-slim (except for operator, as it is recommended to use distroless there). This should remove any glibc and musl compatibility issues.
Checklist

[x] Tested in playground or other setup
[ ] Screenshot (Grafana) from playground added to PR for 15+ minute run

This change is

source: gharchive/pull-request

repo: fluxninja/aperture


text:
🛑 Cartilla is down

In c36e302, Cartilla (https://extranet.osam.org.ar/Consulta/cartilla) was down:

HTTP code: 502
Response time: 1124 ms

Resolved: Cartilla is back up in 7540779.

repo: flvanney/OSAMuptime

license: MIT


text:
SchedulerSuite.TestDeployController: scheduler job count missmatch

----------------------------------------------------------------------
FAIL: test_scheduler.go:452: SchedulerSuite.TestDeployController

++ 18:06:42.051 got deployment event: deployer starting
++ 18:06:42.841 got deployment event: deployer up
++ 18:06:42.851 got deployment event: deployer stopping
++ 18:06:42.891 got deployment event: deployer down
++ 18:06:42.911 got deployment event: deployer starting
++ 18:06:43.551 got deployment event: deployer up
++ 18:06:43.571 got deployment event: deployer stopping
++ 18:06:53.731 got deployment event: web starting
++ 18:06:54.571 got deployment event: web up
++ 18:06:54.571 got deployment event: web stopping
++ 18:06:54.653 reconnecting deployment event stream
++ 18:06:54.688 got deployment event: deployer starting
++ 18:06:54.688 got deployment event: deployer up
++ 18:06:54.688 got deployment event: deployer stopping
++ 18:06:54.688 got deployment event: deployer down
++ 18:06:54.688 got deployment event: deployer starting
++ 18:06:54.688 got deployment event: deployer up
++ 18:06:54.688 got deployment event: deployer stopping
++ 18:06:54.688 got deployment event: web starting
++ 18:06:54.688 got deployment event: web up
++ 18:06:54.688 got deployment event: web stopping
++ 18:06:54.708 got deployment event: web down
++ 18:06:54.718 got deployment event: web starting
++ 18:06:55.578 got deployment event: web up
++ 18:06:55.588 got deployment event: web stopping
++ 18:06:55.653 reconnecting deployment event stream
++ 18:06:55.716 got deployment event: deployer starting
++ 18:06:55.716 got deployment event: deployer up
++ 18:06:55.717 got deployment event: deployer stopping
++ 18:06:55.717 got deployment event: deployer down
++ 18:06:55.717 got deployment event: deployer starting
++ 18:06:55.717 got deployment event: deployer up
++ 18:06:55.717 got deployment event: deployer stopping
++ 18:06:55.717 got deployment event: web starting
++ 18:06:55.717 got deployment event: web up
++ 18:06:55.717 got deployment event: web stopping
++ 18:06:55.717 got deployment event: web down
++ 18:06:55.717 got deployment event: web starting
++ 18:06:55.717 got deployment event: web up
++ 18:06:55.717 got deployment event: web stopping
++ 18:06:56.176 got deployment event: web down
++ 18:06:56.186 got deployment event: scheduler starting
++ 18:06:56.196 got deployment event: scheduler starting
++ 18:06:56.196 got deployment event: scheduler starting
++ 18:06:56.197 got deployment event: scheduler starting
++ 18:06:57.577 got deployment event: scheduler up
++ 18:06:57.658 got deployment event: scheduler up
++ 18:06:58.266 got deployment event: scheduler up
++ 18:06:58.466 got deployment event: scheduler up
++ 18:06:58.476 got deployment event: scheduler stopping
++ 18:06:58.476 got deployment event: scheduler stopping
++ 18:06:58.486 got deployment event: scheduler stopping
++ 18:06:58.486 got deployment event: scheduler stopping
++ 18:06:58.696 got deployment event: scheduler down
++ 18:06:58.776 got deployment event: scheduler down
++ 18:06:58.866 got deployment event: scheduler down
++ 18:06:59.307 got deployment event: scheduler down
++ 18:06:59.307 got deployment event:
test_scheduler.go:537:
    t.Assert(actual, c.DeepEquals, expected)
... obtained map[string]map[string]int = map[string]map[string]int{"e147761137604b4cb34c7826614af7c5":map[string]int{"scheduler":4, "deployer":2, "web":2}}
... expected map[string]map[string]int = map[string]map[string]int{"e147761137604b4cb34c7826614af7c5":map[string]int{"web":2, "deployer":2, "scheduler":3}}

https://s3.amazonaws.com/flynn-ci-logs/20150226180025-2b79d3a6-build-a58fb7e32511670554f0f55eaad0e17b38477aca-2015-02-26-18-09-08.txt

(same ci job as #1097 and #1098)

Might be related to #1182

Closing, this test failure does not appear in the CI logs dating back to May 1st.

authors: jvatic jzila titanous

repo: flynn/flynn


text:
scheduler: Don't try to start jobs which have already started

This updates the scheduler to stop trying to add a job when it knows it has already started (regardless of whether AddJob continues to fail).
The host has also been updated to reject duplicate jobs, meaning the scheduler can continue to try starting a job with the same ID until it actually starts without leading to duplicate jobs.
I've also thrown in an update to the receiver to add type=slugbuilder to slugbuilder jobs as the scheduler now handles this correctly.
Closes #2545.

LGTM

P.S. although I haven't added explicit tests, I tested this manually by adding random sleeps to the host's HTTP API and verifying the scheduler exhibits the correct behaviour.

authors: lmars titanous


text:
pkg/httpclient: Don't use a timeout in ResumingStream

Fixes #2546.

LGTM


text:
没有设置默认的ObjectMapper

麻烦加下这块代码，用自己创建的objectMapper来序列化

@babyfish-ct   Whether need to initialize sqlClient DefaultSerializedTypeObjectMapper in extension
@tzxylao  This is a universal solution

Jimmer's author says no

authors: flynndi tzxylao

repo: flynndi/quarkus-jimmer-extension


text:
Fix #3105 Is Not a good idea: It prints too many logs while I have many insert-scripts

Which version and edition of Flyway are you using?
7.7.2
If this is not the latest version, can you reproduce the issue with the latest one as well? (Many bugs are fixed in newer releases and upgrading will often resolve the issue)
not fix or change in 7.7.3 (newest as for now)
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
maven plugin
Which database are you using? (Type & version)
postgresql V13 (v11 in another workspace)
Which operating system are you using?
mac and ubuntu
What did you do? (Please include the content causing the issue, any relevant configuration settings, the SQL statement(s) that failed (if any), and the command you ran)
I have many Insert-sql-scripts (since I use flyway5). And in this new version, the log code in SqlExecutor changed. It prints all the affect row count msg (it's debug level before and info now) like X rows affected.
When I start a new database and do the migrate (it's quite often when I do local dev),  there are tons of affected msg on my log screen.
What did you expect to see?
I expected that I can configure when I want to see these msg. I tried Override createSqlScriptExecutor method but have no idea how to inject the class I create.
What did you see instead?
tons of x rows affected msg

Fix #3105  this is the pull request I'm talking while the issue it fixed is #3105

+1 really annoying

See https://github.com/flyway/flyway/issues/3132 for a proposed solution we will try, as we need to balance not hiding information people find useful vs spam

@DoodleBobBuffPants what is the proposed solution?  I'm not seeing it on #3132 .

+1 really annoying

FWIW a poor workaround I found is to add a beforeMigration script that to SET NOCOUNT ON.

repo: flyway/flyway


text:
H2 vulnerability

Which version and edition of Flyway are you using?
Latest, via flyway/flyway Docker image.
If this is not the latest version, can you reproduce the issue with the latest one as well? (Many bugs are fixed in newer releases and upgrading will often resolve the issue)
N/A
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
Command line with Docker.
Which database are you using? (Type & version)
PostgreSQL 14.1 (latest)
Which operating system are you using?
Windows with WSL
What did you do? (Please include the content causing the issue, any relevant configuration settings, the SQL statement(s) that failed (if any), and the command you ran)
Trivy is run against our Docker images before they're deployed.
What did you expect to see?
The Flyway image usually runs without any issues raised by Trivy.
What did you see instead?
Flyway is flagged with an H2 vulnerability affecting versions below 2.0.206. Flyway is on version 2.0.202.
I'm not familiar with H2 so this may not be an issue directly affecting Flyway, incorrectly flagged by Trivy.

Thank you for bringing this to our attention. We will investigate further and get back to you as soon as possible.

authors: Barry-RG dblackstock


text:
javadoc for repeatable SQL Migrations

Hi just a little contribution to tell in javadoc that "R__" prefixed scripts are scanned

I am considering using flyway and then I see a simple PR like this sitting since July.

Thanks for the pull request. We ended up fixing this ourselves.

authors: Bludwarf axelfontaine chb0github


text:
🛑 Site nxtcATS is down

In 8f3a6b9, Site nxtcATS ($SECRET_SITE_4) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Site nxtcATS is back up in b4e4aae after 996 days, 3 hours, 34 minutes.

repo: fmmaia/fmAtAllUptime


text:
🛑 Contaboo is down

In d701cc1, Contaboo (https://contabo.com) was down:

HTTP code: 403
Response time: 408 ms

Resolved: Contaboo is back up in 4b84fbd after 31 minutes.

repo: fnzv/status


text:
fixed bugs for responsive view

Chat - Button in last line need margin to down
Solved: added margin-bottom 30px

Manage Users - Additional users below first user have missing title headers in left side
Solved: added the headers within each user's row when the screen size is detected as mobile

Manage roles - Never ending loop occurs and title headers below first role are missing
Solved: No loop detected now, it seems that backend works slowly, added headers in mobile for all items

Domains page - missing title headers below first one
Solved:  added headers in mobile view for all items

Model Viewer is too high in height
Solved: added css

Photo/Video - close buttons were hidden, added styles for showing in mobile view

Hi,
3D Model Viewer not looking good in my Full HD display.

And not with small display resolution.

Also close modal button is missing.

authors: Makuzaza foghorn-hash


text:
Documentation improvements

Improvement proposal for Prerequisites in the readme.md
Remove death link

@Bengelsoft thanks!

authors: Bengelsoft foldingbeauty

repo: foldingbeauty/kelda


text:
UIGS-25 Split GOBI Integration permission to view and edit perms

Purpose

https://folio-org.atlassian.net/browse/UIGS-25
Screenshot
https://github.com/user-attachments/assets/1fd4a5cc-cace-47e7-803a-90520a283eb5
Pre-Merge Checklist
Before merging this PR, please go through the following list and take appropriate actions.

[x] I've added appropriate record to the CHANGELOG.md
Does this PR meet or exceed the expected quality standards?

[x] Code coverage on new code is 80% or greater
[x] Duplications on new code is 3% or less
[x] There are no major code smells or security issues

Does this introduce breaking changes?

[ ] If any API-related changes - okapi interfaces and permissions are reviewed/changed correspondingly
[x] There are no breaking changes in this PR.

If there are breaking changes, please STOP and consider the following:

What other modules will these changes impact?
Do JIRAs exist to update the impacted modules?

[ ] If not, please create them
[ ] Do they contain the appropriate level of detail?  Which endpoints/schemas changed, etc.
[ ] Do they have all they appropriate links to blocked/related issues?

Are the JIRAs under active development?

[ ] If not, contact the project's PO and make sure they're aware of the urgency.

Do PRs exist for these changes?

[ ] If so, have they been approved?

Ideally all of the PRs involved in breaking changes would be merged in the same day to avoid breaking the folio-testing environment.  Communication is paramount if that is to be achieved, especially as the number of intermodule and inter-team dependencies increase.
While it's helpful for reviewers to help identify potential problems, ensuring that it's safe to merge is ultimately the responsibility of the PR assignee.

@folio-org/fe-tl-reviewers @alisher-epam please take a look at the PR

repo: folio-org/ui-gobi-settings


text:
Adding mixed styles or a citation to a bulleted list line

I'm having trouble rendering different styles to the same bulleted-list bullet.
Ex. Let's say I want to render a list item with two words in it with the second being a link, I might do:
doc.list(['See'], { continued: true });
doc.fill('blue');
doc.list(['Github'], { continued: true, link: 'github.com' });

My expectation is that it renders:

See Github

But it doesn't work. The two words will overlap and share the same bullet point.
Any advice on how to get this working?

@snlamm were you ever able to find any work-arounds to mixed styles within a single list item? I'm also seeing the issue where the text overlaps.

authors: ejmudrak snlamm

repo: foliojs/pdfkit


text:
how to overwrite the name of a key group.

Hey first of all, thanks for this amazing plugin. This is just a pure esthetic nitpick and not an issue; I was wondering if it was possible to overwrite the name of the <space> keyword group. to something like SPC for example.
Why ?
with <space> the whole whichkey window doesn't look even, I think it could look better if it was possible to overwrite it to SPC.
Look at doom-emacs for example:

To represent the space key they just use SPC and the whole think looks more even.
And this is which-key:

The space takes a lot of space compared to the other keys.

I just added a new config option key_labels. Refer to the docs on how to use this. Thanks

Awesome, Thanks!

authors: folke rafamadriz


text:
Unable to check Status value in Automation

The problem
I would like to check the Status in an automation, but I only see the options: Unavailable & Unknown. I would expected to see: disconnected, awaiting_start, charging, ready_to_charge, completed, error.
I have solved this using an template but for readability it would be nicer to have these status values to check on.
Version of Easee integration having the issue?
0.9.55
Version of Home Assistant Core having the issue?
Home Assistant 2023.10.3
Anything in the logs that might be useful for us?
No response
Additional information

You can type "disconnected" etc in that field, you do not have to select something from the drop-down.
Not sure if it is possible to populate the drop-down with other values, it would look nicer of course...

This is not a bug, it is a missing feature. The concept in Home Assistant that handles these menus is called Device Automations. We put it on the ToDo-list.

Hi am sorry but a cant see this working now. Think it worked 6 months ago when a set up some notification automations completed, disconnected and charging. Trying to add a notification for error but the list is still as above. Running 0.9.55
Regards Mats

@Mats1717

Hi am sorry but a cant see this working now. Think it worked 6 months ago when a set up some notification automations completed, disconnected and charging. Trying to add a notification for error but the list is still as above. Running 0.9.55 Regards Mats

You can type the state in the select box.
There is a new feature that is not released yes (#364). You will then be able to create a trigger on the device level with full GUI support. Note that triggers on the status entity will still have to be entered as text.

authors: Mats1717 astrandb olalid ridderr


text:
Jetbrains Mono - 400, 500, 700 specific stylesheets give an error

Describe the bug
I'm not able to load the 400, 500, and 700 weights specifically via their respective stylesheets in JavaScript. I've used this same technique to load specific font weights from Inter (open source) and Sora (google font) via fontsource.
To Reproduce
Steps to reproduce the behavior:

install fontsource-jetbrains-mono (I'm using yarn if that matters)

Add stylesheets to JavaScript:

import 'fontsource-jetbrains-mono/400.css'
import 'fontsource-jetbrains-mono/500.css'
import 'fontsource-jetbrains-mono/700.css'

Console error:
Module not found: Error: Can't resolve 'fontsource-jetbrains-mono/400.css'
Module not found: Error: Can't resolve 'fontsource-jetbrains-mono/500.css'
Module not found: Error: Can't resolve 'fontsource-jetbrains-mono/700.css'

Expected behavior
I expected those weights to load based on the Fontsource page here that says they are available.
If I do a generic import (import 'fontsource-jetbrains-mono') there is no error.

Hey @austriker27, thanks for checking in.
#92 should address why this issue exists and that it is on the agenda to be fixed. If you refer to the package readme on NPM or GitHub, it has a filler subset called 'all'.
The current method to import this would be:
import 'fontsource-jetbrains-mono/all-400.css'
import 'fontsource-jetbrains-mono/all-500-normal.css'
import 'fontsource-jetbrains-mono/all-700-italic.css'

I'll be closing this for now since #92 will address how to improve the issue you will be seeing.

repo: fontsource/fontsource


text:
new vendor-specific profile: Type Network

This is a followup pull-request adding my maintainer edits to the code contributed at PR #4260
A portion of that code, related to improvements to the HTML reporter, was already merged as part of PR #4263
This PR is meant to cover all remaining code to actually add the new profile.

@guidoferreyra, I'm happy with the current state of this PR.
There's only one thing missing: code-tests. I will add a couple of them as examples and then merge the PR. Ideally you should consider adding code-tests to all checks in the Type Network profile, to ensure the quality of the checks themselves.

@felipesanches I’ve been checking the commits you made, thanks a lot and sorry for the incoveniences. We developed this only for internal use so there is sloppy in many situations. I‘m embracing all the code quality routines and looking forward to streamline everyhing. Thanks for all the work!

authors: felipesanches guidoferreyra

repo: fonttools/fontbakery


text:
add unit tests for ttCollection module

#1207

Suggestions for *.ttc currently in repository test data directories to use for these tests?  There is this in the ttx test data directory: https://github.com/fonttools/fonttools/blob/master/Tests/ttx/data/TestTTC.ttc

Volunteers?

There's a couple tests there now at least.

authors: anthrotype behdad chrissimpkins

repo: fonttools/fonttools

license: mit

license_source: bigquery


text:
[GitHub] Add release gerber files workflow

This provides GitHub actions workflows that creates GitHub releases with gerber files:

Release workflow is intended to be triggeref manually, and can be used to release older v2.1 version
Release on tag will automatically trigger the first one when a vx.y tag is pushed

Releases are created as draft so you can edit the description before publishing it.
You can see Release examples there: v2.1,  v2.2.
You need to add a PERSONAL_TOKEN secret for this to work as explained there.
The gerber files are produced in a docker container with kicad-exports and looks fine to me, but I've never ordered PCBs from them, some settings changes could be required.

Closing as I will open a new PR later with improvements.

repo: foostan/crkbd


text:
Build transactions_by_address function

Description

Checklist

[ ] Targeted PR against correct branch.
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Wrote unit tests.
[ ] Re-reviewed Files changed in the Github PR explorer.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@cb7fd10). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #220   +/-   ##
=========================================
  Coverage          ?   72.37%
=========================================
  Files             ?       47
  Lines             ?     1832
  Branches          ?        0
=========================================
  Hits              ?     1326
  Misses            ?      437
  Partials          ?       69

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 cb7fd10...ad6f403. Read the comment docs.

authors: codecov-commenter dadamu

repo: forbole/soljuno


text:
latest SFDX command warning issue SFDX_AUTOUPDATE_DISABLE. Please use SF_AUTOUPDATE_DISABLE instead.

(node:2329) Warning: Deprecated environment variable: SFDX_AUTOUPDATE_DISABLE. Please use SF_AUTOUPDATE_DISABLE instead.
(Use node --trace-warnings ... to show where the warning was created)
(node:2329) Warning: Deprecated environment variable: SFDX_DISABLE_AUTOUPDATE. Please use SF_DISABLE_AUTOUPDATE instead.
im getting the above warning while running the latest SFDX Commands in my pipeline which is running under the agent "ubuntu" should i be worried about this waring or i need to set any environment variables while running the command in the pipeline? please help me to resolve this issue.

Do you have that env (SFDX_AUTOUPDATE_DISABLE) set in your CI environment?  If so, you can update it like the warning says to avoid seeing the warning.
If you don't set that env, I'd be really interested in where it's coming from (and what version of the CLI your CI is using) because we removed all our uses of it.  https://github.com/search?q=org%3Asalesforcecli+SFDX_AUTOUPDATE_DISABLE++NOT+is%3Aarchived&type=code

Hi @mshanemc nope i didn't set any environment variables im just installing the latest CLI using this command "npm install --global sfdx-cli@latest-rc " after runnning this installation command in my CI CD pipeline im running the jwt login and project deploy start command so when im running those command im seeing this warning in my CI CD pipeline even though i didn't set any environmental variables.

I'm not able to replicate this with what's in RC right now sfdx-cli/7.199.7 darwin-x64 node-v18.13.0.
We did recently add the warnings about old envs, so I'm 100% sure this is coming to that change, but I can't figure out how you got to it since no CLI code refers to that variable anymore.
I do see various other people's code on github that sets it.  Maybe your CI or a plugin uses the env?  https://github.com/search?q=SFDX_AUTOUPDATE_DISABLE&type=code

In my CI CD pipeline i have two set of stages one for QA validation and another one for UAT Validation
   In QA we did added a plugin for to scan the lwc apex and aure code the plugin is Salesforce code analyzer this is the installation command which im using -->  "sfdx plugins:install @salesforce/sfdx-scanner" and we are running the scanner command to scan the code --> "sfdx scanner:run --target "**/classes/**" " and after this step we are running the Jwt login and deployment command so in that stage only where we running the sfdx scanner plugin there we getting this warning which i mentioned the earlier command

      In UAT validation where we didn't run the scanner plugin to scan the code there is no warning showing for the sfdx commands.

so the issue is with where im running sfdx scanner plugin command
sorry for not telling you the issue properly at start.

im using the latest cli only in CI CD pipeline but yeah lets see it''ll go away in future or not and thanks for your help in this issue and has you mentioned ill ignore this warning for now

(node:7284) Warning: Deprecated environment variable: SFDX_JSON_TO_STDOUT. Please use SF_JSON_TO_STDOUT instead.
(Use node --trace-warnings ... to show where the warning was created)
TypeError: this.config.getPluginsList is not a function

authors: NagarjunaParala adityasfdev mshanemc

repo: forcedotcom/cli


text:
SF Project Retrieve Start --package-name also downloads "unpackaged" folder

Summary
Running the command sf project retrieve start --package-name 'name-of-changeset' will also download the folder 'unpackaged' which contains all the metadata in the environment.
Steps To Reproduce:
Using the following version of SF: @salesforce/cli/1.79.0 darwin-arm64 node-v18.15.0

create a change set with 1 or more components called testchangeset1
open a terminal and navigate to a folder with a Salesforce project
run the following command: sf project retrieve start --package-name testchangeset1
confirm that the change set as well as the unpackaged folder are downloaded

Expected result

testchangeset1 should be downloaded, no other folders

Actual result

There are two folders: testchangeset1 and unpackaged

System Information

Which shell/terminal are you using? (e.g. bash, zsh, powershell 5, powershell 7, cmd.exe, etc.)

If you are using sfdx

Run sfdx version --verbose --json

If you are using sf

Run sf version --verbose --json

{
"cliVersion": "@salesforce/cli/1.79.0",
"architecture": "darwin-arm64",
"nodeVersion": "node-v18.15.0",
"osVersion": "Darwin 22.1.0",
"shell": "zsh",
"rootPath": "/Users/bambrick/.local/share/sfdx/client/7.201.6-4edd82d/sf",
"pluginVersions": [
"@oclif/plugin-autocomplete 2.2.0 (core)",
"@oclif/plugin-commands 2.2.15 (core)",
"@oclif/plugin-help 5.2.9 (core)",
"@oclif/plugin-not-found 2.3.23 (core)",
"@oclif/plugin-plugins 3.0.1 (core)",
"@oclif/plugin-search 0.0.17 (core)",
"@oclif/plugin-update 3.1.14 (core)",
"@oclif/plugin-version 1.3.4 (core)",
"@oclif/plugin-warn-if-update-available 2.0.36 (core)",
"@oclif/plugin-which 2.2.20 (core)",
"@salesforce/cli 1.79.0 (core)",
"apex 2.2.17 (core)",
"auth 2.7.15 (core)",
"data 2.3.16 (core)",
"deploy-retrieve 1.8.20 (core)",
"info 2.6.10 (core)",
"limits 2.3.14 (core)",
"login 1.2.8 (core)",
"org 2.8.2 (core)",
"schema 2.3.10 (core)",
"settings 1.4.6 (core)",
"sobject 0.1.18 (core)",
"source 2.10.7 (core)",
"telemetry 2.2.0 (core)",
"templates 55.4.13 (core)",
"trust 2.4.16 (core)",
"user 2.3.10 (core)"
]
}
Additional information
Feel free to attach a screenshot.

Hey @jxbambrick, is this a recent change in behavior? If so, what version of the CLI where you seeing the desired behavior?

I had an error after updating SFDX to the latest version. I don't know what my previous version was. In an attempt to resolve the error and update my deployment scripts, I switched from using SFDX commands to SF commands. I only need to download the specified change sets but it's including the unpackaged folder.
SFDX:

sfdx force:source:retrieve -x package_xml -u user_alias_placeholder --json

SF:

sf project retrieve start--target-org --target-metadata-dir dir_placeholder --manifest manifest_placeholder --json

Ok, I am still not able to reproduce your issue due to something unrelated, but I have been able to show that this used to work with sfdx force:mdapi:retrieve -p testchangeset1 -r export-dir -o hub
The structure created was (after unzipping):
.
|____testchangeset1
| |____package.xml
| |____objects
| | |____Broker__c.object
|____unpackaged.zip

Note that the unpackaged.zip only contained the the contents of the unpackaged directory

authors: iowillhoit jxbambrick


text:
project is not a sf command

Summary
Running sf project deploy start results in Warning: project is not a sf command.
Steps To Reproduce:
run a sf command.  I get a similar result for:
 »   Warning: deploy start is not a sf command.```

### Expected result

I expect my project to deploy to the org specified.

### Actual result

results in `Warning: project is not a sf command.`

### System Information

sfdx version
sfdx-cli/7.203.6 win32-x64 node-v18.15.0
sf --version
@salesforce/cli/0.0.38 win32-x64 node-v14.17.5

- Which shell/terminal are you using? (e.g. bash, zsh, powershell 5, powershell 7, cmd.exe, etc.)
Same result in cmd.exe and git bash
cmd.exe --version => Microsoft Windows [Version 10.0.19045.2965]
bash --version => GNU bash, version 5.1.16(1)-release

@thedavidhanks you have an old version of sf:
@salesforce/cli/0.0.38 win32-x64 node-v14.17.5
latest sf is 1.80.6.
See update instructions:
https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_setup_update_cli.htm


text:
Use subcommand verify on the ci

Previously used cargo msrv --verify. Since cargo-msrv v0.14.0, this flag is deprecated in favour of the new cargo msrv verify subcommand.

bors r+

repo: foresterre/cargo-msrv


text:
Error at passing Object to HandleChange

🐛 Bug report
I'm trying to save an Object on form.values to work with it later on a Query.
The problem is, even I have used it on other project, this time it gives this error:
handleChange error
Anyone has some clue about this?
The specific line I'm inputting this is this one:
onChange={form.handleChange('MultipleSelect')({})}
where "{}" is the object I'm passing to it...
I'm not sure, but I think it is not finding the '_eventOrTextValue' function...
I have tried passing integers, objects, arrays, but the only kind of value it accepts is string... Oddly I used this same mirrored function on other project the exactly same way...
Thanks.

Software
Version(s)

Formik
^2.0.3

React
16.9.0

TypeScript
--

Browser
--

npm/Yarn
Yarn

Operating System
Ubuntu 19.10

Having the same issue. This used to work fine on Formik@1.5.2, I am only having this issue on Formik V2.

It seems that this function has changed to only handle events. For values you should you setFieldValue now, it's pretty the same actually

We should accept object values. It's esp. an issue for third parties like React Select that expect an object value (though I question their API choice in this regard)

Was this fixed? Why was it closed? I just upgraded from 1x to 2, and handleChange("fieldName")(true) gives me the "cannot read property 'type' of undefined" error. Is there a solution or workaround?

@JulianKingman OP closed their own issue. Feel free to open a new issue if one doesn't exist already (check the search!).

authors: JulianKingman JulioCRFilho Unforgiven-wanda johnrom oTodi

repo: formium/formik


text:
Typescript error vscode FormKitComponent

Reproduction
https://formkit.link/e6e026b413c717931d3dc9524a174080
Describe the bug
Hi,
Look at the screenshot I don't know why there's this typescript error on vscode ?

Environment
• OS: MacOS Ventura
• Browser chrome

Gonna need a bit more details on this one. Can you provide your implementation of the component?

It's not the same error, but I am also getting a TS error relating to the Multi-step plugin for VS Code. My #stepNext override is returning a TS error in the most recent update.

This is the exact same example from https://formkit.com/plugins/multi-step

There is an updated version that fixes errors with typings for the multi-step that came with 0.18.

Gonna need a bit more details on this one. Can you provide your implementation of the component?

@justin-schroeder yes paste this : https://formkit.link/e6e026b413c717931d3dc9524a174080 into vscode :)

@justin-schroeder yes paste this : https://formkit.link/e6e026b413c717931d3dc9524a174080 into vscode :)

I meant things like — your version of formkit, your version of formkit pro, your version of vue etc. This error should not happen if you have 0.114.x and beta 0.18.x installed.

authors: GustavoFenilli gunter423 justin-schroeder njoswald

repo: formkit/formkit


text:
Rupees and Subitems

Began work on subitems (Can be used for Rupees, Hearts, Keys, etc)

Credit: lisacvuk and Rirdeg for their HP container/drop code

Got distracted while implementing networking for this, will check back in tomorrow. Also going to ping #14 and #17 here real quick before I close them.

Networking! Subitems are dropped by the current_map itself, so subitems will spawn even if the enemy died before the subitem packet arrived on clients. Names are also synced as a random integer, maybe this could've been done better. That ensures that the names are always the same for everyone so there's no "node not found" errors.
One thing that is not implemented is spawning subitems for joining players who weren't there when the subitem dropped. We can keep an array of active subitems and spawn them for people coming in, but that's low priority.

authors: fornclake gboydhub

repo: fornclake/TetraForce


text:
Set credentials

Hi,
How do we set authentication params like user and password, while using tcli_connect or connect methods?

There is a PR https://github.com/forward3d/rbhive/pull/23 that offers Kerberos connectivity, but this is yet to be merged into master.

@Selenium-hari here is an example:

RBHive.tcli_connect('address', 10_000, { transport: :sasl,:sasl_params  => {:username => "username",:password  => "password"},logger: Logger.new(STDOUT), hive_version: 10 }) do |connection|
  connection.fetch 'SELECT * FROM users LIMIT 5'
end

authors: 0bserver07 Selenium-hari lloydpick


text:
Added Amazon Sagemaker API and Gradiot API

Greetings !!
This closes #117  and  #118
I have succesfully added the Amazon's Sagemaker API and it sdescription .
Hope this find useful to everybody.
Thank You :)

They are not Gen AI APIs.


text:
EventDetailsFragment display unaccepted sessions/speakers

Describe the bug
Sessions/Speakers should only be displayed when they are accepted by the Organizer
The same for public/private events/speakerscall
Would you like to work on the issue?
Yes

Parent issue?

I removed child-issue. I mistakenly added that tag

repo: fossasia/open-event-android


text:
[WIP] feat: Add event detail activity

Fixes #453

@mejariamol Please review

@iamareebjamal
Why separate activity for it? I think it should be hosted in MainActivity itself.
And we already showing event image in the nav head.

How can we show this in MainActivity?

How can we show this in MainActivity?

Only the content which is shown in 2nd screen shot. Event Image is not required to show in the about page separately as we are showing it already in the nav header.

But how will we show this info in MainActivity? MainActivity is just a host for fragments.
About the image, the screen also shows logo. I obviously showed the image because it was an activity and collapsing toolbar could be used. Also, option for editing the event can be added in future in this activity.
Detail views are generally activities

But how will we show this info in MainActivity? MainActivity is just a host for fragments.

I am saying host AboutFragment in MainActivity.

I think detail views should be shown in separate activities. Because navigationally, they are not flat with the hierarchy. Like track -> track detail should not be in same frame (activity) and some isolated functionalities just related to event info can be handled through this. This is a standard in material guidelines to show a detail view with a collapsing toolbar. Using collapsing toolbar in Fragments is not easy and the stack management will be disrupted due to it. Same with the User Detail
It should be handled in another activity as well. This will also make it easy to create master detail in future because the natural process for it is - mobile -> detail activity | tablet -> detail fragment

@mejariamol Please review

@mejariamol Please review now

authors: iamareebjamal mejariamol

repo: fossasia/open-event-orga-app


text:
Reduce Repository size

Actual Behaviour
When cloning the Repository, it's more than 1GB.
Expected Behaviour
Update Readme to make developer to only clone the development branch and also delete the history of gh-pages branch.
Would you like to work on the issue?
Yes. @iamareebjamal Would require your help in this.

@prateekj117 I want to work on this issue.

I can provide you the solution to this problem.

OK

I was having problem while cloning the Repository after forking it. The size of repository was too large to download so it always got interrupted while cloning.
So to solve this I used the depth as 1 and it worked. The size of repository was only 11.50 MB after cloning.
You can follow these two steps to solve this issue.

Provide an argument of -- depth 1 to the git clone command to copy only the latest revision of a Repository.
git clone -–depth [depth] [remote-url]

You can also use git shallow clone to access a single branch.
git clone [remote-url] --branch [name] --single-branch [folder]

That's not a solution. That's a workaround we are already aware of

I want to work on this issue(#2142)

repo: fossasia/open-event-wsgen


text:
fixes #2 and #3 Improved documentation images and updated package.json

Removed windows from images, and the height, width attributes from README.

@niranjan94 Ok.

I think we should put mobile screenshots side by side, in a table. Like this https://github.com/fossasia/open-event-android

Please let me know if any more changes are required. Thank you.

Thank you. In future please add the link to the issue in the description. Please read about our best practices in this blog post http://blog.fossasia.org/open-source-developer-guide-and-best-practices-at-fossasia/

authors: Manveer695 heysadboy mariobehling


text:
Pipeline

What this PR does / why we need it
This PR introduces the Pipeline object, which is a purely config-based SDG pipeline that consists of a list of blocks chained together.
Special notes for your reviewer
There are three main files to look at:

pipeline.py (main pipeline object, inherits from Databuilder to maintain input/output and tasks functionality)
registry.py (I added a dynamic import system to help mitigate dependency I was starting to see with users, however, this could be bad practice...)
blockchain.py (first instance of compositional blocks)

If applicable**

[X] this PR contains documentation
[X] this PR contains unit tests
[X] this PR has been tested for backwards compatibility

@mvcrouse looks like you need to rebase with signoff:
# NOTE: "origin" is the central repo not the fork here, so swap as needed
git fetch origin main
git rebase origin/main --signoff
git push -f

@mvcrouse looks like you need to rebase with signoff:
# NOTE: "origin" is the central repo not the fork here, so swap as needed
git fetch origin main
git rebase origin/main --signoff
git push -f

Ahh yes,

authors: gabe-l-hart mvcrouse

repo: foundation-model-stack/fms-dgt


text:
Cannot reproduce blog post results

I'm trying to reproduce the blog post results on 70b, but am not able to.
Running the following on a single node with 8 A100-80G
torchrun --nproc_per_node=8 ./benchmark_inference.py --architecture=llama --variant=70b --tokenizer=./tokenizer.model --batch_size=2 --seq_len=500
Getting the following results
Uncompiled results:
- with use_cache=True
        175.89 ms per token
- with use_cache=False
        191.00 ms per token
End-to-end sequence generation
- with use_cache=True
        181.31 ms per token
- with use_cache=False
        195.16 ms per token
Compiled results:
- with use_cache=True
        92.01 ms per token
- with use_cache=False
        140.54 ms per token
(Compiled) End-to-end sequence generation
- with use_cache=True
        98.07 ms per token
- with use_cache=False
        143.84 ms per token

The 98.07 ms/token is much more than than the 29 ms/token from https://pytorch.org/blog/pytorch-compile-to-speed-up-inference/.
Let me know if I am running something incorrectly.

Looks like the benchmark does not have reduce-overhead on by default.
With mode="reduce-overhead" I am getting
Uncompiled results:
- with use_cache=True
        178.23 ms per token
- with use_cache=False
        190.61 ms per token
End-to-end sequence generation
- with use_cache=True
        183.15 ms per token
- with use_cache=False
        195.30 ms per token
Compiled results:
- with use_cache=True
        30.69 ms per token
- with use_cache=False
        142.48 ms per token

But full sequence generation with the compiled model is leading to this error
Traceback (most recent call last):
  File "/home/ray/foundation-model-stack/scripts/./benchmark_inference.py", line 231, in <module>
    bench_end_to_end(True)
  File "/home/ray/foundation-model-stack/scripts/./benchmark_inference.py", line 191, in bench_end_to_end
    e2e_expected = end_to_end(model, use_cache)
  File "/home/ray/foundation-model-stack/scripts/./benchmark_inference.py", line 163, in end_to_end
    result = generation.generate(
  File "/home/ray/anaconda3/lib/python3.10/site-packages/fms/utils/generation.py", line 58, in generate
    output = model.forward(input_ids, **kwargs)
  File "/home/ray/anaconda3/lib/python3.10/site-packages/torch/_dynamo/eval_frame.py", line 328, in _fn
    return fn(*args, **kwargs)
  File "/home/ray/anaconda3/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
    return self._call_impl(*args, **kwargs)
  File "/home/ray/anaconda3/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1527, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/ray/anaconda3/lib/python3.10/site-packages/fms/models/llama.py", line 310, in forward
    def forward(
  File "/home/ray/anaconda3/lib/python3.10/site-packages/torch/_dynamo/eval_frame.py", line 328, in _fn
    return fn(*args, **kwargs)
  File "/home/ray/anaconda3/lib/python3.10/site-packages/torch/_dynamo/external_utils.py", line 17, in inner
    return fn(*args, **kwargs)
  File "/home/ray/anaconda3/lib/python3.10/site-packages/torch/_functorch/aot_autograd.py", line 3905, in forward
    return compiled_fn(full_args)
  File "/home/ray/anaconda3/lib/python3.10/site-packages/torch/_functorch/aot_autograd.py", line 1482, in g
    return f(*args)
  File "/home/ray/anaconda3/lib/python3.10/site-packages/torch/_functorch/aot_autograd.py", line 2533, in runtime_wrapper
    all_outs = call_func_with_args(
  File "/home/ray/anaconda3/lib/python3.10/site-packages/torch/_functorch/aot_autograd.py", line 1506, in call_func_with_args
    out = normalize_as_list(f(args))
  File "/home/ray/anaconda3/lib/python3.10/site-packages/torch/_functorch/aot_autograd.py", line 1594, in rng_functionalization_wrapper
    return compiled_fw(args)
  File "/home/ray/anaconda3/lib/python3.10/site-packages/torch/_inductor/codecache.py", line 374, in __call__
    return self.get_current_callable()(inputs)
  File "/home/ray/anaconda3/lib/python3.10/site-packages/torch/_inductor/compile_fx.py", line 680, in run
    return compiled_fn(new_inputs)
  File "/home/ray/anaconda3/lib/python3.10/site-packages/torch/_inductor/cudagraph_trees.py", line 378, in deferred_cudagraphify
    fn, out = cudagraphify(model, inputs, new_static_input_idxs, *args, **kwargs)
  File "/home/ray/anaconda3/lib/python3.10/site-packages/torch/_inductor/cudagraph_trees.py", line 405, in cudagraphify
    return manager.add_function(
  File "/home/ray/anaconda3/lib/python3.10/site-packages/torch/_inductor/cudagraph_trees.py", line 1921, in add_function
    return fn, fn(inputs)
  File "/home/ray/anaconda3/lib/python3.10/site-packages/torch/_inductor/cudagraph_trees.py", line 1741, in run
    out = self._run(new_inputs, function_id)
  File "/home/ray/anaconda3/lib/python3.10/site-packages/torch/_inductor/cudagraph_trees.py", line 1780, in _run
    self.apply_checkpoint_execution_state_in_allocator()
  File "/home/ray/anaconda3/lib/python3.10/site-packages/torch/_inductor/cudagraph_trees.py", line 2113, in apply_checkpoint_execution_state_in_allocator
    torch._C._cuda_setCheckpointPoolState(
RuntimeError: Expected curr_block->ptr == block_state.ptr to be true, but got false.  (Could this error message be improved?  If so, please report an enhancement request to PyTorch.)

When running with tensor-parallel, optimal performance does require use of mode='reduce-overhead', and there are certain combinations of tests/options where we sometimes see instability. IIRC, certain PyTorch nightlies may behave differently too.
There's a PR here, not-yet-landed, that makes it a bit easier to evaluate different combinations of options/tests: https://github.com/foundation-model-stack/foundation-model-stack/pull/72
cc @ani300 who has more detail, and @eellison who was investigating improvements to reduce-overhead.

Hi! I'll be dealing with the last few comments in #72 and trying to merge that in today. As @nairbv points out, in order to get the e2e test running, we had to run it by itself, as otherwise we would run into exactly the bug you pointed out.
On top of that, there is a memory race condition when running with "reduce-overhead" and the allReduce NCCL collective, which should be solved by https://github.com/pytorch/pytorch/pull/112439, but the results can be reproduced by turning the correct results assertion off until that lands.

With the up-to-date #72 (soon in main) and running torchrun --nnodes=1 --nproc-per-node=8 --standalone scripts/benchm ark_inference.py --architecture=llama --variant=70b --tokenizer="/lustre/llama_weights/tokenizer.model" --distributed --compile_mode="reduce-overhead" --skip_eager_runs --skip_single_token_runs --skip_nok vcache_runs --skip_correctness_check, I get the following:
[2023-11-08 19:01:28,510] torch.distributed.run: [WARNING] master_addr is only used for static rdzv_backend and when rdzv_endpoint is not specified.
[2023-11-08 19:01:28,510] torch.distributed.run: [WARNING]
[2023-11-08 19:01:28,510] torch.distributed.run: [WARNING] *****************************************
[2023-11-08 19:01:28,510] torch.distributed.run: [WARNING] Setting OMP_NUM_THREADS environment variable for each process to be 1 in default, to avoid your system being overloaded, please further tune the variable for optimal performance in your application as needed.
[2023-11-08 19:01:28,510] torch.distributed.run: [WARNING] *****************************************
loading modelloading model

loading modelloading modelusing tensor parallel

using tensor parallel
loading model
using tensor parallel
using tensor parallelusing tensor parallel

loading model
using tensor parallel
loading model
loading model
using tensor parallel
using tensor parallel
loading complete on rank 6
loading complete on rank 3
loading complete on rank 1
loading complete on rank 0
loading complete on rank 5
loading complete on rank 7
loading complete on rank 4
loading complete on rank 2
Results for batch size 2, sequence length 512, new tokens generated 256
Compiling model...
Warming up the compiled model e2e in rank 1
Warming up the compiled model e2e in rank 5

Compiled results:
==========

Warming up the compiled model e2e in rank 0
Warming up the compiled model e2e in rank 7
Warming up the compiled model e2e in rank 6
Warming up the compiled model e2e in rank 4
Warming up the compiled model e2e in rank 3
Warming up the compiled model e2e in rank 2
(... warnings ...)
Model has warmed up e2e in rank 4
Model has warmed up e2e in rank 3
Model has warmed up e2e in rank 5
Model has warmed up e2e in rank 1
Model has warmed up e2e in rank 7
Model has warmed up e2e in rank 6
Model has warmed up e2e in rank 2
Model has warmed up e2e in rank 0
(Compiled) End-to-end sequence generation
- with use_cache=True
        31.04 ms per token

Should we close this issue now?
If we want to track the stability issues with mode=reduce-overhead we could file a new issue, or change the title on this one. Is there a PyTorch github issue we can reference for that too?

Closing this issue. Remaining work for failing case tracked in pytorch: https://github.com/pytorch/pytorch/issues/113895

authors: amogkam ani300 nairbv


text:
Accordion: Deep Link: Scroll to open title, offset for sticky headers

What is missing?

When using a Foundation Accordion with data-deep-link, the page should scroll to the top of the data-accordion-item, not the top of the data-tab-content. Further, there should be a means of allowing this to include an offset in order to account for e.g. a sticky header.
What is wrong now?

Currently, when data-deep-link is enabled, the URL fragment points to the id of the data-tab-content. When a user navigates to a URL with that fragment, the browser scrolls to that data-tab-content and opens it. In doing so, however, the title is hidden above the view port. Further, if there's a sticky header, then the content itself will also be hidden under this area.
To help provide context, this is the markup for the Accordion:

    Item 1

      …

Possible Solution

There are currently two attributes—data-deep-link-smudge and data-deep-link-smudge-offset—which provide similar types of control. They scroll to the top of the data-accordion, however, not to the top of the data-tab-content. One could imagine a similar set of attributes for controlling the scroll position of deep links to the top of the data-accordion-item.

Note: It's not entirely clear to me what the utility of data-deep-link-smudge is, as it can result in the open tab not even being visible in cases where the height of the accordion panel is higher than the viewport. Personally, I'd have expected data-deep-link-smudge to operate as I've proposed here, but that doesn't appear to be the design intent.

Your Environment

Foundation version(s) used: 6.6.3
Browser(s) name and version(s): Google Chrome 86.0.4240.198
Device, Operating System and version: Windows 10 Pro 20H2

Checklist

[x] I have read and follow the CONTRIBUTING.md document.
[x] There are no other issues similar to this one*.
[x] The issue title and template are correctly filled.

There was a somewhat similar issue in 2013 related to clicking on the title/label. My request, however, relates to the opening a URL with a data-deep-link fragment.

I'm on 6.4.3 and having this issue as well.

authors: JeremyCaney angelicochris

repo: foundation/foundation-sites


text:
CORS Error on upload

I recently followed the guide and created this setup for my frontend react app as well as the express API on a separate project
Frontend

Backend

and i have a config.js with the secret key and access key to access my AWS. Once i put a .jpg image to drop zone i get this on server log

but i get this on fronted log
Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:3000' is therefore not allowed access. The response had HTTP status code 403
Is there a way to find out what the actual issue is?

fixed when CORS was configured from AWS


text:
does this do anything?

https://github.com/foundpatterns/torchbear/blob/2b7737008f925b793dff466dbdd508ece9baacf5/src/managers/web_server.lua#L23
I don't see returned_response in use anywhere else

This is an old commit, it's now
https://github.com/foundpatterns/torchbear/blob/eb1754460b8098d7dc4e448aac572bad8496a180/src/managers/web_server.lua#L22
and it's being set here
https://github.com/foundpatterns/lighttouch-libs/blob/eae1a284b7d94d0c8a0fbecd4d053b509fc6b086/package_loader.lua#L240
(You actually scared me because that code would break)

it should be outgoing_response

when is the outgoing response getting set?  in the handler, action loader, 1 arbitrary action, ... ?

I already sent you where it's being set
https://github.com/foundpatterns/lighttouch-libs/blob/eae1a284b7d94d0c8a0fbecd4d053b509fc6b086/package_loader.lua#L240
The final response is first one returned by any action

regarding last comment
https://github.com/foundpatterns/lighttouch-base/issues/24

The final response is first one returned by any action
https://github.com/foundpatterns/lighttouch-base/issues/62

repo: foundpatterns/torchbear


text:
Flush fork rpc cache more regulary

Component
Forge
Describe the feature you would like
currently, the cache is flushed only when the program ends.
instead, we should flush it more regularly for longer running fork jobs, this can be easily added in #1715
Additional context
No response

this was added and is now flushed on regular basis

repo: foundry-rs/foundry


text:
Do not run coverage if "--via-ir" is enabled

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
forge 0.2.0 (d3d8c0b 2022-12-24T12:38:26.644536Z)
What command(s) is the bug in?
forge coverage
Operating System
macOS (Apple Silicon)
Describe the bug
See discussion in https://github.com/foundry-rs/foundry/issues/3527, particularly this comment.
If the coverage command is not meant to run over IR-optimized code, I consider it a bug that the coverage implementation does not catch the activation of --via-ir, and does not throw a more specific error to the user.

happy to take over this! just need confirmation on how we should proceed with the issue, as I will have some time next week.
The steps I see are:

Explicitly state that --via-ir can't be used on forge coverage
Detect the --via-ir flag either passed in on the command or foundry.toml and throw a more specific error.

If the coverage command is not meant to run over IR-optimized code, I consider it a bug that the coverage implementation does not catch the activation of --via-ir, and does not throw a more specific error to the user.

I'm not sure I follow the bug here. Assuming a user wants to compile/deploy with via-ir, and given that forge coverage requires no optimizer/via-ir and effectively ignores the config file when invoked, there are two scenarios:

forge coverage is able to compile normally, so you get coverage results with no via-ir, then deploy with via-ir
forge coverage is not able to compile normally, so it exits with an error and you are unable to run coverage

What am I missing here / what is the bug?

If you don't like the "bug" terminology, I am happy to let go of it in this context.
My point is simply that it would be nice for Forge to give a clearer error when the user attempts to run the coverage command and they have --via-ir enabled.

Do you mean a more clear error when forge coverage fails to compile, or a general message telling users it's ignoring their compilation settings even when successful?
Note that this would also apply when the user doesn't use via-ir, but does use the regular optimizer (i.e. via-ir isn't unique here)

I mean failing early - not even trying to compile if Forge sees that --via-ir is enabled. Just stop the execution and show an error there.
It is odd that you say that the regular optimizer is not enabled, because I have managed to successfully obtain a coverage report even with the optimizer enabled.

It is odd that you say that the regular optimizer is not supported, because I have managed to successfully obtain a coverage report even with the optimizer enabled.

Hmm I think we might be misunderstanding each other a bit here. @mattsse can correct me if I'm wrong but my understanding of forge coverage is it behaves as follows: when you run forge coverage it ignores all solidity build settings you have configured and compiles with default solc settings, i.e. no optimizer and no via-ir.
In your case, it just meant your contracts are able to be compiled both with and without the optimizer.

I mean failing early - not even trying to compile if Forge sees that --via-ir is enabled. Just stop the execution and show an error there.

Say I want to deploy with via-ir because it results in cheaper functions for users. Let's also say my contract still compiles normally, even if via-ir is not used. In this case, why would I want forge coverage to fail early? Getting coverage information is still useful, even though it was compiled differently than the production version will be

when you run forge coverage it ignores all solidity build settings you have configured

Oh, I didn't know this! Oh my goodness. It all makes sense now. The reason I thought otherwise was because my code used to not compile without --via-ir.

In this case, why would I want forge coverage to fail early?

yeah, you wouldn't want that in this case. As per my explanation above, this was a misunderstanding on my end.
I will close this issue now.

Thanks a lot for elucidating this issue for me, @mds1!

No problem!

authors: Evalir PaulRBerg mds1


text:
Typesafe contract declare

We should consider native name providing solutions with declare, like providing the full path to the contract module, and possibly referring to a generated constant (like a NAME for example).
This task should result in a POC if possible
Blocks #1507
This is not going to be merged in 2.5.0 scarb (postponed) - this relies on the info that will be output in the artifacts.

Artifacts with module info was merged
https://github.com/software-mansion/scarb/pull/1082

repo: foundry-rs/starknet-foundry


text:
🛑 Advantage Print Solutions is down

In 1805839, Advantage Print Solutions (https://www.advantageprintsolutions.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Advantage Print Solutions is back up in fd3e134.

repo: fourthfloor/uptime


text:
perf: performance regression on RisingWave with 0.11

There is an obvious regression on nexmark Q7 and Q014 for RisingWave with foyer 0.11 rather than with foyer 0.10.

Based on the flamegraph, the regression comes from 3 stacks:

Which are:

and

and

Let's see why.
Full flamegraphs:

Grafana:
010: https://grafana.test.risingwave-cloud.xyz/d/EpkBw5W4k/risingwave-dev-dashboard?orgId=1&var-datasource=cdtasocg64074c&var-namespace=xx-foyer-010-1&var-instance=benchmark-risingwave&var-pod=All&var-component=All&var-table=All&from=1726042331594&to=1726086587137
011: https://grafana.test.risingwave-cloud.xyz/d/EpkBw5W4k/risingwave-dev-dashboard?orgId=1&var-datasource=cdtasocg64074c&var-namespace=xx-foyer-011-1&var-instance=benchmark-risingwave&var-pod=All&var-component=All&var-table=All&from=1726041953341&to=1726086965390

Seems the memory buffer overhead in foyer 0.11 caused heavier operator memory eviction in RW.

Seems the memory buffer overhead in foyer 0.11 caused heavier operator memory eviction in RW.

Can you share the memory consumption metrics from the foyer side ?

Seems the memory buffer overhead in foyer 0.11 caused heavier operator memory eviction in RW.

Can you share the memory consumption metrics from the foyer side ?

Actually, I don't think there is a metrics showing it. It is caused by a temporary buffer that was introduced in 0.11. I'm trying to remove it when there is no compression needs.

Solved. The regression is caused by the misleading argument buffer_threshold in v0.11. I'll rename it.

repo: foyer-rs/foyer


text:
Update artemis-jms-client-all to 2.38.0

About this PR
📦 Updates org.apache.activemq:artemis-jms-client-all from 2.19.1 to 2.38.0
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.apache.activemq", artifactId = "artemis-jms-client-all" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.apache.activemq", artifactId = "artemis-jms-client-all" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #466.


text:
Readd BlastHttp package

Checklist:

[x] Meaningful commit message - please not Update build-constraints.yml

[x] Some time passed since Hackage upload

[ ] On your own machine, in a new directory, you have successfully run the following set of commands (replace $package with the name of the package that is submitted, $version is the version of the package you want to get into Stackage):
stack unpack $package
cd $package-$version
stack init --resolver nightly
stack build --resolver nightly --haddock --test --bench --no-run-benchmarks

There are a few roadblocks to accepting this. Mainly lens (blocked by simple-reflect) and http-conduit (blocked by blaze-builder). Actually I think I can address the lens one fairly easily...
BiobaseTypes-0.1.3.0 is out of bounds for:

[ ] BiobaseBlast-0.2.1.0 (==0.1.2.*). No maintainer. Used by: library

BiobaseXNA-0.10.0.0 is out of bounds for:

[ ] BiobaseBlast-0.2.1.0 (==0.9.3.*). No maintainer. Used by: library

biocore (not present) depended on by:

[ ] BlastHTTP-1.3.0 (-any). Florian Eggenhofer egg@informatik.uni-freiburg.de @eggzilla. @eggzilla. Used by: library

biofasta (not present) depended on by:

[ ] BlastHTTP-1.3.0 (-any). Florian Eggenhofer egg@informatik.uni-freiburg.de @eggzilla. @eggzilla. Used by: library

blastxml (not present) depended on by:

[ ] BlastHTTP-1.3.0 (-any). Florian Eggenhofer egg@informatik.uni-freiburg.de @eggzilla. @eggzilla. Used by: library

http-conduit (not present) depended on by:

[ ] BlastHTTP-1.3.0 (-any). Florian Eggenhofer egg@informatik.uni-freiburg.de @eggzilla. @eggzilla. Used by: library

hxt (not present) depended on by:

[ ] BlastHTTP-1.3.0 (-any). Florian Eggenhofer egg@informatik.uni-freiburg.de @eggzilla. @eggzilla. Used by: library

lens (not present) depended on by:

[ ] BiobaseTypes-0.1.3.0 (>=4.0). No maintainer. Used by: library
[ ] BiobaseXNA-0.10.0.0 (>=4.0). No maintainer. Used by: library
[ ] DPutils-0.0.1.0 (>=4.0). No maintainer. Used by: test-suite

log-domain (not present) depended on by:

[ ] PrimitiveArray-0.8.0.1 (>=0.10). No maintainer. Used by: library

pipes-bytestring (not present) depended on by:

[ ] DPutils-0.0.1.0 (>=2.0). No maintainer. Used by: test-suite

tasty-silver (not present) depended on by:

[ ] BiobaseBlast-0.2.1.0 (>=3.1.9). No maintainer. Used by: test-suite

tuple (not present) depended on by:

[ ] BiobaseXNA-0.10.0.0 (>=0.3). No maintainer. Used by: library

The updated list is:
BiobaseTypes-0.1.3.0 is out of bounds for:

[ ] BiobaseBlast-0.2.1.0 (==0.1.2.*). No maintainer. Used by: library

BiobaseXNA-0.10.0.0 is out of bounds for:

[ ] BiobaseBlast-0.2.1.0 (==0.9.3.*). No maintainer. Used by: library

biocore (not present) depended on by:

[ ] BlastHTTP-1.3.0 (-any). Florian Eggenhofer egg@informatik.uni-freiburg.de @eggzilla. @eggzilla. Used by: library

biofasta (not present) depended on by:

[ ] BlastHTTP-1.3.0 (-any). Florian Eggenhofer egg@informatik.uni-freiburg.de @eggzilla. @eggzilla. Used by: library

blastxml (not present) depended on by:

[ ] BlastHTTP-1.3.0 (-any). Florian Eggenhofer egg@informatik.uni-freiburg.de @eggzilla. @eggzilla. Used by: library

tuple (not present) depended on by:

[ ] BiobaseXNA-0.10.0.0 (>=0.3). No maintainer. Used by: library

For those "not present", they are listed as omitted due to a build failure. I will take a closer look to see what failed and file a bug report.

There were build failures with OneTuple and biocore. Neither seem to have issue trackers so I'll go ahead and paste the errors here:
OneTuple: BuildFailureException Process exited with ExitFailure 1: ./Setup build

Building library for OneTuple-0.2.1..
[1 of 1] Compiling Data.Tuple.OneTuple ( Data/Tuple/OneTuple.hs, dist/build/Data/Tuple/OneTuple.o )

Data/Tuple/OneTuple.hs:71:10: error:
    • Could not deduce (Semigroup (OneTuple a))
        arising from the superclasses of an instance declaration
      from the context: Monoid a
        bound by the instance declaration
        at Data/Tuple/OneTuple.hs:71:10-42
    • In the instance declaration for ‘Monoid (OneTuple a)’
   |
71 | instance (Monoid a) => Monoid (OneTuple a) where
   |          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

biocore: BuildFailureException Process exited with ExitFailure 1: ./Setup build

Building library for biocore-0.3.1..
[1 of 3] Compiling Bio.Core.Sequence ( src/Bio/Core/Sequence.hs, dist/build/Bio/Core/Sequence.o )

src/Bio/Core/Sequence.hs:43:10: error:
    • No instance for (Semigroup SeqData)
        arising from the superclasses of an instance declaration
    • In the instance declaration for ‘Monoid SeqData’
   |
43 | instance Monoid SeqData where
   |          ^^^^^^^^^^^^^^

src/Bio/Core/Sequence.hs:52:10: error:
    • No instance for (Semigroup SeqLabel)
        arising from the superclasses of an instance declaration
    • In the instance declaration for ‘Monoid SeqLabel’
   |
52 | instance Monoid SeqLabel where
   |          ^^^^^^^^^^^^^^^

src/Bio/Core/Sequence.hs:69:10: error:
    • No instance for (Semigroup QualData)
        arising from the superclasses of an instance declaration
    • In the instance declaration for ‘Monoid QualData’
   |
69 | instance Monoid QualData whe

These, in turn, block their revdeps:
biofasta: DependencyFailed (PackageName "biocore")
blastxml: DependencyFailed (PackageName "biocore")
tuple: DependencyFailed (PackageName "OneTuple")
I'm closing this PR for now. Feel free to open a new PR once these dependency and constraint issues have been sorted out.

Ping @sid-kap re: OneTuple and tuple
Ping @ketil-malde re: biocore, biofasta, blastxml
See above.

Hi,
Thanks for the ping!  I don't do much bio nor Haskell these days, but I suppose Semigroup is the result of some redesign of base or other libraries.  The fix might be so simple as just adding it to a deriving clause, but rather than me fumbling around with a library I don't really use much anymore, perhaps somebody else could take over my bio* and maintain them?

authors: DanBurton eggzilla ketil-malde

repo: fpco/stackage


text:
Inline values being used instead of templates

Inline values prevent templates from being checked as individual files externally, but this is only a nuisance. The real danger is that forgetting to close an inline delimiter changes semantics of the entire .tf file. Check the example below:
module "a" {
  source = "some-path"
  param = <<EOF
bar
EOT
}

module "b" {
  source = "some-path"
  param = <<EOF
baz
EOF
}

The following code above will terraform apply correctly, but module.a.param will not be bar, and module.b will never be created. In modules with nested resources or a large amount of modules this can easily pass unnoticed — specially common since modules take no count.
A counter-argument is that syntax highlight could potentially showcase this problem. But this cannot be checked without human intervention, as a checker cannot know if module.b should or not be created.
The following modules are currently using inline values and should be changed to use templates with external files instead:
examples/nexus-asg/nexus.tf
58:  init_prefix = <<END_INIT
64:  init_suffix = <<END_INIT

examples/cloud-dev-workspace/main.tf
93:  user_data = <<END_INIT

examples/vpc-scenario-1/main.tf
91:  user_data = <<END_INIT

examples/kube-stack-private/bastion.tf
50:  user_data = <<END_INIT

examples/kube-stack-public/bastion.tf
47:  user_data = <<END_INIT

examples/gitlab-asg/main.tf
158:  init_prefix = <<END_INIT
164:  init_suffix = <<END_INIT

examples/legacy/main.tf
43:    extra_init = <<EOF
139:    extra_init = <<EOF

examples/vpc-scenario-2-nat-instances-per-az/main.tf
245:  user_data = <<END_INIT

examples/vpc-scenario-2/main.tf
149:  user_data = <<END_INIT

modules/elk-stack/main.tf
141:  extra_config = <<END_CONFIG

modules/init-snippet-gitlab-docker/main.tf
77:  template = <<EOC
91:  template = <<END_INIT

modules/snapshot-bucket/main.tf
22:  policy = <<EOF

examples/vpc-scenario-2-nat-instance/main.tf
241:  user_data = <<END_INIT

modules/dnsmasq-server/main.tf
21: *       template = <<END_CONF
53: *       user_data = <<END_INIT

modules/kibana/variables.tf
62:  description = <<DOC

modules/kube-stack/main.tf
70:  user_data = <<END_INIT
108:  user_data = <<END_INIT

modules/kibana/main.tf
128:  user_data = <<USER_DATA

modules/persistent-ebs-volumes/iam.tf
9:  policy = <<END_POLICY

modules/persistent-ebs/iam.tf
11:  assume_role_policy = <<END_POLICY
33:  policy = <<END_POLICY

modules/scale-asg-iam-policy/main.tf
13:  policy = <<EOF

modules/elasticsearch/data-nodes.tf
102:    extra_setup_snippet = <<EXTRA_SETUP
133:    extra_config       = <<EXTRA_CONFIG

modules/elasticsearch/variables.tf
133:  description = <<DOC
158:  description = <<DOC

modules/elasticsearch/iam.tf
39:  assume_role_policy = <<END_POLICY
60:  assume_role_policy = <<END_POLICY
80:  policy = <<END_POLICY

modules/single-node-asg/main.tf
52:  user_data = <<END_INIT

modules/logstash/iam.tf
44:  assume_role_policy = <<END_POLICY

modules/consul-demo-server/main.tf
32:  init_suffix = <<END_INIT

modules/elasticsearch/master-nodes.tf
103:    extra_setup_snippet = <<EXTRA_SETUP
131:    extra_config = <<EXTRA_CONFIG

modules/prometheus-server/main.tf
44:  user_data = <<END_INIT
68:  init_prefix = <<END_INIT
75:  prometheus_pillar = <<END_PILLAR

modules/ec2-nat-instances/main.tf
32:  init   = <<END_INIT
52:  template = <<END_INIT

modules/credstash-setup/data.tf
14:  template = <<END_TEMPLATE

modules/consul-agent-generic-init/main.tf
32: *     extra_init = <<EOF

modules/ebs-snapshot-iam/main.tf
43:  policy = <<EOF

modules/prometheus-server/tests/main.tf
73:  init_suffix = <<END_INIT

modules/credstash-setup/main.tf
56:  policy = <<END_POLICY
78:  policy = <<END_POLICY

modules/ec2-auto-recover-instances/main.tf
45: *       user_data = <<END_INIT

I would prefer to have a tool that warns us when a mistake has been made, over classifying all use of inlines as evil. I believe we should review occurrences of this individually, and I'm not sure how I feel about a single issue to encompass of occurrences of this pattern.

There is nothing inherently evil in this, just as there is nothing evil in pointer arithmetic in C. But designing a tool that checks when either is correct is a very large challenge. It’s just a set of tradeoffs.
I will remove the checks from #103 until we do a manual review then.
We can add the review for the items above in this issue here until all occurrences have been documented as OK or not, since it has to be tracked somewhere and this has the list already. Then we close it. Sounds good?

authors: kerscher ketzacoatl

repo: fpco/terraform-aws-foundation


text:
Aggregate metadata from parallel task

A parallel task running e.g. on N images already produces N *_metadiff.json files. These files all have content {}, since we were implementing fractal-tasks-core under the assumption that parallel tasks cannot contribute back any information to the server/DB.
Let's relax this assumption, and integrate a feature for aggregating in a safe way (to be better defined) those N JSON objects into a single object that can be used to update Dataset.meta after the N parallel executions are complete.

For the record: given the upcoming separation of components from meta (ref #850), the provisional choice of aggregation function is not critical.
The most relevant use case will be to aggregate new components, where we can use a strictly defined aggregation rule.
The aggregation of meta is less crucial, and we will eventually (post #850) decide whether we should allow it (and with which rule) or simply ignore it.


text:
Replace loading .zattrs file with accessing zarr attrs

We currently do it at least in the following cases:
$ git grep -n "with open(" | grep zattr

lib_zattrs_utils.py:36:    with open(zattrs_path, "r") as jsonfile:
tasks/cellpose_segmentation.py:397:    with open(zattrs_file, "r") as jsonfile:
tasks/cellpose_segmentation.py:430:        with open(f"{zarrurl}/labels/.zattrs", "r") as f_zattrs:
tasks/napari_workflows_wrapper.py:200:    with open(zattrs_file, "r") as jsonfile:
tasks/napari_workflows_wrapper.py:431:            with open(f"{zarrurl}/labels/.zattrs", "r") as f_zattrs:

while it'd be more general to directly access the attrs of a zarr group, rather than depending on a specific on-disk storage.

After #528, this issue will appear only in a few places.

[ ] Update get_table_path_dict to take a zarr group rather than a path
[ ] Update apply_registration_to_image.py to access labels via the appropriate Ngff object
[ ] Update napari_workflows_wrapper.py, re: multiscales

A small fix to the cellpose was still missing. Done with 3d62b29.


text:
I would like to be able to create dynamic pages with a custom url

In a website I did, I created a code that when the user clicks on a link a page appears with the load message and the url changes with the link.

But to do it first you have to call a dynamic page that has an ugly url (#content-4) and then request to reload the page with the actual link being requested by the user (it was the only form I found in the documentation). But sometimes this causes a browsing problem because when the user clicks back the browser returns to a "#content-4" page.
I wanted a more practical way of doing this just by request for something like:
app.router.navigate({
     'path': '/post/the-good-place',
     'content': '<div class="page"> ... </div>',
});
There is a tip there for you to add in the second version.

http://framework7.io/docs/pages-dynamic.html

It will be realized and already partial available in v2

authors: httpiago lailton nolimits4web


text:
There is not Email icon in SVG folder

Where i use f7-icons, add class email and email-fill, but it's not work

https://framework7.io/icons/

There us no email_fill icon


text:
refactor: refactor code based on peer review

What does this PR do?

refactor code to improve performance

Description of Task to be completed?

refactor code to improve performance based on peer reviews

How should this be manually tested?

none

Any background context you want to provide?

none

What are the relevant pivotal tracker stories?

none

Screenshots (if appropriate)

none

Questions:

Coverage increased (+0.01%) to 91.121% when pulling 3843e72d9e0bd486be7aaf98b44b503fa6a34b5e on refactor/refactor-code into 635903a8074434725c38b514771efe7ef8719f72 on develop.

Coverage decreased (-4.5%) to 86.598% when pulling 38442390feddbfd00358784ad5b5c52c9852639b on refactor/refactor-code into 635903a8074434725c38b514771efe7ef8719f72 on develop.


text:
🛑 PEDCO is down

In b7bdc82, PEDCO (https://pedco.uncoma.edu.ar/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: PEDCO is back up in 6aad052 after 23 minutes.


text:
sync repo

sync repo

sync repo


text:
Missing feature: Inverse Kinematics

Greetings everyone. I recently started looking into using libfranka in control loops and I thought I would have been able to find a method to obtain the inverse kinematics from the franka::Model class.
As far as I can understand, the IK is computed anyway within the FCU when a cartesian trajectory is commanded. What is the recommended way of solving the IK for any workspace pose without the need to install third-party libraries?
Not being able to query the FCU for a IK computation seems like a weird oversight, maybe there is a very reasonable explanation though.

Hi @fbottarel ,
if you are still interested, then we followed a slightly different route... in a ROS environment, there is plenty of 3rd party software which can give you a whole plethora of IKs. We also provide an example in ROS 2 which could be used as a start point: https://github.com/frankaemika/franka_ros2/blob/humble/franka_example_controllers/src/joint_impedance_with_ik_example_controller.cpp
Cheers,
Andreas

authors: AndreasKuhner fbottarel

repo: frankaemika/libfranka


text:
Logout button not shown when logging in via 401 pop-up

Describe the bug
When going directly to the console (for example, /iaf/gui/#!/status), no logout option appears in the console. When logging in via /iaf/gui/#!/login the logout option does appear.
Reporter
Ricardo
Category
Use following Tags to categorize your bug report

Frank Console

To Reproduce
Steps to reproduce the behavior:

Go to the console via /iaf/gui/#!/status
Log in with your credentials
No logout option appears
Force a logout by manually browsing to /iaf/gui/#!/logout (this should also place you at /iaf/gui/#!/login)
Log in with your credentials
The logout option now is present
Open a new tab and go to /iaf/gui/#!/status
Logout option is gone again

Expected behavior
The logout to also be available when not entering the console using the login screen
Screenshots
N/A
Environment:

Application server (f.e. Tomcat/WebSphere/JBOSS/Jetty): WbSphere
Browser [e.g. chrome, safari]: Chrome
IAF Version [e.g. 7.5 RC3, 7.6]: 7.6-20201030.100621

Additional context
N/A

You can now logout via /logout behind the servlet path. A frontend change is still required to show the logout button (and potentially cleanup the authservice).

repo: frankframework/frankframework


text:
Add device info for Pi

Closes #31
Implementation

Add an API to fetch device info if on raspberry pi, otherwise return an object with all values set to "Cannot determine".
This API needs access to raspberry pi from the node docker container (password-manager service), and thus makes use of a named pipe to do so (more details here).
Update the API call to use this new API instead of using the CPU temp API to display all of these device information.
To prevent calling the program to fetch new system info every time the page is visited, the API results are cached and are only updated (i.e. command is sent to pipe for execution) only after a certain threshold has been crossed since the last time the file was updated, otherwise the previous results are served from the file.

Tested on Pi, and it looks good, caching is working as well.


text:
Release on GoReleaser

It would be very convenient if this project could be installed via GoReleaser. Installing it via go get -u is not optimal because that doesn't install the latest released version but rather the latest state of the master branch.

Hi @mastertinner the project is indeed available as a binary release (released through goreleaser nonetheless 😄 ), see the README.md for homebrew install steps or check out the releases page for docker containers and binaries alike.

Thanks for your quick reply and sorry for missing that!

authors: frapposelli mastertinner

repo: frapposelli/wwhrd


text:
Create and use JSON parameters file for Bicep template

This is a workaround until issue: https://github.com/Azure/arm-deploy/issues/139 is resolved.

LGTM!

repo: frasermclean/adoptrix


text:
Add Toast

It has a nice simulator, which means anyone working on the code will be able to run their code and see what happens right away!

This effectively is a superset of Issue "Add GradleRIO"


text:
not getting

Challenge Create a Bootstrap Button has an issue.
User Agent is: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:

<link href="https://fonts.googleapis.com/css?family=Lobster" rel="stylesheet" type="text/css">

CatPhotoApp

Click here for cat photos.

  <input type = "button" class="btn">Like</input>

Things cats love:

cat nip

laser pointers

lasagna

Top 3 things cats hate:

flea treatment

thunder

other cats

  <form action="/submit-cat-photo">
    <input type="radio" name="indoor-outdoor"> Indoor
    <input type="radio" name="indoor-outdoor"> Outdoor
    <input type="checkbox" name="personality"> Loving
    <input type="checkbox" name="personality"> Lazy
    <input type="checkbox" name="personality"> Crazy
    <input type="text" placeholder="cat photo URL" required>
    <button type="submit">Submit</button>
  </form>

I'm guessing this is the code you have added...
<input type = "button" class="btn">Like</input>

Looking at the instructions of that challenge, it is asking you to create a button element, but you have created an input element. I would also remove the spaces around the = just for good practice.
Don't forget to ask in chat or the forum first if you have any problems with challenges, as you will often get help quicker 👍

Thank you, yes, I got confused. :-) I made necessary changes.
Working fine.

repo: freeCodeCamp/freeCodeCamp