how to build and get  a new demo address？

how to build and get a new demo address？

how to build and get a new demo address？

To build the react demo you just need to run npm i && npm run build from within the examples/react folder.
If you don't want to mess with building the library remember to change "vosk-browser": "../../lib" to "vosk-browser": "0.0.5" in examples/react/package.json (before running the npm commands)

Let me know if you have any other issues.

when  I run “npm run build”， I get the error  ```
sh: react-scripts: command not found
npm ERR<EMAIL_ADDRESS>build: react-scripts build

Did you run npm install before that?

i only  run “npm install vosk-browser”

I  run “npm i“ ,get follows error:
npm WARN tar ENOENT: no such file or directory, open '/home//vosk-browser/examples/react/node_modules/.staging/webpack-dev-server-912e0be5/client/clients/SockJSClient.js' npm WARN tar ENOENT: no such file or directory, open '/home//vosk-browser/examples/react/node_modules/.staging/webpack-dev-server-912e0be5/lib/servers/SockJSServer.js' npm WARN tar ENOENT: no such file or directory, open '/home//vosk-browser/examples/react/node_modules/.staging/webpack-dev-server-912e0be5/bin/webpack-dev-server.js' npm WARN tar ENOENT: no such file or directory, open '/home//vosk-browser/examples/react/node_modules/.staging/webpack-dev-server-912e0be5/client/clients/WebsocketClient.js' npm WARN tar ENOENT: no such file or directory, open '/home//vosk-browser/examples/react/node_modules/.staging/webpack-dev-server-912e0be5/lib/servers/WebsocketServer.js' npm ERR! Unexpected end of JSON input while parsing near ''

This looks like an issue with your setup. Try installing in another location that is not your home folder (you can see in the error log your user name does not appear in the webpack server path)

due to the secret ， i delete  “user name".
I  change a registry ，it seems that the command “npm i” pass and get some warning as follows:
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^5.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of fibers@>= 3.1.0 but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed.
Failed to compile.

createRequire is not a function
Referenced from: BaseConfig

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build: `react-scripts build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in 2021-11-19T09_59_11_656Z-debug.log

detail errors in 2021-11-19T09_59_11_656Z-debug.log:
10 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c', 'react-scripts build' ]
11 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null
12 info lifecycle<EMAIL_ADDRESS>Failed to exec build script
13 verbose stack Error<EMAIL_ADDRESS>build: `react-scripts build`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (/usr/local/node/node-v10.9.0-linux-x64/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:304:16)
13 verbose stack     at EventEmitter.emit (events.js:182:13)
13 verbose stack     at ChildProcess.<anonymous> (/usr/local/node/node-v10.9.0-linux-x64/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:182:13)
13 verbose stack     at maybeClose (internal/child_process.js:961:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:250:5)
14 verbose pkgid<EMAIL_ADDRESS>15 verbose cwd /home/.open_source/vosk-browser/examples/react
16 verbose Linux 3.10.0-1160.36.2.el7.x86_64
17 verbose argv "/usr/local/node/node-v10.9.0-linux-x64/bin/node" "/usr/local/node/node-v10.9.0-linux-x64/bin/npm" "run" "build"
18 verbose node v10.9.0
19 verbose npm  v6.2.0
20 error code ELIFECYCLE
21 error errno 1
22 error<EMAIL_ADDRESS>build: `react-scripts build`
22 error Exit status 1
23 error Failed at the<EMAIL_ADDRESS>build script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

@ccoreilly update the node version 15， it work.  whether  can I modify the default port 3000?

That is the port of the react development server, you should not use that server in production. I think you can change the port via the PORT environment variable.
PORT=8080 npm run start

@ccoreilly thanks

I get a warning，whether it will affect some usage?
Compiled with warnings.

./node_modules/vosk-browser/dist/vosk.js
Module not found: Can't resolve 'worker_threads' in '/home/ybZhang/.open_source/vosk-browser/examples/react/node_modules/vosk-browser/dist'

That's a normal warning of react, no worries


Supporting SIMPLE_RADIAL camera, default from COLMAP

I remember talking to you guys about this at CVPR but I forget what the resolution was. I have run COLMAP with the default settings which generates a camera with SIMPLE_RADIAL parameters. However, when running the structure from motion demo with my own COLMAP output, I ran into the assertion error about camera.model == 'PINHOLE' (because the default from COLMAP is 'SIMPLE_RADIAL').
Is your feature request related to a problem? Please describe.
I want to be able to run rerun with my default output from COLMAP.
Describe the solution you'd like
Support more cameras!
Describe alternatives you've considered
I can still run it without the assert, it just looks funny.
Additional context
If you could support a weak-perspective camera too that would be great!
Thanks~.

Thanks again for coming by our booth at CVPR and bringing this up. Rerun is definitely in need for more different kind of camera and camera distortion models.
We'll need to reconsolidate all these different asks into different workstreams and see where the delimiting lines and imlementation strategies for these are 🤔

I was able to get my COLMAP output slightly visualized by rerun by ignoring the assert, shown here incase it's of curiosity.

I thought I might be able to get around it by manually editing the cameras.txt file to ditch the k and then reconverting to binary but COLMAP's model_converter does not approve of such things.

For anyone with a related issue, I found a way to get around my issue by just closing my ears and yelling "radial distortion doesn't exist".
Basically, I take the COLMAP cameras and throw away the K and I can get an improved visualization:
colmap model_converter \
        --input_path $WORKSPACE_PATH/sparse \
        --output_path $WORKSPACE_PATH/sparse \
        --output_type TXT

colmap model_converter \
        --input_path $WORKSPACE_PATH/sparse/0 \
        --output_path $WORKSPACE_PATH/sparse/0 \
        --output_type TXT

python fix_cam.py
rm $WORKSPACE_PATH/sparse/cameras.bin
rm $WORKSPACE_PATH/sparse/0/cameras.bin

colmap model_converter \
        --input_path $WORKSPACE_PATH/sparse \
        --output_path $WORKSPACE_PATH/sparse \
        --output_type BIN

colmap model_converter \
        --input_path $WORKSPACE_PATH/sparse/0 \
        --output_path $WORKSPACE_PATH/sparse/0 \
        --output_type BIN

Where fix_cam.py looks like this:
#!/usr/bin/env python
# -*- coding: utf-8 -*-

def convert_camera_model(input_file):
    with open(input_file, 'r') as fin:
        lines = fin.readlines()

    new_lines = []
    for i, line in enumerate(lines):
        if i < 3:  # Skip the first 3 lines (header)
            new_lines.append(line)
        else:
            parts = line.strip().split()
            parts[1] = 'PINHOLE'  # Change camera model
            parts.insert(5, parts[4])  # Duplicate fx as fy
            parts = parts[:-1] # Ditch k
            new_lines.append(' '.join(parts) + '\n')

    with open(input_file, 'w') as fout:
        fout.writelines(new_lines)

convert_camera_model('./pinhole_workspace/sparse/cameras.txt')
convert_camera_model('./pinhole_workspace/sparse/0/cameras.txt')


Avoid the JSON parse error on empty strings

The _changes feed from couchdb can return an empty string which cradle was trying to parse and causing a JSON parse error. This code joins the buffer fragments and test for string length > 0 before sending to JSON.

glad I could help :)

@donpdonp @nhunzaker Thanks, but I've updated Cradle to use the changes library from IrisCouch: follow

That's exactly what I wanted to here :)

Great choice! thanks.


Bump near-api-js to 1.1.0

Thanks for taking the time to submit a pull request!
If you haven't already, be sure to take a look at the CONTRIBUTING documentation to get up to speed with the practices in this repository.
When you're ready, switch to the "Preview" tab to select an applicable template:

General template (most common)
Wallet integration template

I think we can postpone upgrading near-api-js in this project. There are too many projects that’d be affected if we merge this. And we honestly have no reason to, since all functionalities work fine with the current version. Developers can use the more recent versions in their own projects.
If you have faced any bugs/issues with the current version we are using please feel free to open a new issue.


hardcode the binary name during compilation

see title. We may do that for additional hardening/defense in depth. The reasoning is that the compiler may be tricked into running commands that print and alter the name. In this case, we would be taking the hash of the wrong binary. (we plan to have the nest step in a separate job)

resolved in https://github.com/asraa/slsa-on-github/pull/52.


blocks org-babel html export of json

flow-minor-tag-present-p gives an error when exporting org-mode code like
#+BEGIN_SRC json
{"foo":[]}
#+END_SRC

to html because it tries to do backward-char from the beginning of the buffer. Changing it to
        (if (equal (point) (point-min))
            (setq stop t)
          (backward-char))

at least stops it from making org html-exports error out.

This mode is not supposed to be used on files that can't be parsed by flow, also i don't really understand the proposed change and the cause of the problem (error) in the first place.

The bug is in the code that tries to determine whether the buffer can be parsed by flow.
org-mode uses the major mode of #+BEGIN_SRC blocks to syntax highlight that block when exporting to html.
Try checking out https://gist.github.com/unhammer/f3a36a3f2bdc29d3cab84c25e51f2637 and doing emacs -Q -l init.el foo.org and C-c C-e h H (M-x org-html-export-as-html). It'll just say Beginning of buffer instead of giving the html export.


#34650 Add missing PostgreSQL functions to dialect

