CommComm Member Travel Fund allocation request for 2017

CommComm Travel Allocation Request for 2017 for Board deck
We would like to encourage as many collaborators to attend/represent at Collab Summit and other relevant events for the remainder of this year, and part of that is making sure it is known that everyone meeting in one place is awesome(and valued) on our non-technical contribution side as well! This estimate is with the hope that all of this will not be needed, but we'll want to heavily evangelize this to all collaborators because we've been hearing a lot of feedback of the financial challenge it can be to attend these events. Calculating for members of CommComm and the Evangelism WG and reducing the count for employees of corporate members, with a North America to non-NA ratio at 60/40, and estimated at a $500 domestic/$1000 international flight rate, I expect at 2 nights' hotel:
***a general rule for our travel funds is that if you are an employee of a corporate member in Node.js, we ask that you refrain from requesting from the public fund and instead ask your employer. We are happy to help provide information on the value of these events.

Whereabouts
Count
Flight Cost
Lodging

North America
12
$500
$210

Everywhere Else
8
$1000
$210

Total
20
$14,000
$8200

Total Allocation Request: $22, 200
This allocation will be contingent upon the Board's approval of the fund being established in #81

i won't make it to the vancouver collab because it's in the same week as my first week of university, so that's roughly $1k less

$22k sounds reasonable to me.
@pup even if you can't make it, there's always a chance we'll get someone else from Europe who wants to attend. I'd prefer to keep you counted for now, for statistical reasons if nothing else.

@nebrius thats fair!

Will there be a collaborator's summit at this event? If so, and it follows the same structure we've done in the past, I'd like to request that hotel accommodations for that be included in this as well.

Will there be a collaborator's summit at this event? If so, and it follows the same structure we've done in the past, I'd like to request that hotel accommodations for that be included in this as well.

There will be a collaborator's summit right after Node Interactive in Vancouver in October, see https://github.com/nodejs/summit/issues/44 for more details.
Hotel is included, see the "Lodging" column. I do have a question though @hackygolucky, how many nights is that for? It sounds like one night to me, but we'll probably need three nights per person.

@nebrius I think the origin comment say its for 2 nights.

@mhdawson ah, yes, you are correct.
I was thinking three nights so that people can arrive the day before and depart the day after the summit. Thinking about it further, two nights is probably sufficient for folks on the west coast, but I think it would be better to give folks with a long flight the ability to fly out the day after (unless you like red-eye flights of course!)
Thoughts?

This whole thing is calculated for the Collaborators Summit only, for travel and lodging. I did not calculate for Node Interactive attendance or ticket registration, as even for collaborators it still costs $$$.

This whole thing is calculated for the Collaborators Summit only, for travel and lodging. I did not calculate for Node Interactive attendance or ticket registration, as even for collaborators it still costs $$$. If I calculated for that, each person would be nearly 5 nights' stay and the added reg cost. To note: this was not done for the TSC travel fund calculations either. I worried about the lack of neutrality of us calculating folks attending this conf and not other ones. Maybe that's nonsensical :-/

Ahh, I see, that makes sense. I think I still lean towards calculating three nights stay, aka assuming folks will not be at the conference. That said, maybe it would make sense to use a proportion? We could assume that, say, 50% of people making use of this fund would be at the conference (and thus have the first night covered), and the other 50% would not. This would mean assuming 2.5 nights per person. What do you think?

@hackygolucky is there anything else that we need to do for this, or can we close it?

This exists in the Admin repo under joint responsibility of the TSC and CommComm for approving requests. Closing because it was approved as a joint effort via the Node.js Board of Directors for funding.


Update Post “2019-01-15-doom”

Automatically generated by Netlify CMS

👷 Deploy Preview for vigorous-darwin-e81d1f processing.
🔨 Explore the source changes: 2543470e50606ea8dea19b5ed85d012f1315abba
🔍 Inspect the deploy log: https://app.netlify.com/sites/vigorous-darwin-e81d1f/deploys/61ce22c281385c00078f1cbc


Manual recovery after "gcs connection failed" with one statefulset pod gone

On preemtible nodes we had one instance of manual recovery, after #30. There was no mariadb-1 pod, and -0 and -2 stayed crashlooping. The were past init but the mariadb containers exited after:
2020-05-27  6:10:26<PHONE_NUMBER>66464 [Warning] WSREP: last inactive check more than PT1.5S ago (PT3.50176S), skipping check
2020-05-27  6:10:55<PHONE_NUMBER>66464 [Note] WSREP: view((empty))
2020-05-27  6:10:55<PHONE_NUMBER>66464 [ERROR] WSREP: failed to open gcomm backend connection: 110: failed to reach primary view: 110 (Connection timed out)
	 at gcomm/src/pc.cpp:connect():158
