[BUG] Issues running the batch_to_eopatch pipeline

Question
I have successfully run the batch download pipeline and would like to convert the batch tiles to eopatches. After locally fixing #12 I've managed to run the batch_to_eopatch pipeline, but I get the following exception in the logs:
Summary of exceptions

    LoadUserDataTask (LoadUserDataTask-29825b248e7b11ecbc3b-f57730fc0853):
        14 times:

        TypeError: execute() missing 1 required positional argument: 'eopatch'

Which is weird, because the LoadUserDataTask is the first Task and no eopatch arguments should be expected.
Here is my config:
{
  "pipeline": "eogrow.pipelines.batch_to_eopatch.BatchToEOPatchPipeline",
  "folder_key": "data",
  "mapping": [
    {"batch_files": ["B01.tif"], "feature_type": "data", "feature_name": "B01", "multiply_factor": 1e-4},
    {"batch_files": ["B02.tif"], "feature_type": "data", "feature_name": "B02", "multiply_factor": 1e-4},
    {"batch_files": ["B03.tif"], "feature_type": "data", "feature_name": "B03", "multiply_factor": 1e-4},
    {"batch_files": ["B04.tif"], "feature_type": "data", "feature_name": "B04", "multiply_factor": 1e-4},
    {"batch_files": ["B05.tif"], "feature_type": "data", "feature_name": "B05", "multiply_factor": 1e-4},
    {"batch_files": ["B06.tif"], "feature_type": "data", "feature_name": "B06", "multiply_factor": 1e-4},
    {"batch_files": ["B07.tif"], "feature_type": "data", "feature_name": "B07", "multiply_factor": 1e-4},
    {"batch_files": ["B08.tif"], "feature_type": "data", "feature_name": "B08", "multiply_factor": 1e-4},
    {"batch_files": ["B8A.tif"], "feature_type": "data", "feature_name": "B8A", "multiply_factor": 1e-4},
    {"batch_files": ["B09.tif"], "feature_type": "data", "feature_name": "B09", "multiply_factor": 1e-4},
    {"batch_files": ["B10.tif"], "feature_type": "data", "feature_name": "B10", "multiply_factor": 1e-4},
    {"batch_files": ["B11.tif"], "feature_type": "data", "feature_name": "B11", "multiply_factor": 1e-4},
    {"batch_files": ["B12.tif"], "feature_type": "data", "feature_name": "B12", "multiply_factor": 1e-4},
    {"batch_files": ["CLP.tif"], "feature_type": "data", "feature_name": "CLP", "multiply_factor": 0.00392156862745098},
    {"batch_files": ["CLM.tif"], "feature_type": "mask", "feature_name": "CLM"},
    {"batch_files": ["dataMask.tif"], "feature_type": "mask", "feature_name": "dataMask"}
  ],
  "userdata_feature_name": "BATCH_INFO",
  "userdata_timestamp_reader": "eogrow.utils.batch.read_timestamps_from_orbits",
  "**global_settings": "${config_path}/sentinel2_l1c_batch_config.json"
}

Let me know if you need to see what sentinel2_l1c_batch_config.json looks like.

Ah, the eopatch is Optional[EOPatch] but apparently we forgot to add a default value.

Thanks for the hint. I tried setting the default to None and got a new error:
❯ eogrow 01_batch_to_eopatch.json
INFO eogrow.core.pipeline:216: Running BatchToEOPatchPipeline
INFO eogrow.core.area.base:176: Loading grid from cache/grid_test_area_BatchAreaManager_0.2_0.004_1_10.0_0.gpkg
INFO eogrow.core.pipeline:159: Searching for Ray cluster
INFO eogrow.core.pipeline:164: No cluster found, pipeline will not use Ray.
INFO eogrow.core.pipeline:174: Starting EOExecutor for 14 EOPatches
  0%|                                                                                | 0/14 [00:00<?, ?it/s]Warning 1: TIFFReadDirectory:Sum of Photometric type-related color channels and ExtraSamples doesn't match SamplesPerPixel. Defining non-color channels as ExtraSamples.
Warning 1: TIFFReadDirectory:Sum of Photometric type-related color channels and ExtraSamples doesn't match SamplesPerPixel. Defining non-color channels as ExtraSamples.
Warning 1: TIFFReadDirectory:Sum of Photometric type-related color channels and ExtraSamples doesn't match SamplesPerPixel. Defining non-color channels as ExtraSamples.
  0%|                                                                                | 0/14 [00:04<?, ?it/s]
Traceback (most recent call last):
  File "/Users/mlubej/.pyenv/versions/surs/bin/eogrow", line 33, in <module>
    sys.exit(load_entry_point('eo-grow', 'console_scripts', 'eogrow')())
  File "/Users/mlubej/.pyenv/versions/3.8.7/envs/surs/lib/python3.8/site-packages/click/core.py", line 1128, in __call__
    return self.main(*args, **kwargs)
  File "/Users/mlubej/.pyenv/versions/3.8.7/envs/surs/lib/python3.8/site-packages/click/core.py", line 1053, in main
    rv = self.invoke(ctx)
  File "/Users/mlubej/.pyenv/versions/3.8.7/envs/surs/lib/python3.8/site-packages/click/core.py", line 1395, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/Users/mlubej/.pyenv/versions/3.8.7/envs/surs/lib/python3.8/site-packages/click/core.py", line 754, in invoke
    return __callback(*args, **kwargs)
  File "/Users/mlubej/work/projects/sh-project/eo-grow/eogrow/cli.py", line 80, in main
    pipeline.run()
  File "/Users/mlubej/work/projects/sh-project/eo-grow/eogrow/core/pipeline.py", line 220, in run
    finished, failed = self.run_procedure()
  File "/Users/mlubej/work/projects/sh-project/eo-grow/eogrow/core/pipeline.py", line 263, in run_procedure
    finished, failed, _ = self.run_execution(workflow, exec_args)
  File "/Users/mlubej/work/projects/sh-project/eo-grow/eogrow/core/pipeline.py", line 185, in run_execution
    execution_results = executor.run(**executor_run_params)
  File "/Users/mlubej/work/projects/sh-project/eo-learn/core/eolearn/core/eoexecution.py", line 187, in run
    full_execution_results = self._run_execution(processing_args, workers, processing_type)
  File "/Users/mlubej/work/projects/sh-project/eo-learn/core/eolearn/core/eoexecution.py", line 219, in _run_execution
    return submit_and_monitor_execution(process_executor, self._execute_workflow, processing_args)
  File "/Users/mlubej/work/projects/sh-project/eo-learn/core/eolearn/core/eoexecution.py", line 398, in submit_and_monitor_execution
    results[future_order[future]] = future.result()
  File "/Users/mlubej/.pyenv/versions/3.8.7/lib/python3.8/concurrent/futures/_base.py", line 432, in result
    return self.__get_result()
  File "/Users/mlubej/.pyenv/versions/3.8.7/lib/python3.8/concurrent/futures/_base.py", line 388, in __get_result
    raise self._exception