tsvector_update_trigger, tsvector_update_trigger_column, substr, bit_count, pg_cancel_backend, pg_log_backend_memory_contexts, pg_reload_conf, pg_rotate_logfile, pg_create_restore_point, pg_current_wal_flush_lsn, pg_current_wal_insert_lsn, pg_current_wal_lsn, pg_backup_start, pg_backup_stop, pg_switch_wal, pg_walfile_name, pg_walfile_name_offset, pg_split_walfile_name, pg_wal_lsn_diff, pg_is_in_recovery, pg_last_wal_receive_lsn, pg_last_wal_replay_lsn, pg_last_xact_replay_timestamp, pg_get_wal_resource_managers, pg_is_wal_replay_paused, pg_get_wal_replay_pause_state, pg_promote, pg_wal_replay_pause, pg_wal_replay_resume, pg_export_snapshot, pg_log_standby_snapshot, pg_create_physical_replication_slot, pg_drop_replication_slot, pg_create_logical_replication_slot, pg_copy_physical_replication_slot, pg_copy_logical_replication_slot, pg_logical_slot_get_changes, pg_logical_slot_peek_changes, pg_logical_slot_get_binary_changes, pg_logical_slot_peek_binary_changes, pg_replication_slot_advance, pg_replication_origin_create, pg_replication_origin_drop, pg_replication_origin_oid, pg_replication_origin_session_setup, pg_replication_origin_session_reset, pg_replication_origin_session_is_setup, pg_replication_origin_session_progress, pg_replication_origin_xact_setup, pg_replication_origin_xact_reset, pg_replication_origin_advance, pg_replication_origin_progress, pg_logical_emit_message, pg_column_size, pg_column_compression, pg_indexes_size, pg_relation_size, pg_size_bytes, pg_size_pretty, pg_table_size, pg_tablespace_size, pg_total_relation_size, pg_relation_filenode, pg_relation_filepath, pg_filenode_relation, pg_collation_actual_version, pg_database_collation_actual_version, pg_import_system_collations, pg_partition_tree, pg_partition_ancestors, pg_partition_root, pg_ls_dir, pg_ls_logdir, pg_ls_waldir, pg_ls_logicalmapdir, pg_ls_logicalsnapdir, pg_ls_replslotdir, pg_ls_archive_statusdir, pg_ls_tmpdir, pg_read_file, pg_read_binary_file, pg_stat_file, pg_advisory_lock, pg_advisory_lock_shared, pg_advisory_unlock, pg_advisory_unlock_all, pg_advisory_unlock_shared, pg_advisory_xact_lock, pg_advisory_xact_lock_shared, pg_try_advisory_lock, pg_try_advisory_lock_shared, pg_try_advisory_xact_lock, pg_try_advisory_xact_lock_shared, family, point, slope, diagonal, to_timestamp, localtime, localtimestamp, sinh, sqrt, tan, sin, round, pi, power, log, log10, floor, gcd, lcm, cosh, cot, cos, atan, atan2, asin, abs, acos, percent_rank
added these missing PostgreSQL functions to dialect

@asifjoardar please merge devel to your branch and resolve conflicts, if there are some.

hi @E1izabeth , i have merged the devel with my branch.

verified


Updating sample tenant name to be onmicrosoft

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


Config wrong session history path

Versions

Weights and Biases version: 0.9.0
Python version: 3.7.7
Operating System: Windows 10 Home
Jupyter Lab:
jupyter-client: 6.1.3
jupyter-console: 6.1.0
jupyter-core: 4.6.3
jupiter: 1.0.0
jupyterlab-server: 1.1.4
jupyterlab: 1.2.6

Description
I am working with Jupyter Lab. I enabled code saving in my personal account and it does upload the code successfully to the code folder. The problem is that the path in the config.yaml has a backslash instead of a forward slash.
wandb_version: 1

_wandb:
  desc: null
  value:
    cli_version: 0.9.0
    is_jupyter_run: true
    is_kaggle_kernel: false
    python_version: 3.7.7
    session_history: code\_session_history.ipynb
test:
  desc: null
  value: true

I am not able to change the path as it gets reset as soon as I rerun the commands below. Because of this error, I get a No such file! error when clicking on the code icon inside the run on www.app.wandb.ai.
What I Did
import wandb

defaults=dict(
    test = True,
)

wandb.init(project="test", config=defaults)

for i in range(10):
    sleep(0.1)
    print(i)
    wandb.log({"epoch": i/10})

Thanks @Xeratec this should be fixed in our new cli library wandb-ng.  If you'd like to try it now you can do pip install wandb-ng you can find more information here:  https://github.com/wandb/client-ng


glb import is not the same between versions

Godot version
4.0 dev
System information
Windows 11, AMD Ryzen 3900X, RTX 2070 S
Issue description
I created a 3D model and imported it in Godot 4 as a glb. The animation broke and parts of the mesh did not follow the skeleton properly. I loaded the same model into Godot 3 and there were no issues with the animation.
https://user-images.githubusercontent.com/83244706/182676673-7b6622a9-55ea-4853-9a9b-1389dd2e1701.mp4
https://user-images.githubusercontent.com/83244706/182676685-fedf750a-9f16-4d01-82ab-119877a1f137.mp4
Steps to reproduce
Create a rig in Blender,
1 - Export as glb, import to Godot
1.1 - Drop the blender file in Godot
2 Animation doesn't play properly
Minimal reproduction project
Project.zip

4.0 dev spans half a year now. Which commit?
Most likely this is animation auto-optimization acting up again. Find it in Godot and disable it.

I'm sorry I have not been up to speed. Where is that located?

I'm sorry I have not been up to speed. Where is that located?

The optimizer can be disabled in the Import dock after selecting the gltf/glb file in the FileSystem dock.

Somehow the older import of the animation was kept. If you delete the .godot folder and let it reimport, I was able to get the animation to look the same as https://threejs.org/editor/.

The keyframe should be solid.

This did not work for me, the animation is still broken

It is unclear what you mean by some of the meshes not tracking. From the video above, I can only say that it is an Optimizer issue that is causing the animation to be wonky.
Please confirm that you have disabled Optimizer and then tell me the commit hash for 4.0.dev.

I meant that the meshes for the shoes were not tracking to the armature properly, you can see in the video that they do not follow the skeleton the way they should. Turning off the optimizer fixed it, and this isn't any build you can currently download. This is from me building the engine from the latest source code at the time(the videos show 4.0.alpha.mono)


Fix the nightly tests

WIP: Got everything hooked up, but some of the inputs don't match up with the quick picks in each implementation.  I assume we may have made some updates while the tests were disabled, and thus never updated the tests to reflect these changes.  I'll spend some time over the next week working on fixing all the tests. 🫡

Will reopen later with finalized split PRs


Hardening Guide - Authentication Mechanisms

I think bellow:
"They cannot be set with an expiry and will remain valid until the associated service account is deleted."
in service account section is not clear. After deleting service account kubernetes api recject comunication.

Page reported in issue (from current title): https://kubernetes.io/docs/concepts/security/hardening-guide/authentication-mechanisms
/language en

/sig security auth

@techitlab Could you please expand on what exactly is not clear in the description?

/triage needs-information

/close
No reply to my question within a month, this can be closed.


Crashes on API server timeout

When the API server is not reachable (timeout) for any reason, this controller crashes. It's then restarted and will resume its work, so it's not a critical issue. I think some work can be done to retry with backoff instead of crashing. I'll post some logs in there when I reproduce the issue.

are you running them on master nodes? and are communicating to themselves?
if yes, there is a 1/${MasterNodeCount} probability that the connection runs in a timeout if you connect from a VMSS to a loadblanacer which is attached to the same VMSS.
Azure LoadBalancers in azure drop traffic if it would hit the same VM where it came from (to prevent loops).

I was not able to reproduce the issue. The pods where not scheduled on the leaders and anyway I'm using RKE which does not support using an external load balancer in front of the leaders (it configures a local nginx-proxy on each worker with the list of the leaders). I'll reopen this issue if needed in the future. Thank you!


Evaluating expressions on inner elements if ui-scroll directive with data item undefined

Hi
I've met strange behaviour of ui-scroll directive.
For example, if I have the following markup:

{{log(item)}}

then

Expression {{log(item)}} is evaluated before first call of datasource.get method, thus item in this call is undefined.
On every digest sycle the expression {{log(item)}} is evaluated with strange item undefined, that doesn't exist.

So the question is - why expression {{log(item)}} is evaluated for strange item undefined that doesn't exist?
I prepared plunk that shows this behaviour http://plnkr.co/edit/uotXYdrCCZlpmYNaX3Re?p=preview

This seems to be a side effect of the watcher you created. Updating scroller takes several digest cycles. The initial ones do not necessarily have everything intialized

I've looked through the code and found out that the problem is caused by additional call of transclusion function that is used just to guess the tagname of an element the directive is placed on.
# Element builder
#
# Calling linker is the only way I found to get access to the tag name of the template
# to prevent the directive scope from pollution a new scope is created and destroyed
# right after the builder creation is completed
linker $scope.$new(), (template) ->

So we should definitely get rid of this transclusion function call to fix the problem described above.
I don't know another way to guess the element tag name.
But maybe we should try another way to handle infinite scrolling that is used in ui-grid component - use margins on first and last elements instead of adding extra dummy elements and setting their height?

This seems to be a side effect of the watcher you created.

No, this is definitely not caused by watcher, I used there watcher just for debug purposes.
I just described above what actually cause the problem.

Well that explains one of them. because this extra linker call only happens once when the scroller is instantiated. I see your point about this not related to watchers, but at this time I do not know what causes these extra calls. If you can investigate it further, i would appreciate the additional information.
About definitely getting rid of extra linker call - I am all for it. As stated in the comment I failed to find a better way to do it. Can you suggest any?

About extra calls with undefined - ok, I'll try to find out the reason.
But if we remove this extra linker call, then these extra calls with undefined are removed either.

When linker call is used to guess element's tag name, new scope is created.
Along with this directives and expressions used in the transcluded element set their watchers on the scope.
This leads to execution of such extra watchers expressions every digest call and this may cause some negative effects.
To fix it we need to destroy the scope.
I created PR that fixes that problem https://github.com/angular-ui/ui-scroll/issues/17

I see it's my fault that this new scope hasn't be destroyed while directive lives: https://github.com/Hill30/NGScroller/commit/98230d9e9cf6486991c4b6eb5e005988b48ba8b2. This new scope doesn't lead to leaks -- that was my logic. And we should accept this PR.

@aantipov thank you for your contribution


BigQuery Java Connection API can hang / deadlock if connection is closed without reading all results

Thanks for stopping by to let us know something could be better!
If you are still having issues, please include as much information as possible:
Environment details

Specify the API at the beginning of the title. For example, "BigQuery: ...").
General, Core, and Other are also allowed as types
OS type and version: Linux Ubuntu
Java version: 17 adoptium
version(s): 2.22.0

Steps to reproduce

Run query that returns enough rows to fill the async buffer
wait for the query to complete,
read some data via JDBC API (but not all of it)
ensure that the buffer is full (can just sleep)
close connection

Code example
ConnectionSettings connectionSettings =
ConnectionSettings.newBuilder()
       .setUseReadAPI(false)
       .setRequestTimeout(10L)
       .setMaxResults(100L)
       .setUseQueryCache(true)
       .build();