2020-05-27  6:10:55<PHONE_NUMBER>66464 [ERROR] WSREP: gcs/src/gcs_core.cpp:gcs_core_open():209: Failed to open backend connection: -110 (Connection timed out)
2020-05-27  6:10:55<PHONE_NUMBER>66464 [ERROR] WSREP: gcs/src/gcs.cpp:gcs_open():1458: Failed to open channel 'my_wsrep_cluster' at 'gcomm://mariadb-0.mariadb,mariadb-1.mariadb,mariadb-2.mariadb': -110 (Connection timed out)
2020-05-27  6:10:55<PHONE_NUMBER>66464 [ERROR] WSREP: gcs connect failed: Connection timed out
2020-05-27  6:10:55<PHONE_NUMBER>66464 [ERROR] WSREP: wsrep::connect(gcomm://mariadb-0.mariadb,mariadb-1.mariadb,mariadb-2.mariadb) failed: 7
2020-05-27  6:10:55<PHONE_NUMBER>66464 [ERROR] Aborting

This could be a case for switching from OrderedReady to Parrallel.
The solution  was to scale down to zero and then back up to three again. Oddly the pods wouldn't go away at scale to zero, so I had to manually delete mariadb-2. Is that the expected behavior for OrderedReady?

We've since had a similar failure (have a look at the logs from 7:43:
mariadb-0                                   1/2     Running   0          24h
mariadb-2                                   2/2     Running   1          11h

# logs mariadb-0
2020-06-03 21:24:47<PHONE_NUMBER>15040 [Warning] WSREP: a0e77878 conflicting prims: my prim: view_id(PRIM,a0e77878,1) other prim: view_id(PRIM,da4a9e7f,88)
2020-06-03 21:24:47<PHONE_NUMBER>15040 [ERROR] WSREP: caught exception in PC, state dump to stderr follows:
...
2020-06-03 21:24:47<PHONE_NUMBER>15040 [ERROR] WSREP: exception from gcomm, backend must be restarted: a0e77878 aborting due to conflicting prims: older overrides (FATAL)
	 at gcomm/src/pc_proto.cpp:handle_state():1001
...
2020-06-03 21:24:47<PHONE_NUMBER>41664 [Note] WSREP: RECV thread exiting -103: Software caused connection abort
2020-06-03 21:24:47<PHONE_NUMBER>20224 [Note] WSREP: New cluster view: global state: 00000000-0000-0000-0000-000000000000:0, view# -1: non-Primary, number of nodes: 0, my index: -1, protocol version -1
2020-06-03 21:24:47<PHONE_NUMBER>20224 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
2020-06-03 21:24:47<PHONE_NUMBER>20224 [Note] WSREP: applier thread exiting (code:6)

# logs mariadb-2
2020-06-04  7:43:26<PHONE_NUMBER>03744 [Note] WSREP: view(view_id(PRIM,af704c35,92) memb {
	af704c35,0
} joined {
} left {
} partitioned {
	da4a9e7f,0
})
2020-06-04  7:43:26<PHONE_NUMBER>03744 [Note] WSREP: save pc into disk
2020-06-04  7:43:26<PHONE_NUMBER>03744 [Note] WSREP: forgetting da4a9e7f (tcp://<IP_ADDRESS>:4567)
2020-06-04  7:43:26<PHONE_NUMBER>06592 [Note] WSREP: New COMPONENT: primary = yes, bootstrap = no, my_idx = 0, memb_num = 1
2020-06-04  7:43:26<PHONE_NUMBER>06592 [Note] WSREP: STATE_EXCHANGE: sent state UUID: 137dfe6e-a637-11ea-a6b3-dab3d14eab1d
2020-06-04  7:43:26<PHONE_NUMBER>06592 [Note] WSREP: STATE EXCHANGE: sent state msg: 137dfe6e-a637-11ea-a6b3-dab3d14eab1d
2020-06-04  7:43:26<PHONE_NUMBER>06592 [Note] WSREP: STATE EXCHANGE: got state msg: 137dfe6e-a637-11ea-a6b3-dab3d14eab1d from 0 (mariadb-2)
2020-06-04  7:43:26<PHONE_NUMBER>06592 [Note] WSREP: Quorum results:
	version    = 6,
	component  = PRIMARY,
	conf_id    = 88,
	members    = 1/1 (joined/total),
	act_id     = 33,
	last_appl. = 0,
	protocols  = 0/9/3 (gcs/repl/appl),
	group UUID = d1704a99-a17e-11ea-86df-d368d39f6188
2020-06-04  7:43:26<PHONE_NUMBER>06592 [Note] WSREP: Flow-control interval: [16, 16]
2020-06-04  7:43:26<PHONE_NUMBER>06592 [Note] WSREP: Trying to continue unpaused monitor
2020-06-04  7:43:26<PHONE_NUMBER>87104 [Note] WSREP: New cluster view: global state: d1704a99-a17e-11ea-86df-d368d39f6188:33, view# 89: Primary, number of nodes: 1, my index: 0, protocol version 3
2020-06-04  7:43:26<PHONE_NUMBER>87104 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
2020-06-04  7:43:26<PHONE_NUMBER>87104 [Note] WSREP: REPL Protocols: 9 (4, 2)
2020-06-04  7:43:26<PHONE_NUMBER>87104 [Note] WSREP: Assign initial position for certification: 33, protocol version: 4
2020-06-04  7:43:26<PHONE_NUMBER>74560 [Note] WSREP: Service thread queue flushed.
2020-06-04  7:43:31<PHONE_NUMBER>03744 [Note] WSREP:  cleaning up da4a9e7f (tcp://<IP_ADDRESS>:4567)
2020-06-04  7:48:32<PHONE_NUMBER>05120 [Warning] IP address '<IP_ADDRESS>' could not be resolved: Name or service not known
2020-06-04  7:50:53<PHONE_NUMBER>13504 [Warning] IP address '<IP_ADDRESS>' could not be resolved: Name or service not known
2020-06-04  7:57:05<PHONE_NUMBER>91904 [Warning] IP address '<IP_ADDRESS>' could not be resolved: Name or service not known
2020-06-04  8:40:44<PHONE_NUMBER>99104 [Warning] IP address '<IP_ADDRESS>' could not be resolved: Name or service not known

Had a similar/identical issue again, mariadb-0 1/2 ready, the other two pods 2/2, logs for mariadb-0:
2020-07-22 04:16:52+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 1:10.2.32+maria~bionic started.
2020-07-22 04:16:53+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
2020-07-22 04:16:53+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 1:10.2.32+maria~bionic started.
2020-07-22  4:16:53<PHONE_NUMBER>10912 [Note] mysqld (mysqld 10.2.32-MariaDB-1:10.2.32+maria~bionic) starting as process 1 ...
2020-07-22  4:16:53<PHONE_NUMBER>10912 [Note] WSREP: Read nil XID from storage engines, skipping position init
2020-07-22  4:16:53<PHONE_NUMBER>10912 [Note] WSREP: wsrep_load(): loading provider library '/usr/lib/galera/libgalera_smm.so'
2020-07-22  4:16:53<PHONE_NUMBER>10912 [Note] WSREP: wsrep_load(): Galera 25.3.29(r3902) by Codership Oy<EMAIL_ADDRESS>loaded successfully.
2020-07-22  4:16:53<PHONE_NUMBER>10912 [Note] WSREP: CRC-32C: using hardware acceleration.
2020-07-22  4:16:53<PHONE_NUMBER>10912 [Note] WSREP: Found saved state: 35de4dd1-ca3e-11ea-9217-0b5c2293d6b7:12, safe_to_bootstrap: 1
2020-07-22  4:16:53<PHONE_NUMBER>10912 [Note] WSREP: Passing config to GCS: base_dir = /data/db/; base_host = <IP_ADDRESS>; base_port = 4567; cert.log_conflicts = no; cert.optimistic_pa = yes; debug = no; evs.auto_evict = 0; evs.delay_margin = PT1S; evs.delayed_keep_period = PT30S; evs.inactive_check_period = PT0.5S; evs.inactive_timeout = PT15S; evs.join_retrans_period = PT1S; evs.max_install_timeouts = 3; evs.send_window = 4; evs.stats_report_period = PT1M; evs.suspect_timeout = PT5S; evs.user_send_window = 2; evs.view_forget_timeout = PT24H; gcache.dir = /data/db/; gcache.keep_pages_size = 0; gcache.mem_size = 0; gcache.name = /data/db//galera.cache; gcache.page_size = 128M; gcache.recover = no; gcache.size = 128M; gcomm.thread_prio = ; gcs.fc_debug = 0; gcs.fc_factor = 1.0; gcs.fc_limit = 16; gcs.fc_master_slave = no; gcs.max_packet_size = 64500; gcs.max_throttle = 0.25; gcs.recv_q_hard_limit =<PHONE_NUMBER>854775807; gcs.recv_q_soft_limit = 0.25; gcs.sync_donor = no; gmcast.segment = 0; gmcast.version = 0; pc.announce_timeout = PT3S; pc.checksum = fa...
2020-07-22  4:16:54<PHONE_NUMBER>10912 [Note] WSREP: GCache history reset: 35de4dd1-ca3e-11ea-9217-0b5c2293d6b7:0 -> 35de4dd1-ca3e-11ea-9217-0b5c2293d6b7:12
2020-07-22  4:16:54<PHONE_NUMBER>10912 [Note] WSREP: Assign initial position for certification: 12, protocol version: -1
2020-07-22  4:16:54<PHONE_NUMBER>10912 [Note] WSREP: wsrep_sst_grab()
2020-07-22  4:16:54<PHONE_NUMBER>10912 [Note] WSREP: Start replication
2020-07-22  4:16:54<PHONE_NUMBER>10912 [Note] WSREP: 'wsrep-new-cluster' option used, bootstrapping the cluster
2020-07-22  4:16:54<PHONE_NUMBER>10912 [Note] WSREP: Setting initial position to 35de4dd1-ca3e-11ea-9217-0b5c2293d6b7:12
2020-07-22  4:16:54<PHONE_NUMBER>10912 [Note] WSREP: protonet asio version 0
2020-07-22  4:16:54<PHONE_NUMBER>10912 [Note] WSREP: Using CRC-32C for message checksums.
2020-07-22  4:16:54<PHONE_NUMBER>10912 [Note] WSREP: backend: asio
2020-07-22  4:16:54<PHONE_NUMBER>10912 [Note] WSREP: gcomm thread scheduling priority set to other:0
2020-07-22  4:16:54<PHONE_NUMBER>10912 [Warning] WSREP: access file(/data/db//gvwstate.dat) failed(No such file or directory)
2020-07-22  4:16:54<PHONE_NUMBER>10912 [Note] WSREP: restore pc from disk failed
2020-07-22  4:16:54<PHONE_NUMBER>10912 [Note] WSREP: GMCast version 0
2020-07-22  4:16:54<PHONE_NUMBER>10912 [Warning] WSREP: Failed to resolve tcp://mariadb-0.mariadb:4567
2020-07-22  4:16:59<PHONE_NUMBER>10912 [Warning] WSREP: Failed to resolve tcp://mariadb-1.mariadb:4567
2020-07-22  4:17:09<PHONE_NUMBER>10912 [Warning] WSREP: Failed to resolve tcp://mariadb-2.mariadb:4567
2020-07-22  4:17:09<PHONE_NUMBER>10912 [Note] WSREP: (2ca50f1c, 'tcp://<IP_ADDRESS>:4567') listening at tcp://<IP_ADDRESS>:4567
2020-07-22  4:17:09<PHONE_NUMBER>10912 [Note] WSREP: (2ca50f1c, 'tcp://<IP_ADDRESS>:4567') multicast: , ttl: 1
2020-07-22  4:17:09<PHONE_NUMBER>10912 [Note] WSREP: EVS version 0
2020-07-22  4:17:09<PHONE_NUMBER>10912 [Note] WSREP: gcomm: bootstrapping new group 'my_wsrep_cluster'
2020-07-22  4:17:09<PHONE_NUMBER>10912 [Note] WSREP: start_prim is enabled, turn off pc_recovery
2020-07-22  4:17:09<PHONE_NUMBER>10912 [Note] WSREP: Node 2ca50f1c state prim
2020-07-22  4:17:09<PHONE_NUMBER>10912 [Note] WSREP: view(view_id(PRIM,2ca50f1c,1) memb {
	2ca50f1c,0
} joined {
} left {
} partitioned {
})
2020-07-22  4:17:09<PHONE_NUMBER>10912 [Note] WSREP: save pc into disk
2020-07-22  4:17:09<PHONE_NUMBER>10912 [Note] WSREP: gcomm: connected
2020-07-22  4:17:09<PHONE_NUMBER>10912 [Note] WSREP: Changing maximum packet size to 64500, resulting msg size: 32636
2020-07-22  4:17:09<PHONE_NUMBER>10912 [Note] WSREP: Shifting CLOSED -> OPEN (TO: 0)
2020-07-22  4:17:09<PHONE_NUMBER>10912 [Note] WSREP: Opened channel 'my_wsrep_cluster'
2020-07-22  4:17:09<PHONE_NUMBER>10912 [Note] WSREP: Waiting for SST to complete.
2020-07-22  4:17:09<PHONE_NUMBER>16192 [Note] WSREP: New COMPONENT: primary = yes, bootstrap = no, my_idx = 0, memb_num = 1
2020-07-22  4:17:09<PHONE_NUMBER>16192 [Note] WSREP: STATE_EXCHANGE: sent state UUID: 3598cf7f-cbd2-11ea-a089-aaa5f521af4b
2020-07-22  4:17:09<PHONE_NUMBER>16192 [Note] WSREP: STATE EXCHANGE: sent state msg: 3598cf7f-cbd2-11ea-a089-aaa5f521af4b
2020-07-22  4:17:09<PHONE_NUMBER>16192 [Note] WSREP: STATE EXCHANGE: got state msg: 3598cf7f-cbd2-11ea-a089-aaa5f521af4b from 0 (mariadb-0)
2020-07-22  4:17:09<PHONE_NUMBER>16192 [Note] WSREP: Quorum results:
	version    = 6,
	component  = PRIMARY,
	conf_id    = 0,
	members    = 1/1 (joined/total),
	act_id     = 12,
	last_appl. = -1,
	protocols  = 0/9/3 (gcs/repl/appl),
	group UUID = 35de4dd1-ca3e-11ea-9217-0b5c2293d6b7
2020-07-22  4:17:09<PHONE_NUMBER>16192 [Note] WSREP: Flow-control interval: [16, 16]
2020-07-22  4:17:09<PHONE_NUMBER>16192 [Note] WSREP: Trying to continue unpaused monitor
2020-07-22  4:17:09<PHONE_NUMBER>16192 [Note] WSREP: Restored state OPEN -> JOINED (12)
2020-07-22  4:17:09<PHONE_NUMBER>16192 [Note] WSREP: Member 0.0 (mariadb-0) synced with group.
2020-07-22  4:17:09<PHONE_NUMBER>16192 [Note] WSREP: Shifting JOINED -> SYNCED (TO: 12)
2020-07-22  4:17:09<PHONE_NUMBER>64384 [Note] WSREP: New cluster view: global state: 35de4dd1-ca3e-11ea-9217-0b5c2293d6b7:12, view# 1: Primary, number of nodes: 1, my index: 0, protocol version 3
2020-07-22  4:17:09<PHONE_NUMBER>10912 [Note] WSREP: SST complete, seqno: 12
2020-07-22  4:17:09<PHONE_NUMBER>10912 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2020-07-22  4:17:09<PHONE_NUMBER>10912 [Note] InnoDB: Uses event mutexes
2020-07-22  4:17:09<PHONE_NUMBER>10912 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-07-22  4:17:09<PHONE_NUMBER>10912 [Note] InnoDB: Using Linux native AIO
2020-07-22  4:17:09<PHONE_NUMBER>10912 [Note] InnoDB: Number of pools: 1
2020-07-22  4:17:09<PHONE_NUMBER>10912 [Note] InnoDB: Using SSE2 crc32 instructions
2020-07-22  4:17:09<PHONE_NUMBER>10912 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M
2020-07-22  4:17:09<PHONE_NUMBER>10912 [Note] InnoDB: Completed initialization of buffer pool
2020-07-22  4:17:09<PHONE_NUMBER>06816 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2020-07-22  4:17:09<PHONE_NUMBER>10912 [Note] InnoDB: Highest supported file format is Barracuda.
2020-07-22  4:17:09<PHONE_NUMBER>10912 [Note] InnoDB: 128 out of 128 rollback segments are active.
2020-07-22  4:17:09<PHONE_NUMBER>10912 [Note] InnoDB: Creating shared tablespace for temporary tables
2020-07-22  4:17:09<PHONE_NUMBER>10912 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2020-07-22  4:17:09<PHONE_NUMBER>10912 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2020-07-22  4:17:09<PHONE_NUMBER>10912 [Note] InnoDB: Waiting for purge to start
2020-07-22  4:17:09<PHONE_NUMBER>10912 [Note] InnoDB: 5.7.30 started; log sequence number 1618260
2020-07-22  4:17:09<PHONE_NUMBER>37120 [Note] InnoDB: Loading buffer pool(s) from /data/db/ib_buffer_pool
2020-07-22  4:17:09<PHONE_NUMBER>10912 [Note] Plugin 'FEEDBACK' is disabled.
2020-07-22  4:17:09<PHONE_NUMBER>37120 [Note] InnoDB: Buffer pool(s) load completed at 200722  4:17:09
2020-07-22  4:17:09<PHONE_NUMBER>10912 [Note] Server socket created on IP: '<IP_ADDRESS>'.
2020-07-22  4:17:09<PHONE_NUMBER>10912 [Note] Reading of all Master_info entries succeeded
2020-07-22  4:17:09<PHONE_NUMBER>10912 [Note] Added new Master_info '' to hash table
2020-07-22  4:17:09<PHONE_NUMBER>10912 [Note] mysqld: ready for connections.
Version: '10.2.32-MariaDB-1:10.2.32+maria~bionic'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution
2020-07-22  4:17:09<PHONE_NUMBER>64384 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
2020-07-22  4:17:09<PHONE_NUMBER>64384 [Note] WSREP: REPL Protocols: 9 (4, 2)
2020-07-22  4:17:09<PHONE_NUMBER>64384 [Note] WSREP: Assign initial position for certification: 12, protocol version: 4
2020-07-22  4:17:09<PHONE_NUMBER>14976 [Note] WSREP: Service thread queue flushed.
2020-07-22  4:17:09<PHONE_NUMBER>64384 [Note] WSREP: GCache history reset: 35de4dd1-ca3e-11ea-9217-0b5c2293d6b7:0 -> 35de4dd1-ca3e-11ea-9217-0b5c2293d6b7:12
2020-07-22  4:17:09<PHONE_NUMBER>64384 [Note] WSREP: Synchronized with group, ready for connections
2020-07-22  4:17:09<PHONE_NUMBER>64384 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
2020-07-22  4:31:17<PHONE_NUMBER>47520 [Warning] IP address '<IP_ADDRESS>' could not be resolved: Name or service not known
2020-07-22  9:01:36<PHONE_NUMBER>13344 [Note] WSREP: (2ca50f1c, 'tcp://<IP_ADDRESS>:4567') connection established to f2cb7e80 tcp://<IP_ADDRESS>:4567
2020-07-22  9:01:36<PHONE_NUMBER>13344 [Note] WSREP: (2ca50f1c, 'tcp://<IP_ADDRESS>:4567') turning message relay requesting on, nonlive peers:
2020-07-22  9:01:37<PHONE_NUMBER>13344 [Note] WSREP: (2ca50f1c, 'tcp://<IP_ADDRESS>:4567') connection established to 7efc2e5a tcp://<IP_ADDRESS>:4567
2020-07-22  9:01:37<PHONE_NUMBER>13344 [Note] WSREP: declaring 7efc2e5a at tcp://<IP_ADDRESS>:4567 stable
2020-07-22  9:01:37<PHONE_NUMBER>13344 [Note] WSREP: declaring f2cb7e80 at tcp://<IP_ADDRESS>:4567 stable
2020-07-22  9:01:37<PHONE_NUMBER>13344 [Warning] WSREP: 2ca50f1c conflicting prims: my prim: view_id(PRIM,2ca50f1c,1) other prim: view_id(PRIM,7efc2e5a,21)
2020-07-22  9:01:37<PHONE_NUMBER>13344 [ERROR] WSREP: caught exception in PC, state dump to stderr follows:
pc::Proto{uuid=2ca50f1c,start_prim=1,npvo=0,ignore_sb=0,ignore_quorum=0,state=1,last_sent_seq=3,checksum=0,instances=
	2ca50f1c,prim=1,un=0,last_seq=3,last_prim=view_id(PRIM,2ca50f1c,1),to_seq=2,weight=1,segment=0
,state_msgs=
	2ca50f1c,pcmsg{ type=STATE, seq=0, flags= 0, node_map {	2ca50f1c,prim=1,un=0,last_seq=3,last_prim=view_id(PRIM,2ca50f1c,1),to_seq=2,weight=1,segment=0
}}
,current_view=view(view_id(REG,2ca50f1c,22) memb {
	2ca50f1c,0
	7efc2e5a,0
	f2cb7e80,0
} joined {
	7efc2e5a,0
	f2cb7e80,0
} left {
} partitioned {
}),pc_view=view(view_id(PRIM,2ca50f1c,1) memb {
	2ca50f1c,0
} joined {
} left {
} partitioned {
}),mtu=32636}
2020-07-22  9:01:37<PHONE_NUMBER>13344 [Note] WSREP: {v=0,t=1,ut=255,o=4,s=0,sr=0,as=-1,f=4,src=7efc2e5a,srcvid=view_id(REG,2ca50f1c,22),insvid=view_id(UNKNOWN,00000000,0),ru=00000000,r=[-1,-1],fs=440865,nl=(
)
} 64
2020-07-22  9:01:37<PHONE_NUMBER>13344 [ERROR] WSREP: exception caused by message: {v=0,t=3,ut=255,o=1,s=0,sr=-1,as=0,f=4,src=7efc2e5a,srcvid=view_id(REG,2ca50f1c,22),insvid=view_id(UNKNOWN,00000000,0),ru=00000000,r=[-1,-1],fs=440867,nl=(
)
}
 state after handling message: evs::proto(evs::proto(2ca50f1c, OPERATIONAL, view_id(REG,2ca50f1c,22)), OPERATIONAL) {
current_view=view(view_id(REG,2ca50f1c,22) memb {
	2ca50f1c,0
	7efc2e5a,0
	f2cb7e80,0
} joined {
} left {
} partitioned {
}),
input_map=evs::input_map: {aru_seq=0,safe_seq=0,node_index=node: {idx=0,range=[1,0],safe_seq=0} node: {idx=1,range=[1,0],safe_seq=0} node: {idx=2,range=[1,0],safe_seq=0} },
fifo_seq=17083,
last_sent=0,
known:
2ca50f1c at
{o=1,s=0,i=1,fs=-1,}
7efc2e5a at tcp://<IP_ADDRESS>:4567
{o=1,s=0,i=1,fs=440867,}
f2cb7e80 at tcp://<IP_ADDRESS>:4567
{o=1,s=0,i=1,fs=9,}
 }2020-07-22  9:01:37<PHONE_NUMBER>13344 [ERROR] WSREP: exception from gcomm, backend must be restarted: 2ca50f1c aborting due to conflicting prims: older overrides (FATAL)
	 at gcomm/src/pc_proto.cpp:handle_state():1021
2020-07-22  9:01:37<PHONE_NUMBER>13344 [Note] WSREP: gcomm: terminating thread
2020-07-22  9:01:37<PHONE_NUMBER>13344 [Note] WSREP: gcomm: joining thread
2020-07-22  9:01:37<PHONE_NUMBER>13344 [Note] WSREP: gcomm: closing backend
2020-07-22  9:01:37<PHONE_NUMBER>13344 [Note] WSREP: Forced PC close
2020-07-22  9:01:37<PHONE_NUMBER>13344 [Warning] WSREP: discarding 2 messages from message index
2020-07-22  9:01:37<PHONE_NUMBER>13344 [Note] WSREP: gcomm: closed
2020-07-22  9:01:37<PHONE_NUMBER>16192 [Note] WSREP: Received self-leave message.
2020-07-22  9:01:37<PHONE_NUMBER>16192 [Note] WSREP: comp msg error in core 103
2020-07-22  9:01:37<PHONE_NUMBER>16192 [Note] WSREP: Closing send monitor...
2020-07-22  9:01:37<PHONE_NUMBER>16192 [Note] WSREP: Closed send monitor.
2020-07-22  9:01:37<PHONE_NUMBER>16192 [Note] WSREP: Closing replication queue.
2020-07-22  9:01:37<PHONE_NUMBER>16192 [Note] WSREP: Closing slave action queue.
2020-07-22  9:01:37<PHONE_NUMBER>16192 [Note] WSREP: Shifting SYNCED -> CLOSED (TO: 12)
2020-07-22  9:01:37<PHONE_NUMBER>16192 [Note] WSREP: RECV thread exiting -103: Software caused connection abort
2020-07-22  9:01:37<PHONE_NUMBER>64384 [Note] WSREP: New cluster view: global state: 00000000-0000-0000-0000-000000000000:0, view# -1: non-Primary, number of nodes: 0, my index: -1, protocol version -1
2020-07-22  9:01:37<PHONE_NUMBER>64384 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification.
2020-07-22  9:01:37<PHONE_NUMBER>64384 [Note] WSREP: applier thread exiting (code:6)


SetSize repositions the window at 0,0 with Cocoa

What OS are you using (uname -a, or Windows version)?
MacOS
What programming language are you using (C/C++/Go/Rust)?
go version go1.12.10 darwin/amd64
What did you expect to see and what you saw instead?
Using SetSize I expected the window to resize and keep it's position. Instead it resized to the right size but went to position 0,0.
In webview.h the code is set to specifically align the the view to 0,0 and set the new size.
objc_msgSend(m_window, "setFrame:display:animate:"_sel,
                   CGRectMake(0, 0, width, height), 1, 0);

The call to CGRectMake(0, 0, width, height) should really be something like CGRectMake(frame.origin.x, frame.origin.y, width, height). Unfortunately I don't quite understand the code well enough to get the frame object, although I have found all the relevant objective C docs and stack overflows:
https://developer.apple.com/documentation/appkit/nswindow/1419697-frame
https://stackoverflow.com/questions/12438224/set-nswindow-size-programmatically
I believe the only thing missing is getting the window's frame and then you can either set the width and height of that or use the x and y in the new frame. If anyone knows how to do this or where to point me so I can figure it out, I'm willing to make a PR for it but I don't have all week to figure this out and I assume its rather trivial if you know what you're doing (or maybe not)

I was able to make it work following this stack overflow:
https://stackoverflow.com/questions/35106971/get-objective-c-property-from-pure-c
I will go ahead and make a PR for the change


Reloading Oni via quick command with multiple windows causes oni split mode

When using oni with multiple windows reloading one causes the newly reloaded oni session to blend with the first.
Steps to reproduce hopefully:

Open an Oni window,
Open a second oni window
Select reload Oni in one window via Command palette

Outcome:

Oni attempts to reload the second window inside the first which opens as an oni split (the [WIP] oni split mode) but with duplicated sidebars.
Possible Cause:
The reload oni command in the CommandPalette has a reference to the first oni instance always so requesting a reload acts the same as trying to open a second oni instance which somehow triggers the code for the Oni split mode.

Seems to have been fixed by changes made in #1747


MSX

Just to let you know, it works on the Brazilian MSXs Gradiente Expert and Sharp Hotbit.
Awesome work, thanks for sharing.

Thanks. Are these the correct models?
https://www.msx.org/wiki/Gradiente_Expert_XP-800
https://www.msx.org/wiki/Sharp_HB-8000


Add .st-file-icons

Addons should contain it too.

Ah. Ok.

My appbar addon works even without this file. The addon doesn't provider any icons so why the should be placed here?

I've just found out that zz File Icons can override icons provided by the theme if its addon contains *.sublime-theme files.

Ah, so if any user installare only the appbar addon, without material theme,  he won't see any icons, instead of seeing the icons from zz-File-Icons

No. If user install the appbar addon without material theme - everything is ok. But when user installs material theme & appbar addon he will see only zz File Icons not the theme's ones.

This is because when the user have installed addon & the theme we have two Material *.sublime-theme files.

Yes. But if i have only the addon package no icons Will be displayed if i put .zz-icons-file. Right?

Ah, I understood you. Right icons will be used in this case. Sublime will search icons in addons folder if it found nothing it will take icons from the theme package.

Ok, Right. 👍🏻

https://github.com/equinusocio/material-theme-appbar/commit/726eeaf5d9e0391efb7c8997ded2153d22f82381


added myself

added profile picture and participant information.
@iamdevvalecha

Thank you for contributing! This PR is successfully part of Hacktoberfest! 🎊


feat(boilerplate): upgrade to Expo SDK 51

Please verify the following:

[x] yarn test jest tests pass with new tests, if relevant
[x] yarn lint eslint checks pass with new code, if relevant
[x] yarn format:check prettier checks pass with new code, if relevant
[x] README.md (or relevant documentation) has been updated with your changes

Describe your PR

Upgrades to SDK 51
Removes unnecessary Flipper disabling code since it's removed from Expo template
Updated relevant versions in README.md

Go!

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fixes cats-effects ScalaJS tests

This PR solves the sbt configuration to allow run tests for scalajs cross building (crossDepSettings ).
On the other hand, there was a problem in tests because:
java.lang.UnsupportedOperationException: cannot synchronously await result on JavaScript; use runAsync or unsafeRunAsync
Hence, I also fixed both existing tests with the recommended way to do it.
Feel free to merge it if this makes sense to you.

Codecov Report

Merging #156 into bf-cats-effect will not change coverage.
The diff coverage is n/a.

@@               Coverage Diff               @@
##           bf-cats-effect     #156   +/-   ##
===============================================
  Coverage           86.94%   86.94%
===============================================
  Files                  36       36
  Lines                 567      567
  Branches                2        2
===============================================
  Hits                  493      493
  Misses                 74       74

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 2d086a3...a6d848d. Read the comment docs.

👍


Have anyone successfully implemented it using bluestacks ? Please share your knowledge.. i would like to know how to handle the proxy

i got same problem with virtual machine installed ubuntu and i use nox...i hope some1 gonna help us

Agreed mate... Let's just wait... Where are u stuck ?

i do evrything im in last part (i must set port)
if you want help (to help each other and try to found solutions) send me message at<EMAIL_ADDRESS>with your skype or with your fb

Yes please continue this somewhere else issues are not a support forum, please close this.

I found the solution.. I'll close this


Files with classes that declare itself to be it's parent can cause an infinite loop when indexing.

I noticed this happening often when a project had phan installed as a dependency.
As a minimal example, the server will enter an infinite loop trying to index this file:
<?php
class C extends C {}
$c = new C;
$c->undef_prop = 1;

PR to follow.

I'm curious: The example code throws Fatal Errors with php7.2 and php7.3; I agree that it shouldn't cause infinite loops in a parser/language-server -- why would such code be written alludes me? Would you care/be so kind to elaborate?

There is no reason. But it shouldn’t cause infinite loops

@tomterl In my case, a project I'm working on uses a dev dependency (phan) that includes code that's deliberately written to trigger an error among it's tests.
Furthermore, simply typing an error like this by mistake is plausible, especially given that VSCode and this extension supports live feedback as you type.

@d0x2f you might wanna suggest to Phan to not ship tests in their package

Now that I'm thinking about it, during typing this might easily occur (class C extends CBase...)

:tada: This issue has been resolved in version 5.4.4 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[Bug][export] after importing an export-json which process contained a sub_process from another environment,the link for sub_process in process is wrong

*For better global communication, please give priority to using English description, thx! *
Please review https://dolphinscheduler.apache.org/en-us/docs/development/issue.html when describe an issue.
Describe the bug
after importing an export-json which process contained a sub_process from another environment,the link for sub_process in process is wrong
To Reproduce
Steps to reproduce the behavior:

Go to 'process definition'
Export a process who contained a sub_process and all its sub processes
Login in  another environment
Import the export-json

Expected behavior
Right sub process link in right node typed sub_process
Screenshots
If applicable, add screenshots to help explain your problem.
Which version of Dolphin Scheduler:
-[1.3.2]
Additional context
I think the reason for this is that the identifiers used to link sub process to their master process are different when import the json
Requirement or improvement

Please describe about your requirements or improvement suggestions.

This issue will be closed because no update for a long time. You can check it again in latest version and reopen it if need.


Create 'ParsePKCS8PrivateKeyRSA' and 'ParsePKCS8PrivateKeyECDSA' to return typed versions of parsed keys

@youmark
I recently utilized your awesome library to handle private key encrypted certificates. I thought I'd make the usage a tiny bit easier for the next guy by taking advantage of Go's strong typing system and create versions of ParsePKCS8PrivateKey where the type assertion is handled internally.
Originally, I think the "problem" sits in Golang's standard library where some crypto functions like x509.ParsePKCS8PrivateKey return interface{} instead of a type. So if/when that is fixed the type assertions could go away, and we would just call the corresponding typed x509 functions inside ParsePKCS8PrivateKeyRSA and ParsePKCS8PrivateKeyECDSA.

Two API variations to make both RSA and ECDSA gue easier, way to go.


installing parity as per docs

step to replicate

git clone https://github.com/ethcore/parity
cd parity
cargo install parity

expected behaviour

parity installs

actual behaviour

$ cargo install parity
Updating registry https://github.com/rust-lang/crates.io-index
error: could not find parity in registry https://github.com/rust-lang/crates.io-index

patch https://github.com/ethereumproject/emerald-rs/pull/4/commits/887197522fbd61600e4007db882ccdb96426b531 solves it


Inconsistent sync between devices

I have a user type object im storing like this:
export type UserType = {
	id: string;
	created: Date;
	pauseStreaks?: boolean;
	pauseEndDate?: Date;
	pauseStartDate?: Date;
	pauses: [Date, Date][];
	collapsed?: boolean;
};

When I go through the following workflow, the data doesn't sync between my phone and laptop, instead, the server data ends up being overwritten:

have tab open on both laptop and phone
Close laptop tab
On my phone, I update "collapsed":

const updatedUser = { ...user };
updatedUser.collapsed = true;
await db.user.put(updatedUser, updatedUser.id);

Open the tab on my laptop (where collapsed was last false)

After step 4, collapsed is reverted and set back to false on my phone as well. I would have expected since the server change was more recent, the value would stay to true.
Any idea as to why this might be happening?

Nevermind, resolved. Had a side effect that was making empty modifications


Directive version errors

Motivation
This library uses components, but with components you have to create divs around container and code creates divs around draggable items. It is slow and doubles the dom element amount.
Another big problem is that those divs break flexbox.
So I made a small directive using plain smooth-dnd.
Problems

For some reason if I don't import vue-smooth-dnd the I get his error on drag start: Uncaught TypeError: Failed to execute 'appendChild' on 'Node': parameter 1 is not of type 'Node'.
The other problem is that css display: block (below) breaks flexbox. When I change it to display: flex then I get and error: Uncaught TypeError: Cannot read property 'setDraggables' of undefined.

Prolem css
.smooth-dnd-container.vertical > .smooth-dnd-draggable-wrapper {
	display: flex !important; /* was: display: block; */
}

Usage example

{{item.value}}

Directive code
This version of code is modified and untested.
// vue-smooth-dnd-directive.js

import { smoothDnD } from 'smooth-dnd'
import 'vue-smooth-dnd/dist/vue-smooth-dnd.esm.js' // error if this is not imported

export const vueSmoothDndDraggable = {
	bind: function (el, binding, vnode) {
		el.classList.add('smooth-dnd-draggable-wrapper')
	}
}

export const vueSmoothDndContainer = {
	bind: function (el, binding) {
		if (el.vueSmoothDndInstance) {
			console.error('v-vue-smooth-dnd-container el.vueSmoothDndInstance exists, it should not exist', el)
			el.vueSmoothDndInstance.dispose()
		}
		let options = binding.value || {}
		if (typeof options !== 'object') {
			console.error('v-vue-smooth-dnd-container options is not an object', el, binding.value)
			options = {}
		}
		el.vueSmoothDndInstance = smoothDnD(el, options)
	},
	unbind: function (el) {
		if (el.vueSmoothDndInstance) {
			el.vueSmoothDndInstance.dispose()
		} else {
			console.error('v-vue-smooth-dnd-container destroy, instance does not exist, el:', el)
		}
	}
}

The other problem is that css display: block (below) breaks flexbox. When I change it to display: flex then I get and error: Uncaught TypeError: Cannot read property 'setDraggables' of undefined.

I was able to fix css problems with overriding my own correct styles with display: flex !important;.
This Uncaught TypeError: Cannot read property 'setDraggables' of undefined error was solved by arranging container and draggable directives in right order.

I would like to know how vue-smooth-dnd changes basic smooth-dnd so that it starts to work.


view page isnt getting updated

please help view page isnt getting updated i have added all cards but while in view page there is no any changes in status while m getting data over serial monitor

hmm , then there is a problem with the wifi module sending the data to the server. Please check that

in order to check that, please navigate to phpmyadmin/localhost/nodemculog and see if details are being added to the table there.

No there is not any data in log file of database
On Thu, 2 Apr, 2020, 10:53 PM SaGPaR<EMAIL_ADDRESS>wrote:

in order to check that, please navigate to phpmyadmin/localhost/nodemculog
and see if details are being added to the table there.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/InfinityWorldHI/NodeMCU/issues/3#issuecomment-607982602,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMZA6BETHJ54ZD66WIHICCTRKTC25ANCNFSM4L2DDTCA
.

hmm, that means your nodemcu is not connected properly to the host data base, use a wifi which is given by another laptop, both to your laptop and node mcu

contact me at +91<PHONE_NUMBER> on whatsapp if you need faster replies


[Chongyang Bai] Add coco mAP evaluator and unit tests.

Could you update setup.py to include pycocotools as dependency?

Could you update setup.py to include pycocotools as dependency?

done, thanks

Could you update setup.py to include pycocotools as dependency?

done, thanks


UI redesign: change font & color of timestamp in a message

As part of UI redesign we want to update the style of timestamp of the message:

The font is. used is same that Zulip is using right now in the body: font-family: "Source Sans 3",sans-serif; (no need to redefine the font-family). The main difference is the new color and small caps feature of the font.
font-style: normal;
font-weight: 400;
font-size: 14px;
line-height: 1;
text-align: right;
font-variant: small-caps;
color: hsla(0, 0%, 50%, 1)

for the dark theme color is hsla(0, 0%, 50%, 1)

Update, based on discussion on #21754
To make the UI look cohesive, we should also update the message header bar as follows.
Light theme:  color is hsla(0, 0%, 37%, 1) and
font-size: 15px;
line-height: 18px;
text-align: right;
font-variant: all-small-caps;
font-weight: 400;

and lets also do font-variant: all-small-caps; as @sayamsamal suggested.
For the dark theme the color is background: hsla(0, 0%, 70%, 1);
Edit from @amanagr to fix the dark theme color of message time based on https://github.com/zulip/zulip/pull/21754#issuecomment-1100689525

@zulipbot claim

is this issue solved or i can work on this ?/


Changing User class on make:policy stub

Instead of stubbing out the  (typically) \App\User-model for typehints on the make:policy command, this PR changes this to be using the \Illuminate\Foundation\Auth\User-class.
Not a breaking change as it only applies to new policies being created from the console command.
Reason:
a) the default app's User-model extends from \Illuminate\Foundation\Auth\User anyhow
b) [main reason for the PR] :  when different "authenticatable" models are used (*) methods of the new policy will match the type of the $user parameter.
(*) for example a Staff or an Admin-model used from their resp. Guards

I think most applications will want to keep this the way it is. You are free to change your own policies if you want.


Gradle 7

In gradle 6 this gives a warning, in gradle 7 it gives an error:
A problem was found with the configuration of task ':compileLibSassProduction' (type 'CompileLibSassProductionTask').

Type 'com.github.fgiannesini.libsass.gradle.plugin.tasks.CompileLibSassProductionTask' property 'description' is missing an input or output annotation.
Possible solutions:

Add an input or output annotation.
Mark it as @Internal.

Please refer to https://docs.gradle.org/7.0.2/userguide/validation_problems.html#missing_annotation for more details about this problem.

I tried to update to the last version of gradle. But this plugin is too old. It should be rewritten from scratch to be aligned to last gradle version.


Submit Button Disabled

From Russell:

I also found a very small bug. On the proposal page if you fill out everything then change the ERC20 dropdown, the submit button is disabled.

Was able to replicate this on the Fund Company form but only with USDC
https://bison-narwhal.vercel.app/#/molochv3/0x89/0x473ca6a81a5bbcdf235920f37bbcc24d9d5ff1e3/new-proposal?formLego=FUND_COMPANY

Was not able to replicate on Become Partner
https://bison-narwhal.vercel.app/#/molochv3/0x89/0x473ca6a81a5bbcdf235920f37bbcc24d9d5ff1e3/new-proposal?formLego=BECOME_PARTNER


Aggregation on array types does not apply filter to the aggreation

This is related to #5069, but a clearly bigger bug. When you filter the multivalue col with an aggregation, you still see all the unique values from the multivalue col.
Table:

foo
array_col

3
[1,2]

select count(foo) where array_col = 1 from table group by array_col;

array_col
count_foo

[1]
1

[2]
1

There is a working query for this, but it requires specifying the same filter twice and adding an extra column to your result
select VALUEIN(array_col, 1), count(foo) where array_col = 1 from table group by array_col;

array_col
count_foo

[1]
1

cc @xiangfu0, curious if this is intended or actually a bug

IMO this seems like a bug. b/c the behavior of
SELECT mvCol FROM tbl WHERE mvCol = 1

will return all the mvCol which CONTAINS the value 1.
thus the behavior of exploding the mvCol during group by should happen after the filter.
use Postgres as example, the logic can be express (without filter)
-- direct unnest
SELECT unnest(arr) AS arr_item, SUM(id)
FROM test
GROUP BY 1
-- nested subquery unnest
SELECT arr_item, SUM(id) FROM (
  SELECT unnest(arr) AS arr_item, id FROM test) t
GROUP BY 1

however it really depending on how MV column is being considered here when filter is added:
-- add to the outer query
SELECT arr_item, SUM(id) FROM (
  SELECT unnest(arr) AS arr_item, id FROM test) t
WHERE arr_item = 1
GROUP BY 1

-- add to the inner query
SELECT arr_item, SUM(id) FROM (
  SELECT unnest(arr) AS arr_item, id FROM test WHERE 1=ANY(arr) ) t
GROUP BY 1

i felt like the inner query version is more acceptable in the MV context b/c it is not possible to add the arr_item = 1 filter against the direct unnest version of the query b/c unnest(arr) itself is not allowed to appear in filter.

thus the behavior of exploding the mvCol during group by should happen after the filter.

well that is what is happening. It seems we fetch all the rows with the filtered column, then explode it.
we were discussing internally, and technically if the behavior were to change such that the filter removes the exploded values, then there would be no way to say "group by all MV values where any value equaled X". So maybe this is fine as is?

I wouldn't call this intended, but this behavior is expected, and I know people using it as a feature to get relevant values (think of a column storing all the skills of a person, these skills are usually relevant).
The reason for this behavior is that pinot performs filtering and projection separately, and it simply returns the rows matching the filter. VALUE_IN is added to perform another filter after projection.


Remove ODES solver

Description
Since the ODES solver was causing issues for upgrading to python 3.12 and might not offer anything outside of our other solvers, it might be able to be removed.
Key checklist:

[x] No style issues: $ pre-commit run (or $ nox -s pre-commit) (see CONTRIBUTING.md for how to set this up to run automatically when committing locally, in just two lines of code)
[x] All tests pass: $ python run-tests.py --all (or $ nox -s tests)
[x] The documentation builds: $ python run-tests.py --doctest (or $ nox -s doctests)

You can run integration tests, unit tests, and doctests together at once, using $ python run-tests.py --quick (or $ nox -s quick).
Further checks:

[x] Code is commented, particularly in hard-to-understand areas
[x] Tests added that prove fix is effective or that feature works

I created this PR very early since I want to test on CI. This is in no way ready for review

🎵  Should Old Acquaintance be forgot... 🎵

For the macOS failures, removing some of the recent pybamm-requires caches should work (this comes from time to time whenever CMake puts out a new release, and I always forget about fixing it)

Since tests seem to be passing, I am going to open this up for review
Extra things for reviewers to check:

[ ] Updated documentation
[ ] Make sure there are no tests/scripts outside of CI that I missed
[ ] If there are use-cases for ODEs that I missed, please mention them

Thanks, @kratman! This looks good!
Dockerfile should also be updated to remove the extra odes dependency. Additionally, the CHANGELOG note should ideally be placed under the "Breaking changes" section and should specify why the solver was removed.

Yeah I was making the changelog now. Good catch on the dockerfile

@pybamm-team/maintainers If you have checked any of the things in my checklist, please check them off

Oops, it looks like @Saransh-cpp reviewed at the same time as I did, lol

Do any of our linux/mac dependencies in the instructions/docker get used for only ODES?

I checked the Dockerfile and it has just SUNDIALS_INST as an unneeded environment variable, all of the system-level dependencies in it (and the docs) are required

On another note, we shouldn't need to install two of the macOS system dependencies now with this, just graphviz and libomp should be required. We are fine with using Accelerate as a BLAS vendor and we needed gcc to get gfortran earlier for compiling scikits.odes (it wasn't being used for compiling IDAKLU anyway, we used the system Clang for that). I guess these changes would probably be better in a separate PR.

On another note, we shouldn't need to install two of the macOS system dependencies now with this, just graphviz and libomp should be required. We are fine with using Accelerate as a BLAS vendor and we needed gcc to get gfortran earlier for compiling scikits.odes (it wasn't being used for compiling IDAKLU anyway, we used the system Clang for that). I guess these changes would probably be better in a separate PR.

