ES6 and Object.defineProperties issue

lets say i have the following class:
class Object3D extends EventDispatcher {

	constructor() {

		super();

		const quaternion = new Quaternion();

		Object.defineProperties( this, {
			quaternion: {
				configurable: true,
				enumerable: true,
				value: quaternion
			}
		} );
      }

       onRotationChange() {
		this.quaternion.setFromEuler(........);
	 }
 }

and the following warning:
core/Object3D.js:123:7: WARNING - [JSC_INEXISTENT_PROPERTY] Property quaternion never defined on Object3D
  123| 		this.quaternion.setFromEuler();
       		   ^^^^^^^^^^

I have no idea what i do wrong, maybe i missed something ?

The compiler does not understand that this.quaternion is instantiated in the constructor. If you remove Object.defineProperties(...) and use this.quaternion = ..., this warning will go away.
Admittedly, it would be best if the compiler could understand the Object.defineProperties statement.

@ctjlewis thanks for your clarification, so it means closure ignores Object.defineProperties/Object.defineProperty ? Ok, i am working on three.js and i didn't want to change the code too much but looks like i have no choice to make it closure compatible.

Yeah, I think we have had issues about this before, for this exact library and this exact situation. @lauraharker, @brad4d, does this issue (with the Object.defineProperties conflicting with ThreeJS Quaternion class) also seem familiar? Also, thoughts on patching?
Some Googling gives me:

#1869
https://github.com/infusion/Quaternion.js/

If it's infeasible to update the actual property declaration to be a simple assignment, it would also work to declare the property separately. Something like /** @type {!Quaternion} */ Object3D.prototype.quaternion; would inform the compiler about the property with no runtime effect.

If it's infeasible to update the actual property declaration to be a simple assignment, it would also work to declare the property separately. Something like /** @type {!Quaternion} */ Object3D.prototype.quaternion; would inform the compiler about the property with no runtime effect.

@nreid260 Thanks for advice, but it not able to do it, coz in my case Quaternion extends Object3D, @type {!Quaternion} needs me to add an export Quaternion in Object3D, that leads to :
Uncaught ReferenceError: Cannot access 'B' before initialization