Connection connection = bigquery.createConnection(connectionSettings);
String selectQuery = "<query that returns more than buffer size rows>";
ListenableFuture<ExecuteSelectResponse> executeSelectFuture = connection.executeSelectAsync(selectQuery, ...);

ExecuteSelectResponse response = executeSelectFuture.get();
ResultSet results = response.getResultSet();

// read some, but not all of the data
resultSet.next()
// sleep for a bit to ensure that the buffer is full
Thread.sleep(10000);

// hangs forever.
connection.close();

Stack trace (from jstack thread dump)
"thread name" #35 prio=5 os_prio=0 cpu=917.01ms elapsed=4251.27s tid=0x0000558529454f40 nid=0x49 waiting on condition  [0x00007f9eefffd000]
   java.lang.Thread.State: WAITING (parking)
	at<EMAIL_ADDRESS>Method)
	- parking to wait for  <0x000000074b91f798> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
	at java.util.concurrent.locks.LockSupport.park(java.base@17.0.6/LockSupport.java:341)
	at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionNode.block(java.base@17.0.6/AbstractQueuedSynchronizer.java:506)
	at java.util.concurrent.ForkJoinPool.unmanagedBlock(java.base@17.0.6/ForkJoinPool.java:3463)
	at java.util.concurrent.ForkJoinPool.managedBlock(java.base@17.0.6/ForkJoinPool.java:3434)
	at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(java.base@17.0.6/AbstractQueuedSynchronizer.java:1623)
	at java.util.concurrent.LinkedBlockingDeque.putLast(java.base@17.0.6/LinkedBlockingDeque.java:389)
	at java.util.concurrent.LinkedBlockingDeque.put(java.base@17.0.6/LinkedBlockingDeque.java:642)
	at com.google.cloud.bigquery.ConnectionImpl.flagEndOfStream(ConnectionImpl.java:767)
	at com.google.cloud.bigquery.ConnectionImpl.close(ConnectionImpl.java:144)
	- locked <0x0000000743dab650> (a com.google.cloud.bigquery.ConnectionImpl)
	at ... my code calling close

Can see that the thread is blocked here: https://github.com/googleapis/java-bigquery/blob/main/google-cloud-bigquery/src/main/java/com/google/cloud/bigquery/ConnectionImpl.java#L767-L768
Async worker thread that is populating the queue is also blocked (as the queue is full).
"pool-67-thread-3" #239 prio=5 os_prio=0 cpu=186.77ms elapsed=8312.48s tid=0x00007f9ef4010560 nid=0x12c waiting on condition  [0x00007f9ee81fe000]
   java.lang.Thread.State: WAITING (parking)
	at<EMAIL_ADDRESS>Method)
	- parking to wait for  <0x000000074b91f798> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
	at java.util.concurrent.locks.LockSupport.park(java.base@17.0.6/LockSupport.java:341)
	at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionNode.block(java.base@17.0.6/AbstractQueuedSynchronizer.java:506)
	at java.util.concurrent.ForkJoinPool.unmanagedBlock(java.base@17.0.6/ForkJoinPool.java:3463)
	at java.util.concurrent.ForkJoinPool.managedBlock(java.base@17.0.6/ForkJoinPool.java:3434)
	at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(java.base@17.0.6/AbstractQueuedSynchronizer.java:1623)
	at java.util.concurrent.LinkedBlockingDeque.putLast(java.base@17.0.6/LinkedBlockingDeque.java:389)
	at java.util.concurrent.LinkedBlockingDeque.put(java.base@17.0.6/LinkedBlockingDeque.java:642)
	at com.google.cloud.bigquery.ConnectionImpl.lambda$populateBufferAsync$4(ConnectionImpl.java:733)
	at com.google.cloud.bigquery.ConnectionImpl$$Lambda$1385/0x0000000801740228.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(java.base@17.0.6/ThreadPoolExecutor.java:1136)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(java.base@17.0.6/ThreadPoolExecutor.java:635)
	at java.lang.Thread.run(java.base@17.0.6/Thread.java:833)

Hey @jonathanswenson, curious if you were able get around this issue?
I think we are running into something very similar. In our case we are reading partial results from the resultSet and using that to do some processing while we hold on to the resultSet.
After the processing is done, we go back to the resultSet again to process some more data. This gets stuck after a couple of iterations.
We checked that of we do it in one go i.e. in a single iteration, we do not have any issues. The issue arises only when we read partial data in iterations from the resultSet.


add additional motivation

@bakkot Does this reflect your motivation well?

I might say "Unicode or RegExp knowledge", but otherwise yes. (How many JS readers know about \p?)


Getting conflict after the login

I'm getting a Conflict 409 status code response from the epiclogin method.
It was working all fine for the last few month but this error started from 2 days ago.
Anyone else had it? is there a solution for it? my account email/password did not change

@Terbau

Seems like epic decided to reset all device auths for bots. You can generate a new one by doing the following:

Navigate to your device_auths.json (considering thats the method for storing auths you are using)
Delete the entry matching the email of the account you want to generate a new device auth for.
Start your fortnitepy application and follow the steps.

Alternatively you could just rename your current device_auths.json file so that a new one is generated upon start. This way you don't have to look for specific device auths to delete.

I'll leave this issue open for a couple of days so that others can easily find it.

Seems like epic decided to reset all device auths for bots. You can generate a new one by doing the following:

Navigate to your device_auths.json (considering thats the method for storing auths you are using)
Delete the entry matching the email of the account you want to generate a new device auth for.
Start your fortnitepy application and follow the steps.

Alternatively you could just rename your current device_auths.json file so that a new one is generated upon start. This way you don't have to look for specific device auths to delete.

I did it but before the exchange code step, when i do the login method i get a 409 response of conflicted(using the device auth method). Usually after the login get request i'd get status of 200 and then the exchange code would be generated but since few days ago it can't even generate an exchange code and the login method returns 409.
I also checked with multiple epic accounts same results, and tried also from different ip's.
Any ideas?

Also, Is it just me, or it happens to you too? wanna make sure the problem isn't just on my end

@Terbau any news?


Connection limits per IP for WebSocket server

Description:

Adds a configurable limit on the maximum connections from a single IP address.
Adds a class for WebSocket errors. I suggest we follow the convention described in this article regarding the error codes. E.g. our error codes should look like 4XXX

Related issue(s):
Fixes #
Notes for reviewer:

Checklist

[ ] Documented (Code comments, README, etc.)
[ ] Tested (unit, integration, etc.)

Codecov Report
Patch coverage: 100.00% and project coverage change: +0.80 :tada:

Comparison is base (470e3c2) 74.63% compared to head (b6e5a54) 75.43%.

:exclamation: Current head b6e5a54 differs from pull request most recent head 1eff6ed. Consider uploading reports for the commit 1eff6ed to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1037      +/-   ##
==========================================
+ Coverage   74.63%   75.43%   +0.80%
==========================================
  Files          30       18      -12
  Lines        2030     1502     -528
  Branches      386      290      -96
==========================================
- Hits         1515     1133     -382
+ Misses        410      299     -111
+ Partials      105       70      -35

Impacted Files
Coverage Δ

packages/relay/src/lib/errors/WebSocketError.ts
100.00% <100.00%> (ø)

packages/relay/src/lib/poller.ts
82.50% <100.00%> (ø)

... and 13 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Twinkling pixels

Hello,
There is some twinkling pixels on my panel :
https://photos.app.goo.gl/ECdXQgufkL1dPgGm8
The less text displayed, the more flickering pixels there are...
When I move the ground cable away (see photo) there are fewer pixels, when I move it closer to another cable, there are more :

I try with another power supply, there are less flickering pixels.
I try to add capacitors 10pF, 1nF, , 10nF,  1uF, 10uF, 1000 uF, no way...
Thank you

You could try reducing the SPI speed in the library. Place
PxMATRIX_SPI_FREQUENCY 10000000
before #include <PxMatrix.h>

Thanks, I Try with 15 000 000 and 12 000 000, it seems not better. At 10 000 000 EPS32 crash because of resolution (I think)

I found a solution to reduce the issue : group all wire and keep all away from the ground wire.
Before :

After :

Cool...impressive that it works with 3 panels

The less text displayed, the more flickering pixels there are...

This strongly indicates that it's an issue with the 3.3V levels driving 5V logic.
When more pixels are lit, more current is drawn and your supply voltage may drop slightly...
Lowering the supply voltage is and should be the proper solution, you actually don't need 5V. If you can, go down to ~4V. (or buy proper and fast level converters)
If you have a power supply with variable voltage, you can easily confirm this. My panel also starts twinkling at 5.05V when only few pixels are lit with an SPI frequency of 16MHz.

Thank you for your expertise. You are right : I have 2 power supply of fixed voltage 5v. But one of them have thinner wire who warm up, then the voltage is about 4.5v and I get less twinkling pixels.


Buttons do not activate on release if frame rate is low.

This is a bug in response to experience with OOBE.
To repro, after pressing a button, move your hand out very quickly.
Alternately, force a very low framerate on your app (e.g. 30 fps).
The button will only fire a release when you were still touching, but crossed back above the press plane.
So, if the following sequence happens:
button press
touch up + cross press plane
Then the event would never fire. The sequence that the current buttons expect are:
button press
cross the press plane
touch up

Ported from internal database

If anyone has a scenario in which this affects non-low perf cases, would be good to have data here.


Add cluster-resources app

Towards https://github.com/giantswarm/roadmap/issues/725
Of course the app needs to be released first.

Superseded by https://github.com/giantswarm/default-apps-openstack/pull/37


[BUG] Error Upon Cloning a Job with Infinite as Data Pool

Describe the bug
Cloning a job with a data pool set as infinite makes the program break until it is reloaded into a different place then the clone job page.
To Reproduce
Steps to reproduce the behavior:

Go to 'Jobs'
Click on Clone on a Job that has data pool set to infinite
See error

Expected behavior
A normal clone window.
Screenshots

Desktop (please complete the following information):

OS: Windows 10
Browser: Firefox
Version: Latest