Can you add this to #3941 and I will look at it there

Coverage will be fixed in #3942


garbage_collect_files works only on second try

Describe the bug
the snippet code I use is here
garbage_collect_files does not work the first time I use it, only the second time.
First time means first call of garbage_collect_files in one thread, second means second call of garbage_collect_files in another thread
Which version of tantivy are you using?
0.9.1
To Reproduce
repo where is all the code I used, look at drop_index() function in src/bin/server.rs
I use POST request to trigger garbage_collect_files like this:
POST http://localhost:8080/drop
When I post at first time all documents are deleted but ./index directory does not become empty, actually it has 36Mb data in it. Original size of index directory was 129Mb
When I post at second time directory size drops to 8,0K. Nothing else but second call to garbage_collect_files happens.
I don't know, maybe it is an expected behavior, but is weird.

There can be multiple reasons why files do not get deleted on your first call :
a merging thread was still running, merging two obsolete segment. It's job would then get discarded when it finished.
If you are on Windows, it can also happen that you had a reader open and it prevented tantivy from removing the files.
This is not a bug as is... But I have an extra question.
If you did not call drop the second time but just waited 1mn. Are your files deleted automatically ?
If not I think this is ok to consider this a bug.

(also sorry for the late answer.)

I am on Mac OS. Same problem on Ubuntu.
I have waited for 5 minutes after first drop, no thread running - index directory is still 32Mb. Again, after second drop index becomes 8Kb