:(

@nreid260 Thanks for advice, but it not able to do it, coz in my case Quaternion extends Object3D, @type {!Quaternion} needs me to add an export Quaternion in Object3D, that leads to :
Uncaught ReferenceError: Cannot access 'B' before initialization

:(

How can Quaternion extend Object3D? Since the constructor of Object3D instantiates Quaternion, that would cause infinite recursion.
More to the point though,/** @type {!Quaternion} */ Object3D.prototype.quaternion; could be added anywhere in the program (even a separate file that just contains property declarations). If you chose to add it in the same file that defines Object3D that would also be fine. Quaternion is only referenced as a type (annotation) here, so this declaration is legal before Quaternion is defined. In compiler terms, this is a "forward reference".
As yet another option, if you're able to patch the code, you could replace the defineProperties call with /** @const {!Quaternion} */ this.quaternion = new Quaternion();. That would be the most idiomatic way to express the property to Closure Compiler. @const would give you very similar compile time guarantees to the ones the code has today by defining the property to be non-writable.

How can Quaternion extend Object3D? Since the constructor of Object3D instantiates Quaternion, that would cause infinite recursion.
More to the point though,/** @type {!Quaternion} */ Object3D.prototype.quaternion; could be added anywhere in the program (even a separate file that just contains property declarations). If you chose to add it in the same file that defines Object3D that would also be fine. Quaternion is only referenced as a type (annotation) here, so this declaration is legal before Quaternion is defined. In compiler terms, this is a "forward reference".
As yet another option, if you're able to patch the code, you could replace the defineProperties call with /** @const {!Quaternion} */ this.quaternion = new Quaternion();. That would be the most idiomatic way to express the property to Closure Compiler. @const would give you very similar compile time guarantees to the ones the code has today by defining the property to be non-writable.

@nreid260 yeah, i know, it sounds strange, but it's very typical for three.js. Cycle deps everywhere ...
I am about to give up adopting three.js to closure, despite the fact, only 260 warning left (initially it was ~3000) ...
thanks for your support !

@nreid260 yeah, i know, it sounds strange, but it's very typical for three.js. Cycle deps everywhere ...
I am about to give up adopting three.js to closure, despite the fact, only 260 warning left (initially it was ~3000) ...
thanks for your support !

Depending on what the warnings are, you could just @suppress them. That's our standard approach to rolling out new diagnostics. The code works today, so the warnings likely don't correspond to real problems, and our optimizations generally behave safely (if less effectively) in response to issues.

Depending on what the warnings are, you could just @suppress them. That's our standard approach to rolling out new diagnostics. The code works today, so the warnings likely don't correspond to real problems, and our optimizations generally behave safely (if less effectively) in response to issues.

Just want to add, the compiler recognizes properties creates by Object.defineProperties during optimizations, but not during typechecking. As such, we believe things are working as intended.
That distinction might feel arbitrary, but optimizations generally require less information about properties (usually just "does this name exist somewhere in the program?") so it's easier to add support. Recognizing them during typechecking is more nuanced.
Additionally, optimization failure can cause runtime behaviour issues, so we need to be very conservative, and often silently cancel optimizations when something might be wrong. In contrast, typechecking failure is a compile-time problem, so we can make it more user visible, and defer to the user (via suppressions or annotations) when we get false positives.

Just want to add, the compiler recognizes properties creates by Object.defineProperties during optimizations, but not during typechecking. As such, we believe things are working as intended.
That distinction might feel arbitrary, but optimizations generally require less information about properties (usually just "does this name exist somewhere in the program?") so it's easier to add support. Recognizing them during typechecking is more nuanced.
Additionally, optimization failure can cause runtime behaviour issues, so we need to be very conservative, and often silently cancel optimizations when something might be wrong. In contrast, typechecking failure is a compile-time problem, so we can make it more user visible, and defer to the user (via suppressions or annotations) when we get false positives.

@nreid260
thanks, it works !
class Test {
    constructor() {
      Object.defineProperty( this, 'isTest', { value: true } );
      Object.defineProperties( this, { isTest2: { value: true } } );
    }
}

so isTest2 can be suppressed, but isTest is always undefined :(
class a{constructor(){Object.defineProperty(this,"isTest",{value:!0});Object.defineProperties(this,{a:{value:!0}})}};

@nreid260
thanks, it works !
class Test {
    constructor() {
      Object.defineProperty( this, 'isTest', { value: true } );
      Object.defineProperties( this, { isTest2: { value: true } } );
    }
}

so isTest2 can be suppressed, but isTest is always undefined :(
class a{constructor(){Object.defineProperty(this,"isTest",{value:!0});Object.defineProperties(this,{a:{value:!0}})}};


Remove redundant log

Alternatively keep this one and remove the other

this isn't redundant? What other one?


setEncoding function not defined

Line 117 of index.js
process.stdout.setEncoding('utf8');

is causing this error on nodejs v0.12.7.
unexpected error
[TypeError: undefined is not a function]
TypeError: undefined is not a function
    at /home/ubuntu/npm/lib/node_modules/pouchdb-dump-cli/index.js:117:22
    at Array.<anonymous> (/home/ubuntu/npm/lib/node_modules/pouchdb-dump-cli/node_modules/lie/lib/unwrap.js:11:21)
    at nextTick (/home/ubuntu/npm/lib/node_modules/pouchdb-dump-cli/node_modules/lie/node_modules/immediate/lib/index.js:61:18)
    at process._tickCallback (node.js:355:11)

On nodejs v0.10 the error was more descriptive and mentioned the function "setEncoding" was not defined.
Looking around I found links to similar issues:
https://github.com/voodootikigod/node-serialport/issues/324
https://groups.google.com/forum/#!topic/nodejs/BAv7deMw_48
Simply commenting out line 117 fixes the issue and allows the script to run.
I was originally running the default nodejs and npm packages on Ubuntu 14.04.
I've since manually upgrade nodejs to the latest version v0.12.7.
I hope this helps.

Hm, it looks like Node removed this method in 0.12. I can't find any documentation about what to do to upgrade, though. :/

This is really weird. I've tested in Node v0.12.7, Node v0.10.40, and iojs 1.5.0, and I cannot reproduce this issue. I'm on Linux Mint Rebecca. I'm able to dump to stdout just fine; the setEncoding line is not throwing an error.

process.stdout.setEncoding exists when process.stdout is of type 'tty', but not when it is of type 'fs'.
To test this, first run the following in a terminal
node -e 'process.stdout.setEncoding("utf8")'
This will workout fine. Then try to run
node -e 'process.stdout.setEncoding("utf8")' > foo
this will fail with "TypeError: process.stdout.setEncoding is not a function". The node code for selecting type of stdout is found in createWritableStdioStream here:
https://github.com/nodejs/node/blob/2ba7baac93d8261d365412b5f000ea9a2de45a04/src/node.js
I have used a later version of node when investigating this but I suspect we see a result of the same issue.
The fix in my case was to replace
process.stdout.setEncoding('utf8')
process.stdout.write(...)
with
process.stdout.write(..., 'utf8')

AFAICT this is fixed in the latest release. Please reopen if I'm wrong: https://github.com/nolanlawson/pouchdb-dump-cli/blob/558b9a8515ef49bf1f3756234c7153a282c73585/index.js#L117-L120


Failure while downloading  reranker model

Bug Report
Description
Failure to download the reranker model from the UI, UI hangs and healthcheck fails. Need to rebuild the container every time.
"GET /ws/socket.io/?EIO=4&transport=polling&t=P3UgWz5&sid=bsurF5q0lo1p8SNnAAEd HTTP/1.0" 200 OK
INFO  [apps.rag.main] Updating reranking model:  to BAAI/bge-reranker-v2-m3
INFO  [config] Saving 'RAG_RERANKING_MODEL' to config.json
ERROR [apps.rag.utils] Cannot determine model snapshot path: Cannot find an appropriate cached snapshot folder for the specified revision on the local disk and outgoing traffic has been disabled. To enable repo look-ups and downloads online, pass 'local_files_only=False' as input.
Traceback (most recent call last):
  File "/app/backend/apps/rag/utils.py", line 353, in get_model_path
    model_repo_path = snapshot_download(**snapshot_kwargs)
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/huggingface_hub/utils/_validators.py", line 114, in _inner_fn
    return fn(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/huggingface_hub/_snapshot_download.py", line 220, in snapshot_download

Bug Summary:
[Provide a brief but clear summary of the bug]
Steps to Reproduce:
From the webui/admin panel/documents click hybrid search and add BAAI/bge-reranker-v2-m3 in the field, and click download icon. It keeps downloading and the server fails.
Expected Behavior:
Should download model and ready for queries.
Actual Behavior:
Server crashes
Environment

Open WebUI Version: [e.g., 0.1.120]

Ollama (if applicable): [e.g., 0.1.30, 0.1.32-rc1]

Operating System: Ubuntu 22.04

Browser (if applicable): [e.g., Chrome 100.0, Firefox 98.0]

Reproduction Details
Confirmation:

[x] I have read and followed all the instructions provided in the README.md.
[x] I am on the latest version of both Open WebUI and Ollama.
[] I have included the browser console logs.
[x] I have included the Docker container logs.

Logs and Screenshots
Browser Console Logs:
[Include relevant browser console logs, if applicable]
Docker Container Logs:
"GET /ws/socket.io/?EIO=4&transport=polling&t=P3UgWz5&sid=bsurF5q0lo1p8SNnAAEd HTTP/1.0" 200 OK
INFO  [apps.rag.main] Updating reranking model:  to BAAI/bge-reranker-v2-m3
INFO  [config] Saving 'RAG_RERANKING_MODEL' to config.json
ERROR [apps.rag.utils] Cannot determine model snapshot path: Cannot find an appropriate cached snapshot folder for the specified revision on the local disk and outgoing traffic has been disabled. To enable repo look-ups and downloads online, pass 'local_files_only=False' as input.
Traceback (most recent call last):
  File "/app/backend/apps/rag/utils.py", line 353, in get_model_path
    model_repo_path = snapshot_download(**snapshot_kwargs)
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/huggingface_hub/utils/_validators.py", line 114, in _inner_fn
    return fn(*args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/huggingface_hub/_snapshot_download.py", line 220, in snapshot_download

Screenshots (if applicable):
[Attach any relevant screenshots to help illustrate the issue]
Installation Method
Docker installation
Additional Information
Added the following suggestions but still crashes: RAG_EMBEDDING_MODEL_AUTO_UPDATE=False
and
RAG_EMBEDDING_MODEL_TRUST_REMOTE_CODE = True
Note
If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!

Try with:
RAG_EMBEDDING_MODEL_AUTO_UPDATE=True
RAG_RERANKING_MODEL_AUTO_UPDATE=True
RAG_EMBEDDING_MODEL_TRUST_REMOTE_CODE=True
RAG_RERANKING_MODEL_TRUST_REMOTE_CODE=True

As env. Worked for me.

Hello, I have the same problem, and setting the four environment variables as suggested above during the startup of the Docker container does not help. Keeps giving the same error message.

I had some non sense issue, and the root cause was ipv6 inside the container. Maybe it worth a try to disable it.

Mind reporting that? I have issues with every reranker other than v2_m3
On Sat, Jul 27, 2024, 19:36 -_- @.***> wrote:

I had some non sense issue, and the root cause was ipv6 inside the
container. Maybe it worth a try to disable it.
—
Reply to this email directly, view it on GitHub
https://github.com/open-webui/open-webui/issues/4086#issuecomment-2254209055,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACPQVDLIEBJUC3ILFHKEGKDZOPLDVAVCNFSM6AAAAABLMIUUJCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJUGIYDSMBVGU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Mind reporting that? I have issues with every reranker other than v2_m3
…
On Sat, Jul 27, 2024, 19:36 -_- @.***> wrote: I had some non sense issue, and the root cause was ipv6 inside the container. Maybe it worth a try to disable it.

My issue was related to web search.

same error encountered, waiting for a resolution

Same problem here but I think is due to the fact that BAAI/bge-reranker-v2-m3 is not supporter by sentence transformer.
For example, with this reranker https://huggingface.co/mixedbread-ai/mxbai-rerank-large-v1 it works well (also web search)

I think I got BAAI/bge-reranker-v2-m3 running.
Container breaks when trying v2-gemma though.
I used the env vars:
RAG_EMBEDDING_MODEL_AUTO_UPDATE=True
RAG_RERANKING_MODEL_AUTO_UPDATE=True
RAG_EMBEDDING_MODEL_TRUST_REMOTE_CODE=True
RAG_RERANKING_MODEL_TRUST_REMOTE_CODE=True

But I didn't change all the parameters in one go, I left the reranker model blank, saving everything else first. And in the last step I enter the reranker model and give it some time to download all files.

Important to note, that I am on a docker-compose setup with ollama always being up-to-date.
The bundled installation had my ollama running some versions behind.

I think that BAAI/bge-reranker-v2-m3 is installed in the docker container of open web ui and didn't use the ollama instance.
If you check the logs of the openwebui container, immediately after a request, it logs any information regarding sentence transformer unable to load the last two layer of v2_m3 (unable to load weights and biases)? the reranker is a xlmroberta with finetuning and cross encoder if i remember correctly and I think that sentence transformer is not able to load this specific architecture (with the addition of the cross encoder)
For v2-gemma i don't have any experience but i suppose it the same problem.
Did you have the models downloaded in the huhhigface cache folder of the openwebui container ( path: /apps/backend/data/cache/embeddings/model or something like this)?

I'll upload my logs later after removing sens content.

any one know how we can download the models manually if we want  ?

I think that From the UI, paste the model name and click the icon with the arrow ⬇
If you want to do it manually I suppose you can enter the terminal of docker container and use hugging face cli

My logs (with no word about the reranker): open-webui_logs(1).txt ollama_logs.txt

Uploaded my logs. Weirdly enough, my AI models tend to forget pre-uploaded files (knowledge base) and just answer like they aren't present.

My logs (with no word about the reranker): open-webui_logs(1).txt ollama_logs.txt

Uploaded my logs. Weirdly enough, my AI models tend to forget pre-uploaded files (knowledge base) and just answer like they aren't present.

Version 0.3.11 seems to have fixed my models from forgetting the knowledge base:

🔧 TAGS HANDLING IN DOCUMENT UPLOAD
Tags are now properly sent to the upload document handler, resolving issues with missing metadata.
📂 STATIC PATH RESOLUTION IN PDF GENERATION
Fixed static paths that adjust dynamically to prevent issues across various environments.

Same problem here but I think is due to the fact that BAAI/bge-reranker-v2-m3 is not supporter by sentence transformer. For example, with this reranker https://huggingface.co/mixedbread-ai/mxbai-rerank-large-v1 it works well (also web search)
This shouldn't be the case as this reranking model is explicitly listed as an example.


Develop Code that opens a specific show in Disney app or prime video

Hi @wdesimini
Thanks for the library,  I want to add deep linking functionality in library. I want that I take a title like "Reacher" on prime video and opens it directly into the app in samsung tv.
However, it is possible to open app like Prime Video or Disney but how to open specific show using Title directly into the app.
Do you know how to do it ?
Thanks

@Alihassan325
Hello, have you solved this problem? I don't know how to get the APP list on the TV and quickly launch the specified APP. Can you help me?

Hi @Kanagizhe
Yes I have solved it, I am able to open a specific app through using @wdesimini tvcommander code.

Hi @Kanagizhe
Yes I have solved it, I am able to open a specific app through using @wdesimini tvcommander code with some modifications in the files.是的，我已经解决了这个问题，我可以通过使用 tvcommander 代码并在文件中进行一些修改来打开特定的应用程序。
Thanks for your reply, what code should I use when I want to start Youtube? can you show a snippet of your code


File too large

Hi,
just noticed the file you provided for download is bigger that 50MB and cannot be uploaded from the lambda console.
thanks
M

@manuelsechi you will need to upload the .zip file to Amazon S3, then will uploading Lambda code, choose Amazon S3 location
Detailed steps are here  Lambda Function Setup.


Purging tasks command doesn't work

Some more focus on this feature would be good.
Maybe allow the purge command to filter "purgables" with an argument of a task ID, project name, timeline name or individual file names.

Sorry. I actually can't remember when I fixed this.
Use the celery command for the time being to purge a queue that isn't the local version constraint key.


GridEngine provider has wrong default wall time

Describe the bug
The GridEngine system expects walltime in seconds, but parsl provides 10, which leads to difficult-to-recognize errors relating to walltime errors.
To Reproduce
Steps to reproduce the behavior, for e.g:

Setup Parsl 0.9.0 with Python 3.6 on cluster
Run a sleep job with GridEngine provider
Watch the qstat, where you will see jobs disappear

Expected behavior
10 minute default walltime
Environment

OS: CentOS 7
Python version 3.6
Parsl version 0.9

Distributed Environment

Where are you running the Parsl script from ? Login node

Where do you need the workers to run ?Worker nodes on same network as login node

The default is provided as a literal walltime="00:10:00" in grid_engine.py and then converted to minutes by job_config["walltime"] = wtime_to_minutes(self.walltime).
A quick google suggests that SGE expects HH:MM:SS format times - although I guess it is accepting a single integer in this case too.
I think this is a bug in the handling of any walltime specification, not only the default value, as an explicitly specified walltime will also go through wtime_to_minutes.


Ethereum - add Sepolia (testnet) network to the connector

Hi,
It would be nice to have sepolia as a network, since it s the new recommended tesnet. I tried just searching for "goerli" and do the appropriate copy paste but doesn't seem to be enough.
Might be really quick for the core team though.
Thanks.

https://github.com/hummingbot/hummingbot/issues/6951


Fix epoch loss calculation in "NMT with attention" colab notebook

The epoch loss that's calculated in the current notebook is a bit inaccurate.
It is currently calculated as total_loss/len(input_tensor). But the total_loss is already averaged across a batch. So, for epoch loss calculation, total_loss needs to be divided by the number of batches instead of total number of examples.
This PR adds code to calculate total number of batches N_BATCH and then calculate the epoch loss as total_loss/N_BATCH.
@lamberta @yashk2810 @tensorflower-gardener

Just a few changes.

Can you please move the total_loss calculation above the variables = encoder.variables + decoder.variables line. It makes the flow of the training loop much clear even though its not used for loss calculation. After that LGTM.

LGTM

@MarkDaoust @caisq Can you merge this PR?

@MarkDaoust I think you also need to add a "ready to pull" label.


[TypeScript] npx create-nuxt-app

I created a Nuxt app and chose TypeScript
But the selection did not come with tsconfig.json instead it was jsconfig.json

This issue will be solved by https://github.com/nuxt/create-nuxt-app/pull/449/


Update installation yamls

Release note:

This is needed to pass https://github.com/istio/pilot/pull/1019/files

/assign @ldemailly


RenderQueueService: Changed From Singleton to Scoped

Description
This small PR changes the RenderQueueService (used only by the docs sites) from singleton to scoped to fix a potential issue if the MudBlazor docs site ever uses BSS for rendering.
In BSS, users share instances of singleton objects.  Thus, all users would have shared the same render queue, and the call to RenderQueue.Clear() in DocsPage.OnInitialized() would have cleared the queue for all users any time any user visited a docs page.   By using scoped, however, each user gets their own render queue.
How Has This Been Tested?
This was tested by running unit tests, as well as by running documentation projects locally:

Running MudBlazor.Docs.WasmHost and MudBlazor.Docs.Server projects
Visiting a big page with lots of sections such as MudTabs and MudTable, as well as MudDataGrid and MudDialog
Spamming clicks to navigate to pages back and forth to ensure that the page navigates quickly and renders completely.

Types of changes

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

[X] The PR is submitted to the correct branch (dev).
[X] My code follows the code style of this project.
[ ] I've added relevant tests.

Notes for Reviewers
This fix only has value if the docs site ever uses BSS, such as when auto-rendering in future .NET versions.  There is no current issue for the WASM site, however, since singleton services in WASM are still a separate instance per tab.

Thanks @jperson2000


⚠ Bofrost.es has degraded performance

In ae9a590, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 2005 ms

Resolved: Bofrost.es performance has improved in 33271fc after 6 minutes.


Add Example: HTTP server: Upload file to Deno by Example

Created a TypeScript file in /examples to illustrate a very basic approach to using Deno.serve() to facilitate uploading files using HTML forms, along with a resource link to Fresh docs to do the same.
Note: I couldn't find any way around encoding the form HTML string to get it to show on the docs page: Lume or whatever isn't auto encoding in the <code> block. This also led me to find what I believe is another bug in Deno docs (or Lume? or codemirror?) not display the generic class (presumably because it's getting interpreted as an HTML element.)
Anyway to make sure the code actually works (and displays on the docs) I used @std/html/entities unescape() on the encoded HTML string before sending it off in the Response.
Closes #42

Request for review @thisisjofrank

Request for review @philhawksworth 🫡

Thanks for this example! I'll take a look at how the examples pages are being generated and see if I can fix that html encoding bug.


'No toolchains found' when building libtensorflow on FreeBSD 13

Trying to build libtensorflow on FreeBSD 13 I was getting this toolchain error:
bazel build --config opt --toolchain_resolution_debug=@bazel_tools//tools/cpp:toolchain_type //tensorflow/tools/lib_package:libtensorflow
INFO: ToolchainResolution: Type @bazel_tools//tools/cpp:toolchain_type: target platform @local_execution_config_platform//:platform: Rejected toolchain @local_config_cc//:cc-compiler-freebsd; mismatching values: freebsd
INFO: ToolchainResolution: Type @bazel_tools//tools/cpp:toolchain_type: target platform @local_execution_config_platform//:platform: No toolchains found.

Looks like something happens to the execution platform here:
https://github.com/tensorflow/tensorflow/blob/9584c52ecfbbc33b3be48903cdadd41b4a2bb083/third_party/remote_config/remote_platform_configure.bzl#L3-L12
I'm not sure exactly how this all works, but adding a branch for freebsd seems to have fixed the issue:
         elif os.startswith("freebsd"):
             platform = "freebsd"

After that the toolchain is selected properly but the library still won't build.  I had to add the following lines to .bazelrc:
build:freebsd --cxxopt=-std=c++14
build:freebsd --host_cxxopt=-std=c++14

Now the code will compile, but it won't link. The linker will fail with ld: error: undefined symbol: environ.
After googling a bit, this seems to be a known issue when building shared objects referencing environ (link)
In the end I just removed -z defs in tensorflow/BUILD and after that libtensorflow built successfully. The mini hello_tf.c example from the official site worked fine too.

FreeBSD 13.1-RELEASE
clang 13.0.0
bazel 5.2.0
python 3.9.13
tensorflow-2.9.1

@desuwa,
Could you try bazel clean --expunge followed by bazel sync. Also please provide the complete error log which helps to debug the issue. Thank you!

Full log after bazel clean --expunge and bazel sync
> bazel build --config opt --config verbose_logs --toolchain_resolution_debug=@bazel_tools//tools/cpp:toolchain_type //tensorflow/tools/lib_package:libtensorflow
WARNING: option '--output_filter' was expanded to from both option '--config=short_logs' (source /usr/home/bsd/misc_tf/tensorflow-2.9.1/.bazelrc) and option '--config verbose_logs' (source command line options)
INFO: Options provided by the client:
  Inherited 'common' options: --isatty=1 --terminal_columns=232
INFO: Reading rc options for 'build' from /usr/home/bsd/misc_tf/tensorflow-2.9.1/.bazelrc:
  Inherited 'common' options: --experimental_repo_remote_exec
INFO: Reading rc options for 'build' from /usr/local/etc/bazel/bazel.bazelrc:
  'build' options: --strategy=Javac=standalone --java_runtime_version=11 --tool_java_runtime_version=11 --action_env=PATH=/bin:/usr/bin/:/usr/local/bin
INFO: Reading rc options for 'build' from /usr/home/bsd/misc_tf/tensorflow-2.9.1/.bazelrc:
  'build' options: --define framework_shared_object=true --define=use_fast_cpp_protos=true --define=allow_oversize_protos=true --spawn_strategy=standalone -c opt --announce_rc --define=grpc_no_ares=true --noincompatible_remove_legacy_whole_archive --enable_platform_specific_config --define=with_xla_support=true --config=short_logs --config=v2 --define=no_aws_support=true --define=no_hdfs_support=true --experimental_cc_shared_library
INFO: Reading rc options for 'build' from /usr/home/bsd/misc_tf/tensorflow-2.9.1/.tf_configure.bazelrc:
  'build' options: --action_env PYTHON_BIN_PATH=/usr/local/bin/python3 --action_env PYTHON_LIB_PATH=/usr/local/lib/python3.9/site-packages --python_path=/usr/local/bin/python3
INFO: Reading rc options for 'build' from /usr/home/bsd/misc_tf/tensorflow-2.9.1/.bazelrc:
  'build' options: --deleted_packages=tensorflow/compiler/mlir/tfrt,tensorflow/compiler/mlir/tfrt/benchmarks,tensorflow/compiler/mlir/tfrt/jit/python_binding,tensorflow/compiler/mlir/tfrt/jit/transforms,tensorflow/compiler/mlir/tfrt/python_tests,tensorflow/compiler/mlir/tfrt/tests,tensorflow/compiler/mlir/tfrt/tests/ir,tensorflow/compiler/mlir/tfrt/tests/analysis,tensorflow/compiler/mlir/tfrt/tests/jit,tensorflow/compiler/mlir/tfrt/tests/lhlo_to_tfrt,tensorflow/compiler/mlir/tfrt/tests/tf_to_corert,tensorflow/compiler/mlir/tfrt/tests/tf_to_tfrt_data,tensorflow/compiler/mlir/tfrt/tests/saved_model,tensorflow/compiler/mlir/tfrt/transforms/lhlo_gpu_to_tfrt_gpu,tensorflow/core/runtime_fallback,tensorflow/core/runtime_fallback/conversion,tensorflow/core/runtime_fallback/kernel,tensorflow/core/runtime_fallback/opdefs,tensorflow/core/runtime_fallback/runtime,tensorflow/core/runtime_fallback/util,tensorflow/core/tfrt/common,tensorflow/core/tfrt/eager,tensorflow/core/tfrt/eager/backends/cpu,tensorflow/core/tfrt/eager/backends/gpu,tensorflow/core/tfrt/eager/core_runtime,tensorflow/core/tfrt/eager/cpp_tests/core_runtime,tensorflow/core/tfrt/gpu,tensorflow/core/tfrt/run_handler_thread_pool,tensorflow/core/tfrt/runtime,tensorflow/core/tfrt/saved_model,tensorflow/core/tfrt/graph_executor,tensorflow/core/tfrt/saved_model/tests,tensorflow/core/tfrt/tpu,tensorflow/core/tfrt/utils
INFO: Found applicable config definition build:short_logs in file /usr/home/bsd/misc_tf/tensorflow-2.9.1/.bazelrc: --output_filter=DONT_MATCH_ANYTHING
INFO: Found applicable config definition build:v2 in file /usr/home/bsd/misc_tf/tensorflow-2.9.1/.bazelrc: --define=tf_api_version=2 --action_env=TF2_BEHAVIOR=1
INFO: Found applicable config definition build:opt in file /usr/home/bsd/misc_tf/tensorflow-2.9.1/.tf_configure.bazelrc: --copt=-Wno-sign-compare --host_copt=-Wno-sign-compare
INFO: Found applicable config definition build:verbose_logs in file /usr/home/bsd/misc_tf/tensorflow-2.9.1/.bazelrc: --output_filter=
DEBUG: Rule 'io_bazel_rules_docker' indicated that a canonical reproducible form can be obtained by modifying arguments shallow_since = "1596824487 -0400"
DEBUG: Repository io_bazel_rules_docker instantiated at:
  /usr/home/bsd/misc_tf/tensorflow-2.9.1/WORKSPACE:23:14: in <toplevel>
  /usr/home/bsd/misc_tf/tensorflow-2.9.1/tensorflow/workspace0.bzl:107:34: in workspace
  /usr/home/bsd/.cache/bazel/_bazel_bsd/54facdc05a3adaa7a5494da058ea6245/external/bazel_toolchains/repositories/repositories.bzl:35:23: in repositories
Repository rule git_repository defined at:
  /usr/home/bsd/.cache/bazel/_bazel_bsd/54facdc05a3adaa7a5494da058ea6245/external/bazel_tools/tools/build_defs/repo/git.bzl:199:33: in <toplevel>
INFO: ToolchainResolution:     Type @bazel_tools//tools/cpp:toolchain_type: target platform @local_config_platform//:host: Rejected toolchain @local_config_cc//:cc-compiler-armeabi-v7a; mismatching values: arm, android
INFO: ToolchainResolution:     Type @bazel_tools//tools/cpp:toolchain_type: target platform @local_config_platform//:host: Rejected toolchain @local_config_cc//:cc-compiler-armeabi-v7a; mismatching values: arm, android
INFO: ToolchainResolution:     Type @bazel_tools//tools/cpp:toolchain_type: execution platform @local_execution_config_platform//:platform: Rejected toolchain @local_config_cc//:cc-compiler-freebsd; mismatching values: freebsd
INFO: ToolchainResolution:   Type @bazel_tools//tools/cpp:toolchain_type: target platform @local_config_platform//:host: execution @local_config_platform//:host: Selected toolchain @local_config_cc//:cc-compiler-freebsd
INFO: ToolchainResolution:     Type @bazel_tools//tools/cpp:toolchain_type: execution platform @local_execution_config_platform//:platform: Rejected toolchain @local_config_cc//:cc-compiler-freebsd; mismatching values: freebsd
INFO: ToolchainResolution:   Type @bazel_tools//tools/cpp:toolchain_type: target platform @local_config_platform//:host: execution @local_config_platform//:host: Selected toolchain @local_config_cc//:cc-compiler-freebsd
INFO: ToolchainResolution: Target platform @local_config_platform//:host: Selected execution platform @local_config_platform//:host, type @bazel_tools//tools/cpp:toolchain_type -> toolchain @local_config_cc//:cc-compiler-freebsd, type @bazel_tools//tools/python:toolchain_type -> toolchain @local_config_python//:py_runtime_pair
INFO: ToolchainResolution: Target platform @local_config_platform//:host: Selected execution platform @local_config_platform//:host, type @bazel_tools//tools/cpp:toolchain_type -> toolchain @local_config_cc//:cc-compiler-freebsd
INFO: ToolchainResolution: Target platform @local_config_platform//:host: Selected execution platform @local_config_platform//:host, type @bazel_tools//tools/cpp:toolchain_type -> toolchain @local_config_cc//:cc-compiler-freebsd
INFO: ToolchainResolution:     Type @bazel_tools//tools/cpp:toolchain_type: target platform @local_execution_config_platform//:platform: Rejected toolchain @local_config_cc//:cc-compiler-armeabi-v7a; mismatching values: arm, androidINFO: ToolchainResolution:     Type @bazel_tools//tools/cpp:toolchain_type: target platform @local_execution_config_platform//:platform: Rejected toolchain @local_config_cc//:cc-compiler-freebsd; mismatching values: freebsd
INFO: ToolchainResolution:   Type @bazel_tools//tools/cpp:toolchain_type: target platform @local_execution_config_platform//:platform: No toolchains found.
ERROR: /usr/home/bsd/.cache/bazel/_bazel_bsd/54facdc05a3adaa7a5494da058ea6245/external/com_google_protobuf/BUILD:415:10: While resolving toolchains for target @com_google_protobuf//:protoc: No matching toolchains found for types @bazel_tools//tools/cpp:toolchain_type. Maybe --incompatible_use_cc_configure_from_rules_cc has been flipped and there is no default C++ toolchain added in the WORKSPACE file? See https://github.com/bazelbuild/bazel/issues/10134 for details and migration instructions.
ERROR: Analysis of target '//tensorflow/tools/lib_package:libtensorflow' failed; build aborted:
INFO: Elapsed time: 140.511s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (170 packages loaded, 3623 targets configured)

@desuwa,
Could you please try to install with a compatible version as mentioned below and check if you are facing the same error.

Version
Python version
Compiler
Build tools

tensorflow-2.9.0
3.7-3.10
Clang from xcode 10.14
Bazel 5.0.0

tensorflow-2.8.0
3.7-3.10
Clang from xcode 10.14
Bazel 4.2.1

tensorflow-2.7.0
3.7-3.9
Clang from xcode 10.11
Bazel 3.7.2

Thank you!

I'm using Python 3.9.13, this should be fine , right?

@desuwa,
Python v3.9.13 is compatible. Could you please the comment and let us know if you are facing the same issue. Thank you!

Yes. Python 3.9.13 is what I've been using initially.
I'll edit the first post to mention this.

@desuwa,
Could you please try to install with a compatible version as mentioned here and let us know if you are facing the same error. Thank you!

Yes, same issue with compatible versions of everything.

Hi @desuwa, Officially, Tensorflow build does not support FreeBSD OS.
Custom builds are available via SIG Build (https://github.com/tensorflow/build), You can try SIG build. Thank you!

It would build fine on FreeBSD if the bazel file I linked in the issue didn't have this oversight of overwriting the "freebsd" platform tag to "linux".

Hi @desuwa, Bazel Config has default OS mentioned as Linux. It will take all the default configurations of Linux to build Tenaorflow. You can try with replacing Linux by freebsd. Thank you!

@jxy posted a patch that makes this work at https://github.com/bazelbuild/bazel/issues/13227#issuecomment-1185231470
Lets get it checked in! I was able to build jaxlib and tensorflow on freebsd just now.

This is a genius way of closing issues!  Bravo!

Hi @jxy, Feel free to reopen if it is unresolved. Thank you!


Navigation to mentioned pages from About Us section

Is your feature request related to a problem? Please describe.
In the About Us section, there are highlighted words that mention the features of the PetMe platform. If these texts could navigate the user to their respective page or section it would ensure better and faster navigation.
Describe the solution you'd like
When the mouse hovers over the highlighted words in the About Us section it should provide a hover action and clicking on it the user should be redirected to desired feature pages or section.
Additional context
Screenshot of the above mention section:

If this feels like a good feature, I would like to contriubte to the project by implementing it.

go for it @gopukr


Not able to unmarshal jwk from mitreid-connect

Expected Behavior
proxy able to use jwk to verify id_token signature on callback to /oauth2/callback endpoint
Current Behavior
Receives jwk from oidc issuer, then fails to unmarshal.
[oauthproxy.go:631] Error redeeming code during OAuth2 callback: unable to update session: could not verify id_token: failed to verify signature: fetching keys oidc: failed to decode keys: got Content-Type = application/json, but could not unmarshal as JSON: illegal base64 data at input byte 33

mitreid-connect jwk
Possible Solution
Not an expert at Go but it seems the package jose struct for json key may not support mitreid jwk json objects?
Steps to Reproduce (for bugs)
Register with OpenId MitreId service.  Provide normal oidc issuer config. Fails on callback endpoint.
Your Environment
Running bitnami/oauth2_proxy:latest image locally.
provider = "oidc"
oidc_issuer_url = "https://ouropenidserver.com/openid/"
http_address = "<IP_ADDRESS>:4180"
upstreams = [
    "https://somecoolwebsite.com"
]
email_domains = [
    "*"
]
client_id = "idstuff"
client_secret = "secretstuff"
cookie_secret = "somethingsupersecret"
cookie_secure = false
scope = "openid email profile"
skip_provider_button = true
insecure_oidc_allow_unverified_email = true

Was a formatting issue with the generated keys coming from mitreid.


Getting error 500 when attempting to pull request

My fork is at https://github.com/mathiasose/django-rest-framework-jwt/commit/a62b8f6595b232dc015190cf32ea2586341ef256
I tried opening a PR on June 10th, didn't work.
Then I forgot about it for a while until today, and it still doesn't work.
If you think this change is OK, feel free to "merge" it manually.

Looking through the comments on open issues it's clear a few people are seeing this 500 error when creating pull requests. I know I am. I submitted a ticket with GitHub on June 21 about it but haven't heard any update after their acknowledgment.
@jpadilla do you have any idea what the issue is? It seems you've been able to accept pull requests in the past.

@MattHardcastle reported this issue to GitHub. Will update when I have more info.

This should be resolved.


Cannot composer install

[InvalidArgumentException]
Could not find a version of package jrmadsen67/laravel-feature-test-generator matching your minimum-stability (stable). Require it with an explicit version constraint allowing its desired stability.
I am running on
"php": ">=7.0.0",
"laravel/framework": "5.5.*",

I solved it using this command instead:
composer require jrmadsen67/laravel-feature-test-generator:dev-master


Unsupported token immediately

Summary
Sorry, I'm still new to GraphQL. I have this part of the GraphQL request,
                    asset {
                        id
                        url @transform (width: 1500, immediately: true)
                    }

but it never runs because it throws the error Unsupported token immediately. I think this is a valid GraphQL and the iOS version seems to be ok.
Version
apollo-runtime:2.3.1

Can you try moving the directive after the arguments?
                    asset {
                        id
                        url(width: 1500, immediately: true) @transform
                    }

thank you very much. moving the directive works.
you can close this if this is not actually a bug.

Nice, thanks for the follow up 👍 !


Update manifest: IPEP.Scantailor-Experimental version 0.2024.02.04

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@russellbanks There is a lot of error between my PR and this correct PR.

@russellbanks There is a lot of error between my PR and this correct PR.

Thanks @Exorcism0666. This issue is mainly due to X86-64 recognising as X86. I'll make some changes to fix this.

@russellbanks There is a lot of error between my PR and this correct PR.

Thanks @Exorcism0666. This issue is mainly due to X86-64 recognising as X86. I'll make some changes to fix this.

/AzurePipelines run

/AzurePipelines run


Folder path for Customizing logos

Hi,
Please assist me with the location for custiomizing the logos and uploading institutional image.
Also, I need the DMPonline logo for the website.
Thank you!

Hi all,
any assistance with the above issuse please?
Thank you
Ya'qub


⚠ Bofrost.es has degraded performance

In f530ff9, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1889 ms

Resolved: Bofrost.es performance has improved in 20063f9 after 310 days, 7 hours, 22 minutes.


Savevalue must use [property]=binding

In the release 83 I get this in the top bar.

Fixed in the new shell-selector release


Upload errors "Lost lock mid-transfer"

I'm submitting a ...
[x] bug report
[ ] feature request
[ ] question about the decisions made in the repository
[ ] question about how to use this project

Summary

We're using sofie-atem-connection to upload still images to an Atem constellation mixer from a RaspberryPi model 3B. This works well, allthough the upload time is rather significant, usually taking somewhere between 100 to 130 seconds for 30 images  in 1080p mode.
I thought that maybe switching to a RaspberryPi model 4B could improve upload times, and indeed it does. The same number of images now take at most 40 seconds to upload (when successful).
Unfortunately, with the newer model 4, I often get the error "Error: Lost lock mid-transfer", leading to failed uploads.
Is there anything I can do to troubleshoot the issue and find the root cause?

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. StackOverflow, personal fork, etc.)

I'm using atem-connection 3.2.0 from the npm repository, and nodeJS v18.15.0.

It seems like a bug related to the use of the ThreadedClass library. Setting disableMultithreaded to true seems to solve it for me, but of course it's just a workaround and I wouldn't recommend it unless your use case allows it.

I believe this is fixed by #147 in v3.3.0

Thank you - I can confirm that the issue indeed seems to be fixed.


all: get the kernel configs for a build test

When multiple kernel configs are used, we generate a hash from them to
add to the test name.
Given a tuxsuite yaml config, we can recreate that hash and print the
kernel configs for that test.
Signed-off-by: Justin Cook<EMAIL_ADDRESS>

@chaws Please review, but do not merge.
Right now I'm recreating the test-name function in this script, but perhaps I should move the one in squad-client/commands/tuxbuild_submit and put that in squad-client/utils and use that in this script.
Probably not a requirement for the first version.

Can you provide an example of tuxconfig.yml ?

@chaws https://gitlab.com/Linaro/lkft/pipelines/lkft-common/-/blob/master/tuxconfig.yml

@jscook2345 LGTM! I'd add a sample output as well. What do you think?
$ ./get-kconfig --tuxconfig tuxconfig.yml --name clang-12-defconfig-b9979cfa
[
  {
    "name": "clang-12-defconfig-b9979cfa",
    "set": "i386-clang-12",
    "build": {
      "target_arch": "i386",
      "toolchain": "clang-12",
      "kconfig": [
        "defconfig",
        "https://raw.githubusercontent.com/Linaro/meta-lkft/sumo/recipes-kernel/linux/files/lkft.config",
        "https://raw.githubusercontent.com/Linaro/meta-lkft/sumo/recipes-kernel/linux/files/lkft-crypto.config",
        "https://raw.githubusercontent.com/Linaro/meta-lkft/sumo/recipes-kernel/linux/files/distro-overrides.config",
        "https://raw.githubusercontent.com/Linaro/meta-lkft/sumo/recipes-kernel/linux/files/systemd.config",
        "https://raw.githubusercontent.com/Linaro/meta-lkft/sumo/recipes-kernel/linux/files/virtio.config",
        "CONFIG_IGB=y",
        "CONFIG_UNWINDER_FRAME_POINTER=y"
      ]
    }
  },
  {
    "name": "clang-12-defconfig-b9979cfa",
    "set": "x86-clang-12",
    "build": {
      "target_arch": "x86_64",
      "toolchain": "clang-12",
      "make_variables": {
        "LLVM_IAS": 0
      },
      "kconfig": [
        "defconfig",
        "https://raw.githubusercontent.com/Linaro/meta-lkft/sumo/recipes-kernel/linux/files/lkft.config",
        "https://raw.githubusercontent.com/Linaro/meta-lkft/sumo/recipes-kernel/linux/files/lkft-crypto.config",
        "https://raw.githubusercontent.com/Linaro/meta-lkft/sumo/recipes-kernel/linux/files/distro-overrides.config",
        "https://raw.githubusercontent.com/Linaro/meta-lkft/sumo/recipes-kernel/linux/files/systemd.config",
        "https://raw.githubusercontent.com/Linaro/meta-lkft/sumo/recipes-kernel/linux/files/virtio.config",
        "CONFIG_IGB=y",
        "CONFIG_UNWINDER_FRAME_POINTER=y"
      ]
    }
  }
]

@chaws Done!

Please do not merge this for now @chaws

@roxell would like this output to be more consistent with the output of tuxsuite. He will provide me an example to work with.

any build.json file https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc/-/pipelines

[
  {
    "set_name": "i386-clang-12",
    "target_arch": "i386",
    "toolchain": "clang-12",
    "kconfig": [
      "defconfig",
      "https://raw.githubusercontent.com/Linaro/meta-lkft/sumo/recipes-kernel/linux/files/lkft.config",
      "https://raw.githubusercontent.com/Linaro/meta-lkft/sumo/recipes-kernel/linux/files/lkft-crypto.config",
      "https://raw.githubusercontent.com/Linaro/meta-lkft/sumo/recipes-kernel/linux/files/distro-overrides.config",
      "https://raw.githubusercontent.com/Linaro/meta-lkft/sumo/recipes-kernel/linux/files/systemd.config",
      "https://raw.githubusercontent.com/Linaro/meta-lkft/sumo/recipes-kernel/linux/files/virtio.config",
      "CONFIG_IGB=y",
      "CONFIG_UNWINDER_FRAME_POINTER=y"
    ]
  },
  {
    "set_name": "x86-clang-12",
    "target_arch": "x86_64",
    "toolchain": "clang-12",
    "make_variables": {
      "LLVM_IAS": 0
    },
    "kconfig": [
      "defconfig",
      "https://raw.githubusercontent.com/Linaro/meta-lkft/sumo/recipes-kernel/linux/files/lkft.config",
      "https://raw.githubusercontent.com/Linaro/meta-lkft/sumo/recipes-kernel/linux/files/lkft-crypto.config",
      "https://raw.githubusercontent.com/Linaro/meta-lkft/sumo/recipes-kernel/linux/files/distro-overrides.config",
      "https://raw.githubusercontent.com/Linaro/meta-lkft/sumo/recipes-kernel/linux/files/systemd.config",
      "https://raw.githubusercontent.com/Linaro/meta-lkft/sumo/recipes-kernel/linux/files/virtio.config",
      "CONFIG_IGB=y",
      "CONFIG_UNWINDER_FRAME_POINTER=y"
    ]
  }
]

Thank you @jscook2345, but when I look at this again, I don't thing we need this script for... What we should do is to allow the squad-client submit_tuxbuild bits to push the kconfig list from the build.json file. This way we will get the correct fragments.
If we do what we do in this script,  if I send a build result today to squad. Tomorrow I update tuxconfig.yml with a new kernel fragment and submit a new build... when you use this script against the same tuxconfig.yml it will get the latest or does the user need to keep track of the tuxconfig.yml version?
Where are we going to use this script?
the script should just be to pull data via squad-client for the exact build "test" we want.

@roxell
I think that we want both.
Given a test name that is hashed, it would be useful to know where in the tuxconfig it is. That information is not completely in squad, so squad isn't really needed for that.
You would need to version the tuxconfig.yml file, but perhaps we could dig through git to search through older versions?
This script was meant as a quick way to determine the kconfigs for a given test hash, but seems to be just as useful to determine where in the tuxconfig it is.
If we want to push the kconfigs and query squad for a test and get all the information about it, that sounds like something I could do in another sprint, if you think that's useful?

@jscook2345 @roxell just FYI, I released squad-client with submitting kconfig as test metadata.

Closing in favor of #10


Move Latte filters and their arguments to one PSI element that encapsulates this

For future improvements (eg: validate filter argument types)

Resolved in v1.1.4


Place Field to support 1D

The place_field method functions with 2D data only. What is required to either adapt it, or write an alternative, 1D method?

in power_spectrum np.fft.rfftfreqs -> np.fft.rfftfreq no s

Unrelated to this issue, but that typo will be fixed in version 0.6.0


Create easy contribution method for people unfamiliar with Git

Preferably an easy-to-fill form that produces the JSON, and hopefully provides a link to immediately open a PR.

Work has begun with the new "Generate a Game" system.


add post process to more pcells

@HelgeGehring
@sebastian-goeldi
@nikosavola
@tvt173
Could we do this in the cell decorator?
this would simplify the definition of the cell
This would need to be supported by kfactory as well if implemented

In kfactory the easiest way I see is this https://github.com/gdsfactory/kfactory/pull/249

this can be used for adding info, padding, or LVS marker layers that are different for each type of container


Generate 256x256 size training data

I have encountered an issue when generating 256x256 training dataset.
However, I can generate 1024x1024 training data without any error.
The generate_fake_data.py script failed with the following error message:
Traceback (most recent call last):
  File "generate_fake_data.py", line 85, in <module>
    main(args)
  File "generate_fake_data.py", line 37, in main
    stylegan_G(tf.ones((1, 512)))
  File "/usr/local/lib/python3.7/dist-packages/tensorflow/python/keras/engine/base_layer.py", line 1012, in __call__
    outputs = call_fn(inputs, *args, **kwargs)
  File "../model/stylegan.py", line 483, in call
    x = self.model_synthesis(x)
  File "/usr/local/lib/python3.7/dist-packages/tensorflow/python/keras/engine/base_layer.py", line 998, in __call__
    input_spec.assert_input_compatibility(self.input_spec, inputs, self.name)
  File "/usr/local/lib/python3.7/dist-packages/tensorflow/python/keras/engine/input_spec.py", line 274, in assert_input_compatibility
    ', found shape=' + display_shape(x.shape))
ValueError: Input 0 is incompatible with layer G_synthesis: expected shape=(None, 14, 512), found shape=(1, 18, 512)

If I change to TF version 2.3.0, the error becomes a warning and the 256x256 data can still be generated.
WARNING:tensorflow:Model was constructed with shape (None, 14, 512) for input Tensor("G_synthesis/dlatents_in:0", shape=(None, 14, 512), dtype=float32), but it was called on an input with incompatible shape (None, 18, 512).

Hi @NTU-P04922004,
Thanks for bringing this bug to my attention. I see a shape mismatch but, weird enough, I don't encounter any error or warning with my TF 2.0 environment.
Anyway, I just pushed a new commit that I believe resolves this issue. Please confirm, as I wasn't able to reproduce the error.

@YotamNitzan
I have tested the updated code and the issue is resolved, thanks.


Company Ledger Page - Show unbilled project and unsettled invoice when click on then in table view

Describe the bug

when we click on unbilled project show unbilled project and when we click on unsettled invoice then show invoice and receipt which are unsettled

https://www.berrycast.com/conversations/69c5ae54-3da5-5500-bd16-e9e17388c78e

Its already showing Unsettled Invoice / Receipt, but
Ledger pe only Invoice Unsettled ka count manga tha
If Invoice / Receipt Count required then please specify here
Now about Click and show part
Filter available on Transaction page can show any one Type at a time
either Invoice or Receipt

Currently Unsettled Filter is already applied with 2 year filter
So Count contains all Transaction Invoice Count beyond any period
but Transaction Page shows only 2 year max period,
Please Clear what to do!

Hum yeh dikhate hai transaction page pe udhar koi problem nahi hai? wohi humko idhar dikhana hai side se


[ASK] How to install on Azure ML

Description
Running pip install ms-recommenders does not work despite saying successfully installed.
So I am using pip install git+https://github.com/microsoft/recommenders#egg=recommenders instead
However, I am not clear how do I have a more permanent way to install the library like in Databricks. Running the quick start notebook also failed with cannot find module reommenders.
Other Comments

Looks like 7.0 renamed back to recommendersand now I am able to do a simplepip install`


Support ENV setup script on CentOS8

Support ENV setup script on CentOS8.

CC: @raulcd

As part of this PR we probably should add a docker-compose Centos build, similar to the one we have for Ubuntu, to test this script. Potentially we should follow up with an additional PR to add a scheduled CircleCI job to validate this does not get out of date.
My concern of merging this as it is is that this utility script is never used at the moment and it can get outdated easily if we don't add ways to easily test it.

Thanks a lot for the PR @zhixingheyi-tian !

Hi @mbasmanova
There is a need to run Velox on CentOS 8, Kernel 4.18.
So need one  one-click setup script.
Have validated this script on bare-mental CentOS 8 server. The Velox can be built successfully after this script..

docker-compose

Hi @raulcd
For CI test, I can provide one CentOS docker image. Then how to set CI job with this image?
Thanks

As part of this PR we probably should add a docker-compose Centos build, similar to the one we have for Ubuntu, to test this script. Potentially we should follow up with an additional PR to add a scheduled CircleCI job to validate this does not get out of date. My concern of merging this as it is is that this utility script is never used at the moment and it can get outdated easily if we don't add ways to easily test it.

Hi @raulcd
For CI test, I can provide one CentOS docker image. Then how to set CI job with this image?
Thanks

Hi  @raulcd
Have add centos-8-stream.dockerfile for further CI validation.
Thanks,

Hi @mbasmanova @raulcd , is this OK?
Thanks!

Hi @raulcd ,
There?


Fix issue with flatmapped stream that ends while value is being emitted

Currently, if you call .flatMap with a callback that returns an ended property (which triggers an optimized code path in flatMap) and during dispatch of the value the flatMapped stream is ended, then an exception is thrown ("can't read length property of null"). This bug was introduced in https://github.com/kefirjs/kefir/pull/274.
I noticed this issue when updating a project to the latest version of Kefir and one of the unit tests using Kefir failed on this.
This PR contains the fix and a newly-fixed test.
(I renamed my Github account recently. It was previously @AgentME.)

This seems fine otherwise but the test itself doesn't validate the behavior. I think you just need to assert the created stream itself is ended.

Yeah that's fair. I'll add an assert or two that verifies everything went through as expected. (The test is checking for a lack of exceptions; pre-patch the test will fail with an exception.)

I updated the test to check that the stream did in fact end, and made use of some pre-existing helpers.

LGTM!


Create saga for fetching all of a contractor's projects

contractorProjects to get all projects a contractor is assigned to. Thank you!


[ZEPPELIN-2467] Restore travis second job functionality

What is this PR for?
issue ZEPPELIN-2467 has resolved by https://github.com/apache/zeppelin/pull/2300. However https://github.com/apache/zeppelin/commit/8194a5e0af0e1b926b27ea9e0d12bdf9d0e43b4b reverts #2300.
This PR apply #2300 again with two more test exclusion:

SecurityRestApiTest (https://issues.apache.org/jira/browse/ZEPPELIN-2545)
NotebookSecurityRestApiTest (https://issues.apache.org/jira/browse/ZEPPELIN-2546)

What type of PR is it?
Bug Fix
What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-2467
How should this be tested?
CI becomes green
Questions:

Does the licenses files need update? no
Is there breaking changes for older versions? no
Does this needs documentation? no

\cc @AlexanderShoshin

Merge to master if no further discussions


Do not restart SQL thread in RestartReplicationQuick

Related issue: https://github.com/openark/orchestrator/issues/1308
Description
This PR  removes stop and start of SQL thread from RestartReplicationQuick function.
This is done to fix the replication lag that could occur because of restart of SQL thread on the replicas as explained in the issue #1308.

Closes #1308


Link click crashes WPinternals 2.9.0 & 2.9.1

Problem Description:
Clicking on the following URL's crashed WPinternals on my devices:

"Buying me a beer"
"www.wpinternals.net"
"Windows Device Recovery Tool"
"google search" (for both listed drivers)
"download" (for ffu-file)
"known bug"
etc.

Reproducing this bug:
Click on any of the listed example URL's (Getting Started Tab), which leads to a crash.
Device Specification:
The bug was reproduced on:

Device
OS
Architecture

Aspire 5520G
Windows 7
x64

I7-4790 system
Windows 10
x64

WPinternals Version
The bug has been verified to be present on version 2.9.0 & 2.9.1.
Suspected Cause
Difference in handling URL's to prior versions.
Image

I'd be happy to provide more information, thank you for your work!

Thanks! Fixed as of 2.9.2.

Hello, WPInternals is a great job, of course about Lumia 950XL is so old issue, and today I have problems, FUU file download stops suddently, and I've try Ir a lot of times and at different hours... Can you help me to get this file?


sqldiff strips size from character varying under Postgres

One of my favorite features of django-extensions is the sqldiff command. It's really useful when working through development of django projects. But we've discovered a small "glitch" when used with Postgres.
model file declared thusly:
myfield = models.CharField(max_length=8)

Becomes this in Postgres:
    Column |     Type                      |
---------------+---------------------------------+
    myfield  |  character varying(9)   |

BUT sqldiff returns:
ALTER TABLE "mytable"
           ALTER "myfield" TYPE VARCHAR;

notice -- sqldiff wants to strip the size from the varchar declaration.
I understand it's a completely harmless suggestion from sqldiff (postgres actually draws no distinction between the two scheme declarations).  BUT -- we prefer having the size field preserved as a form of documentation in the schema.
We're somewhat familiar with the django-extensions code base but we're still a bit new to it -- and it does some pretty sophisticated things (cool -- but sophisticated). Any suggestions on where in the code we could focus our attention to apply our own "patch" would be greatly appreciated!
Thanks
Jim

Closing this ticket. If it's still an issue please open a new ticket.


Break users into its own class

This is part of issue https://github.com/pyapi-gitlab/pyapi-gitlab/issues/243

This will hold all methods related to https://docs.gitlab.com/ce/api/users.html

DONE!


[FIX,AUTOTVM] Print warning when all autotvm tasks fail with errors

I recently encountered an issue where all my autotvm tasks failed. Unfortunately, I got no warnings, so I was very confused when I got a bunch of fallback config messages.
This PR fixes this situation by printing an error message is no config can be generated.

@comaniac CI is all green now.

Thanks @tkonolige


Demos template typo

"Prefer bize-sized descriptions in bullet points:" -> bite-sized
Also, perhaps a section for similar/alternate use cases?

Perhaps the similar/alternate use case section could be put into its own issue?

See #108 for alternative use cases


dht: Error on device update! - DHT11 sensor doesn't work

Home Assistant release with the issue: 0.66.1
Last working Home Assistant release (if known): N/A
Operating environment (Hass.io/Docker/Windows/etc.): Raspberry Pi3
Component/platform: DHT11 Temperature/Humidity Sensor
https://www.home-assistant.io/components/sensor.dht/
Description of problem:
I got the following error messages:
dht: Error on device update!
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/helpers/entity_platform.py", line 188, in _async_add_entity
    await entity.async_device_update(warning=False)
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/helpers/entity.py", line 327, in async_device_update
    yield from self.hass.async_add_job(self.update)
  File "/usr/lib/python3.5/asyncio/futures.py", line 380, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/lib/python3.5/asyncio/tasks.py", line 304, in _wakeup
    future.result()
  File "/usr/lib/python3.5/asyncio/futures.py", line 293, in result
    raise self._exception
  File "/usr/lib/python3.5/concurrent/futures/thread.py", line 55, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/sensor/dht.py", line 125, in update
    self.dht_client.update()
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/util/__init__.py", line 319, in wrapper
    result = method(*args, **kwargs)
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/sensor/dht.py", line 160, in update
    self.sensor, self.pin)
  File "/srv/homeassistant/lib/python3.5/site-packages/Adafruit_DHT/common.py", line 94, in read_retry
    humidity, temperature = read(sensor, pin, platform)
  File "/srv/homeassistant/lib/python3.5/site-packages/Adafruit_DHT/common.py", line 81, in read
    return platform.read(sensor, pin)
  File "/srv/homeassistant/lib/python3.5/site-packages/Adafruit_DHT/Raspberry_Pi_2.py", line 34, in read
    raise RuntimeError('Error accessing GPIO.')
RuntimeError: Error accessing GPIO.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

sensor:
  - platform: dht
    sensor: DHT11
    pin: 4
    temperature_offset: 2.1
    humidity_offset: -3.2
    monitored_conditions:
      - temperature
      - humidity

See https://www.home-assistant.io/docs/installation/hassbian/integrations/#raspberry-pi-gpio


Table PUT statements don't support values that are lists

Lists are not supported in the following PUT endpoints:
PUT /v1/networks/{networkId}/tables/{tableType}
PUT /v1/networks/{networkId}/tables/{tableType}/columns/{columnName}

Fixed in c946690216f9798296cbacf0aaf4257f0604a6ea
Awaiting release.


Several fixes, including fixing a timing attack

Hi, thanks for making sms-over-xmpp (and providing such helpful docs)!  While looking over the code, I noticed a few issues which I fixed in this pull request. Let me know if you'd like me to split this into multiple pull requests.

Hi.  Thanks for the pull request.  At a glance these changes look sensible.
I'm no longer using sms-over-xmpp (I migrated my infrastructure to IRC last year), so I'm not in a position to test your changes.  However, I'll gladly transfer this repository to your ownership so that you can maintain the project. Alternatively, I can archive this project and link it to your repository so future users can find you.
Let me know how you'd like to proceed.

@mndrix I'd be happy to take ownership of sms-over-xmpp via a repository transfer - I will definitely be using it going forward, and have familiarized myself with the codebase.  Thanks again!


Please update for using go modules to govern module delivery

Please update repo to support go mod features, such that we can import tingyuapm easily

updated


Error Formatting with OpenID/OAuth 2.0 Standards

Problem Description:
The current error formatting structure in the camera project diverges from the established standards of OpenID/OAuth 2.0. Although it includes fields like status, code, and message, as outlined in the provided ErrorInfo, it lacks key components such as error, error_description, and optionally error_uri, which are vital for effective error handling according to OpenID/OAuth 2.0 standards.
Here is the existing ErrorInfo structure:
ErrorInfo:
  type: object
  required:
    - status
    - code
    - message
  properties:
    status:
      type: integer
      description: HTTP response status code
    code:
      type: string
      description: Code given to this error
    message:
      type: string
      description: Detailed error description

Expected Behavior:
To ensure compliance with OpenID/OAuth 2.0 standards, the error formatting for the camera project should include the following fields:

error: Represents the error code or identifier.
error_description (optional): Provides a human-readable explanation of the error.
error_uri (optional): Includes a URI that offers additional information about the error.

Alternative Solution:
Alternatively, to align with OpenID/OAuth 2.0 standards, the camera project's error formatting can be updated as follows:
error:
  type: object
  required:
    - error
    - error_description
  properties:
    error:
      type: string
      description: Error code or identifier.
    error_description:
      type: string
      description: Optional human-readable description of the error.
    error_uri:
      type: string
      description: Optional URI providing additional information about the error.

Additional Context:
These suggested modifications closely adhere to the specifications outlined in the OpenID/OAuth 2.0 standard. For further clarity, please refer to the documentation provided in RFC 6749 - The OAuth 2.0 Authorization Framework, Section <IP_ADDRESS>.

Whenever OIDC and OAuth2 are used in CAMARA the error responses MUST follow the respective OIDF and IETF standard.
Please refer to https://github.com/camaraproject/Commonalities/issues/128#issuecomment-1942012539
Since this issue is recurring, it looks that Section 6 of API Design Guidelines needs to be updated.

Whenever OIDC and OAuth2 are used in CAMARA the error responses MUST follow the respective OIDF and IETF standard. Please refer to #128 (comment)
Since this issue is recurring, it looks that Section 6 of API Design Guidelines needs to be updated.

Which working group is responsible for this?

Please also refer to #129 (comment)
OIDC and OAuth2 have their own error formats and within CAMARA, Service APIs are defined whose error format is defined in Commonalities Design Guidelines, so as it has not to be the same as defined for OpenID/OAuth 2.0

If the CAMARA standard is to be adopted by others, it should be defined in the same manner as OpenID/OAuth 2.0 to ensure consistency and simplify integration.

To be indicated in PR #213


README.md examples have issues

The examples in the README.md have issues around the log level.  Example:
GoogleScraper -m http --keyword "apple" -v2

This generates the following Traceback:
Traceback (most recent call last):
  File "/Users/lscarisb/.venv/scratch/bin/GoogleScraper", line 11, in <module>
    sys.exit(main())
  File "/Users/lscarisb/.venv/scratch/lib/python3.5/site-packages/GoogleScraper/core.py", line 173, in main
    setup_logger(level=config.get('log_level').upper())
  File "/Users/lscarisb/.venv/scratch/lib/python3.5/site-packages/GoogleScraper/log.py", line 23, in setup_logger
    logger.setLevel(level)
  File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/logging/__init__.py", line 1255, in setLevel
    self.level = _checkLevel(level)
  File "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/logging/__init__.py", line 187, in _checkLevel
    raise ValueError("Unknown level: %r" % level)
ValueError: Unknown level: '2'

Looking at the source, it appears as though arguments to -v should correspond to syslog severity level strings, not integers.  Not sure whether the source or the documentation should change here.

This hint on stackoverflow worked for me:
GoogleScraper -m http --keyword "apple" -v INFO


Silvered Weapons

Weapons marked as silvered are not imported.  The item is but the check box to mark them silvered is not coming over.

This is actually fixed in the next version, the silvered and adamantine flags were only added in the most recent version of the D&D 5E system.

This is actually fixed in the next version, the silvered and adamantine flags were only added in the most recent version of the D&D 5E system.

cool thanks, this was just more of a suggestion to post, but I didn't know any other way but to post it under issues.  Great Job!!!

cool thanks, this was just more of a suggestion to post, but I didn't know any other way but to post it under issues.  Great Job!!!


Implemented naturalPrev function in Hierarchy class

This has been marked as "todo" since forever. I just need it for a project.
naturalNext function doesn't have unit tests, so they both need unit tests at some stage.
Only tested with parent->children relationship so far, rather than deep nesting.

I think this needs to go against 3 branch

This also needs tests

This actually needs to go against master as it's a breaking API change... even though it was never implemented :(

@tractorcow is there any value in someone picking this up? I don't even know why there's a function stub for this

We should just remove the stub in 4.x.


Create sonarcloud workflow

Overview
Added SonarCloud workflow
How it was tested
Checklist

[x] The title contains a short meaningful summary
[ ] I have added a link to this PR in the Jira issue
[ ] I have described how this was tested
[ ] I have included screen shots for changes that affect the user interface
[ ] I have updated unit tests
[ ] I have run unit tests locally
[ ] I have updated documentation (including README)

Closing this because there's no point in creating a separate workflow for SonarCloud. We should either use Automatic Analysis which runs faster, or add sonar to the build-test workflow so it can analyze code coverage.


semantic segmantation

which face areas do you required to form a face like ears, hair face, mouth (lower or upper or both lips) and what else

As shown in the figure blow, the 2nd column is the head region  decided by semantic segmentation, including face, ear, and hair. The 3nd column shows the region of rendered face  , and the last column shows the region for our depth estimation, which is calculated by  .

For the definition of face region in semantic segmentation, please refer to Face Parsing with RoI Tanh-Warping.

Thank you for the great code! The code works well with the provided examples images. However, to use my own images, I do not know how to generate the initial .mat file with the semantic segmentation. Do you have any links to an implementation of "Face Parsing with RoI Tanh-Warping" that returns the matrix or directly creates the .mat file? Unfortunately, I did not find any.
Help would be greatly appreciated, thank you already!

For your purpose, you can refer to #15 .

Thanks for your reply. For anybody else struggling with this: In the meantime I found this repo that does an excellent job with segmentation. It produces an segmentation image with the different regions coloured, but some small changes to the code (you can check the branch on my profile) let you create a .mat file that works really well with this repository here.

@LeoGitGuy , cool! Thanks for your suggestion, I will keep this issue open for other people's reference.

感谢您的回复。对于其他一些苦苦的人的人：在楼上，我发现这个repo在对颜色的证明上非常棒。它会生成一个带有不同区域的分割图像，但是有一些更改（您可以在我的个人资料中查看）让您创建一个 .mat 文件，该文件非常适合这里的存储库。

I want to use my photos to generate a 3D portrait model.

I can't find a specific method to generate mat files on your home page. I am a novice. I hope you can give me as detailed steps as possible to answer my doubts. Thank you very much for your help.

Thanks for your reply. For anybody else struggling with this: In the meantime I found this repo that does an excellent job with segmentation. It produces an segmentation image with the different regions coloured, but some small changes to the code (you can check the branch on my profile) let you create a .mat file that works really well with this repository here.

You can use the repo of the face segmentation on my profile. If you execute the main function test_enhance_single_unalign.py it creates a .mat file in the results folder

I can't find a specific method to generate mat files on your home page. I am a novice. I hope you can give me as detailed steps as possible to answer my doubts. Thank you very much for your help.

You can use the repo of the face segmentation on my profile. If you execute the main function test_enhance_single_unalign.py it creates a .mat file in the results folder

@LeoGitGuy How about the _landmark.txt and _detection.txt files?

Also, the said python file does NOT generate a .mat file.

I can't find a specific method to generate mat files on your home page. I am a novice. I hope you can give me as detailed steps as possible to answer my doubts. Thank you very much for your help.

You can use the repo of the face segmentation on my profile. If you execute the main function test_enhance_single_unalign.py it creates a .mat file in the results folder

but，in your repo, after running test_enhance_single_unalign.py . I can't  find .mat in results folder

Is there a repo or any method to generate the _detection.txt input file,

Also is there a method(repo or a code) to generate semantic segmentation .mat file only using cpu (without using gpu).

You can use this code to generate landmark.txt
import face_alignment
import cv2
import numpy as np
fa = face_alignment.FaceAlignment(face_alignment.LandmarksType._2D, flip_input=False)
img = cv2.imread('./test.png')
preds = fa.get_landmarks(img)[0] # (68,2)
w0 = img.shape[1]
h0 = img.shape[0]
lm = np.stack([preds[:,0],h0 - 1 - preds[:,1]], axis = 1)
np.savetxt("_landmark.txt", lm)

pip install face_alignment before running this code

I can't find a specific method to generate mat files on your home page. I am a novice. I hope you can give me as detailed steps as possible to answer my doubts. Thank you very much for your help.

You can use the repo of the face segmentation on my profile. If you execute the main function test_enhance_single_unalign.py it creates a .mat file in the results folder

Can you provide the details of the modifications to test_enhance_single_unalign.py when you generated the .mat file? Thank you so much!


fix for malformed IPv6 Network Solicitation packet

Problem
This fixes the issue reported here - https://github.com/project-chip/connectedhomeip/issues/9791
The current version of lwip has a bug that creates a malformed Network Solicitation packet that can cause certain cable-modem/router models to crash (ex. https://www.motorola.com/us/mg7550/p).  It takes a power cycle to recover from the crash.
Change overview
A code update to fix the issue.
Testing
This was manually tested with the examples/lock-app/p6 application.  The problem occurs on the "Enable WiFi Network" step during the provisioning before Test Event tests are run.
zcl NetworkCommissioning EnableNetwork 1234 0 0 networkID=str:<WIFI SSID> breadcrumb=0 timeoutMs=1000
The problem no longer occurs after the code update in this pull request.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Bill Waters seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

@pan-apple - I see you may have imported this repo to start with. How are changes to the repo expected? Why was git submodules not used?

Was this change upstreamed to the official LWIP repository?

The latest version of LWIP does not have this issue.

I think this was fixed on mainline in https://git.savannah.nongnu.org/cgit/lwip.git/commit/?id=bc08c1d2b79b4763fc0f8f0bf0ed58e0c2899b3a - may want to just pull that patch rather than re-patch here.

@cecille, the version of lwip that this patch was applied to is different from the version in the Matter repo.  It seemed safer to only apply the changes from latest LWIP tag that fix the issue.

Ok, yeah - fair if it doesn't apply cleanly. However, that patch applies a similar fix to a few other places in the code. Ex. you can see the same pattern in the send_na function - does it need to be changed there as well?

Ok, yeah - fair if it doesn't apply cleanly. However, that patch applies a similar fix to a few other places in the code. Ex. you can see the same pattern in the send_na function - does it need to be changed there as well?

@cecille, I have been directed to only fix "point issues", and this "zero length Network Solicitation packet" is the only issue that I am aware of.  For broader fixes/updates, I would recommend that Matter move to a more recent version of lwip.

Up until this new platform, I wasn't actually aware of anyone using this version of lwip - network stack stuff for most platforms is supplied by the SDK. I actually thought this was dead legacy code. I'd be fine with updating, personally. There's some excellent ipv6 bugs in older versions of lwip, and this one looks relatively old.


Testing 1.4.1 release candidate

I did some test flights on a quad with Pixhack hardware. Seems like this hardware is not the best choice as the IMU isolation tend to oscillate.
While flying a straight line in POSCTL mode I got following issue. The copter increased altitude and yaw started turning right. When I centered the stick to stop the quad started flying backwards. From this point POSCTL wasn't working anymore for the rest of the flight. I had to switch to manual mode do safe the quad. I tried a few more times to switch back to POSCTL within the same flight but every time the quad started to fly in a random direction.
http://logs.uaventure.com/view/A6PHi8W8qnW386EgEk7SPo

@sirPerna I had a quick look at the plots in logmuncher. The position states of the estimator diverge and are being reset several times. This mostly indicates towards a inconsistency between IMU measurements and position / height measurements. The acceleration data shows strange noise at several points in the log. I'll have a closer look when I'm home.

@sirPerna Could you try for comparison the stable version 1.3.4? With latest master, I've had also strange results regarding pitch, that do not occur with 1.3.4 with the same set of parameters.

I did a proper IMU vibration isolation and now it works. Maybe the old log is still interesting as other people will face such an issue too if they have high vibration on the frame.
http://logs.uaventure.com/view/uTTPh2WZuRtDc4SJcZ5V5e#Power_PLOT

@sirPerna Looks much better now! I noticed that your baro innovations are rather large, it looks like the baro measurements are rather noisy.

@tumbili According to Lorenz the barometer should have it's own SPI bus. This hardware runs it on a shared bus which may be the source for the additional noise.


Strip embeds in params_for

I had an issue that params_for didn't work for my model that had embed fields in it; you have to strip embed structs down to plain maps for them to be allowed inside a changeset.
I removed the pattern matching dealing with Ecto.Schema.Metadata because embedded_schemas don't have metadata; it should always be safe as all traversed objects have Ecto schemas by the context of the recursively_strip method.

Would that be beneficial to add tests covering this work also for params_with_assocs/2, string_params_for/2, string_params_with_assocs/2?

I believe it will address this issue: https://github.com/thoughtbot/ex_machina/issues/210

Rebased from latest master to resolve conflicts

@paulcsmith Done!


Change from a mock server to live OData service for TechEd

Step 6

Comment out server.init() on line 14 by adding 2 forward slashes (//) to the beginning of the line.

Unfortunately there is nothing like server.init() on line 14 when I check my code. What am I missing? I would appreciate any help. I am trying to find out if I am the only one with this problem or there are others seeing this as well. Any pointers would be helpful.

@mhassett92

@mhassett92 thanks but not sure if i understand. This issue I am facing is from the topic of 2018 pre teched challenge. Let me know if I am missing anything. Your help is appreciated.
This could be found under Bullet 9 of the Challenge
9. Change from a Mock Server to Live OData Service for TechEd
Then Open the Step 6
>>6. Change the component file. You will find the line
>>Comment out server.init() on line 14 by adding 2 forward slashes (//) to the beginning of the line.

component_dot_js.pdf

Whoops, looks like an old instruction crept into this tutorial. Please ignore that instruction. There may have been a merge error and it ended up back in the tutorial. I am removing that line.

Thanks for the clarification. This can be closed.


Clean up README?

Do you plan to keep support for both JSON and JSON-LD output in the future? Perhaps it would be better to clean up the README by removing the JSON output part, especially if it is outdated.

  The JSON can be useful in testing and real serialization where we have to write something out and read it back in for further processing.  However, it is incomplete and outdated.  It could be kept in the code for our internal use but not advertised on the front page.  I think others who know more about the future will want to weigh in.

I kinda like it not being on front page as well, as it changes regularly
with updates to the system.  It also takes a while to scroll through.
Perhaps on another page linked from front page?
On Thu, May 3, 2018 at 11:04 AM, Keith Alcock<EMAIL_ADDRESS>wrote:

I'm ignorant of most plans. The JSON can be useful in testing and real
serialization where we have to write something out and read it back in for
further processing. However, it is incomplete and outdated. It could be
kept in the code for our internal use but not advertised on the front page.
I think others who know more about the future will want to weigh in.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/clulab/eidos/issues/303#issuecomment-386384934, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFIniUYTEL6HtXe2tViH7yIq-azbkz7Zks5tu0awgaJpZM4Txg5L
.

I vote for replacing the JSON and JSON-LD output in the README with links to Github wiki pages. In fact, I would suggest deprecating the pure JSON functionality altogether for ease of maintenance.


[CT-32] [Bug] cannot run dbt - module typing has no attribute OrderedDict

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
I run command
dbt --version
And get following result:
Traceback (most recent call last):
  File "C:\Users\dpbev\AppData\Local\Programs\Python\Python37\Lib\runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "C:\Users\dpbev\AppData\Local\Programs\Python\Python37\Lib\runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "C:\Users\dpbev\Leroy Merlin\dbt_venv\Scripts\dbt.exe\__main__.py", line 4, in <module>
  File "c:\users\dpbev\leroy merlin\dbt_venv\lib\site-packages\dbt\main.py", line 2, in <module>
    from dbt.logger import GLOBAL_LOGGER as logger, log_cache_events, log_manager
  File "c:\users\dpbev\leroy merlin\dbt_venv\lib\site-packages\dbt\logger.py", line 60, in <module>
    class LogMessage(dbtClassMixin):
  File "c:\users\dpbev\leroy merlin\dbt_venv\lib\site-packages\mashumaro\serializer\base\dict.py", line 23, in __init_subclass__
    raise exc
  File "c:\users\dpbev\leroy merlin\dbt_venv\lib\site-packages\mashumaro\serializer\base\dict.py", line 19, in __init_subclass__
    builder.add_to_dict()
  File "c:\users\dpbev\leroy merlin\dbt_venv\lib\site-packages\mashumaro\serializer\base\metaprogramming.py", line 385, in add_to_dict
    self._to_dict_set_value(fname, ftype, metadata)
  File "c:\users\dpbev\leroy merlin\dbt_venv\lib\site-packages\mashumaro\serializer\base\metaprogramming.py", line 442, in _to_dict_set_value
    metadata=metadata,
  File "c:\users\dpbev\leroy merlin\dbt_venv\lib\site-packages\mashumaro\serializer\base\metaprogramming.py", line 499, in _pack_value
    fname, args[0], parent, metadata=metadata
  File "c:\users\dpbev\leroy merlin\dbt_venv\lib\site-packages\mashumaro\serializer\base\metaprogramming.py", line 622, in _pack_value
    elif PY_37_MIN and issubclass(origin_type, typing.OrderedDict):
AttributeError: module 'typing' has no attribute 'OrderedDict'

Windows 11 Home
Python 3.7.0
Expected Behavior
No response
Steps To Reproduce

python -m venv dbt_venv
dbt_venv\Scripts\activate
pip install dbt
pip install dbt-postgres
dbt test

Relevant log output
No response
Environment
- OS: Windows 11 Home
- Python: 3.7.0
- dbt: 0.21.1

What database are you using dbt with?
postgres
Additional Context
No response

I've upgraded my python to 3.6.3 and it's working

Hi, @d1bevz thanks for your but report! I'm glad to hear it's working for you. I looked into it and I was able to reproduce your error with Python 3.7.0 on both dbt 0.21 and dbt 1.0.0. Since in dbt 1.0.0 we have removed support for Python 3.6, when you update dbt you'll want to use the latest Python 3.7 patch since it seems to not be a problem in Python 3.7.9.
I'm closing the ticket since the issue is resolved, however feel free to reopen if you need to.

So we can't run dbt in python 3.7.0?

So we can't run dbt in python 3.7.0?

This compatibility issue in mashumaro was fixed in the version 3.0. dbt-core uses this version since 1.3. I recommend you to update dbt-core to the latest version.

@jeff-skoldberg, today dbt does not run with Python 3.7.0 nor Python 3.7.1. I have filed a new ticket to check and see if we can undo this restriction with the information @Fatal1ty has provided. In general, we recommend running dbt with the latest Python patch release if possible.

Makes sense.  I have a 3.9 version that worked.
For what it's worth, I run 3.7 for all things Snowflake due to an issue I had with the snowflake-connector-python on the latest version of python.  At least as of a year ago, if you had the latest version of python, you had to install an older version of the connector.  I wanted the latest snowflake-connector-python so I had to use an older python to get it to work.  Maybe that sorted all that out since then.

@jeff-skoldberg That makes sense. dbt also lags behind the latest minor release of Python which is pretty common. For anything that doesn't support Python 3.10, using Python 3.9.14 is preferred to using Python 3.9.0 is all. Glad you were able to get it working.

I think as long as this issue is not being solved documentation  should not mention python minimum requirement 3.7.0 when it is just not working per default for dbt 1.0.0

I am using python version 3.7 and I am getting following issue.


firefox, thunderbird, librewolf: Enable wayland unconditionally

This causes unnecessary confusion and even bugs, where people use the wrong firefox package for their window protocol.
https://discourse.nixos.org/t/firefox-all-black-when-first-launched-after-login/21143
Tested on GNOME with X11 and Wayland, the window protocol is correctly chosen based on what session type was chosen.
Description of changes
TODO: Release notes, if everyone agrees this is a good change.

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Fixes #163206

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/firefox-all-black-when-first-launched-after-login/21143/15

So using MOZ_ENABLE_WAYLAND=1 also on X11 is fine?
Does anyone know why firefox doesn't enable this by default itself?
I've run with MOZ_ENABLE_WAYLAND=1 for a while on Wayland, and it does fix the occasionally black screen / crash on startup, so +1 from me.

So using MOZ_ENABLE_WAYLAND=1 also on X11 is fine?
Does anyone know why firefox doesn't enable this by default itself?
I've run with MOZ_ENABLE_WAYLAND=1 for a while on Wayland, and it does fix the occasionally black screen / crash on startup, so +1 from me.

Some bugs supposedly:
https://bugzilla.mozilla.org/show_bug.cgi?id=1752398

Funnily, there are both kinds in there – bugs in running on Xwayland ("Blocks") and bugs in running on Wayland ("Depends on").

Ah, right, this might have licensing implications since we'd be distributing a branded non-standard build.
Sigh.

All this does is set an environment variable in the wrapper script we use to invoke Firefox; does that really constitute changing the build for purposes of licensing?

Well, the thing is, we could severely degrade UX by enabling wayland. You and I are comfortable with that but some of our users wouldn't even know that the terrible bug they just experienced could have been caused by wayland being enabled or that that's even the case.
I don't think Mozilla will be coming after us in any capacity if we did a minor thing like this (even if they'd rather we didn't) but, as a packager, it's a general courtesy to follow upstream projects explicit UX decisions wherever possible.
Fedora stoke a nice balance I think but, from Mozilla's perspective, they'd probably rather have us keep it the way it was (convenient yet explicit wayland opt-in).

I was baffled to find out that I'd been using Firefox with XWayland all the time. As of 2022, I'd expect applications to use Wayland by default if they support it. Since this is just an environment variable and not a compile flag, and that setting it does not affect X11 support, I am not concerned about licensing stuff.
However, I think we should still provide a way to opt-out of Wayland, i.e. to force the usage of XWayland if desired. Since we are setting the environment variable in the wrapper, setting MOZ_ENABLE_WAYLAND=0 won't work. Having a firefox-x11 package as discussed above is a viable option.
An alternative would be to set this environment variable globally, for example as part of a programs.firefox.wayland option that defaults to true. The obvious disadvantage is that this would then only apply to NixOS systems.

An alternative would be to set this environment variable globally, for example as part of a programs.firefox.wayland option that defaults to true. The obvious disadvantage is that this would then only apply to NixOS systems.

A nixpkgs config option would work, and apply to non-NixOS systems.

Since we are setting the environment variable in the wrapper, setting MOZ_ENABLE_WAYLAND=0 won't work

if we use --set-default instead of --set, this won't be an issue

I was baffled to find out that I'd been using Firefox with XWayland all the time. As of 2022, I'd expect applications to use Wayland by default if they support it.

Then that should be taken up with Mozilla.

Since this is just an environment variable and not a compile flag, and that setting it does not affect X11 support, I am not concerned about licensing stuff.

The method does not really matter. GTK_USE_PORTAL was also an environment variable and it lead to a massive slowdown of some users’ boot that was difficult to pinpoint. The issue is that we would be potentially making a non-trivial change in behaviour.
And since Mozilla only allows us to use the Firefox trademark as long as our changes do not break their product, it is our responsibility to make sure that any changes are in fact non-breaking, if we want to keep using the Firefox branding.
At minimum, we should probably find out why exactly it is not enabled by default. But final decision whether the change would be fine with Mozilla can only be done by Nixpkgs Firefox maintainers, hoping that their mental model of Mozilla is good enough.

if we use --set-default instead of --set, this won't be an issue

--set-default doesn't help because Wayland is used if MOZ_ENABLE_WAYLAND exists at all. In other words, MOZ_ENABLE_WAYLAND=1 and MOZ_ENABLE_WAYLAND=0 (or anything else) do the same thing.

(fwiw, I generally agree with @jtojnar)

The basic change here is that nobody will use XWayland by default anymore. Nobody will be able to pick the wrong firefox package anymore. XWayland is most certainly the variant that gets the least maintenance at this point.
I think keeping a firefox-x11 variant around is pretty much pointless, when Firefox with Wayland enabled will gracefully fallback to X11 when the session is based on X11. There is also the possibility to force the usage of X11 by overriding MOZ_ENABLE_WAYLAND as outlined by @ajs124.
We're not the first distro to enable Wayland by default, Ubuntu went first.
I do not expect any licensing issue with this.


Mistake in wiring diagram

There is a mistake in diagram version D. Wrong polarity of battery.

You're right, I fixed it now in commit 86c9a865e17aad74b8ada2b31e17f73adba216dc. Thanks for pointing that out!


Added warning about default TTL in memo

Description
My web app overloaded my server's bandwidth because network calls weren't being memoized as expected. Upgrading from v9 to v10 fixed it, but I wish the documentation had warned me about the default TTL in old versions.

Awesome! Thanks for approving the request :)


pull request for e2e test at 12/04/2016 03:56:04

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.