Error
[2021-04-17T14:47:43.508Z] Error: System.NullReferenceException: Object reference not set to an instance of an object.

   at OpenBullet2.Shared.DataPoolSelector.<BuildRenderTree>b__0_31(RenderTreeBuilder __builder3) in D:\a\OpenBullet2\OpenBullet2\OpenBullet2\Shared\DataPoolSelector.razor:line 96
   at Microsoft.AspNetCore.Components.Forms.InputSelect`1.BuildRenderTree(RenderTreeBuilder builder)
   at Microsoft.AspNetCore.Components.Rendering.ComponentState.RenderIntoBatch(RenderBatchBuilder batchBuilder, RenderFragment renderFragment)
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.RenderInExistingBatch(RenderQueueEntry renderQueueEntry)
   at Microsoft.AspNetCore.Components.RenderTree.Renderer.ProcessRenderQueue()

Did you perhaps change your Environment.ini file since when you created the original job? Because the exception hints to OB2 searching for a Wordlist Type that is not present anymore.

Did you perhaps change your Environment.ini file since when you created the original job? Because the exception hints to OB2 searching for a Wordlist Type that is not present anymore.

I haven't changed anything in that file. And i tried this on multiple jobs and even made new ones and i always experienced that issue/error.

Sorry I tried again but I cannot reproduce this :(

Sorry I tried again but I cannot reproduce this :(

I could offer to send you the environment file or anything else that might help.

Sorry I tried again but I cannot reproduce this :(

I could offer to send you the environment file or anything else that might help.

Send it to my inbox by mail. You can find the address in the readme of the repo.


Update build docs

Point to sample project.
Point to new LitElement build guide.
Fix ref to open-wc webpack info.
Assorted other improvements.

Updated and hopefully clean now, PTAL.


[Draft] [Reproduce Issue] Same consumer subscribe twice

Motivation

time
subscribe 1st and 2nd
unload topic
reconnect due to unload topic
reconnect due to subscribe 2nd timeout

1
subscribe 1st success

2

unload the topic

3
subscribe 2nd started due to unload topic

4
the consumer registered on the subscription, and the future of creating consumer is not complete yet

5

unload the topic

6

subscribe 3rd started due to unload topic
subscribe 4th started due to subscribe timeout

7

compare and set consumer.cnx to null
set consumer.cnx to null

8

ask broker remove the previous consumer

9

subscribe success

10

subscribe success 2nd

You can reproduce the flow above by the test testCnxInactiveWhenDoingSubscribe, this test only injects some sleep to reproduce the flow above(Because the timeout exception was manually injected, resetCursor was used instead of unload topic in the test, which will not make the injected exception will not be invalidated ).
Since the same consumer subscribing success twice will make the messages lost[1], we should solve it.

Footnotes
[1]

time
subscribe 1st
subscribe 2nd

1
subscribe start

2
Clear messages in memory

3
subscribe success

4
receive 712 messages

5

subscribe start

6
Clear messages in memory.(Highlight) 712 messages were lost

7
subscribe success

Modifications
A test to reproduce the issue that the same consumer can subscribe twice.
Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository: x

The test does not verify when the 2nd subscribe finished, the cursor has already been moved ahead and the previous 712 messages wouldn't be redelivered.

Oh I got it. The following logic happened twice
https://github.com/apache/pulsar/blob/0cc3d7329cf5c77879f81b99e574972bdae90988/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/ServerCnx.java#L1194-L1198
But the issue becomes, why return a success response when the same consumer subscribes again? I think we should return an error response here.


Error during Boss Swarms when in Multiplayer.

When using a boss summon + overloader in stacks of >= 10 this error happens and occasionally the entire multiplayer server crashes. I run the server instance separate from my client as my son plays on a 2nd computer w/o me.

Server hosted logs
server.log
client.log
Self-hosted logs
client.log

I just setup a server and let my son attempt the same and here are those logs. the errors look the same to me.
server.log


remove cxf-rest project as archetype still gets generated and forge itests fail further down the pipeline

[merge]


[BEAM-1397] Introduce IO metrics

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

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

R: @bjchambers @staslev
CC: @amitsela

Coverage increased (+0.05%) to 70.138% when pulling 5e9d6b6550b4c0347093f42a606fd89030d35ab0 on aviemzur:introduce-io-metrics into 2f96bc3260b98a97d532f8451d8fa63809f1ae51 on apache:master.

Coverage increased (+0.04%) to 70.128% when pulling 76f750cd1b0777edcfb3c7042b3215cb65959428 on aviemzur:introduce-io-metrics into 2f96bc3260b98a97d532f8451d8fa63809f1ae51 on apache:master.

Failing tests will pass when https://github.com/apache/beam/pull/2171 is merged.

Coverage increased (+0.03%) to 70.165% when pulling aa51188aec88f2b0e9b9558258a64a4ae9793c09 on aviemzur:introduce-io-metrics into 781e4172c3f36863d1c9145d4c18cd0910f2436a on apache:master.

Run Spark RunnableOnService

Rebased on master. #2171 did the trick. All tests pass now.
R: @bjchambers @staslev
CC: @amitsela
PTAL

Coverage increased (+0.03%) to 70.165% when pulling 60b4aab4d5d8552918f9d1de649863ca23a728b6 on aviemzur:introduce-io-metrics into 7447147e034fc952cedae85bf3cff05e4f58b97c on apache:master.

Run Spark RunnableOnService

Retest this please

Coverage increased (+0.04%) to 70.167% when pulling 60b4aab4d5d8552918f9d1de649863ca23a728b6 on aviemzur:introduce-io-metrics into 7447147e034fc952cedae85bf3cff05e4f58b97c on apache:master.

Rebased on master. #2171 did the trick. All tests pass now.
R: @bjchambers @staslev
CC: @amitsela
PTAL

Run Spark RunnableOnService

Retest this please.

Retest this please.

Coverage increased (+0.03%) to 70.156% when pulling dbec42e292d0ff74044a62aba32cf21a852aceef on aviemzur:introduce-io-metrics into faa9645d234cd1400faf4b0c32af1768579bf15b on apache:master.

Retest this please.

Coverage increased (+0.04%) to 70.166% when pulling dbec42e292d0ff74044a62aba32cf21a852aceef on aviemzur:introduce-io-metrics into faa9645d234cd1400faf4b0c32af1768579bf15b on apache:master.

Run Spark RunnableOnService

@aviemzur the ResumeFromCheckpointStreamingTest.testWithResume is well known to flake (which also bought him the ticket out of PreCommit tests..) so if it passes for you locally, and you feel confident that your changes don't affect it (really shouldn't in this case), feel free to ignore it.
But just to give it another go:   Run Spark RunnableOnService

Run Spark RunnableOnService

Coverage decreased (-0.2%) to 69.942% when pulling e62dec045f8086442246ab22c365c3c4be23016e on aviemzur:introduce-io-metrics into faa9645d234cd1400faf4b0c32af1768579bf15b on apache:master.

Run Spark RunnableOnService

Run Spark RunnableOnService

@aviemzur I'm not sure what's going on with the test and whether it's related.
If it's not, we might want to @Ignore it to keep the build reasonably green, if it a fix should follow.

Run Spark RunnableOnService

@staslev Looks like Jenkins is back to normal, ROS tests pass now.
@bjchambers moved all metrics related tests added in this PR to MetricsTest as requested.

Coverage increased (+0.03%) to 70.216% when pulling 879312de6f2f529082adc08e5e8e10603b84f120 on aviemzur:introduce-io-metrics into 3473055f2358533dfb18af225ffdee2c8eca4000 on apache:master.

Run Spark RunnableOnService

R: @amitsela made the change you suggested.
PTAL


Install xdebug.

Note to @dmatthew: https://github.com/copious-cookbooks/php/blob/master/attributes/default.rb

Okay @hardyjohnson, should be ready for another look.


[draft] convert some match to new matches! macro

Motivation
The matches! macro was introduced in Rust 1.42.
It allows us to get rid of a common verbose pattern.
Test Plan
need to test

(had to update the toolchain to satisfy the move-prover)

:umbrella: The latest upstream changes (presumably 55dd614fc0f2e79edd60c3b6f0cb6aa90d3ea47a) made this pull request unmergeable. Please resolve the merge conflicts.

@bors-libra r=davidiw

:pushpin: Commit 5c0bcb9 has been approved by davidiw

:hourglass: Testing commit 5c0bcb92bb1b1b8f08b7841fdb84c6293d0af27b with merge 37bbc4df4ff3ee9bc08d1faa3a89fa2a1358c813...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: davidiw
Pushing 37bbc4df4ff3ee9bc08d1faa3a89fa2a1358c813 to master...


pytest doubles %PYTHONPATH% in a debug run

Issue Type: Bug
If %PYTHONPATH% is set, VSC test (pytest) plugin double %PYTHONPATH% in debug configuration. Not the case with run configuration.
Example (run):
test_example.py::test_printPythonPath
%PYTHONPATH%:
	 PYTHONPATH_ENV_VAR
PASSED

Example (debug):
test_example.py::test_printPythonPath
%PYTHONPATH%:
	 PYTHONPATH_ENV_VAR
	 PYTHONPATH_ENV_VAR
PASSED

Doesn't really affect my use case, but I consider this as a bug.
Extension version: 2020.8.105045
VS Code version: Code 1.48.2 (a0479759d6e9ea56afa657e454193f72aef85bd0, 2020-08-25T10:13:11.295Z)
OS version: Windows_NT x64 10.0.19041

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz (4 x 3193)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.89GB (6.95GB free)

Process Argv
vsCodeTest.code-workspace

Screen Reader
no

VM
0%

Hi @schperplata 👋
Unfortunately I am unable to reproduce this. I would need to know how you're running it, how you're setting the environment variables, preferably the file content you're trying to run where you print the variable (Are you printing it to a file?).

@schperplata  I can reproduce this when I set environment variables using .env file, and print environment variables to file, thanks! Btw how were you setting environment variables?

In this specific case, I have a .bat file that set PYTHONPATH and open VSC workspace. I figured out this is the simplest way of configuring VSC workspace without mulitplying source paths for pylint, pylance, autocomplete, ...
Anyway, I don't know if that happened before when we also used .env files.

Can you please elaborate on what you mean by multiplying source paths?

In this specific case, I have a .bat file that set PYTHONPATH and open VSC workspace.

Does this issue happen when you set PYTHONPATH using a .bat file as well?

Can you please elaborate on what you mean by multiplying source paths?

This is a problem when multiroot workspaces/projects are used or modules anywhere in the project tree must be runnable. If %PYTHONPATH% is set globaly, for example by .bat file, all extensions /VSCode tools can make use of it (Pylance, Pylint, Pytest, ...). All paths are defined at one single place (.bat/.env). Otherwise, user must configure these paths for extensions, for example Pylance "python.analysis.extraPaths". This was already a discussion on a couple of other places, here is one example. Anyway, don't be bothered with this, as it is not the problem here (at least I think so) :)

Does this issue happen when you set PYTHONPATH using a .bat file as well?

Yes. In fact, this is the way I initially discovered (and reported) the issue.

Hello! We have just finished our testing rewrite and are beginning the roll out to users. If you are able, it would be very helpful to know if your issue still exists on the rewrite! To try it yourself, you need to be on the most recent release of the Python extension and add this setting to your users settings.json "python.experiments.optInto": ["pythonTestAdapter"].
You can confirm you have the rewrite enabled by setting  "python.analysis.logLevel": "Trace", in your user settings then check for Experiment 'pythonTestAdapter' is active in your python logs.
Let me know if the rewrite fixes your issue. Thanks!


question: Deny default

I want to set two groups of users and deny by default all the rest. Currently I am doing it like this, is there a better way of not having to list the emails twice?
                        transform user {
                                match email<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>                                action add role authp/user
                        }
                        transform user {
                                match email<EMAIL_ADDRESS>                                action add role authp/admin
                        }
                        transform user {
                                no match email<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>                                block
                        }

Currently I am doing it like this, is there a better way of not having to list the emails twice?

@CruzMarcio , are the users from the same domain?

Currently I am doing it like this, is there a better way of not having to list the emails twice?

@CruzMarcio , are the users from the same domain?

No, different domains. I should have made a better example, but they are all different domains.

@CruzMarcio , what is the purpose of “no match email” and block? Are you trying to explicitly block certain users? or it is your way of saying don’t allow anyone else?
if it is the later, then match on the previously granted role, i.e. no match role authp/admin authp/user. Then, block.

@CruzMarcio , what is the purpose of “no match email” and block? Are you trying to explicitly block certain users? or it is your way of saying don’t allow anyone else?
if it is the later, then match on the previously granted role, i.e. no match role authp/admin authp/user. Then, block.

Do the transforms work in order? What I noticed is that if I do it like your suggestion, I still can acess the whoami endpoint and I see the the user has the authp/guest role. I also tried doing match role authp/guest and block but it didn't work.

@CruzMarcio , wait :-) match role authp/guest and block :-)

Do the transforms work in order?

i think yes. The issue might be the difference between match any and match all. You will need to experiment and read the docs https://authp.github.io/docs/authorize/acl-rbac#granting-access-with-access-lists


Find in topic (help panel) #463

See #463
Is your feature request related to a problem? Please describe.
Search for words, code snippets, etc. in a manual opened by HelpView
Describe the solution you'd like
Add an icon to the top of the panel which opens a search field if clicked. If the user starts typing, highlight the matching elements in the content of the view, and let the user step through the hits.

Tested on macOS and it works quite nicely.


Multirow filtered rep

This Pull Request tracks the changes for implementing multiValueInsert in filtered Replication side.
I have added some of tests in keyrange_filter_test.go and sqlannotation_test.go. Let me know if some other tests needs to be added.

This change is

go/vt/binlog/keyrange_filter.go, line 59 at r6 (raw file):
Previously, sougou wrote…
We may need to bulk up these queries for efficiency. Basically, make splitMultiValueInsertQuery return a single sql that's applicable to the current keyrange.

Done. Incorporated the change in the latest commit.

Comments from Reviewable

go/vt/binlog/keyrange_filter.go, line 27 at r8 (raw file):
Previously, alainjobart (Alain Jobart) wrote…
Why this change? pre-allocating the filtered array with the approximate size sounds better?

This was done initially, since a multivalue insert was being broken to individual statements. However after discussion with Sugu, it came up that let it go as one multiValue insert statement only. I have reverted this change in the latest commit.

Comments from Reviewable

Review status: 0 of 4 files reviewed at latest revision, 7 unresolved discussions, some commit checks failed.

go/vt/binlog/keyrange_filter.go, line 52 at r8 (raw file):
Previously, alainjobart (Alain Jobart) wrote…
I think we can put a 'continue' here and then the next block can be un-indented, and not in the 'else'?

Done.

go/vt/binlog/keyrange_filter.go, line 55 at r8 (raw file):
Previously, alainjobart (Alain Jobart) wrote…
The 'err != nil' case should probably log something?

Logged the Sql statement as well as the corresponding error.

go/vt/binlog/keyrange_filter.go, line 124 at r8 (raw file):
Previously, alainjobart (Alain Jobart) wrote…
In this section, could we just build a new 'rows' value, and then re-print the SQL statement as is with it, instead of re-generating it all? Would that be simpler?

This sounds much better. I have incorporated this change. Thanks.

go/vt/sqlannotation/sqlannotation.go, line 77 at r8 (raw file):
Previously, alainjobart (Alain Jobart) wrote…
We use Keyspace as a word, not as two words, so it should be 'Keyspace' not 'KeySpace', in this function name, and below in 'hasKeySpaceID'.

Done.

go/vt/sqlannotation/sqlannotation.go, line 82 at r8 (raw file):
Previously, alainjobart (Alain Jobart) wrote…
These two lines can be moved inside the next 'if hasKeySpaceID' block, right?

Done.

Comments from Reviewable

I have incorporated all the review comments. I will be adding a test-case for this in resharding.py

For the test case, we discussed 0+1 and 1+2. It just occurred to me that 0+1 is the normal single row insert case. What we really want is 0+2 and 1+2.

Review status: 0 of 6 files reviewed at latest revision, 12 unresolved discussions.

go/vt/binlog/keyrange_filter.go, line 109 at r10 (raw file):
Previously, sougou wrote…
Saves allocation if nothing matches: var values sqlparser.Values

Done

go/vt/binlog/keyrange_filter.go, line 124 at r10 (raw file):
Previously, sougou wrote…
Nit (this saves one allocation):
queryBuf.WriteString(trailingComments)
return queryBuf.String(), nil

Done

go/vt/sqlannotation/sqlannotation.go, line 85 at r10 (raw file):
Previously, alainjobart (Alain Jobart) wrote…
I would just:
return nil, &ExtractKeySpaceIDError{
...
}
here, that avoids a level of indentation.
then the two lines ksidStr := ... and keyspaceIDs = ... can be moved after the check.

Done.

go/vt/sqlannotation/sqlannotation.go, line 107 at r10 (raw file):
Previously, alainjobart (Alain Jobart) wrote…
same here, just return nil, &ExtractKeySpaceIDError{...}

Done.

go/vt/sqlannotation/sqlannotation.go, line 116 at r10 (raw file):
Previously, alainjobart (Alain Jobart) wrote…
These two cases always return?
Then again, I would swap the original
if hasKeyspaceID {
...
} else {
...
}
into:
if !hasKeyspaceId {
if A {
return ...
} else {
return ...
}
}
then no need to indent.

Done. Changed the logic according to the way you have suggested and also what was recommended by golint :).

Comments from Reviewable

I have made the changes for incorporating the review comments and adding the test for multi_row_insert during re-sharding for both the scenarios that we discussed.
Please take a look.

It looks like the resharding test is failing on Travis. Once we figure out and fix the root cause, we should be good to merge.

Ok. I've found the problem. You have accidentally changed the file mode of resharding.py to 644. You can fix this by running the following commands:
git update-index --add --chmod=+x test/resharding.py
git commit -m 'Fixing file mode'

Also, gpylint generated some errors that you have to fix: https://gist.github.com/sougou/53b972250fdb6690e011b1bea71ff36f

Since pylint doesn't work on OS X, i was making changes on mac and trying it out on ubuntu. It seems like due to this i might have changed the file permissions. I have fixed it in this commit and also the pylint issues. Lets check this version of Travis.

I think the permission is still 644. The build is still failing.

LGTM

vtctld_web looks flaky. I'm going to ignore that failure.


UnMinified js

Hi,
Can you include an unminified js in the project.
We run all our files through a minifier (UglifyJS) and bundle them into a single file.
UglifyJS goes extremely slow when trying to minify already minified JS (like dist/braintree.js)
Every other npm/bower library we use provides a non-minified file, which could also be useful for development purposes.
Here is the discussion about this issue: https://github.com/webpack/webpack/issues/615

This is a duplicate of #1

We hope to include unminified source in a future version, but as of now there are no plans to include an unminified version here.

https://js.braintreegateway.com/js/braintree-2.19.0.js
Sorry.


Requirements for the account name is not fully described

Problem
The creation of an account with the Account ID that has a length of more than 64 characters is not possible and it is not clarified in the hint. The current hint is:
Your account ID can contain any of the following:
Lowercase characters (a-z)
Digits (0-9)
Characters (_-) can be used as separators
Your account ID CANNOT contain:
Characters "@" or "."
Expected Behavior
Users should know the maximum length of the Account ID (rules can be found here: https://docs.near.org/docs/concepts/account#account-id-rules). Also, it should be clarified, that acc length consists of acc name and network suffix.
Steps to reproduce

Go to https://wallet.testnet.near.org/create
Enter Account ID with 65 or more characters

I'd take the following approach:

Rename the translation keys to be more descriptive https://github.com/near/near-wallet/blob/7be53589264513200c6df9416cdbe06ae99d46f5/src/translations/en.global.json#L582-L587
Add a list item (currently called "note") describing the length limit restriction https://github.com/near/near-wallet/blob/7be53589264513200c6df9416cdbe06ae99d46f5/src/components/common/AccountNote.js#L27
Ensure that changes are reflected across all languages

If this sounds good, I'll go ahead and make a PR!


styles Second argument passed into a variable object the type cannot be determined

The example is wrong. It's vars

 The example is wrong. It's vars

need to add const to the returned object, otherwise TypeScript cannot infer the specific value type.
function getStyle(){
   return {...} as const
}

这个例子是错误的。这是变量

需要给返回的对象添加const，否则TypeScript无法推断出具体的值类型。
function getStyle(){
   return {...} as const
}

Why do I need to infer to specific types that the source code has done internally?

When using vars, which relies on value rather than key, the actual type obtained when using a variable is { gridTemplateColumns: string }. Therefore, it's not possible to obtain the type of a value like $grid-cols. When adding const, the type obtained is {readonly gridTemplateColumns: "$grid-cols" }.

I'm going to close this issue, feel free to reopen if there are any other issues


Update Blog “a-wizard-of-earthsea/index”

Automatically generated by Netlify CMS

👷 Deploy Preview for tubular-cheesecake-3ca0e1 processing.

Name
Link

🔨 Latest commit
e197166867e12f74604fb760513b85fb9c8b2d76

🔍 Latest deploy log
https://app.netlify.com/sites/tubular-cheesecake-3ca0e1/deploys/651df45141eac500084c8882


Merge berkeley develop 28 08 2023

Merge berkeley to develop.

@Trivo25 to merge the latest berkeley to this PR, as there are some conflicts

Merge completed in another PR


style(images): remove files filter from upload image task EE-1944

The ngf-accept file filter has been removed as it erroneously hides accepted file types such as .tar.xz and .tar.bz2
(I raised that issue because I thought that those formats were not accepted by the front-end).
Attempts to add application/x-bzip2 and application/x-xz failed as they are not accepted MIME types.
Closes https://github.com/portainer/portainer/issues/5220

/azp run


Website has a render issue

might affect confidence in the library to have just an erratic render issue on it's main site.

Only happens while scrolling/hovering over the site intermittently


Add njit

@hy-zhao23 I am sorry, the domain njit.edu is removed from our trusted domains list because it was abused in the past. If you are the student of this school, please enroll to GitHub Student Developer Program. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).


UCCSD calculation starting from UKS orbitals.

Hi,
I want to do the KUCCSD calculation on MnO crystal which the initial reference state for the CC calculations was generated from unrestricted  Kohn-Sham density functional calculations.
So first I put the dft.KUKS calculation in the input file befor the CCSD one.
But the CCSD calculation should be initialized with HF object, and we must convert the DFT object can be converted to HF object.
How we should do it?
This is a part of calculation :
kmf = dft.KUKS(cell, kpts, exxdiv=exxdiv).density_fit()
kmf.xc = 'pbe'
kmf.with_df = gdf
kmf.with_df._cderi = gdf_fname
kmf.conv_tol = 1e-8
kmf.chkfile = chkfname
kmf.max_cycle = 300
kmf.kernel()
mycc = cc.KUCCSD(kmf)
mycc.conv_tol = 5e-5
mycc.conv_tol_normt = 1e-3
mycc.direct = True
mycc.kernel()
Thanks

You can manually convert the KS object to an HF object.
mycc = cc.KUCCSD(kmf.to_hf())

Thank you but, it gives an error:
File "/.nput.py", line 140, in
mycc = cc.KUCCSD(kmf.to_hf())
File "/.../python3.10/site-packages/pyscf/dft/rks.py", line 411, in to_hf
elif isinstance(self, scf.hf.UHF):
AttributeError: module 'pyscf.scf.hf' has no attribute 'UHF'. Did you mean: 'RHF'?

Yes, You are right.
the problem is the PySCF version. It was 2.2. I upgrade it to V-2-6, now it works.
Another way for this issue is to create a new KUHF object and set the mo_coeff and mo_occ to the one from HF, something like the following after dft calculation is done:
kmf = scf.KUHF(cell, kpts=kpts, exxdiv=None).density_fit()
kmf.with_df = mydft.with_df
kmf.mo_coeff = mydft.mo_coeff
kmf.mo_occ = mydft.mo_occ
It worked for me too.


docs(windows): add win-node-env instructions to develop build from source

Description
Same thing as #912 but for develop instructions.
Screenshot (if UI-related)
To-Dos

[ ] Successful build pnpm build
[ ] Translation keys pnpm i18n:extract
[ ] Database migration (if required)

Issues Fixed or Closed

Fixes #XXXX

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

v2.0.0
GitHub release

Your semantic-release bot :package::rocket:


Adding ephemeral nodes to Monsoon

Until now, Typhoon needed Flatcar Container Linux to be installed on a machine in order to start working on it. This impedes the implementation of ephemeral workers, hence the reason for this change. This commit allows one to set a variable enable_install which defaults to true, and boots the machines live without the need of installing Flatcar Container Linux while using a persistent partition for things such as SSH host keys or Kubernetes certificates. The disk used for this persistent partition will either be a disk specified with its path in the controller or worker's definition or the smallest disk available on a given machine as we do not need to store a lot of information. This is done by introducing conditions and logic  in the yaml templates and sending the controller/worker ignition files instead of the install ignition file as well as making some changes to what is done through SSH, transferring it to the ignition file.
This means that, if a worker were to become unhealthy, after investigating the cause of its failure, it can simply be rebooted with an ipmi power reset command or a systemctl reboot and it will be reimaged and reprovisioned with the ignition file, except for some of the persistent data such as some Kubernetes certificates or manifests or SSH host keys.
This Pull Request only affects Monsoon's Flatcar Container Linux and does not change Monsoon's Fedora CoreOS.
This pull request has been tested with the test-suite : bootstrapping works as expected and a worker that is restarted registers in the cluster again after finishing its reboot.

Had to work on this a little, there was an issue where etcd data, which is what is used to store Kubernetes objects in our case, was not persistent, and we would thus lose all our secrets, namespaces and so on when the controller reboots.
Finished fixing this and testing the fix


Register Oceananigans v0.9.4

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/3008
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if Julia TagBot is installed, or can be done manually through the github interface, or via:
git tag -a v0.9.4 -m "<description of version>" 2fea5908f58d6efae49577fb68526d0844eac7d1
git push origin v0.9.4


Feature request to add curved "l" character.

Love everything about this font except "l" character. Is it possible to add curved variant of "l" character ?

Do you have some images as examples of the request?

May be something like jetbrains mono.

Oh hey!
This is one of the modifications made in Serious Shanns:

@jesusmgg as I've said before I kinda like keeping Comic Shanns Mono more faithful to the original Comic Shanns, but if you'd prefer to add this glyph to CSM also I'm always happy to share!
@kkirankk if you're interested in a version that alters several other glyphs as well, give Serious Shanns a shot!


Important Topics

Async Javascript
Difference between == and ===
variable scoping
Local storage and Session storage
Event Listeners , etc...
I will explain in detail, step by step  and also I will add code snippets as well.
I would like to add these , assign this , under hacktoberfest 2024 : )

@Bharath-KumarReddy you can go ahead with your contribution.
Before you start working on your PR, please make sure to:

⭐ Star the repository if you haven't already.
Pull the latest changes to avoid any merge conflicts.
Include the issue number in your PR description for better tracking.

I'm excited to see your contribution as part of Hacktoberfest 2024! 🎉
Don't forget to follow me on GitHub for more updates.
Happy open-source contributing! 🚀

once please check the PR and kindly merge it _hacktoberfest_2024


refactor: dispatcher.Outbound interface was changed

Currently, it is hard to work with a message which is an interface. My suggestion is to separate common fields into the Header structure. It allows us to get common fields easier. Instead of sending an interface we are going send a Headerable message. All messages in the framework should be Headerable.
type Headerable interface {
	MsgID() string
	MsgThread() *decorator.Thread
	MsgType() string
}

The outbound interface looks like follow:
type Outbound interface {
	// Sends the message after packing with the sender key and recipient keys.
	Send(service.Headerable, string, *service.Destination) error

	// Sends the message after packing with the keys derived from DIDs.
	SendToDID(msg service.Headerable, myDID, theirDID string) error

	// Forward forwards the message without packing to the destination.
	Forward(interface{}, *service.Destination) error
}

As you can see Send and SendToDID function were modified.
Instead of receiving an interface we will receive a Headerable message.
The benefits of this change:

messages across the framework will use a common pattern (ID,Type and ThreadID)
this change will be used to count how many messages were sent (needed for the threading e.g sender_order)

Part of #1025
Signed-off-by: Andrii Soluk<EMAIL_ADDRESS>

I think the main issue is that we do not have layer separation.

Lower layer DIDComm messaging should handle DIDComm semantics including threading. The higher layer protocols should not be aware of these details. The lower layer package should be useable independently - as if higher layer protocols do not even exist.
Higher layer protocols should concern themselves with:

their own semantics.
declaring their type.
calling appropriate lower-layer functions (e.g., sending a message, replying on a thread, replying on a parent thread, etc).

This PR has difficulty because the responsibilities are currently inverted. The higher layer protocol embeds the lower layer "header". It then calls Send which marshals whatever is provided (effectively still an empty interface despite changing the type). Instead the higher layer should call Send with a payload and the lower-layer injects into a DIDComm message structure which is then marshalled.


Fix InjectKey of simscreen

So that we can test for special key sequences. Fixes #198.

Thank you!


Updating nav for parent/child relationships

Updated the secondary navigation for parent/child relationships in the passed array
Additions

None

Removals

None

Changes

Updates sidenav macro to utilize @scotchester's child items layout
Updates styles to move border into the gutter space
Updates all vars to move child items under parent
Fixed a few templates with incorrect navs
Fixed an issue where the nav/content divider was too low when ever a breadcrumb existed

Testing

navigate to any secondary page that uses the side-nav on a large screen

Review

@Scotchester
@anselmbradford
@sebworks
@KimberlyMunoz

Preview

Preview this PR without the whitespace changes
Notes

None

Well, the nav works, but I don't see the formatting changes that puts it in the gutter.

@Scotchester @jimmynotjim Could you clarify what the question is? I can't quite follow the convo above.

@schaferjh We're trying to figure out how best to determine what the hidden side navigation heading (for screenreader users) should be.

Ah. I actually think "section navigation" sounds good across the board since it's flexible but accurate.

@schaferjh Good enough for me!

Is there a reason that we aren't using recursion to create the hierarchy. Will it ever be more than two levels?

"Never" is always a dangerous word, but we do not intend to have more than two levels of hierarchy in the left side navigation.

@sebworks The navigation for each section seems to be dissimilar enough to merit not using recursion. With the new backend coming in, recursion could probably be a viable option.

I think this one should be good now as well. Originally we wanted #655 in first, but it looks like that's held up by another PR in Sheer.

Can I get some sign-offs on this one before a new conflict pops up?

:+1:

looks good. Only thing I noticed was that the spacing between the parent and first nav item seemed different than the other nav items.

@sebworks Good catch, not sure what's causing that but I'll fix it.

Take care of the conflicts in the subpage and office vars files before merging.

Fixed spacing issue. Squashing and pulling in conflicting files.

:+1:

Bit of a mess to fix the changelog conflicts. Had to go ahead and push some fixes to refresh and flapjack first to be able to make my updates here. Waiting to hear back from Travis and then will merge.


ci: tests update for pcs-0.12 and pacemaker-3

Enhancement:
Update test scripts to work with the latest pcs and pacemaker versions
Reason:
Result:
Issue Tracker Tickets (Jira or BZ if any):

[citest]

Python Unit Tests / python (ubuntu-24.04, main) is failing due to an issue in pcs that only happens on Ubuntu. This will be fixed in pcs later. All other Python Unit Tests are passing. I'm moving this PR from Draft to Ready so that needed fixes for testing latest cluster versions are not blocked unnecessarily.
This branch is also needed to be merged for #231

[citest bad]

CentOS-10 failures:

tests_cib_constraints_create - Caused by Pacemaker behaving like version 3 while announcing version 2. There is nothing that could be done about that. New release of Pacemaker will fix it.
tests_cib_rsc_op_defaults - Same as tests_cib_constraints_create
tests_sbd_* - Caused by a version mismatch between SBD and Pacemaker. There is nothing that could be done about that. New release of Pacemaker / SBD will fix it.
tests failing with "Error: unable to get cib" on TASK [fedora.linux_system_roles.ha_cluster : Set stonith-watchdog-timeout cluster property in CIB] - I'm not sure what's going on there and why it fails for some tests while passing for others. This error doesn't happen on any of my systems. It may get fixed once new packages get into CentOS.

@tomjelinek how long until there is a new release of pacemaker in the compose?

tests_cib_constraints_create - Caused by Pacemaker behaving like version 3 while announcing version 2. There is nothing that could be done about that. New release of Pacemaker will fix it.
tests_cib_rsc_op_defaults - Same as tests_cib_constraints_create

Correction: the latest pcs is also required for these tests to pass. It should get into the compose shortly, it was built yesterday. I'm also working on fixing these tests - they were originally checking Pacemaker version, which was not a good approach, as it just turned out.

how long until there is a new release of pacemaker in the compose?

Not sure about that. It was built recently, so hopefully in a couple of days.

tests_cib_constraints_create - Caused by Pacemaker behaving like version 3 while announcing version 2. There is nothing that could be done about that. New release of Pacemaker will fix it.
tests_cib_rsc_op_defaults - Same as tests_cib_constraints_create

Correction: the latest pcs is also required for these tests to pass. It should get into the compose shortly, it was built yesterday. I'm also working on fixing these tests - they were originally checking Pacemaker version, which was not a good approach, as it just turned out.

how long until there is a new release of pacemaker in the compose?

Not sure about that. It was built recently, so hopefully in a couple of days.

https://kojihub.stream.centos.org/koji/buildinfo?buildID=71808 - pcs-0.12.0~b1-1.el10 ?
I don't see it in https://mirror.stream.centos.org/10-stream/HighAvailability/x86_64/os/Packages/

[citest]

tests_cib_constraints_create - Caused by Pacemaker behaving like version 3 while announcing version 2. There is nothing that could be done about that. New release of Pacemaker will fix it.
tests_cib_rsc_op_defaults - Same as tests_cib_constraints_create

Correction: the latest pcs is also required for these tests to pass. It should get into the compose shortly, it was built yesterday. I'm also working on fixing these tests - they were originally checking Pacemaker version, which was not a good approach, as it just turned out.

This is fixed now.

how long until there is a new release of pacemaker in the compose?

Not sure about that. It was built recently, so hopefully in a couple of days.

Pacemaker packages are available already - pacemaker-3.0.0-2.el10

https://kojihub.stream.centos.org/koji/buildinfo?buildID=71808 - pcs-0.12.0~b1-1.el10 ? I don't see it in https://mirror.stream.centos.org/10-stream/HighAvailability/x86_64/os/Packages/

Yes, that's the one. Let's wait one more day, buttons have been pushed, hopefully this will make the pcs packages available.

CentOS-Stream-10|ansible-2.17 tests are failing due to broken SBD packages. New packages should be available tomorrow.

https://mirror.stream.centos.org/10-stream/HighAvailability/x86_64/os/Packages/pcs-snmp-0.12.0~b1-1.el10.x86_64.rpm

[citest]

Still waiting for fixed sbd packages

[citest bad]

Fixed SBD packages are available in CentOS Stream 10. Tests are passing.


Bloomsky stopped working

Home Assistant release with the issue: 0.67b0

Last working Home Assistant release (if known): NA
Operating environment (Hass.io/Docker/Windows/etc.):

Component/platform: Bloomsky

Description of problem: Starting this morning, Bloomsky has not been working for me. Here's the error log:
Press the button to load the full Home Assistant log.

2018-04-11 08:51:55 ERROR (MainThread) [homeassistant.setup] Error during setup of component bloomsky
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.6/site-packages/urllib3/connectionpool.py", line 601, in urlopen
    chunked=chunked)
  File "/srv/homeassistant/lib/python3.6/site-packages/urllib3/connectionpool.py", line 346, in _make_request
    self._validate_conn(conn)
  File "/srv/homeassistant/lib/python3.6/site-packages/urllib3/connectionpool.py", line 850, in _validate_conn
    conn.connect()
  File "/srv/homeassistant/lib/python3.6/site-packages/urllib3/connection.py", line 326, in connect
    ssl_context=context)
  File "/srv/homeassistant/lib/python3.6/site-packages/urllib3/util/ssl_.py", line 329, in ssl_wrap_socket
    return context.wrap_socket(sock, server_hostname=server_hostname)
  File "/usr/lib/python3.6/ssl.py", line 407, in wrap_socket
    _context=self, _session=session)
  File "/usr/lib/python3.6/ssl.py", line 814, in __init__
    self.do_handshake()
  File "/usr/lib/python3.6/ssl.py", line 1068, in do_handshake
    self._sslobj.do_handshake()
  File "/usr/lib/python3.6/ssl.py", line 689, in do_handshake
    self._sslobj.do_handshake()
ssl.SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:777)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.6/site-packages/requests/adapters.py", line 440, in send
    timeout=timeout
  File "/srv/homeassistant/lib/python3.6/site-packages/urllib3/connectionpool.py", line 639, in urlopen
    _stacktrace=sys.exc_info()[2])
  File "/srv/homeassistant/lib/python3.6/site-packages/urllib3/util/retry.py", line 388, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='api.bloomsky.com', port=443): Max retries exceeded with url: /api/skydata (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:777)'),))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/setup.py", line 145, in _async_setup_component
    component.setup, hass, processed_config)
  File "/usr/lib/python3.6/concurrent/futures/thread.py", line 56, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/bloomsky.py", line 44, in setup
    BLOOMSKY = BloomSky(api_key)
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/bloomsky.py", line 65, in __init__
    self.refresh_devices()
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/util/__init__.py", line 319, in wrapper
    result = method(*args, **kwargs)
  File "/srv/homeassistant/lib/python3.6/site-packages/homeassistant/components/bloomsky.py", line 72, in refresh_devices
    self.API_URL, headers={AUTHORIZATION: self._api_key}, timeout=10)
  File "/srv/homeassistant/lib/python3.6/site-packages/requests/api.py", line 72, in get
    return request('get', url, params=params, **kwargs)
  File "/srv/homeassistant/lib/python3.6/site-packages/requests/api.py", line 58, in request
    return session.request(method=method, url=url, **kwargs)
  File "/srv/homeassistant/lib/python3.6/site-packages/requests/sessions.py", line 508, in request
    resp = self.send(prep, **send_kwargs)
  File "/srv/homeassistant/lib/python3.6/site-packages/requests/sessions.py", line 618, in send
    r = adapter.send(request, **kwargs)
  File "/srv/homeassistant/lib/python3.6/site-packages/requests/adapters.py", line 506, in send
    raise SSLError(e, request=request)
requests.exceptions.SSLError: HTTPSConnectionPool(host='api.bloomsky.com', port=443): Max retries exceeded with url: /api/skydata (Caused by SSLError(SSLError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:777)'),))
2018-04-11 08:51:55 ERROR (MainThread) [homeassistant.setup] Unable to setup dependencies of camera.bloomsky. Setup failed for dependencies: bloomsky
2018-04-11 08:51:55 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform camera.bloomsky: Could not setup all dependencies.

Same issue here, ended up disabling it looks like something changed on their end.

The SSL certificate at https://api.bloomsky.com expired earlier today - I've raise it elsewhere with them.

Same here, hopefully its back up quickly.

Looks like it is back online.


[poll] ThinData extractor

React to this issue with a "👍🏻" to vote for this feature. Highest voted features will graduate to Actix Web sooner.

https://github.com/actix/actix-web/pull/3446

Graduated in Actix Web v4.9.0 🎉


Make BeamChannel implement Serializable

It is needed, for example, in Android client, to persist list of channels during an Activity re-creation.
Maybe other classes should have this interface, too.

@ttaylorr Please mark as serializable all the types that are referenced by the class' fields. Otherwise serialization mechanism will not work

Will do shortly, or you can take over in the meantime if you'd like. Busy with the deploy today :/

I'm sorry, I have some troubles with my IDE. Please be sure to update all referenced types to the deepmost level. This includes changing some interfaces to Serializable classes (e.g. List -> ArrayList). Thanks

All done!


Disable console.error()

A call to console.error() is present at line 22.
Would be nice to be able to disable it, especially when writing/running tests (can clutter the terminal output).

@tkrotoff If you're running into error.status >= 500, it's kind of an issue and you should look at fixing it to use better status code (>= 500 are server errors). I don't have any comment on whether there should have a flag to disable it though. In production, you definitely want to be notified of this.

i don't mind a flag, but yeah, there's almost no reason these should be logged even in testing since you should be handling them.

As said, I'm not talking about production.
What is your workflow when working on an Express app? As of myself, I do write unit tests for failure cases like:
it('should not create a user without a name', done => {
  request(app).post('/Users/')
    .send({}) // Instead of {name: 'Edgar'}
    .expect(422) // Checks an error occurred
    .end((err, res) => {
      // blabla
    });
});

but then I end up with hundreds of lines like this one in my terminal (*):
error: insert into "Users" default values returning "id" - null value in column "name" violates not-null constraint
    at Connection.parseE (node_modules/pg/lib/connection.js:539:11)
    at Connection.parseMessage (node_modules/pg/lib/connection.js:366:17)
    at Socket.<anonymous> (node_modules/pg/lib/connection.js:105:22)
    at emitOne (events.js:77:13)
    at Socket.emit (events.js:169:7)
    at readableAddChunk (_stream_readable.js:146:16)
    at Socket.Readable.push (_stream_readable.js:110:10)
    at TCP.onread (net.js:523:20)

lines that I don't care about in testing mode: jasmine/mocha already tells me if something is wrong.
(*) that don't occur when console.error() is commented

well 1, that's a server error so it should be logging that error. your app should be silencing the error.
2, it's not a 5xx error, so that that line in this module shouldn't be what's logging the error

@jonathanong

it's not a 5xx error

Pretend you did not see the 422 (I've edited the example) :)

that's a server error [...] your app should be handling the error

I see, my mistake, I should never ever have 5xx errors.
My code lazily pass all PostgreSQL errors to api-error-handler (.query().catch(error => next(error))) without a HTTP status code (so api-error-handler automatically sets it to 500).
Instead I should parse PostgreSQL errors and compute the proper HTTP status code.
To follow with the above example: if someone tries to create a user without a name, I should parse the PostgreSQL error and return 422 because of "Integrity Constraint Violation" (23502) instead of letting api-error-handler returning 500.
Hence my terminal cluttered by logs from api-error-handler, sorry for the bad report.


Swapped the Licensing

As well as master to main. but we can sweep that under the rug this way. no worries buddy.

Why did you make this offer? Because the repository does not have a code؟

Great if that's the case.

Why did you make this offer? Because the repository does not have a code؟

Great if that's the case.

It was more of a metacommentary on the futility of trying to get society to even be able to commit to a standard linguistically without it somehow becoming politically charged? I get the repression from the word, and the muscle memory complaint... feels silly to let it bother the scientific method that permeates all of computer technology.
But when I saw the error in the freedom mismatch for being able to write code in CC0, I thought; please let that be enough humor to make my sarcasm about the difference in main/master to be seen.
I may be over exerting the importance of CC0 licensing to mean "for the good of all mankind" when summed up though. so. grain of salt.

Why did you make this offer? Because the repository does not have a code؟

Great if that's the case.

It was more of a metacommentary on the futility of trying to get society to even be able to commit to a standard linguistically without it somehow becoming politically charged? I get the repression from the word, and the muscle memory complaint... feels silly to let it bother the scientific method that permeates all of computer technology.
But when I saw the error in the freedom mismatch for being able to write code in CC0, I thought; please let that be enough humor to make my sarcasm about the difference in main/master to be seen.
I may be over exerting the importance of CC0 licensing to mean "for the good of all mankind" when summed up though. so. grain of salt.

Hi, I translated with Google Translator and found your reaction harsh! Sir, I did not intend to dare at all, I just wanted to know the reason for your order, which I realized a few moments later and answered.
Of course, it is possible that I was wrong and so are you! Because Google Translator does not work well with the Persian language yet!

Probably Best to assume neither of us has a more correct than the other
attitude then. I like your poised response.
I’ll work on my…
https://www.thesaurus.com/browse/overzealous
…Attitude problem.
On Mon, Aug 9, 2021 at 15:43 komeil parseh @.***> wrote:

Why did you make this offer? Because the repository does not have a code؟
Great if that's the case.
It was more of a metacommentary on the futility of trying to get society
to even be able to commit to a standard linguistically without it somehow
becoming politically charged? I get the repression from the word, and the
muscle memory complaint... feels silly to let it bother the scientific
method that permeates all of computer technology.
But when I saw the error in the freedom mismatch for being able to write
code in CC0, I thought; please let that be enough humor to make my sarcasm
about the difference in main/master to be seen.
I may be over exerting the importance of CC0 licensing to mean "for the
good of all mankind" when summed up though. so. grain of salt.
Hi, I translated with Google Translator and found your reaction harsh!
Sir, I did not intend to dare at all, I just wanted to know the reason for
your order, which I realized a few moments later and answered.
Of course, it is possible that I was wrong and so are you! Because Google
Translator does not work well with the Persian language yet!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kelseyhightower/nocode/pull/4522#issuecomment-895491147,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJFASHTQYWXNN4HT4QNMSJDT4AVW5ANCNFSM465DV2AA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.


Instruction for build

Hi @jadarve,
I would like to try lluvia. I tried compiling using CMake without success as some files cannot be found.
Is there any plan on adding build and installation instruction?
Thank you!

Hey @xEnVrE
I changed the build system from CMake to Bazel a while ago, but I still have not removed the CMakeLists files.
You can follow the instructions at https://lluvia.io/en/latest/installation.html for compiling the library for Linux.
The documentation for how to actually use lluvia is lacking at the moment :( I need to do more work on that side. Check the optical flow demo to get an idea on how to use it: https://github.com/jadarve/lluvia/blob/master/samples/opticalFlow/python/opticalFlow.py
Let me know your specific case and I can help you.
Cheers.

Hi @jadarve,
thank you for the information. I also had the possibility to try the optical flow algorithm from the old implementation repository.


Autogenerated type CssVersionParam

hanna-css
Typescript type CssVersionParam added to autogenerated style-server-info.ts from built step and then used in CssBundleOpts type in getCssBundleUrl url.

@kristjanjoksig check out the madditions I pushed in the above two commits


Add lang documentation

A harmless PR mainly for the purposes of helping Quinn out in learning the repository. All it does is adds documentation on building, testing and packaging @squiggle/lang. It also adds some build files required to package using typescript.

Nice! Happy to see the documentation, we probably could use READMEs for each package, at some point.


Computed properties should return null value by default

sl-modal does not have any computed properties

@theoshu addon/components/sl-modal-header.js does - it is part of the sl-modal ecosystem

Oops. Glad I put the comment in.


Do not show the language selection menu at every start

Hello,
since most users will only learn one language at a time I think it would be better to save the currently studied language and add an option in the main menu to change the studied language. This way the user does not need to select his language at every start.

Good idea; actually I was thinking about removing the language selecting menu altogether; what do you think about this?


Fix another small typo

Thanks again! Don't hesitate to send a PR if you see other issues. Maintaining documentation is hard :)


⚠ Bofrost.at has degraded performance

In 1728d6d, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1245 ms

Resolved: Bofrost.at performance has improved in 299ba9c.


Include date when PrettyPrinter(printTime: true)

PrettyPrinter only prints the time of a log event, but not the date, and I think it would be very useful to get that information.
Perhaps it could be even more configurable by adding a printDate parameter, so things remain backwards compatible.

Hi, good idea!
I tried to create a customizable but still backwards-compatible API for a custom DateTime format.
Could you please check out the date_time_format branch and let me know if this would fulfill your use-case? (feel free to provide other feedback as well)
You should be able to just add this to your pubspec.yaml:
dependency_overrides:
  logger:
    git:
      url: https://github.com/SourceHorizon/logger
      ref: date_time_format

Hey! Yes, I think that is a pretty cool feature. It's nice that you have the power to format it however you like but you also get some defaults to choose from. Thanks!

Thanks for the nice feedback, that's exactly what I was aiming for.
Since this isn't yet in the main branch, I would like to keep the issue open until it is merged.


Request

Can I make a request for a feature?
Add some custom data to the widget setting
and be able to show only those with that setting
ie
    'model' => $model,
'language' => 'de',
'languageStrict' => TRUE,
    'relatedTo' => 'User...

This stores de in the record field 'language'
if languageStrict== TRUE then it only shows those records where the languageis the same (de)
if languageStrict== FALSE it shows ALL the records (like current)
This way people can easy implement  multilingual
I could ofcourse copy your code and modify it...but this way more people can benefit from your work

Hi, i'm not sure that this functionality is needed for the basic comments widget. You can override the comment model and implement this feature for your own project.
@disem what do you think about this feature?


Using a createStore array with createContext

Describe the bug
I have been trying to wrap my head around this one for quite some time, but I cannot seem to find the issue.
Let's start with some code:
type ColumnType = Store<{
    name: string
    validator: string
}>;

type ColumnContextType = [
    Array<ColumnType>,
    {
        addCol: (name: string, validator: string) => void
    }
];

export const ColumnContext = createContext<ColumnContextType>([
    [],
    {
        addCol: () => undefined,
    },
]);

export const ColumnProvider: Component<{
    name: string;
    validator: string;
}> = (props) => {
    const a: Array<ColumnType> = [{
        name: props.name,
        validator: props.validator,
    }];
    const [state, setState] = createStore(a);

    const addCol = (name: string, validator: string) => {
        // todo
    };

    return (
        <ColumnContext.Provider value={[state, { addCol }]}>
            {props.children}
        </ColumnContext.Provider>
    );
};

When setting up the FieldContext.Provider, the state variable complains with the following error:
The type 'readonly { readonly name: string; readonly validator: string; }[]' is 'readonly' and cannot be assigned to the mutable type '{ readonly name: string; readonly validator: string; }[]'.

Your Example Website or App
N/A
Steps to Reproduce the Bug or Issue
N/A
Expected behavior
It should work, and it does work if I scrap the array, but for some reason using an array just doesn't want to play nice regardless of what I do.
Screenshots or Videos
No response
Platform
Using Solidjs  1.3.10
Additional context
No response

Sorry for the delay here. Is this a TS problem only?
Top level arrays in state have limitations since you can't listen to the array itself since the state object itself isn't reactive. So like it is unsuitable for iteration where entries can be added/removed. You are better nesting the array under a property. However, it should still "work" for existing indexes.
What I am seeing from the error is it is complaining about the difference between readonly and mutable types. Stores are treated as readonly types so I imagine that bug might be a red herring. Simply a type mismatch.

Use ReadonlyArray instead of Array, or instead type the array as the store instead of the array's contents only:
type ColumnType = {
    name: string
    validator: string
};

type ColumnContextType = [
    Store<Array<ColumnType>>,
    {
        addCol: (name: string, validator: string) => void
    }
];

Without further information I believe the solution has been provided. Closing.