Does someone have bandwidth to create a branch and create a unit test to reproduce?
"do a (.add_document()s, .commit()s) sequence that triggers it", index.wait_merge_threads, and check for the number of documents in the directory.
Do a gc, and see if this number decrease. (if so this is a bug. GC should not be required.)

I think I found the problem. The fix is on the way.
@kkonevets
Could you confirm that the problem is fixed when you depend on master once the branch is merged,
and comment on this ticket and possibly reopen it if you can still reproduce.

Nope, it does not work. Actually it became worse. Now index size increased after first call. Later it was 36Mb now it is 87Mb. Initial size was 140Mb.
I did not change my code and data.

If you wish I can give you the data and you can try on your own.

im interested yes

To reproduce:

download the database https://yadi.sk/d/-k357Cgo-vFQlw
Install https://dev.mysql.com/downloads/workbench/  (I am on Mac OS)
create new schema and name it ssergeev

Server->Data Import and Import from self-Contained file, choose the file I gave you with extension .sql
In cargo.toml set dependency on master as you said:
tantivy = { git = "https://github.com/tantivy-search/tantivy" }
create index cargo run --release --bin commit
start the server cargo run --release --bin server
I use this extension for VS Code to test REST API
Then open test.http file in the root directory and press send request button:

This will call garbage_collect_files once.