concurrent.futures.process.BrokenProcessPool: A process in the process pool was terminated abruptly while the future was running or pending.
Error in atexit._run_exitfuncs:
Traceback (most recent call last):
  File "/Users/mlubej/.pyenv/versions/3.8.7/lib/python3.8/logging/__init__.py", line 2123, in shutdown
    h.close()
  File "/Users/mlubej/work/projects/sh-project/eo-grow/eogrow/core/logging.py", line 253, in close
    self.local_file.close()
  File "/Users/mlubej/work/projects/sh-project/eo-grow/eogrow/utils/fs.py", line 90, in close
    self.copy_to_remote()
  File "/Users/mlubej/work/projects/sh-project/eo-grow/eogrow/utils/fs.py", line 103, in copy_to_remote
    fs.copy.copy_file(self._filesystem, self._local_path, self._remote_filesystem, self._remote_path)
  File "/Users/mlubej/.pyenv/versions/3.8.7/envs/surs/lib/python3.8/site-packages/fs/copy.py", line 142, in copy_file
    copy_file_if(
  File "/Users/mlubej/.pyenv/versions/3.8.7/envs/surs/lib/python3.8/site-packages/fs/copy.py", line 221, in copy_file_if
    copy_file_internal(
  File "/Users/mlubej/.pyenv/versions/3.8.7/envs/surs/lib/python3.8/site-packages/fs/copy.py", line 277, in copy_file_internal
    _copy_locked()
  File "/Users/mlubej/.pyenv/versions/3.8.7/envs/surs/lib/python3.8/site-packages/fs/copy.py", line 270, in _copy_locked
    dst_fs.upload(dst_path, read_file)
  File "/Users/mlubej/.pyenv/versions/3.8.7/envs/surs/lib/python3.8/site-packages/fs_s3fs/_s3fs.py", line 774, in upload
    self.client.upload_fileobj(
  File "/Users/mlubej/.pyenv/versions/3.8.7/envs/surs/lib/python3.8/site-packages/boto3/s3/inject.py", line 537, in upload_fileobj
    future = manager.upload(
  File "/Users/mlubej/.pyenv/versions/3.8.7/envs/surs/lib/python3.8/site-packages/s3transfer/manager.py", line 329, in upload
    return self._submit_transfer(
  File "/Users/mlubej/.pyenv/versions/3.8.7/envs/surs/lib/python3.8/site-packages/s3transfer/manager.py", line 524, in _submit_transfer
    self._submission_executor.submit(
  File "/Users/mlubej/.pyenv/versions/3.8.7/envs/surs/lib/python3.8/site-packages/s3transfer/futures.py", line 474, in submit
    future = ExecutorFuture(self._executor.submit(task))
  File "/Users/mlubej/.pyenv/versions/3.8.7/lib/python3.8/concurrent/futures/thread.py", line 181, in submit
    raise RuntimeError('cannot schedule new futures after '
RuntimeError: cannot schedule new futures after interpreter shutdown

We discovered that the issue is not in multithreading but instead lies in reading tiffs with ImportFromTiffTask. Investigating further.

Fixed in https://github.com/sentinel-hub/eo-grow/pull/15


Why we cannot define two networks in the same graph when they are trained independently

Please make sure that this is a feature request. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:feature_template
System information

TensorFlow version (you are using): 1.4.1
Are you willing to contribute it (Yes/No): No

Describe the feature and the current behavior/state.
Why we cannot define two networks in the same graph when they are trained independently.
It can be done only using two different grpahs.
Will this change the current api? How?
No, just allow to define two networks in the same graph that have to be trained independently.
Who will benefit with this feature?
Developers and production code. Because it's time and memory consuming to create two graphs.
Any Other info.

@Firyuza,
Here is the work-around, please try from your end.
Please try to make a separate graph for each network to run them in parallel in different sessions:
graph1 = tf.Graph()
with graph1.as_default():
  model1 = build_model()

graph2 = tf.Graph()
with graph2.as_default():
  model2 = build_model()

the build_model() defines all placeholders, variables and training ops. Both models should use the same naming for variables, which will allow them to swap easily.
Each network can be trained using a snapshot of the other network for the target (the latest or previous best). Periodically, each network is saved to the disk via tf.Saver() and restored using the weights of one of the networks.  Thank you!


Issue with argo-cd upgrade

Chart: snapshot-controller:4.0.0
Default values
Getting the following errors
apiextensions.k8s.io/v1/CustomResourceDefinition
linstor
volumegroupsnapshotclasses.groupsnapshot.storage.k8s.io
SyncFailed
CustomResourceDefinition.apiextensions.k8s.io "volumegroupsnapshotclasses.groupsnapshot.storage.k8s.io" is invalid: status.storedVersions[0]: Invalid value: "v1alpha1": must appear in spec.versions
apiextensions.k8s.io/v1/CustomResourceDefinition
linstor
volumegroupsnapshotcontents.groupsnapshot.storage.k8s.io
SyncFailed
CustomResourceDefinition.apiextensions.k8s.io "volumegroupsnapshotcontents.groupsnapshot.storage.k8s.io" is invalid: status.storedVersions[0]: Invalid value: "v1alpha1": must appear in spec.versions
apiextensions.k8s.io/v1/CustomResourceDefinition
linstor
volumegroupsnapshots.groupsnapshot.storage.k8s.io
SyncFailed
CustomResourceDefinition.apiextensions.k8s.io "volumegroupsnapshots.groupsnapshot.storage.k8s.io" is invalid: status.storedVersions[0]: Invalid value: "v1alpha1": must appear in spec.versions

Even when I attempt to replace and force

Looks like this is something done intentionally by the upstream project :facepalm:

This PR entirely removes the capability to serve the v1alpha version. Existing clients will be broken.
This is consistent with the https://github.com/kubernetes-csi/external-snapshotter/pull/1150#discussion_r1852973872 and the related https://github.com/kubernetes-csi/external-snapshotter/pull/1150#discussion_r1853037522.

Note: I closed this issue here, as this is not really the place to fix the issue. If there are any workarounds found, they can still be added here.

See: https://github.com/kubernetes-csi/external-snapshotter/pull/1150#issuecomment-2557947586

I guess we could try to configure a pre-upgrade or pre-install hook for this :thinking:


Undefined body on error

Information

Version: 5.x
Type: Story

Description
All error returns using the GlobalErrorHandlerMiddleware have their body undefined, i want to be able to see the body on these requests. I think we don't need it for 500 errors, but adding the line bellow can solve this problem
Example
if (error instanceof Exception || error.status) {
      request.log.error({
        error: {
          body: request.body,
          message: error.message,
          stack: error.stack,
          status: error.status,
          origin: error.origin
        }
      });

      this.setHeaders(response, error, error.origin);

      response.status(error.status).send(toHTML(error.message));

      return;
    }

Or do it optional when someone use an overridlemiddleware, something like this:
Example
@OverrideMiddleware(GlobalErrorHandlerMiddleware)
export class OverrideGlobalErrorHandler extends GlobalErrorHandlerMiddleware {

    constructor() {
        super();
    }

    use(@Err() error: any,
        @Req() request: Req,
        @Res() response: Res): any {

        error = {
              ...error,
              body: request.body
        }
        return super.use(error, request, response);
    }
}

and then on Global:
Example

if (error instanceof Exception || error.status) {
      request.log.error({
        error: {
          body: error.body || undefined,
          message: error.message,
          stack: error.stack,
          status: error.status,
          origin: error.origin
        }
      });

      this.setHeaders(response, error, error.origin);

      response.status(error.status).send(toHTML(error.message));

      return;
    }

Any thoughts on it?

Hello @striquer,
Log body and other parameters aren't a good idea by default. LogIncomingRequestMiddleware log some data but it's configurable. We can add extra settings to add extra data in the GlobalErrorHandlerMiddleware also.
Override middleware are right now the best solution if you have to customize error before logging.
See you
Romain

Hello again, i was looking in the LogIncomingRequestMiddleware and i think there is an error with the output. The params that i set into the serversettings doesn't match the output result and i think i know why.
If you look in this function:
minimalRequestPicker(request) {         const { fields = LogIncomingRequestMiddleware_1.DEFAULT_FIELDS } = this.injector.settings.logger;         const info = this.requestToObject(request);         return fields.reduce((acc, key) => {             acc[key] = info[key];             return acc;         }, {}); }
It's expecting an field called fields from the server settings, but on the server settings it's defined to requestFields:
logger: {         debug: false,         logRequest: true,         requestFields: ["reqId", "method", "url", "headers", "body", "query", "params", "duration"] }
I tested and if you replace that fields to requestFields it'll work with the server settings configuration

Hoo... can you make a pr ? Thanks for your investigation ;)

Sure, will do it. Thanks

Thanks a lot ;)


Make TaskRunner stateless component.

It is better and looks cleaner.

@dragfire nice. Could you just please make it a function instead?
function TaskRunner(props) { ... }


:clown_face: Chore: COmment out errors test scripts

Description
Concise description of proposed changes
Testing
Explain the quality checks that have been done on the code changes
Additional Information

[ ] I read the contributing docs (if this is your first contribution)

Your ENS/address:

#1455
#1454  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @roninjin10 and the rest of your teammates on  Graphite


Fix singularities in Quat::to_euler()

Quat::to_euler() has issues when the second rotation is (near) PI/2 or -PI/2 radians, causing the first and third angles to be incorrectly calculated.
This PR addresses this issue for all supported order of rotations. It favors angles on the first axis over the third axis (e.g., a quaternion constructed from euler angles (a, PI/2, b) will convert back to either (a+b, PI/2, 0) or (a-b, PI/2, 0), depending on the requested order). In any way, converting a quaternion to euler angles and back to a quaternion will always yield the original quaternion, barring any rounding errors.

@oisyn Looks like quite a few unit tests are failing with this new code, would be worth investigating.

Yeah I know, it's wasm failing because of rounding errors. Very weird.


Update install-azure-cli-windows.md

fixes MicrosoftDocs/azure-docs-cli#3101

#sign-off

This is missing other folders that are used by cli like cliextensions and other files specific to az cli.

Great catch here @RyanHill-MSFT. Thank you!


migrate storage to AWS S3

migrate storage from Supabase to AWS S3 to levarage more stable APIs and ecosystem

I'll close it for now. we're not facing any important issue with Supabase storage


Enable the floating point unit

Hi Chris (@ckormanyos),
In this pull-request the FPU is enabled and the compiler flags is set accordingly to support the target RISC-V extension.
According to the Hardware instruction set register (misa) the ISA is rv32imafcxw :

but the toolchain issue an error when I use -march=rv32imafcxw:
Error: x ISA extension `xw' must be set with the versions
As I don't have this information, I just used -march=rv32imafc.
I tested the FPU on the debugger it gave the expected result, I committed the test code in main() as example we can delete it later together with the dummy C++ class that I added just to verify that ctor initialization is working.
@gdobato @sajtkukac

Hi Amine (@Chalandi) as usual you are moving fast and it's challenging to keep up.
The code and flags look good to me. I still need to get my target running. At that later time we can run some even more demanding FP-benchmarks on 4-byte float. At the moment, however, this will still take a couple of days.
I had applied branch protection yesterday which isno longer compatible to the name of the single run in CI. I just corrected this problem.
Since this is a really strong step forward in theis PR, let's commit this and return for more dedicated FP-benchmarks at a later point in time.


Not working on AWS EC2

I tried to run the repo on an EC2 instance with Ubuntu OS but the web interface is stuck and showing the progress circle.

me too...

the problem is in the key and secret key of binance.
edit the .env and check if it is correct.

It runs perfectly on my windows machine with the same keys!

@edebie please check your docker status.
$ docker ps -a

And if there is anything wrong with the container, check the log.
Refer this wiki page  - https://github.com/chrisleekr/binance-trading-bot/wiki/Troubleshooting#how-to-get-the-logs-by-installing-bunyan-npm-package

Thanks @chrisleekr
The log was showing a wrong api key. I copied it again from binance account into e.nv file and recompiled it and it is working now!


Updated README.md

Digital Clock with Js #557
Close #557
Checklist:

[x] I have mentioned the issue number in my Pull Request.
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have created a helpful and easy to understand README.md

@pranjay-poddar  pls review and add hacktoberfest labels to pull request.

updating readme of existing projects is not the aim of this repository on valid code contributions or legitimate amount of low level code are accepted.


I can't download PreTrained weights from GoogleDrive!

Hi,
Thanks for your wonderful contribution.
I'm using Google Colab..
I've used this command.
!python ./script/Download_data.py 1f_w7HQxTfXGxOPrkriu7jTyCTC-KPEH3 Weights/TIN_HICO.zip
!python ./script/Download_data.py 1iU9dN9rLtekcHX2MT_zU_df3Yf0paL9s/Weights/TIN_VCOCO.zip
i got this error!
Traceback (most recent call last):
File "./script/Download_data.py", line 52, in
download_file_from_google_drive(file_id, destination)
File "./script/Download_data.py", line 40, in download_file_from_google_drive
save_response_content(response, destination)
File "./script/Download_data.py", line 24, in save_response_content
with open(destination, "wb") as f:
FileNotFoundError: [Errno 2] No such file or directory: 'Weights/TIN_HICO.zip'
Traceback (most recent call last):
File "./script/Download_data.py", line 52, in
download_file_from_google_drive(file_id, destination)
File "./script/Download_data.py", line 40, in download_file_from_google_drive
save_response_content(response, destination)
File "./script/Download_data.py", line 24, in save_response_content
with open(destination, "wb") as f:
FileNotFoundError: [Errno 2] No such file or directory: 'Weights/TIN_VCOCO.zip'
Thanks in advance.

Hi,
I have tried the link and they are all alive. Maybe you could try to create the folder "Weights", then run the script. Or you could try to download the files using:
https://drive.google.com/open?id=1f_w7HQxTfXGxOPrkriu7jTyCTC-KPEH3
https://drive.google.com/open?id=1iU9dN9rLtekcHX2MT_zU_df3Yf0paL9s

BTW
"1iU9dN9rLtekcHX2MT_zU_df3Yf0paL9s/Weights/TIN_VCOCO.zip" is "1iU9dN9rLtekcHX2MT_zU_df3Yf0paL9s /Weights/TIN_VCOCO.zip"

Thanks DirtyHarryLYL!
I forgot to create Weights folder.
now, above code is working.


Link to stream backport library

Hi, I am a great fan of retrolambda and I have been using it for months, thanks so much for this great tool.
Recently I found another interesting library which goes very well with Retrolambda, namely streamsupport, a backport of Java8 stream API (http://sourceforge.net/projects/streamsupport/). I think this might be useful for many users of Retrolambda, and I was wondering if you could add a link to the readme, I think that project would deserve more attention.
Anyway, thanks so much for retrolambda!

Sounds like a good idea as both libraries complement each other.

Done. I also mention the ThreeTen project there. Are there also others?


Adding a border to ct-grids

Hello,
I am trying to add a border to the ct-grids
As you can see here : http://s14.postimg.org/tr5tdzb8x/chartist.jpg
It isn't working :(
Any other way to add a border around that area.
Thanks :)

Hi there. SVG elements cant have border. Usually you talk about strokes on SVG paths. However, group elements like the ct-grids element, can't have fills and strokes. You will need to create your own element using events. This is very easy to do: http://jsbin.com/kakixe/edit?html,js,output

Please reopen if you're not ok with the solution outlined in the bin.


Play/pause button doesn't look like play/pause button

Pause button looks like a lot of lines in a sort of pause button formation, play button looks like a triangle with a bite out of it with 2 other lines

Remove bloom.js from config-xpui and re-apply.

Duplicate of #102

It was a conflict with fluent, removed fluent.js and it's fixed now. So not a bloom.js issue, but still thanks for helping me fix it


move dummy_parent_id to scratch

I use several layout algorithms in  a project, where the user can choose out of a list of layouts. For the case-bilkent layout I recognized an added property in the data section of nodes called dummy_parent_id and sometimes tempchildren.
This messes up the data-editor as my app assumes that only clean data is stored there. Cytoscape.JS has a scratch-store for such things, that to my opinion is much more suitable in this particular case.
I made some small modifications in order to store the data in scratch instead of data.

@bastiion Great!  Scratchpad data is definitely the right approach.  One small thing though: The scratch data should be namespaced, e.g. ele.scratch('coseBilkent') = {} ...  Otherwise, you can collide with other extensions.

@maxkfranz would it be sufficient to prefix the namespace like coseBilkent_dummy_parent_id and coseBilkent_temp_children?

It's safer to use a separate object, because that's what's encouraged in the documentation.  Each extension is supposed to be able to assume it can use it's camelcase name for an object, and there are no guarantees of collision avoidance otherwise.

@bastiion thanks for your contribution. I have relased '1.3.8' after merging this PR.


OK button is greyed out

this page does not mention what might be the issue, if when selecting the column to be the date column, and it even passes validation.. the OK button is still greyed out.

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

ID: 09750051-75cf-7829-b70b-8912f822ea8c
Version Independent ID: b761024d-5166-47db-9c19-410073e5f46e
Content: Set and use date tables in Power BI Desktop - Power BI
Content Source: powerbi-docs/transform-model/desktop-date-tables.md
Service: powerbi
Sub-service: pbi-transform-model
GitHub Login: @davidiseminger
Microsoft Alias: davidi

Thanks for your comment, @rderidder-lda. This issue has been assigned to the doc author for review.

Thanks for your post, this sounds like a technical and feature question best answered by the community or support. If you need technical support, you might find a solution in the Power BI Community, found at https://community.powerbi.com. If not, you can get support by going to https://support.powerbi.com.


Request: Method to get available countries and states

Hi
Would you mind adding a method to get the available countries, their ISO code and states for that country?
I'm planning to use this dynamically instead of limiting it to a single country, so that would help a lot!
Thanks in advance

It seems that you are not the only one: https://stackoverflow.com/q/70237552/2988730
You can get what you want with something like this:
for cname in holidays.list_supported_countries():
    country = getattr(holidays, cname)()
    if cname != country.country:
        continue
    # Do stuff with country object
    if hasattr(country, 'PROVINCES'):
        # Do stuff with provinces
    if hasattr(country, 'STATES'):
        # Do stuff with states

Yes, this is being discussed in #575 .. please follow up there!
Thx cheers


Power issue

My power doesn't come trough Tesseract to ultimate cables, to fix it I must replace the cables...
Cables just stop working after chunks get unloaded, no power goes into those. It might be same with mechanical pipes.

I'm experiencing this as well, although some tesseracts still work, but only ones that were placed before the issue arose. It seems to have occurred in one of the recent Resonant Rise 3 updates (that's the modpack I'm running).
All in all, I'm having some extremely odd problems with my Mekanism power network.

My induction matrix outputs no power. It's a 4x4x4 matrix (including the casing) with 7 basic cells and 1 advanced provider. It's got 8 ports on 2 sides, 4 on each. One side is connected to my power plant, and I've tried drawing power from the other side, but to no avail. It's filling up with power from my power plant just fine, but I can't get any power back out of it.

Since I exchanged my 8 ultimate energy cubes with the induction matrix, no power has been going into my tesseract power network, obviously, since no power comes out of the induction matrix. I've even removed the tesseract connected to the induction matrix. However, I have at least one network being fed power from a tesseract on that frequency. It appears that infinite power is somehow being generated out of thin air.

Tesseracts are strange in the way they handle power.  You could try setting the cable to output mode- if that doesn't work then I'll take a look at this again.


Userbar errors after refreshing script.

Issue Summary

An error occurs after reloading the page (No hard refresh!) and the userbar script gets evaluated a second time.
This causes the userbar to behave buggy in general, or even disappear!
It will also cause the accessibility tab to not be responsive, as in you click it - nothing happens.
Steps to Reproduce

Setup SPA
Add userbar into template
re-execute the userbar script to update the current page's url. (am using htmx, userbar is included in template, script gets executed automatically)
error occurs

Any other relevant information. For example, why do you consider this a bug and what did you expect to happen instead?

The error occurs in the userbar.js sourcecode.

Technical details
userbar.js?v=7f96c3e7:2 Uncaught DOMException: Failed to execute 'define' on 'CustomElementRegistry': the name "wagtail-userbar" has already been used with this registry
    at 4917 (http://<IP_ADDRESS>:8080/static/wagtailadmin/js/userbar.js?v=7f96c3e7:2:499558)
    at n (http://<IP_ADDRESS>:8080/static/wagtailadmin/js/userbar.js?v=7f96c3e7:2:499700)
    at http://<IP_ADDRESS>:8080/static/wagtailadmin/js/userbar.js?v=7f96c3e7:2:501100
    at n.O (http://<IP_ADDRESS>:8080/static/wagtailadmin/js/userbar.js?v=7f96c3e7:2:499982)
    at http://<IP_ADDRESS>:8080/static/wagtailadmin/js/userbar.js?v=7f96c3e7:2:501114
    at http://<IP_ADDRESS>:8080/static/wagtailadmin/js/userbar.js?v=7f96c3e7:2:501120

customElements.define("wagtail-userbar", s) is the line which causes the error.

Are you sure the script isn't being run twice in the same session?
Can you provide some of the template code in your bug report?
You say you're using an SPA and htmx, is htmx driving the SPA experience? Or is some other tech doing this (such as React).
It may be helpful to get some of the html from your main template, if you're using htmx swap with a region of the DOM that includes the Userbar script, maybe this is being patched in / swapped on a URL change.
Maybe you can try to ensure that the userbar script template tag is only included in a region of the DOM that won't change.
Either way, more information is going to be needed to reproduce this, 'setup SPA' as a step to reproduce is very ambiguous.


Bot not making sound

when i start the bot and play a song, the bot doesn't make any noise.
My volume is set to default

Nvm, started working when i shutdown the bot and relaunched it for some reason and iv done that a few times before.


[Troubleshooting] Errors that occur during NNTrainer learning after TFlite export

in case of below, nntrainer get error
model->compile();
model->initialize();
model->exports(ml::train::ExportMethods::METHOD_TFLITE, "Exported.tflite");
model->train();

Make some exception, and make robust for this case

:octocat: cibot: Thank you for posting issue #2256. The person in charge will reply soon.

yes i tried this method too for tflite export to didnt work caused error


ubuntu apt can't get lastest vscode

VSCode reminded me there is an available update, but I can't update it use apt on ubuntu.
The latest version is 1.41.0, but apt tell me it's 1.40.2
l@leviniepc:/etc/apt$ apt list -a code
Listing... Done
code/now 1.40.2-1574694120 amd64 [installed,local]
https://code.visualstudio.com/
Version 1.41 is now available! Read about the new features and fixes from November.

I know why I can't get lastest vscode now.
I change the ubuntu default apt source to other source. And this source seems to add vscode in itself, but not update the lastest version.
I add the following line in at first line of the source.list
deb [arch=amd64] http://packages.microsoft.com/repos/vscode stable main
Now all is ok.


PyEPR imports attrdict which deprecates in Python 3.9

Information

Qiskit Metal version:
Python version:
Operating system:

What is the current behavior?

Steps to reproduce the problem
Instantiate a TransmonPocket
What is the expected behavior?
No Error
Suggested solutions
I think this issue occurs in part because pyEPR includes attrdict library.
Maybe open pyEPR to allow for later attrdict if possible

Not on my end

This has been addressed by @GyeonghunKim  and issue should be closed.


Comparison to fastmod

Hey.  Interesting project.  I wondered: are you aware of https://github.com/facebookincubator/fastmod?  It seems to have a similar goal as your project and is also written in Rust.  I wondered if you wanted to include a comparison to it (somewhere).

Good suggestion.
I did not know about fastmod so I installed it and ran it a few times. Here's a  list of differences I've seen so far:

fastmod is interactive by default, ruplacer is not
Interactive display is nice (and the edit feature is cool) but then you can't see the whole diff at once
Small bug: If the same word is changed 3 times on the same line, the diff is shown 3 times
You can accept all diffs but then you don't see what changed

The equivalent to --go is --accept-all --print-changed-files and it only display the files that changed, not the diff.
ruplacer has --subvert, fastmod does not
fastmod has --multiline, ruplacer does not
fastmod can use several CPUs when 'fast mode' is used. Not really sure there's a bottleneck there, need to make some measurements
There are a few more flags in fastmod to select which files to run like --glob or --extensions.
Hope this helps!

Lovely.  Thanks!


Add DRPC plug-in to issuer-agent image

IAS needs to use the DRPC plug-in in their agent to orchestrate some request.
Changes go here

Resolved by #243


<EMAIL_ADDRESS>decompress error

7-Zip 22.01 (x64) : Copyright (c) 1999-2022 Igor Pavlov : 2022-07-15

Scanning the drive for archives:
1 file, 39995334 bytes (39 MiB)

Extracting archive: C:\Users\...\scoop\apps\avidemux\2.8.1\dl.7z

Can't open as archive: 1
Files: 0
Size:       0
Compressed: 0
ERROR: C:\Users\...\scoop\apps\avidemux\2.8.1\dl.7z
C:\Users\...\scoop\apps\avidemux\2.8.1\dl.7z
Open ERROR: Cannot open the file as [7z] archive

ERRORS:
Is not archive

Duplicate of #9689


exclude patterns

enhancement:
allow to exclude files based an a regular expression

available with release 0.6.0


la-go-live

Docs Build status updates of commit e3d9185:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/prepare-test-tenant/admin-center.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/prepare-test-tenant/turn-on-sideload.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/prepare-test-tenant/upload-for-contoso.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/validation-tool/preliminary-checklist.png
:white_check_mark:Succeeded
View

msteams-platform/assets/images/validation-tool/validator.png
:white_check_mark:Succeeded
View

msteams-platform/concepts/build-and-test/prepare-your-o365-tenant.md
:white_check_mark:Succeeded
View

msteams-platform/concepts/deploy-and-publish/appsource/prepare/submission-checklist.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/proactive-bots-and-messages/graph-proactive-bots-and-messages.md
:white_check_mark:Succeeded
View

msteams-platform/messaging-extensions/how-to/link-unfurling.md
:white_check_mark:Succeeded
View

msteams-platform/messaging-extensions/what-are-messaging-extensions.md
:white_check_mark:Succeeded
View

msteams-platform/tabs/how-to/authentication/auth-aad-sso.md
:white_check_mark:Succeeded
View

msteams-platform/task-modules-and-cards/cards/cards-format.md
:white_check_mark:Succeeded
View

msteams-platform/whats-new.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


[FRE-1271] feat: add onTransactionHash callback and improve transaction handling

show swap in progress on wallet confirmation

Just pushed those previous suggestions @codingki , let me know if you have further guidance!

Remove onTransactionSubmitted callback in executeRoute. we can use onTransactionSigned or onTransactionBroadcast. because onTransactionSubmitted is basically the same with onTransactionBroadcast

Remove onTransactionSubmitted callback in executeRoute. we can use onTransactionSigned or onTransactionBroadcast. because onTransactionSubmitted is basically the same with onTransactionBroadcast

Resolved!

I don't think you need anything for onTransactionBroadcast because it's already in client.ts line 315 @ericHgorski

client.ts

ah ok I see your point, yea makes sense!


Add single-line comments

Based on your answer on #79 I thought i would give it a try, at least single-line comments for now.

This PR implements single-line comments which are saved as SingeLineCommentTriva in the SyntaxTokens. WhitespaceToken got changed to WhitespaceTrivia and EndOfLineTrivia as well.
I choose // for the syntax, because I was interested how this interacts with the SlashToken.
Multiline comments themself are not that hard, but it needs some changes to the way the REPL handles syntax coloring (each line is parsed separately). I have tried something, but that's not yet ready for a pull request. 😅
Thanks a lot for this series. 👍
PS: No worries if you don't merge this, I know it might not fit with your roadmap.

Thanks, but I'll do this on the stream (#100, #101)


Validate "value" property passed to sl-date-picker

{{sl-date-picker value="11111"}}

Currently, the above would pre fill the date picker with 11111. The value should be parsed to make sure it's a valid date before being passed to the input.

#1458 will likely close this issue.
Previously the date was bound to the 'value' property, which is a string.  #1458 changes this to force binding on an object of type moment, using the 'selectedDate' property.  The value property of the input tag is now generated from 'selectedDate' and parsed by property 'format'.


sched/pthread: thread id should updated before start routine

Summary
sched/pthread: thread id should updated before start routine
if the created thread has a higher priority than the parent process, the pthread id obtained in the thread will be an invalid value
Impact
pthread_create
Testing
static pthread_t pid = -1;

static void *start_routine(void *arg)
{
  printf("%s: %d, pthread_t: %d\n", __func__, __LINE__, pid);
  return NULL;
}

int main(int argc, FAR char *argv[])
{
  struct sched_param sparam;
  pthread_attr_t pattr;

  pthread_attr_init(&pattr);
  sparam.sched_priority = 101;
  pthread_attr_setschedparam(&pattr, &sparam);

  pthread_create(&pid, &pattr, start_routine, NULL);
  pthread_attr_destroy(&pattr);

  pause();
  return 0;
}

before patch:
nsh> start_routine: 36, pthread_t: -1
after patch:
nsh> start_routine: 36, pthread_t: 5

to me, it seems like a bug in the code in the description.
the child thread should not use "pid" before the successful return of pthread_create.

to me, it seems like a bug in the code in the description. the child thread should not use "pid" before the successful return of pthread_create.

@yamt I am not quite sure if this behavior is correct, could you please share some references for

"the child thread should not use "pid" before the successful return of pthread_create."

there are too many developers facing similar issue.

Personally I do not see any harm in assigning thread ID before taking pjoin->data_sem and if it helps to users, then I think we should proceed with this change. On the other hand I understand comment from @yamt and accessing global variable from a child thread assuming that it should already contain a value is a signal of bad software design and pthread_self should be used instead and the exact behaviour in such situation is not documented.

@pkarashchenko
Thanks for your comment, pthread_self is a good suggestion, but some developers use pthread_t and pthread_self() for comparison, eg:
static pthread_t playbackid = -1;
static pthread_t captureid = -1;
...

static void *start_routine(void *arg)
{
  if (pthread_equal(playbackid, pthread_self()))
    {
    }
  else if (pthread_equal(captureid, pthread_self()))
    {
    }
  ...
  return NULL;
}

since there is no convincing standard to define this behavior, it is difficult for us to convince them to change the source code on some projects, because this behavior does not happen any issues on linux

I don't believe the spec require that thread id must update before or after the thread start. So, the implementation is free to decide when to update thread id.

This issue will be resolved after https://github.com/apache/incubator-nuttx/pull/6038 merge, let us close this PR


proposal: init-only package level variables

Mutable state held in package-level variables can be problematic for a few reasons, e.g. concurrency and repeated imports of a single package.
It would be useful to be able to declare a form of "assign-once" variable that can only have its value set via an initializer in the declaration or in a subsequent init function. Once all init functions have completed the value of the variable cannot be changed.
Some other languages use a special keyword to indicate this type of variable (e.g. pony uses let for assign-once variables and var for others)

This is a language change so marking as a proposal for Go 2.

@iand This is somewhat vague a proposal. Can you elaborate a bit? For instance, how "deep" is the "freezing" of such assign-once variables? If I have a pointer or slice in an assign-once variable, can I still change the contents of the value pointed to or the elements of the slice?

I can imagine how to implement this for composite liberals, but it is harder for init functions—many creative ways to get bits of the structure to escape, particularly if it is a compile time check.
One nice thing about this for maps is that it would let the compiler substitute data structures optimized for lookups, which could provide very substantial speed-ups.

"repeated imports of a single package" — aren't packages only imported and initialized once in an output binary, thanks to the guarantee of no import cycles? Do c-archives/c-shareds/plugins each have their own separate copies of packages?


Deserialize JSON into a type

Rather than doing all the heavy lifting of parsing yourself... you should just deserialize into a type:
https://www.newtonsoft.com/json/help/html/SerializingJSON.htm#JsonConvert
ResourceFileData deserializedProduct = JsonConvert.DeserializeObject<ResourceFileData>(_requiredResourceJson);

Then you can have another file for ResourceFileData.cs with the type definition there and Newtonsoft will magically convert the Json into an instance of that type.
Let me know if you need help with this or let me know if you didn't want to go down this route for a specific reason.
Originally posted by @TylerLeonhardt in https://github.com/PowerShell/PowerShellGet/pull/139

This would likely remove this code (with the exception of psd1 logic):
https://github.com/PowerShell/PowerShellGet/blob/c21f21a19f1f8a021d108c28c72dcf21bfb4509b/src/InstallPSResource.cs#L407-L621

It might look something like:
// read in or get json string

ResourceFileData deserializedProduct = JsonConvert.DeserializeObject<ResourceFileData>(jsonStr);
InstallBeginning(
    deserializedProduct.PkgName,
    deserializedProduct.Version,
    deserializedProduct.Prerelease,
    deserializedProduct.Repository,
    deserializedProduct.Scope,
    deserializedProduct.AcceptLicense,
    deserializedProduct.Quiet,
    deserializedProduct.Reinstall,
    deserializedProduct.Force,
    deserializedProduct.TrustRepository,
    deserializedProduct.NoClobber);

This StackOverflow shows how you can use a custom JsonSerializer:
https://stackoverflow.com/questions/54815199/newtonsoft-json-serialize-deserialize-nested-property
This is what you can use to handle packages that just have a version string, vs packages that have a full object.

Resolved in  #139


webpack Build fails, and succeeds next time

Current behavior

Expected behavior

Steps to reproduce the issue

Issue reproduction repository

Environment

fork-ts-checker-webpack-plugin: [version from the package.json]
typescript: [version from the package.json]
eslint: [version from the package.json]
webpack: [version from the package.json]
os: [e.g. Ubuntu 19.04]

Please feel the termplate, I will not be able to help you otherwise


Only allow two rollover at the time

With this change we only allow two rollover at the time to reduce the load on the maker.
The current amount of CFDs requires to allow more than 1, so we opt for 2 for now until we know if that helps with stability.

bors r+

bors retry


Silverfish are useless in the End

Silverfish had a nerf to preserve old stone builds in the end that was never undone leaving them non-existent in the end.
BTW-Community/BTW-Source#4

More information on the current system and issues can be found here: http://www.sargunster.com/btwforum/viewtopic.php?f=14&t=9743

Done for next release


STX balance does not take into consideration locked balance

When sending STX, if the account is stacking, the "send max" and balance displays are of the total amount, but does not consider the difference.

@aulneau should the use case be tested:
-When sending STX, if the account is stacking in desktop wallet the "send max" and balance displays are of the total amount, but does not consider the difference in webwallet.
Should I cross check both of the places ?

Test passed hence moving it to QA Done


Example for cardiac image segmentation

Hi Martin,
I found that it might take a while to adapt my image I/O and network into DLTK. Also, you mentioned that currently you would focus more on reproducibility. So I contribute my code into the models repository, instead into DLTK/examples. There is a python script demo.py there, which people should be able to run (download two test images and perform segmentation).
BW,
Wenjia

Hi Wenjia,
thanks for the PR. We have just set up travis for flake8. If you could make another push (editing something irrelevant), we will get automated confirmation that all is in order.


chore: upgrade node (v16 -> v20)

ℹ About

Upgrade Node from v16 to v20

[x] Has 🧪 tests
[x] Has 📖 documentation

Hi @JoshCoady do you have time to take a look and create a new release with this change ? It will solve deprecation on github actions. Thanks

+1

done, just upgrade to v1.1


Hide code-fenced comments that begin with #

The generator should exclude code blocks from lines it considers when searching for headings for the TOC.
The following will reproduce:
Section 1
# Look for processes
> ps -aux

Can't reproduce with latest version, this should be closed.


chore: Add context to ACK isUpToDate and return diff

Description of your changes
Fixes #1828
Depends on https://github.com/aws-controllers-k8s/code-generator/pull/458
I have:

[x] Read and followed Crossplane's contribution process.
[x] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested
Most of the code remains untouched. Only function parameters were added and context.TODO was replaced with the real context. In some cases the controllers and tests needed to bed changed since their weren't using the ...WithContext APIs. In some other cases cmp.Equal was replaced with diff := cmp.Diff(...); diff != "" to keep the diff and return it later.

I'm not super fan about the name utils, ref. https://github.com/golang/go/wiki/CodeReviewComments#package-names - if you have an alternative that would be nice.
And as you say, we should wait with this until merged upstream to prevent depending on a unmerged PR.
maybe in a followup, it would be nice if cases like this returned a hint like "spec.forProvider.pitStatus" instead of the empty string?
	if !isPitrUpToDate(cr, pitrStatusBool) {
		return false, "", nil


Quarter Hour Values

At the moment only daily data (Yesterday, Day before Yesterday) is supported. Is it possible to extend it to 0.25h Values?
afaik the Background is already there via verbrauch_raw()

Yeah would be nice!


Updgrade Command is not working

User Story
Upgrade command is not working, need to fix for HA
user should able to run chef-automate upgrade

https://github.com/chef/automate/pull/6141/files


Subtitles?

Subtitles, do we have any? Or is it just because I use fus ro do’h

You should be able to turn Subtitles on in the Skyrim options menu. I have been playing with Closed Caption all the time as I usually am playing muted.

that's the issue though i have subtitles enabled

i think this is a compatibility issue with fus ro duh


Config file for the first connection

It would be great if the Rocket.Chat client would support some options to simplify deployment:
(Other parts of this task #96, #140)

possibility to deploy a config file for the first connection (e.g. server address, username, toggled server list status, ...)

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

+1

+1

+1

This expands the functionality of the servers.json file feature, which loads the default server list.


Minimize to notification area?

Would it be possible to add a button that minimizes the app to the notification area?

I assume you're running windows?

I assume you're running windows?

yes


gtnh-2.7.0-beta2 crush while loading

你的整合包版本
gtnh-2.7.0-beta2
Bug的具体细节
gregtech-api has some break change。

this pull request has failed QAQ

this pull request has failed QAQ

Any logs?

I saw it. Thank you very much.

I test on my 2.7.0 beta3 server and it works perfectly, fantastic.


Improved Storage API (looking for feedback)

Feature Request
The storage APIs are very hard to use, so WXT should provide a standard storage API that's much simpler to use.

Here's an idea for the implementation using unstorage:
import { WatchCallback, createStorage, defineDriver } from "unstorage";
import type { Storage } from "webextension-polyfill";

const webExtensionDriver = defineDriver<{
  storageArea: "sync" | "local" | "managed" | "session";
}>((opts) => {
  if (browser.storage == null)
    throw Error(
      "You must request the 'storage' permission to use webExtensionDriver"
    );

  // Only ever create a single listener per storage area
  const storageListener: (
    changes: Storage.StorageAreaSyncOnChangedChangesType
  ) => void = (changes) => {
    Object.entries(changes).forEach(([key, { newValue }]) => {
      _listeners.forEach((callback) => {
        callback(newValue ? "update" : "remove", key);
      });
    });
  };
  browser.storage[opts.storageArea].onChanged.addListener(storageListener);
  const _listeners = new Set<WatchCallback>();

  return {
    name: "web-extension:" + opts.storageArea,
    async hasItem(key) {
      const res = await browser.storage[opts.storageArea].get(key);
      return res[key] != null;
    },
    async getItem(key) {
      const res = await browser.storage[opts.storageArea].get(key);
      return res[key] ?? null;
    },
    async getItemRaw(key) {
      const res = await browser.storage[opts.storageArea].get(key);
      return res[key] ?? null;
    },
    async getItems(items) {
      const res = await browser.storage[opts.storageArea].get(
        items.map((item) => item.key)
      );
      return items.map((item) => ({
        key: item.key,
        value: res[item.key] ?? null,
      }));
    },
    async setItem(key, value) {
      await browser.storage[opts.storageArea].set({ [key]: value ?? null });
    },
    async setItemRaw(key, value) {
      await browser.storage[opts.storageArea].set({ [key]: value ?? null });
    },
    async setItems(items) {
      const map = items.reduce<Record<string, any>>((map, item) => {
        map[item.key] = item.value ?? null;
        return map;
      }, {});
      await browser.storage[opts.storageArea].set(map);
    },
    async removeItem(key) {
      await browser.storage[opts.storageArea].remove(key);
    },
    async getKeys() {
      const all = await browser.storage[opts.storageArea].get();
      return Object.keys(all);
    },
    async clear() {
      await browser.storage[opts.storageArea].clear();
    },
    watch(callback) {
      _listeners.add(callback);
      return () => void _listeners.delete(callback);
    },
  };
});

const storage = createStorage();
storage.mount("local", webExtensionDriver({ storageArea: "local" }));
storage.mount("session", webExtensionDriver({ storageArea: "session" }));
storage.mount("sync", webExtensionDriver({ storageArea: "sync" }));
storage.mount("managed", webExtensionDriver({ storageArea: "managed" }));
export default storage;

I might try and submit webExtensionDriver to unstorage in a PR. I know the storage listener setup isn't optimized, but it works for a basic setup. I wouldn't add the listener until its needed in WXT's implementation.

Usage would looks something like this:
const installDate = await storage.getItem("local:install-date");

storage.watch("session:counter", (event, key) => {
  console.log(`${key} ${event}d!`); // session:counter updated/removed!
});
await storage.setItem("session:counter", 123);

Is your feature request related to a bug?
Related to https://github.com/wxt-dev/wxt/discussions/227
What are the alternatives?
Here are some alternative storage libraries:

https://webext-core.aklinker1.io/guide/storage/ - localStorage-esk APIs for chrome extensions
https://www.npmjs.com/package/webext-storage - This one is really interesting, it takes a unique approach, but is different from standard storage patterns. That doesn't make it bad though.
https://www.npmjs.com/package/use-chrome-storage - A hook for react

I have nothing to add. I like the impl. idea and unstorage seems to be amazing.
The usage looks quite native, with the exception to watch instead of listen for example, but watch sounds better, indeed...
I'd simplify it even further:
const installDate = await storage.get("local:install-date");

storage.watch("session:counter", (event, key) => {
  console.log(`${key} ${event}d!`); // session:counter updated/removed!
});

await storage.set("session:counter", 123);

I do not think there's need for Item suffix. I'm looking forward to this feature!

Released in v0.10.0

After using impl. of unstorage, I find it weird that in comparison of built-in storage, watcher doesn't return value(s), but only key.
Is it possible to hijack the implementation so that it return k:v pair that changed?

It's definitely not intended, and I didn't explore that. I think I can append an argument to the watch callback without breaking unstorage's interface. I'll add that, because I agree, the vue composable I shared is a little inefficient without it.

I gave it a try, but it didn't work. Because we define a driver instead of the storage object itself, passing additional arguments into the callback are ignored inside unstorage.
So no, this is not possible if using unstorage. I could consider moving to a fully custom storage util if unstorage isn't good enough, but not right now. I have other things I need to work on, and it's in a usable state.
Feel free to contribute a different implementation if this isn't good enough for you.

I understand. Was hoping it's possible, but at the moment on the watcher I have to get the current value with they key, so I guess it's not that big of a deal, was just hoping to avoid that extra step.
No clues why they decided to go with this specific approach on the watcher, but I guess it's for a good reason.
I tried to use the snippet you wrote for me in Vue, previously with two dependencies:
https://github.com/wxt-dev/wxt/discussions/227#discussioncomment-7541284

provide/inject
useAsyncState

But I failed to make it work with new wxt/storage. I'll need to play around more.
At the moment, I'm using your unstorage driver as is, making a mess in my codebase... Testing if all puzzles fit, before I dig in deep into extension details.
What can I say man, you did some amazing work in such short time, while I've been testing wxt and I wish if I knew this much to help with contributions, but some of the source code magic I simply don't understand.

But I failed to make it work with new wxt/storage. I'll need to play around more.
At the moment, I'm using your unstorage driver as is, making a mess in my codebase... Testing if all puzzles fit, before I dig in deep into extension details.

I'll share the entire example, maybe that will help.

If you get time for it...
I made a contribution, I guess this will help wxt in the future, if they approve it?
https://github.com/unjs/unstorage/pull/342
Not sure I did it right, but looks good to me 👍

@dvlden Here's a full example with a working composable:
https://github.com/wxt-dev/wxt-examples/blob/main/examples/vue-storage-composable/README.md

Was using the storage API yesterday, and realized unstorage saves things as strings (at least it saves numbers as strings).
await storage.setItem("local:installDate", Date.now());
await storage.getItem("local:installDate"); // "1703427743358" instead of<PHONE_NUMBER>358

So that's not acceptable... Will probably implement a custom version soon.

Here's what I'm thinking considering the feedback in this thread, my personal experience, and research into other libraries:

I like unstorage's API and patterns

While getItem is verbose compared to get, it is fairly standard. It also allows for obvious plural forms of the functions, like getItems. It also allows for other setters, like setMeta, which could be useful in versioning fields.
The : separated keys are a nice approach, and using the local:/session:/sync:/managed: prefixes have worked well

Change listener will report the new and old values
I like the idea of creating a StorageItem from webext-storage, but recognize that it's not something everyone would use

I would prefer this over adding a storage schema to define the keys and their types, because that leads to circular imports
Migrations is always something I've wanted from a storage API, this could be a good

I've never had performance issues with reading and writing directly to storage, so I don't see a reason to add a cache.

With all that in mind, here's the API I'm proposing for WXT 1.0:
// wxt/storage
export const storage: WxtStorage = ...;

export interface WxtStorage {
  /**
   * @example
   * await storage.getItem<number>("local:installDate");
   */
  getItem<T>(key: string): Promise<T | null>;
  /**
   * Return an object containing metadata about the key. Object is stored at `key + "$"`. If value is null or not an object, it returns an empty object.
   *
   * @example
   * await storage.getMeta("local:installDate");
   */
  getMeta<T extends Record<string, unknown>>(key: string): Promise<T>;
  /**
   * @example
   * await storage.getItems(["local:installDate", "session:someCounter"]);
   */
  getItems(keys: string[]): Promise<Array<{ key: string, value: any }>>;

  /**
   * Setting a value to `null` or `undefined` is equivalent to calling `removeItem`.
   *
   * @example
   * await storage.setItem<number>("local:installDate", Date.now());
   */
  setItem<T>(key: string, value: T | null): Promise<void>;
  /**
   * Sets metadata fields. If some fields are already set, but are not included in the `fields` parameter, they will not be removed.
   * @example
   * await storage.setMeta("local:installDate", { v: appVersion });
   */
  setMeta<T extends Record<string, unknown>>(key: string, fields: T | null): Promise<void>;
  /**
   * @example
   * await storage.setItem([
   *   { key: "local:installDate", value: Date.now() },
   *   { key: "session:someCounter, value: 5 },
   * ]);
   */
  setItems(values: Array<{ key: string, value: any }>): Promise<void>;

  removeItem<T>(key: string): Promise<void>;
  /**
   * Remove the entire metadata for a key, or specific fields by name.
   */
  removeMeta<T>(key: string, fields?: string[]): Promise<void>;
  removeItems<T>(keys: string[]): Promise<void>;

  onItemChange<T>(key: string, cb: OnChangeCallback<T>): Unsubscribe;

  /**
   * Define a constant with utilities for reading/writing to a single value in storage.
   *
   * @example
   * export const installDateStorage = storage.defineItem<number>("local:installDate");
   */
  defineItem<T>(key: string, options?: WxtStorageItemOptions): WxtStorageItem<T>;
}

/**
 * Same as `WxtStorage`, but you don't have to specify the key or types every time.
 */
export interface WxtStorageItem<T> {
  getItem(): Promise<T>;
  setItem(value: T | null): Promise<void>;
  setMeta<TMeta extends Record<string, unknown>>(value: TMeta): Promise<void>;
  removeItem(): Promise<void>;
  removeMeta(fields?: string[]): Promise<void>;
  onChange(cb: OnChangeCallback<T>): Unsubscribe;
};

export interface WxtStorageItemOptions<T> {
  defaultValue?: T;
  /**
   * The current version of the field to store in metadata. If provided, it will be used to run migration functions when the version is updated.
   */
  version?: number;
  /**
   * A record of version numbers to the functions used to migrate the data to that version.
   */
  migrations?: Record<number, ((oldValue: any) => any)>;
};

export type OnChangeCallback<T> = (newValue: T, oldValue: T) => void;
export type Unsubscribe = () => void;

New storage API was released in v0.13.0. Feel free to create new issues if you have problems or suggestions.

Oooh, very interesting. Dropping dependency sounds good, especially cause they did not care about our improvement. Plenty of dangling open PR's.
I just updated to v0.13.0 and going through refactor.
Got a question tho. I see everywhere literal examples of storing single primitive value per key in the storage. Would you advice to have a single storage item that stores an object instead?
Thinking about it, it's the way I used storage with my custom wrapper in the v2 of my extension. So now while developing v3, I do wonder why everyone is showing it as primitive values in storage only?
Since you have a lot of knowledge regarding development and extensions, please let me know. Would you advice me to use single source of truth basically or split it into multiple storage items?
I love the update!

Would you advice to have a single storage item that stores an object instead?

When working with storage, I never use a single key with an object containing multiple fields that need to be set independently for two reasons:

Avoid race conditions with other functions setting a different field in the same object
Watch listeners are fired more than necessary - because listeners are based on top-level keys, listeners will fire when changing any value in the object, when you usually only care about one specific value

That's not to say you can't store objects. But you should only store objects that are updated as a single value instead of updating parts of the object.
For example, if you have 5 settings in your extension, I would store those 5 in separate keys, not a single "preferences" key.
But if you are saving auth tokens for the logged in user, maybe a token and refresh token, those could be stored in a single "auth" key because they're never updated independently.

Also, how performant is setting watcher per key vs single watcher and switch statement inside per key, as it was with unstorage?

I decided to change this because I thought the old implementation might be a classic example of premature optimization. I've never measured the performance of the two approaches, so I don't have an answer for that.
Extension storage is implemented in native code in all browsers, so my thinking is that it's probably easier to let the native code managing the listeners.
If you are experiencing performance issues related to storage, I'll optimize it then.

Here's what I'm thinking considering the feedback in this thread, my personal experience, and research into other libraries:
1. I like `unstorage`'s API and patterns

   * While `getItem` is verbose compared to `get`, it is fairly standard. It also allows for obvious plural forms of the functions, like `getItems`. It also allows for other setters, like `setMeta`, which could be useful in versioning fields.
   * The `:` separated keys are a nice approach, and using the `local:`/`session:`/`sync:`/`managed:` prefixes have worked well

2. Change listener will report the new and old values

3. I like the idea of creating a `StorageItem` from [`webext-storage`](https://www.npmjs.com/package/webext-storage), but recognize that it's not something everyone would use

   * I would prefer this over adding a storage schema to define the keys and their types, because that leads to circular imports
   * Migrations is always something I've wanted from a storage API, this could be a good

4. I've never had performance issues with reading and writing directly to storage, so I don't see a reason to add a cache.

With all that in mind, here's the API I'm proposing for WXT 1.0:
// wxt/storage
export const storage: WxtStorage = ...;

export interface WxtStorage {
  getItem<T>(key: string): Promise<T | null>;
  getMeta<T extends Record<string, unknown>>(key: string): Promise<T>;
  getItems(keys: string[]): Promise<Array<{ key: string, value: any }>>;
  setItem<T>(key: string, value: T | null): Promise<void>;
  setMeta<T extends Record<string, unknown>>(key: string, fields: T | null): Promise<void>;
  setItems(values: Array<{ key: string, value: any }>): Promise<void>;
  removeItem<T>(key: string): Promise<void>;
  removeMeta<T>(key: string, fields?: string[]): Promise<void>;
  removeItems<T>(keys: string[]): Promise<void>;
  watch<T>(key: string, cb: WatchCallback<T>): Unwatch;
  defineItem<T>(key: string, options?: WxtStorageItemOptions): WxtStorageItem<T>;
  snapshot(base: string): Promise<any>;
  restoreSnapshot(base: string, data: any): Promise<void>;
}

export interface WxtStorageItem<T> {
  getItem(): Promise<T>;
  setItem(value: T | null): Promise<void>;
  setMeta<TMeta extends Record<string, unknown>>(value: TMeta): Promise<void>;
  removeItem(): Promise<void>;
  removeMeta(fields?: string[]): Promise<void>;
  watch(cb: WatchCallback<T>): Unwatch;
};

export interface WxtStorageItemOptions<T> {
  defaultValue?: T;
  version?: number;
  migrations?: Record<number, ((oldValue: any) => any)>;
};

export type WatchCallback<T> = (newValue: T, oldValue: T) => void;
export type Unwatch = () => void;

Edit 1: I removed comments since the function names are pretty self-explanatory. I also added the snapshot and restoreSnapshot functions. Edit 2: Renamed onChange to watch and Unsubscribe to Unwatch.

I'd love a Migration API. It's something that I had tried to bake into my extension, but didn't quite get it right — tbf I was new to extensions at the time and tried a quick implementation within a week while developing the rest of it.

@KnightYoshi Try it out in v0.13.0 and let me know what you think :)
https://wxt.dev/guide/storage.html#versioning-and-migrations


grant on schema does not take effect on future objects created in a schema by schema's authorized users

grant on schema does not take effect on future objects created in a schema by the schema's authorized users
When a user u1 is granted ownership on a schema s1 at the time of creation. And there is grant select on schema permission on s1 to u2. The future objects created by the users dbo and u1 should be accessible by the user u2
Earlier, if u1 created a table in s1 schema since it's authorized to do so, the user u2 was not allowed to access the object created by u1.
With this commit, future objects created by u1 and dbo will be accessible to the user u2.
Task: BABEL-5172
Signed-off-by: Shalini Lohia<EMAIL_ADDRESS>

Pull Request Test Coverage Report for Build<PHONE_NUMBER>9
Details

60 of 113 (53.1%)  changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.04%) to 74.469%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

contrib/babelfishpg_tsql/src/pltsql_utils.c
50
54
92.59%

contrib/babelfishpg_tsql/src/catalog.c
0
49
0.0%

Totals

Change from base Build<PHONE_NUMBER>0:
-0.04%

Covered Lines:
45105

Relevant Lines:
60569

💛  - Coveralls


[zh]translation tweek.

"until version 4" means "not used in v4"

LGTM 👍
@HugoGiraudel wanna hit dat merge?

Thanks!


Remove prevent going back from status page until we create review screens

After they send the interview, they need to be able to go back and change their entries.

Fixed by #60


Link to enterprise store is not work

https://go.microsoft.com/fwlink/p/?LinkID=722910

文档详细信息
⚠ 请勿编辑此部分。 docs.microsoft.com ➟ GitHub 问题链接必须具有此部分。

ID: 4043626d-5475-cd46-e107-6077ff4701f7
Version Independent ID: 59ffa7ff-97ca-2f34-3c92-a09ab10c0a4e
Content: 使用 System Center Configuration Manager (Windows 10) 创建和部署 Windows 信息保护 (WIP) 策略
Content Source: windows/security/information-protection/windows-information-protection/create-wip-policy-using-sccm.md
Product: w10
GitHub Login: @Justinha
Microsoft Alias: justinha

@officedocsbot assign @OfficeGlobal

@OfficeGlobal - Do you have any updates on this issue? Kindly assist with this Translation (Localization) issue. Thank you.

@officedocsbot assign @mypil

@dongmicro - Can you assist with this Translation (Localization) issue?
Thank you.

@mypil I submitted a fix on my side, ETa to publish is Monday morning. I just replaced the fwlink with a direct link to the Store for business at https://businessstore.microsoft.com/store

Any downsides to deploying WIP via SCCM vs. Intune? or full parity?

@HaoHoo - From our understanding, the issue has been resolved but it may take a few days for the merged content to appear in the article. If you feel it hasn't been resolved, please re-open this issue.
Thank you for your contribution to make the docs better! Much appreciated!

@officedocsbot add label localization

@officedocsbot close


MF-1314 - Add value comparison filters for readers

Signed-off-by: Manuel Imperiale<EMAIL_ADDRESS>Resolves #1314

Codecov Report

Merging #1353 (f31bf6e) into master (13c426c) will decrease coverage by 0.00%.
The diff coverage is 76.66%.

@@            Coverage Diff             @@
##           master    #1353      +/-   ##
==========================================
- Coverage   60.56%   60.56%   -0.01%
==========================================
  Files         123      123
  Lines        9314     9346      +32
==========================================
+ Hits         5641     5660      +19
- Misses       3188     3196       +8
- Partials      485      490       +5

Impacted Files
Coverage Δ

readers/api/transport.go
79.19% <50.00%> (-0.81%)
:arrow_down:

readers/cassandra/messages.go
58.88% <50.00%> (-1.34%)
:arrow_down:

readers/postgres/messages.go
62.36% <70.00%> (-2.47%)
:arrow_down:

readers/influxdb/messages.go
75.18% <75.00%> (-1.15%)
:arrow_down:

readers/mongodb/messages.go
78.08% <90.00%> (+2.22%)
:arrow_up:

readers/api/requests.go
100.00% <100.00%> (ø)

things/service.go
53.40% <0.00%> (-1.14%)
:arrow_down:

Continue to review full report at Codecov.

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


Vector cleanups

Added lerp(vector, vector, number)
Optimized min and max to use square magnitude instead
Optimized vector:toAngle
Changed randVec to use Vector.Random
Changed parameter names on mix to be more descriptive
Changed mix to use LerpVector
Changed ANGLE_ZERO constant to use preexisting angle_zero constant
Remove temporary bezier fix

Fixes #2893

congratulation, you successfully broke the bezier function.


[DOCS] Getting Started - Incorrect JDK install links

Describe the issue
Getting started guide  under the Prerequisites > JDK + Maven section lists https://docs.aws.amazon.com/corretto/ as the link to install Corretto. This link points to the user guide for Corretto and do not provide a download option. A better link to provide here would be https://aws.amazon.com/corretto/ which provides multiple download options.
Links
https://aws.github.io/aws-pdk/getting_started/index.html

Hi Anoop,
Sorry this got auto-closed - I'm just back from leave!
I agree with your suggestion, https://aws.amazon.com/corretto/ is a much more helpful link!
Would you be happy to contribute a PR?
Cheers,
Jack


feat: persist last opened env per collection

fixes #112
Description
This PR add the feature of save the last env that was opened for a collection.

Contribution Checklist:

[x] The pull request only addresses one issue or adds one feature.
[x] The pull request does not introduce any breaking changes
[x] I have added screenshots or gifs to help explain the change if applicable.
[x] I have read the contribution guidelines.
[x] Create an issue and link to the pull request.

Looks great to me :D

Thanks!

It's duplicated with the PR already waiting to be merged
#1971

+1

This functionality has been delivered as a part of https://github.com/usebruno/bruno/pull/3215
Closing this PR


AWS ELB Proxy IP forwarded for occurs errors

We got some trouble regarding the "Keep-source-ip" setting on voyager, if we set this to true, the voyager returns 504 code and error message on controller
Received something which does not look like a PROXY
protocol header.

Our setup is a classic loadbalancer on aws. Found issue regarding ssl on serverfault, but does not cover our issue.
How to achieve getting IP from source on AWS setup with ingress voyager?

Did you enable proxy protocol in the ELB?

No..

Testet with and without enabled proxy protocol..
For the moment, we are not able to use the flag Keep-source-ip, is there any option to fix that issue, to receive the X-FORWARDED-FOR and whitelist that in ingress-voyager?

seems no solution provided here

@fragtom, were you able to solve this problem?

no, there is no valid IP from Loadbalancer .. I only get the kubernetes IP.


Write script to find TODOs mentioning closed github issues

Motivation
There are a number of TODO comments in the code which refer to issues which have already been closed.
In order to get a full list of all of these comments and issues, we are going to try to write some scripting that finds TODOs that mention github issues that have been closed and update the list in #6281.

A reference: https://github.com/ZcashFoundation/developers/blob/main/zcash-issue-dag.py has code to check if an issue has been closed or not


fix(xlnet): Set training mode to False and set dropout to zero

Attempts to fix #45
Taken directly from https://github.com/zihangdai/xlnet/pull/151/commits/d1d0ff4d0d2e536e897adabcdd04683e62dfa7a4
Todo:

[ ] Test manually
[ ] Add a test for C/I if possible

@chiragjn  LGTM, should we merge this?

unfortunately, this still does not solve the problem, without going component by component it is hard to tell what is still causing the variance :(

Closing this for now, this still remains a issue :upside_down_face:


Problem with document form when updating a standard

Describe the bug

When trying to edit this record:
https://catalogue.library.cern/backoffice/documents/cvbss-zdb50/edit
(i.e. adding a value in the field edition)
The system sends an error message on the field: "extensions.standard_review_validity: Unknown field."

So it is impossible to modify the record.
To Reproduce

issue fixed


Trace log displays every time I open Code

I first just want to say we are loving Live Share in the classroom 😄
Product and Version [VS/VSCode]: 1.24.1
OS Version [macOS/Windows]: macOS 10.13.5
Live Share Extension Version: VSLS/0.3.292
Target Platform or Language [e.g. Node.js]: ?
Whenever I open a VS Code window, a Visual Studio Live Share terminal opens and gives me a bunch of output:

I immediately close it and move on with my code. Is it possible to have this not open for every window?
Thanks!

@ericandrewlewis Hey! Thanks for trying out Live Share and reaching out 😁 I’d love to hear more about how you’re using Live Share, since classroom scenarios are actually something we’re looking to understand better and optimize the experience for (e.g. increase the guest limit, allow sharing read/only access, etc.)
Regarding this bug, yeah we should be able to correct this behavior. Let us look into it and get back to you. Thanks!

@ericandrewlewis We're prepparing a fix and tracking this issue via #545. So I'm going to close this as a duplicate, but would still love if you were able to share any details about how you're using Live Share (feel free to email me if that is easier: joncart@microsoft.com).
As an aside, you can workaround this issue by setting the liveshare.diagnosticLogging setting to false. Stay tuned for a fix. Thanks again!

I’d love to hear more about how you’re using Live Share, since classroom scenarios are actually something we’re looking to understand better and optimize the experience for (e.g. increase the guest limit, allow sharing read/only access, etc.)

While teaching a lesson I'll have students join, and they'll write code while learning about a new topic. This is really useful. I can make sure that students are able to take navigator instructions from me, and give them small exercises on the spot to check for comprehension before sending them to more independent practice.
I've used sharing both in the editor and the terminal modes to success.
Sometimes the session gets a little wacky and I'll take over and code a bit, sorry I haven't been able to submit exact bugs for these situations yet.
Increasing the guest limit would be amazing. Sharing with read only access would be useful but not a huge need, I can just tell students not to edit anything.
Glad to chat more, feel free to reach out at<EMAIL_ADDRESS>


fix(Attestation): Fix attestation from rootless pods

This PR contains the following changes:

Updated attestation logic for rootless containers

@vishnusomank @seswarrajan can we merge it?


fix: cargo run -p dfx -- --version prints incorrect version

Description
Fixes https://dfinity.atlassian.net/browse/SDK-664
Currently, when cargo run -- --version is issued, we get incorrect results
❯ cargo run -- --version
   Compiling dfx v0.11.2 (sdk/src/dfx)
    Finished dev [unoptimized + debuginfo] target(s) in 11.39s
     Running `target/debug/dfx --version`
dfx 0.9.1-378-gb9ace030

Even though the latest version is 0.11.2 or 0.12.0-beta.1 (depending on how you look at it: 0.11.2 is the latest datewise, whereas 0.12.0-beta.1 is the latest feature-wise).
This PR attempts to fix this.
❯ cargo run -- --version
    Blocking waiting for file lock on build directory
   Compiling dfx v0.11.2 (sdk/src/dfx)
    Finished dev [unoptimized + debuginfo] target(s) in 14.84s
     Running `target/debug/dfx --version`
dfx 0.12.0-beta.1-b9ace030

The b9ace030-part is the SHA of the current HEAD commit
The tag name (0.12.0-beta.1) is being found from the list of all tags in the repository, based on the least revisions between the HEAD and the tag. Based on my experiments, it's better to use the count of revs than time, for a reason I'll try to illustrate below: Sep 3rd  :  o <- HEAD of master branch
             |  o <- tag:0.2
 Sep 2nd  :  |  | <- branch:release-0.1-patch.1
             | /
 Sep 1st  :  |/  o <- HEAD of release-0.1-patch.1 branch
             |   | <- branch:release-0.1-patch.1
             |   |
             |   |
             |   |
             |  /
 Jul 1st  :  | o <- tag:0.1
             | | <- branch:release-0.1
             | |
             |/
 Jun 1st  :  | <- branch:master

If you'd be working on branch release-0.1-patch.1, and you'd issue cargo run -- --version, you'd expect to see dfx 0.1-SHA (which is the latest release if you walk git graph), rather than dfx 0.2-SHA (which is the latest datewise release)

Credit
The change is based on the following shell command (source):
git tag | while read t; do echo `git rev-list --count $t..HEAD` $t; done | sort -n | head -n1 | awk -F ' ' '{print $2}'

How Has This Been Tested?
CI
Checklist:

[x] The title of this PR complies with Conventional Commits.
[x] I have edited the CHANGELOG accordingly.
[ ] I have made corresponding changes to the documentation.

Thanks for the feedback! I didn't fully understand the dirty part at the time of submitting the PR, but now you've explained it, it makes perfect sense to have it - I just added it
~/Desktop/sdk mnl/fix-dfx-…rect-version *2 !1
❯ git status -s

~/Desktop/sdk mnl/fix-dfx-…rect-version *2
❯ cargo run -- --version
   Compiling dfx v0.11.2 (/Users/mnl/Desktop/sdk/src/dfx)
    Finished dev [unoptimized + debuginfo] target(s) in 43.24s
     Running `target/debug/dfx --version`
dfx 0.12.0-beta.1-47875662

~/Desktop/sdk mnl/fix-dfx-…rect-version *2
❯ echo "fn x() {}" >> src/dfx/src/main.rs

~/Desktop/sdk mnl/fix-dfx-…rect-version *2 !1
❯ git status -s
 M src/dfx/src/main.rs

~/Desktop/sdk mnl/fix-dfx-…rect-version *2 !1
❯ cargo run -- --version
   Compiling dfx v0.11.2 (/Users/mnl/Desktop/sdk/src/dfx)
warning: function is never used: `x`
   --> src/dfx/src/main.rs:212:4
    |
212 | fn x() {}
    |    ^
    |
    = note: `#[warn(dead_code)]` on by default

warning: `dfx` (bin "dfx") generated 1 warning
    Finished dev [unoptimized + debuginfo] target(s) in 12.38s
     Running `target/debug/dfx --version`
dfx 0.12.0-beta.1-47875662-dirty


Whitlist issues with autolathe materials (seismic charge uncraftable)

Description
Silver can not be feed into the autolathe, making seismic charges impossible to craft. Despite Whitelist inside of MaterialStorageComponent allowing the Ingot tag, the separate MaterialWhiteList inside the same component does not include silver, likely causing the issue.
Additionally sheets of reinforced glass are uncraftable in the autolathe due to the inability to insert coal. The autolathe recipe for reinforced glass probably shouldn't require coal, since it's there for convenience over hand crafting.
Reproduction
Try to put coal or silver in the lathe.

coal is a tag issue, silver is an issue of checking (emag) static/dynamic recipes but not all blueprints

still untriaged and still in the game

I'll take a crack at this.


ruby 2.2.4 -> 2.3.1

This PR updates ruby 2.2.4 to 2.3.1 . Review && merge Please !

Thank you. But I already modified it on my local env. I pushed yesterday. https://github.com/hsbt/docker-ruby-builder/commit/bd6200ba457459ea21aa03aa243cb04ef2d10f57

oh OK であります!  I should have git pull at first ... 🙇


How do I set proxy for WebDriverHttpFetcher in Collector 3.0?

I try to add a proxy to WebDriverHttpFetcher but it not working with the config below. It correct to add proxy tag in capabilities? I don't know what format to insert in the value of capability tag. Can you show me example for set capabilities?
<httpFetchers>
    <fetcher class="WebDriverHttpFetcher">
        <browser>firefox</browser>
        <capabilities>
            <capability name="proxy">{"proxyType":"manual", "httpProxy":"<IP_ADDRESS>:8888"}</capability>
        </capabilities>
    </fetcher>
</httpFetchers>

Firefox typically works with profiles. The exact syntax has changed a few times.  I am unsure about configuring it via XML alone.  You can try the following:
        <capabilities>
            <capability name="network.proxy.type">1</capability>
            <capability name="network.proxy.http">yourproxyhost</capability>
            <capability name="network.proxy.http_port">999</capability>
            <!-- If using SSL -->
            <capability name="network.proxy.ssl">yourproxysslhost</capability>
            <capability name="network.proxy.ssl_port">999</capability>
        </capabilities>

Possibly you can also try to reference a firefox profile one of these two ways:
            <capability name="profile">/path/to/your/firefox/profile.def</capability>
            <capability name="firefox_profile">/path/to/your/firefox/profile.def</capability>

If you know your Java, another thing to try is setting the Java proxy yourselves via coding.  You can extend the WebDriverHttpFetcher#fetcherStartup(...) method like this:
    @Override
    protected void fetcherStartup(HttpCollector c) {
        MutableCapabilities options = getConfig().getCapabilities();

        // you can set any custom capabilities, e.g.:
        options.setCapability("aKey", "aValue);

        // you can also create your own firefox profile via coding:
        FirefoxProfile profile = new FirefoxProfile();
        profile.setPreference("network.proxy.type", 1);
        profile.setPreference("network.proxy.http", "yourproxyhost");
        profile.setPreference("network.proxy.http_port", 123);
        // profile.setXYZ whatever else you want to configure
        options.setCapability(FirefoxDriver.PROFILE, profile);

        super.fetcherStartup(c);
    }


Interface with The Thing System

I've just come across The Thing System (Github), and it would be nice if we could link the two together; can Huginn be the magic they talk about?
http://thethingsystem.com/dev/supported-things.html
@TheThingSystem

I'm going to close this issue.  Please reopen if you want to discuss further!


[Question] Reading document status

Context / Scenario
Hello, thank you for supporting kernel memory, it's a powerful service.
The question is regarding running the container as a separate service.
Question
I am wondering if the GetDocumentStatusAsync is the only way to know if a document is processed?
I thought that it might be possible to post a message on a queue once the document is processed, so we skip the polling of status.
I had a look through the code but I could not find anything that suggests that.

I thought that it might be possible to post a message on a queue once the document is processed, so we skip the polling of status.

hi @Valkozaur - if we posted a message on a queue, how would the client know that the message is there? wouldn't the client have to poll the queue?

You can implement your approach adding a "custom handler".
When importing a document, you can provide in input a list of steps, which corresponds to the list of handlers to execute.
In the service, you can add a custom handler, used to post a message in a queue that you own, if that helps your scenario.
How to:

write a custom handler class responsible for posting messages in your custom queue
change the service to load your custom handler with a predefined name - see service config and examples
when storing a memory, pass the steps parameter, it's a list of strings, include the name of your handler, e.g. steps: ["extract", "partition", "gen_embeddings", "save_records", "my_post_to_queue"]


[UI] Initialize Repository

Why
We need to initialize the repository from the template.
Acceptance Criteria

Initialize the project.
Setup the git templates
Setup project backlog

Design
n/a

## Why
We need to initialize the repository from the template.

## Acceptance Criteria
- Initialize the project.
- Setup the git templates
- Setup project backlog

## Design
n/a

also, this is a [Chore] not [UI] :D


Feature - automatically remove/detect duplicates

Individual TV Episodes are no longer included in search, this removes all duplicates.


GraphQLError: Unknown argument "formatString" on field "time_added" of type "PocketArticle".

I'm trying to change the date format used by Pocket but it give me this error from title. Looks like Gatsby don't work well with non-iso formats. I've tried to change directly on GraphQl query using  time_added(formatString: "YYYY-MM-DD") when got this message. Formating the node before the query didn't work too, using moment or date-fns returns invalid_date.

I don't know why but changing the node using moment or format didn't work for graphql but using both together works.. I've tried format(node.time_added) and moment(node.timeadded, 'X) when creating my nodes, both returned a Invalid Date but using format(moment(node.time_added, 'X')) works fine.  Using only moment for conversion should work, right?

I'm on my phone but looking at my example project I used format(new Date(time_read * 1000), "dddd ha").

@rdricco did you get this working?

I didn't have time to work on a better solution, at moment I'm using this format+moment conversion.

To get a date object from a Pocket time stamp such as time_read, you need to multiply it by 1000, as follows new Date(time_read * 1000). You can then wrap it in a date library of your choosing.


If you want that behaviour you can use -f or --fail, i.e.:
python3 curl-benchmark.py -- -f localhost:8081

No worries :)


Index button in issues is white

Index button is white, also overwrite these classes:

.topic-item .topic-content .topic-metadata {
    color: rgba(103,103,109,0.5);
}

Additionally there is a highlighting animation that goes white.


pc.Curve is throwing error:  "this.sort is not a function"

The following code placed inside of an initialize method,
var heightmapData = [1,2,3,4];
var curve = pc.Curve();
for(var i = 0; i < heightmapData.length; i++)
{
    curve.add(i/heightmapData.length, heightmapData[i]);
}

throws the following error, consistently
TypeError: this.sort is not a function
playcanvas-stable.dbg.js:22809 unhandled exception while calling "initialize" for "raceTestPixelGet"
script:  TypeError: this.sort is not a function
    at Object.Curve (playcanvas-stable.dbg.js:2460)
    at script.RaceTestPixelGet.initialize (raceTestPixelGet.js?id=9074118:8)
    at Func._scriptMethod (playcanvas-stable.dbg.js:22805)
    at Func._onInitialize (playcanvas-stable.dbg.js:22822)
    at Func._callComponentMethod (playcanvas-stable.dbg.js:23070)
    at Func._onInitialize (playcanvas-stable.dbg.js:23076)
    at Function.fire (playcanvas-stable.dbg.js:608)
    at Function.initialize (playcanvas-stable.dbg.js:20867)
    at Application.start (playcanvas-stable.dbg.js:20424)
    at launch.js:6753

You forgot the new keyword.. Should be
var curve = new pc.Curve();

I just caught that, sorry and thanks :)


Host API Proxy Token Support

This shouldn't be merged until we merge the cattle change that introduces that hostApiProxyToken resource.

Closing in preference to #28


⚠ Avatar API Endpoint has degraded performance

In 7aa8fcd, Avatar API Endpoint (https://avatar.roblox.com/v1/avatar-rules) experienced degraded performance:

HTTP code: 200
Response time: 1001 ms

Resolved: Avatar API Endpoint performance has improved in a41fc1b.


example reverted from 64ab3a3

- What I did
Reverted example from 64ab3a3

@yahu1031 could you please check it again?
The example lost the switching theme feature in your PR.

@sonle-geekyants Can you please check this now.

Look good!