These are very thorough instructions... but I unfortunately don't have time to install Microsoft SQL Server :-S

The problem looks fixed on my computer.
I'm sorry to ask something like that but can you double check?

Fix the revision of tantivy to something specific (e.g.: c23a7c992bcf0f9b052995941fdfe1f3e87e3d53)
Index your files without calling your manual garbage collect. Ideally, run your program with the  RUST_LOG=info command and send me the logs.
Commit.
Wait for 5 minutes. (it is normal for files to appear and disappear after a commit. Tantivy merges segment together. This should appear in the logs.)
Send me the list of files in your directory.
Send me the meta.json at this point.
Trigger your garbage_collect
Confirm that some file got deleted.

What do you mean by commit? In my terminology commit is actually indexing.
 For example index/d04d0c8b05e34584bb6ee7551f0eb624.idx is 11Mb.

"List of files after my garbage_collect"

Do you really mean after calling your drop function ? or is it really just garbage collect ?
Calling garbage collect cannot do what you are decribing. Something else is happening that modified your meta.json file too.

OK, I got it!
I have waited for 5 minutes after commit and then deleted files and then called garbage_collect_files(). And yes, the index directory became empty.
How can I wait for workers to finish merging segments without specifying 5 minutes manually? Is there something like await possibility?

For the first set of files and... The discrepancy between meta.json and the list of segments is of 3 segment files. I'm going to bluntly assume that these are the result of segment merging, you just had to wait.

The issue is that you should not have to call garbage_collect_files() manually. My question is what happens if you do not call it.

IndexWriter has a wait_merging_threads method, but it consumes your index_writer instance.

My question is what happens if you do not call it.

If I wait for 5 minutes and do not call garbage_collect_files() manually it works correct.
But if I do not wait for 5 mins and do not call garbage_collect_files() manually index does not become empty.
So I guess I should call wait_merging_threads manually, I will try now

Ok, closing issue then.
The technique you used for clearing the index should be obsolete thanks to @petr-tik work. If you can work on master, you can try it. It should make your app much simpler and faster.

Wait a minute, I used my own technique, what you mean by technique?

Yes. On the same ticket you linked, there is a link to a  PR from @petr-tik,
He added a .delete_all_documents() on the index writer. It should be much more efficient.
It is in master, and will be in 0.10 once released.

Question regarded to wait_merging_threads():
what am I supposed to do when I can't consume IndexWriter, like when using Mutex?


how to run livebook behind a TLS terminating reverse proxy

Environment

Elixir & Erlang/OTP versions: OTP 26.2.1, Elixir 1.15.7
Operating system: FreeBSD
How have you started Livebook: escript style, livebook server ...
Livebook version (use git rev-parse HEAD if running with mix): 0.21.1
Browsers that reproduce this bug (the more the merrier): Firefox
Include what is logged in the browser console:

Failed to connect runtime - Elixir terminated unexpectedly, please check your logs for errors

Include what is logged to the server console: nothing

Current behavior

livebook launches successfully, creates a new livebook, and can add/edit cells
on running evaluate no output is produced, and error appears after a few seconds

Expected behavior
It used to be possible to run livebook behind a common reverse proxy with a single
port/hostname, such as https://live.example.org/ but now it appears an additional
URL is required. I was unable to find a working combination for this.
What Failed
I tried a few variations, all basically around tweaking the iframe settings:
$ env LIVEBOOK_DEBUG=true \
      LIVEBOOK_PASSWORD=... \
      LIVEBOOK_PORT=4000 \
      LIVEBOOK_IFRAME_PORT=4001 \
      LIVEBOOK_IFRAME_URL=https://live.example.org/iframe/ \
    livebook server --name pair

Proxy configured as:

https://live.example.org/ -> http://localhost:4000/
https://live.example.org/iframe/ -> http://localhost:4001/

I also tried LIVEBOOK_IFRAME_URL=https://livebookusercontent.com/ per the iframe/README.md doc
I'm ofc happy to PR docs fix once I understand what I'm doing wrong :rainbow: :umbrella: :mango:

From your description, the issue is not related to iframes at all, but to the Erlang Distribution. For some reason we can't talk or communicate to the Erlang instance we spawn to be used for the runtime. Try starting the server using --sname pair instead. If using --name, make sure the host you give can be reached by the current machine.

using --name<EMAIL_ADDRESS>fixed it, thanks @josevalim :mango: :passenger_ship: :sun_behind_rain_cloud:


Moved templates out of PR #3464

Problem
PR #3464 is huge. Break down into multiples small PR to facilitate review.
Summary of Changes
Add Zap Templates in the CHIP repo
Partial Fix of  #1733

@woody-apple Restyled seems to fail because of the Javascript file included in this PR (third_party/repo/templates/helper-chip.js). Do you know what is the proper way to fix it ?

Looks pretty good. A few minor comments/nits mostly related to style consistency.
My biggest concerns would be that I would really prefer those templates to live inside examples. It would make it extra clear that they are used to generate the examples and are basically glued to them.

My point of view is that templates are an extension of ZAP. By themselves, they're useless. Moving them elsewhere would give the impression that they can be "standalone".  And yes, as for now only the examples use them, but when people will start using CHIP for their own project, having the templates hidden under /examples won't make that much sense anymore.

Looks pretty good. A few minor comments/nits mostly related to style consistency.
My biggest concerns would be that I would really prefer those templates to live inside examples. It would make it extra clear that they are used to generate the examples and are basically glued to them.

My point of view is that templates are an extension of ZAP. By themselves, they're useless. Moving them elsewhere would give the impression that they can be "standalone". And yes, as for now only the examples use them, but when people will start using CHIP for their own project, having the templates hidden under /examples won't make that much sense anymore.

I think these belong under src/app, as they are part of CHIP, they're effectively libraries/source files for CHIP's interaction with ZAP.

please move to src/app/zapt/xxx.zapt ?
@rwalker-apple

Only the templates files or everything that is under third_party/zap/templates/ ?

Looks pretty good. A few minor comments/nits mostly related to style consistency.
My biggest concerns would be that I would really prefer those templates to live inside examples. It would make it extra clear that they are used to generate the examples and are basically glued to them.

My point of view is that templates are an extension of ZAP. By themselves, they're useless. Moving them elsewhere would give the impression that they can be "standalone". And yes, as for now only the examples use them, but when people will start using CHIP for their own project, having the templates hidden under /examples won't make that much sense anymore.

I think these belong under src/app, as they are part of CHIP, they're effectively libraries/source files for CHIP's interaction with ZAP.

+1
These files

Looks pretty good. A few minor comments/nits mostly related to style consistency.
My biggest concerns would be that I would really prefer those templates to live inside examples. It would make it extra clear that they are used to generate the examples and are basically glued to them.

My point of view is that templates are an extension of ZAP. By themselves, they're useless. Moving them elsewhere would give the impression that they can be "standalone". And yes, as for now only the examples use them, but when people will start using CHIP for their own project, having the templates hidden under /examples won't make that much sense anymore.

I think these belong under src/app, as they are part of CHIP, they're effectively libraries/source files for CHIP's interaction with ZAP.

I agree with moving them.
IMO, the things that belongs in third_party/X are

additions that could be upstream (like adding a build file for a different build system)
dependency readme and other administrivia (scripts to update it, etc)

For projects that add tools supporting a domain specific language such as ZAP, the sources in that language don't go in third_party. They are go in the regular directory structure of CHIP.

@woody-apple Restyled seems to fail because of the Javascript file included in this PR (third_party/repo/templates/helper-chip.js). Do you know what is the proper way to fix it ?

I opened #3708 for that. The issue being that clang-format is trying to parse helper-chip.js but .clang-format does not contain any rules about JS files...

didn't want to use the name src/app/zapt?

If the folder was named zapt one could expect to only find *.zapt file inside. Also @vivien-apple requested the zap-templates.

didn't want to use the name src/app/zapt?

If the folder was named zapt one could expect to only find *.zapt file inside. Also @vivien-apple requested the zap-templates.

This is exactly why I asked for zap-templates instead of zapt.

@mspang @andy31415 so we can merge this PR.


Fix issue 11796

Fix Issue 11796: Add missing pragma weak declaration to lhash.h for solaris builds
pragma weak OPENSSL_LH_flush

Note: signed CLA has been sent via email.

Reopen with CLA in place.

Try again...

Thanks.  I amended the commit and changed the commit message as suggested and force-pushed. This is new ground for me and am not sure I did it correctly.

We do not allow merge commits. So please just drop the last commit (git reset --hard HEAD~), it is not needed. Also if you can please amend the commit message of the actual commit once more - instead of the Fix issue 11796 the last line should say Fixes #11796 for the automatic close to work.

Thanks. I amended the commit and changed the commit message as suggested and force-pushed. This is new ground for me and am not sure I did it correctly.

Don't worry, you're doing fine. We all started as beginners. Please follow the instructions of @t8m to drop the merge-commit and amend the commit message once more. (The result needs to force-pushed, as before.) Again, if you need any assistance don't hesitate to ask.  And if at some point our git-gymnastic-assignments become too tedious  for you, just let us know. We can fix the commit also when we merge it.

Thanks. I amended the commit and changed the commit message as suggested and force-pushed. This is new ground for me and am not sure I did it correctly.

Don't worry, you're doing fine. We all started as beginners. Please follow @t8m's instructions to drop the merge-commit and amend the commit message once more. (The result needs to force-pushed, as before.) Again, if you need any assistance don't hesitate to ask. And if at some point our git-gymnastic-assignments become too tedious for you, just let us know. We can fix the commit also when we merge it.

Ok, done. Third time's a charm.  I tried to follow the instructions precisely. Hope I got it right this time.

The commit looks good now.
The only thing which you might want to check is the fact that GitHub doesn't seem to know your email address, it shows a grey Octocat avatar next to your commit:

The email address provided in your patch coincides with the one on your profile, but it does not seem to be configured in your email settings. You might want to check your settings.

Thanks.  Looks like my work email was not in my profile. I've fixed that.

24 hours has passed since 'approval: done' was set, but this PR has failing CI tests.  Once the tests pass it will get moved to 'approval: ready to merge' automatically, alternatively please review and set the label manually.

Merged to master. Thank you for your contribution.


[BugFix] Fix column overflow in RowsetUpdateState and CompactionState

Fixes #33247
When the compaction output file is too large and contains many rows, the resulting buffer containing all encoded pk in this segment file may be huge and overflow. This PR fixes this by changing BinaryColumn<uint32> to BinaryColumn<int64>, adding some checks for overflow, and refactoring some compaction memory logs.
What type of PR is this:

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.2
[x] 3.1
[x] 3.0
[x] 2.5

[FE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[BE Incremental Coverage Report]
:disappointed: fail : 8 / 18 (44.44%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/storage/rowset_update_state.cpp
0
1
00.00%
[208]

:large_blue_circle:
src/storage/update_compaction_state.cpp
2
6
33.33%
[130, 131, 132, 138]

:large_blue_circle:
src/storage/primary_key_encoder.cpp
3
8
37.50%
[336, 337, 338, 339, 340]

:large_blue_circle:
src/column/binary_column.cpp
3
3
100.00%
[]

[FE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[BE Incremental Coverage Report]
:disappointed: fail : 9 / 19 (47.37%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/storage/rowset_update_state.cpp
0
1
00.00%
[208]

:large_blue_circle:
src/storage/update_compaction_state.cpp
2
6
33.33%
[130, 131, 132, 138]

:large_blue_circle:
src/storage/primary_key_encoder.cpp
4
9
44.44%
[336, 337, 338, 339, 340]

:large_blue_circle:
src/column/binary_column.cpp
3
3
100.00%
[]

[FE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[BE Incremental Coverage Report]
:disappointed: fail : 91 / 154 (59.09%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/storage/update_compaction_state.cpp
1
7
14.29%
[130, 131, 132, 138, 139, 140]

:large_blue_circle:
src/storage/primary_key_encoder.cpp
86
143
60.14%
[336, 337, 339, 516, 517, 518, 519, 520, 521, 522, 525, 528, 529, 530, 531, 532, 534, 535, 538, 571, 572, 573, 574, 575, 576, 577, 578, 580, 653, 654, 655, 656, 657, 671, 672, 673, 674, 675, 677, 678, 679, 680, 681, 689, 690, 691, 692, 693, 695, 696, 697, 698, 699, 701, 702, 719, 720]

:large_blue_circle:
src/storage/lake/update_compaction_state.cpp
1
1
100.00%
[]

:large_blue_circle:
src/column/binary_column.cpp
1
1
100.00%
[]

:large_blue_circle:
src/storage/lake/rowset_update_state.cpp
1
1
100.00%
[]

:large_blue_circle:
src/storage/rowset_update_state.cpp
1
1
100.00%
[]

[FE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[BE Incremental Coverage Report]
:disappointed: fail : 91 / 154 (59.09%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/storage/update_compaction_state.cpp
1
7
14.29%
[130, 131, 132, 138, 139, 140]

:large_blue_circle:
src/storage/primary_key_encoder.cpp
86
143
60.14%
[336, 337, 339, 516, 517, 518, 519, 520, 521, 522, 525, 528, 529, 530, 531, 532, 534, 535, 538, 571, 572, 573, 574, 575, 576, 577, 578, 580, 653, 654, 655, 656, 657, 671, 672, 673, 674, 675, 677, 678, 679, 680, 681, 689, 690, 691, 692, 693, 695, 696, 697, 698, 699, 701, 702, 719, 720]

:large_blue_circle:
src/storage/lake/update_compaction_state.cpp
1
1
100.00%
[]

:large_blue_circle:
src/column/binary_column.cpp
1
1
100.00%
[]

:large_blue_circle:
src/storage/lake/rowset_update_state.cpp
1
1
100.00%
[]

:large_blue_circle:
src/storage/rowset_update_state.cpp
1
1
100.00%
[]

[FE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[BE Incremental Coverage Report]
:disappointed: fail : 91 / 154 (59.09%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/storage/update_compaction_state.cpp
1
7
14.29%
[130, 131, 132, 138, 139, 140]

:large_blue_circle:
src/storage/primary_key_encoder.cpp
86
143
60.14%
[336, 337, 339, 516, 517, 518, 519, 520, 521, 522, 525, 528, 529, 530, 531, 532, 534, 535, 538, 571, 572, 573, 574, 575, 576, 577, 578, 580, 653, 654, 655, 656, 657, 671, 672, 673, 674, 675, 677, 678, 679, 680, 681, 689, 690, 691, 692, 693, 695, 696, 697, 698, 699, 701, 702, 719, 720]

:large_blue_circle:
src/storage/lake/update_compaction_state.cpp
1
1
100.00%
[]

:large_blue_circle:
src/column/binary_column.cpp
1
1
100.00%
[]

:large_blue_circle:
src/storage/lake/rowset_update_state.cpp
1
1
100.00%
[]

:large_blue_circle:
src/storage/rowset_update_state.cpp
1
1
100.00%
[]

[FE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[BE Incremental Coverage Report]
:disappointed: fail : 109 / 172 (63.37%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/storage/update_compaction_state.cpp
1
7
14.29%
[130, 131, 132, 138, 139, 140]

:large_blue_circle:
src/storage/primary_key_encoder.cpp
86
143
60.14%
[336, 337, 339, 516, 517, 518, 519, 520, 521, 522, 525, 528, 529, 530, 531, 532, 534, 535, 538, 571, 572, 573, 574, 575, 576, 577, 578, 580, 653, 654, 655, 656, 657, 671, 672, 673, 674, 675, 677, 678, 679, 680, 681, 689, 690, 691, 692, 693, 695, 696, 697, 698, 699, 701, 702, 719, 720]

:large_blue_circle:
src/storage/lake/update_compaction_state.cpp
1
1
100.00%
[]

:large_blue_circle:
src/column/binary_column.cpp
1
1
100.00%
[]

:large_blue_circle:
src/storage/tablet_updates.cpp
13
13
100.00%
[]

:large_blue_circle:
src/storage/lake/rowset_update_state.cpp
1
1
100.00%
[]

:large_blue_circle:
src/storage/rowset_update_state.cpp
1
1
100.00%
[]

:large_blue_circle:
src/storage/persistent_index.cpp
5
5
100.00%
[]

[FE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[BE Incremental Coverage Report]
:disappointed: fail : 109 / 172 (63.37%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/storage/update_compaction_state.cpp
1
7
14.29%
[130, 131, 132, 138, 139, 140]

:large_blue_circle:
src/storage/primary_key_encoder.cpp
86
143
60.14%
[336, 337, 339, 516, 517, 518, 519, 520, 521, 522, 525, 528, 529, 530, 531, 532, 534, 535, 538, 571, 572, 573, 574, 575, 576, 577, 578, 580, 653, 654, 655, 656, 657, 671, 672, 673, 674, 675, 677, 678, 679, 680, 681, 689, 690, 691, 692, 693, 695, 696, 697, 698, 699, 701, 702, 719, 720]

:large_blue_circle:
src/storage/lake/update_compaction_state.cpp
1
1
100.00%
[]

:large_blue_circle:
src/column/binary_column.cpp
1
1
100.00%
[]

:large_blue_circle:
src/storage/tablet_updates.cpp
13
13
100.00%
[]

:large_blue_circle:
src/storage/lake/rowset_update_state.cpp
1
1
100.00%
[]

:large_blue_circle:
src/storage/rowset_update_state.cpp
1
1
100.00%
[]

:large_blue_circle:
src/storage/persistent_index.cpp
5
5
100.00%
[]

[FE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[BE Incremental Coverage Report]
:disappointed: fail : 98 / 166 (59.04%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
be/src/storage/update_compaction_state.cpp
1
7
14.29%
[130, 131, 132, 138, 139, 140]

:large_blue_circle:
be/src/storage/primary_key_encoder.cpp
89
151
58.94%
[516, 517, 518, 519, 520, 521, 522, 525, 528, 529, 530, 531, 532, 534, 535, 538, 571, 572, 573, 574, 575, 576, 577, 578, 580, 652, 653, 654, 655, 656, 657, 658, 664, 670, 671, 672, 673, 674, 675, 676, 677, 678, 679, 680, 681, 682, 689, 690, 691, 692, 693, 694, 695, 696, 697, 698, 699, 700, 701, 702, 719, 720]

:large_blue_circle:
be/src/storage/persistent_index.cpp
2
2
100.00%
[]

:large_blue_circle:
be/src/storage/lake/rowset_update_state.cpp
1
1
100.00%
[]

:large_blue_circle:
be/src/storage/lake/update_compaction_state.cpp
1
1
100.00%
[]

:large_blue_circle:
be/src/storage/primary_index.cpp
2
2
100.00%
[]

:large_blue_circle:
be/src/column/binary_column.cpp
1
1
100.00%
[]

:large_blue_circle:
be/src/storage/rowset_update_state.cpp
1
1
100.00%
[]

https://github.com/Mergifyio backport branch-3.1-cs


optimize: Add an exported Test() function to functions subpackage

I don't really recall what I meant with this back then, what I wanted to test. I transferred it in case @btracey  remembers but otherwise we can close this.


Format80 and Format40 are now LCW and XORDelta

I've been out of the C&C modding/reverse-engineering community for so long that I missed these updates: what we've been calling "format80" for so long had the name "LCW" internally at Westwood: http://www.shikadi.net/moddingwiki/Westwood_LCW
And "format40" -> "XORDelta": http://www.shikadi.net/moddingwiki/Westwood_XOR_Delta
😁

And the thing I've been calling "Format2" is probably Westwood RLE-Zero: http://www.shikadi.net/moddingwiki/Westwood_RLE-Zero


Use rustup for Rust installation

Rustup is the preferred method for installing and managing Rust
toolchains. This commit modifies the buildpack to use rustup to install
the desired version of Rust using a handful of new environment
variables.
This commit additionally cleans up some extraneous code, comments, etc.
This resolves #2 and #1

I am facing the below issue:
2016-06-26T10:16:07.31+0530 [API/2]      OUT Created app with guid e49409cd-f00f-41ee-91a6-1ca4e79fdaec
2016-06-26T10:16:13.07+0530 [API/0]      OUT Updated app with guid e49409cd-f00f-41ee-91a6-1ca4e79fdaec ({"route"=>"199f07af-88b9-4b9e-bdc4-b9887a72e378"})
2016-06-26T10:16:35.73+0530 [DEA/66]     OUT Got staging request for app with id e49409cd-f00f-41ee-91a6-1ca4e79fdaec
2016-06-26T10:16:37.53+0530 [API/1]      OUT Updated app with guid e49409cd-f00f-41ee-91a6-1ca4e79fdaec ({"state"=>"STARTED"})
2016-06-26T10:16:38.18+0530 [STG/66]     OUT -----> Downloaded app package (26M)
2016-06-26T10:16:38.34+0530 [STG/0]      ERR Cloning into '/tmp/buildpacks/cloudfoundry-buildpack-rust'...
2016-06-26T10:16:40.79+0530 [STG/0]      OUT info: downloading installer
2016-06-26T10:17:19.01+0530 [STG/0]      ERR info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'
2016-06-26T10:17:19.99+0530 [STG/0]      ERR info: downloading component 'rustc'
2016-06-26T10:20:20.89+0530 [STG/0]      ERR info: downloading component 'rust-std'
2016-06-26T10:24:39.86+0530 [STG/0]      ERR info: downloading component 'rust-docs'
2016-06-26T10:25:10.90+0530 [STG/0]      ERR info: downloading component 'cargo'
2016-06-26T10:25:36.43+0530 [STG/0]      ERR info: installing component 'rustc'
2016-06-26T10:25:37.64+0530 [STG/0]      ERR info: installing component 'rust-std'
2016-06-26T10:25:39.30+0530 [STG/0]      ERR info: installing component 'rust-docs'
2016-06-26T10:25:43.04+0530 [STG/0]      ERR info: installing component 'cargo'
2016-06-26T10:25:43.21+0530 [STG/0]      ERR info: default toolchain set to 'stable'
2016-06-26T10:25:43.24+0530 [STG/0]      OUT   stable installed - rustc 1.9.0 (e4e8b6668 2016-05-18)
2016-06-26T10:25:43.37+0530 [STG/0]      ERR error: Invalid arguments.
2016-06-26T10:25:43.37+0530 [STG/0]      ERR Usage:
2016-06-26T10:25:43.37+0530 [STG/0]      ERR     cargo build [options]
2016-06-26T10:25:43.38+0530 [STG/0]      OUT Staging failed: Buildpack compilation step failed
2016-06-26T10:25:43.51+0530 [API/1]      ERR encountered error: App staging failed in the buildpack compile phase

It looks like Rust is installing fine, but cargo is failing for some reason...
What do you have CARGO_BUILD_FLAGS set to, if anything?

The following is my manifest.yml file
---
applications:
- name: catacomb
  instances: 1
  memory: 512MB
  env:
    CARGO_BUILD_FLAGS: build -j 4 --release
    START_COMMAND: ./target/release/catacomb

Ah, that's the problem.
This change also changed the CARGO_BUILD_FLAGS variable to be just the flags to cargo build.
Try changing CARGO_BUILD_FLAGS to just CARGO_BUILD_FLAGS: -j 4 --release

Sorry about that, I should have been more clear in my commit message or in the README

## It Worked!!!
Not your fault, I see that you have changed even the documentation accordingly, I should have paid attention to it.
You are thorough in your work.

Thanks! If this is looking OK to you I'm going to merge this into master.

Yes this is good. Thanks once again.
PS: I have dropped you an email


SlideShow should be lazy

Spawning a slide show should be lazy. In particular, the dropdown should be lazy.

What about implementing the grid layout using the infinite list? Alex mentioned that it is possible for grid using existing code. It will require coding for the flow layout.

Hi Juraj,
Thanks for the suggestion.  The slides were originally being rendered lazily, but the preview (dropdown) caused everything to be rendered in advance.
I've got the slides rendering in TaskIt.  The previews were being rendered in the UI process one at a time, but after speaking with Alex is should be easy to also render the previews in the task.  The only issue left is that for some reason the preview isn't displaying - probably a constraints problem (again).
Thanks again,
Alistair

The tour works nicely.
However, now GtTextAndElementSlide has an issue:
show := GtSlideShow new.
show addSlide: (GtTextAndElementSlide new
        text: 'Number Examples';
        element: (GtInspector createOn: 42)).
show


Update ResourceCommand.php

Add the force case insensitive to make the search case insensitive for searching in json fields, for example translation fields.
Copied the code from the Filament Resource and added the current resource to the function.

Sorry, closing this as the PR is a bit old and I don't fully understand all the changes. Happy to reopen if you are still interested.

Hello
If you have a field that you store in the database as json and you try to search on this when resource 'isGlobalSearchForcedCaseInsensitive' is set to true then the record will not be displayed when you go to search CaseInsensitive.
{"de": "GROEP DE", "en": "GROEP EN", "fr": "GROEP FR", "nl": "Groep NL"}

This is what you get when using the code in my pull request:

And this is what you get when using your code:

I hope it is more clear now :)

I had to create a new PR since I couldn't push changes to your branch. #50


test_HDFStore uses hardcoded absolute filename which breaks parallel test sessions

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): any Linux
Modin version (modin.__version__): current master (25928495ed5bf69ae54067952e41a05306fc596b)
Python version: any
Code we can use to reproduce: create a read-only file /tmp/test_read_hdf.hdf5 and run test_io.py::test_HDFStore

Describe the problem

Pandas up to (including) 1.1.5 use some "funny" logic when opening a HDFStore - if opening in write mode fails it silently (well, it prints to stdout which itself is a strange decision for a library) opens the store in read-only mode.
So if the file exists and, for example, was created by another user, all other test sessions on that box would fail.
This was fixed in Pandas via https://github.com/pandas-dev/pandas/pull/36859, but that isn't released yet.
Source code / logs

Current proposal: do not use hardcoded absolute path for the store.
cc @YarShev

Update: it should be enough to just run test session from one user to permanently (until that file is remove) break testing HDF for all others.


refactor: :recycle: Updated naming to use metadata/create/ instead of file-upload

Description

This PR refactors the code, paths, and names to follow the metadata/create/ style rather than file-upload.
I made these changes because as I was digging into #171, I was getting anxious and stressed because there are already files and functions called file-upload, but that don't actually upload the data and rather are used for extracting the metadata. It is part of the reason I started the issues #196 and #224. I get very confused when trying to reuse existing functions (that I think are to upload file), but do a lot of secondary things too (like creating and storing metadata).
So this PR starts changing the names to match what they actually are doing internally, and so I can create HTML templates for the data upload part.
I think we'll also need to split out some of the functionality of the renamed metadata_create function to focus only on extracting the metadata from the file, and have another function that uploads and saves the file (which I will need for #171). But I'll do another PR for that.
Related Issues
Related to #196 and #224
Testing

[x] Yes
[ ] No, not needed (give a reason below)
[ ] No, I need help writing them

Reviewer Focus

This PR only needs a quick review.

Checklist

For all PRs that are not general documentation

[x] Tests accompany or reflect changes to the code
[x] Tests ran and passed locally
[x] Ran the linter and formatter
[x] Build has passed locally
[x] Relevant documentation has been updated

I understand the confusion, and maybe it originates from more than just the name.

The metadata for the table is created in a dialog on the previous page and then the metadata for the columns/properties are created on this page based on the uploaded file. Maybe we should move the input fields with table name and table description to this page.
And yes the file-dropzone.html part is confusing. It calls the url where it is included

We should quickly let you merge it in, so you can relax a bit again

@philter87 no, no, thankfully no ripple effect. Just that explicit structure and organization are things I really need to work effectively and to dive deeper into problems, hence why I emphasize it so much. I know people might not always use words like "anxious" and "stressed" in regular (work) settings, but there isn't anything wrong with it ☺ feelings like those are guides to tell us something isn't right or that needs improving. In this case, when I am feeling anxious or stressed when looking through code/data, it tells me these are areas to improve on, that's all ☺


crashing on meteor add

On windows, trying to add the package crashes with the following error.
Works as expected on linux.
Tested on a working Meteor <IP_ADDRESS> app we are working on and on a brand new Meteor 1.6.1 app :
meteor add mhagmajer:server-router
C:\Users\xxx\AppData\Local\.meteor\packages\meteor-tool\1.6.1\mt-os.windows.x86_64\dev_bundle\lib\node_modules\meteor-promise\promise_server.js:218
      throw error;
      ^

Error: ENOENT: no such file or directory, open 'C:\Users\xxx\AppData\Local\Temp\mt-1l8591f.zq4xl\os\definitions\flow_v0.46.x\mhagmajer:server-router_v1.x.x.js'
    at Object.fs.openSync (fs.js:646:18)
    at Object.wrapper [as open] (C:\tools\fs\files.js:1564:35)
...

Hi @marcpmichel, thanks for reporting the issue!
I was able to confirm that package installs okay on Meteor 1.6.1 and Mac OS. This makes me think that this issue might be better addressed by the Meteor community itself at https://github.com/meteor/meteor/issues. Would you mind posting your issue there? That might be related some incorrect handling of file names on Windows by Meteor package manager.

Done.
Thanks for the quick reply !


Problem with dependencies

I get the error object stratio is not a member of package com
I don't understand what is wrong.
Here is my build.sbt
name := "spark-demo"
version := "0.0.1"
scalaVersion := "2.11.7"

libraryDependencies ++= Seq(
  "org.apache.spark" %% "spark-core" % "1.6.0",
  "org.apache.spark" % "spark-streaming_2.11" % "1.6.0"
  "com.stratio.receiver" % "spark-rabbitmq" % "0.2.0",
)

Here is my app
package app

import org.apache.spark.SparkContext
import org.apache.spark.SparkConf
import org.apache.spark.streaming._
import org.apache.spark.storage.StorageLevel
import org.apache.spark.streaming.{Seconds, StreamingContext}
import com.stratio.receiver.RabbitMQUtils

object Main {
  def main(args: Array[String]): Unit = {

    val sparkConf = new SparkConf().setAppName("WordCount")
    val ssc = new StreamingContext(sparkConf, Seconds(5))
    ssc.checkpoint(".")

    val initialRDD = ssc.sparkContext.parallelize(List(("hello", 1), ("world",2)))

    val rabbitParams = Map(
      "host" -> "localhost",
      "queueName" -> "some-queue",
      "exchangeName" -> "amqp.topic",
      "exchangeType" -> "topic",
      "routingKeys" -> "some-topic",
      "username" -> "guest",
      "password" -> "guest"
    )

    val lines = RabbitMQUtils.createStream(ssc, rabbitParams)
    val words = lines.flatMap(_.split(" "))
    val wordDstream = words.map(x => (x, 1))

    val mappingFunc = (word: String, one: Option[Int], state: State[Int]) => {
      val sum = one.getOrElse(0) + state.getOption.getOrElse(0)
      state.update(sum)
      (word, sum)
    }

    val stateDstream = wordDstream.mapWithState(
      StateSpec.function(mappingFunc).initialState(initialRDD))

    stateDstream.print()
    ssc.start()
    ssc.awaitTermination()
  }
}

Hi,
The artifact id is either spark-rabbitmq_1.4 or spark-rabbitmq_1.5
Regards

Hi, what about spark 1.6? Should a new dedicated pom.xml file be made for it or can we use the spark-rabbitmq_1.5 artifact?

Exactly. Insisde another folder

Hi,
This issue is solved, I close it.
Thanks for all.
Regards Jose Carlos.

I'm facing the similar issue.
Versions:- Spark: 1.6.0 | Scala: 2.10.5
spark-shell --packages com.stratio.receiver:spark-rabbitmq_1.6:0.3.0
Action:
scala> import com.stratio.receiver.RabbitMQUtils <console>:25: error: object stratio is not a member of package com          import com.stratio.receiver.RabbitMQUtils                     ^ scala>

I'm also facing a similar issue on Zeppelin 0.6.0 with Spark 1.6.1.

@oscarcastaneda : Check this: https://github.com/Stratio/Spark-RabbitMQ/issues/62