General Rule Filtering / First-Class Blocking Support

Think about a general filter clause that applies to every type of rule.
In logical rules we usually just use things like blocks, but if the block is in a filter clause we may be able to apply some additional optimizations since we really know it is a block.

After talking with Sandia, this seems like something that could be quite useful.
If we can identify predicates that act as blocks, then we can automatically know what we can distribute on.

We could potentially also introduce general arithmetic or boolean expressions on both variables and atoms.


Race with incomming CALL/CALL_RESULT in 1.6

The code in v16.go sets up handerls like this:
	cp.client.SetResponseHandler(func(confirmation ocpp.Response, requestId string) { 		cp.confirmationHandler <- confirmation 	})
	cp.client.SetErrorHandler(func(err *ocpp.Error, details interface{}) { 		cp.errorHandler <- err 	})
	cp.client.SetRequestHandler(cp.handleIncomingRequest)
The problem is that resonseHandler pushes incomming reply messages (CALL_RESULT) on to a channel, while regular CALLs have a direct callback. This means that in some cases that an incoming CALL can "overtake" a CALL_RESULT which arrives just before it.
In my case the reply to a StartTx (with the txID) was received before but handled after the SetChargingProfile with TxProfile for that id. And the client got confused...

I changed the response and error handlers to call two new functions which did the same thing as what was done in chargePoint.asyncCallbackHandler() to the messages, but without the channel. It seems to work, but I have to test a bit to see if there are any side effects to this.


API LoRAWAN codec incompatible

API chirpstack is not compatible with the payload API LoRAWAN codec (TS013-1.0.0 Payload Codec API 22)
in the code APi from lorawan the UlplinDecode is:

the documentation of chirpstack gives:
// Decode uplink function.
//
// Input is an object with the following fields:
// - bytes = Byte array containing the uplink payload, e.g. [255, 230, 255, 0]
// - fPort = Uplink fPort.
// - variables = Object containing the configured device variables.
//
// Output must be an object with the following fields:
// - data = Object representing the decoded payload.
function decodeUplink(input) {
return {
data: {
temp: 22.5
}
};
}
so it seems recvTime argument is not present to be compatible with API from lorawan.

I believe this is only a documentation issue, the variable is there:
https://github.com/chirpstack/chirpstack/blob/master/chirpstack/src/codec/js/mod.rs#L65


DocsArchive-<IP_ADDRESS>Auto archive content

Auto archive content from https://github.com/OPS-E2E-PPE/docs-archive-test-source

Docs Build status updates of commit 6e2a661:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Release_Archive_master_2020-02-05-10-57-25 has been deleted or has been force pushed: fatal: couldn't find remote ref refs/heads/Release_Archive_master_2020-02-05-10-57-25

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.


Add a node at the Beginning of the Circular Doubly Linked Lists

Is your feature request related to a problem? Please describe.
The problem is to get input data from the user, create a Node with the data and add it to the Beginning of the Circular Doubly Linked Lists.
Describe the solution you'd like
I would like to provide a C++ coded solution for this problem

@smv1999 I would like to work on this

Sure @kiruba-r11 , you can go ahead !


client unable to connect using SSL?

I've been running a websocket server successfully without SSL and can connect to and interact with it just fine using this client. Now I'm trying to get the client working against an SSL-enabled server (HTTPS) and seeing what looks like a validation error. After a connect attempt it gets the 'connectFailed' event with this error;
err.code: "UNABLE_TO_VERIFY_LEAF_SIGNATURE"
err.message: "unable to verify the first certificate"
I can connect to this server just fine with a browser websocket client, and I know its a good certificate. Has anyone got this working? I don't see a test case in the code where it tries connecting to a 'wss://' server.

Looking at this further, I am able to connect to 'wss://echo.websocket.org/' with no problem. However, I've got a Multi-Domain certificate (a SAN or UC certificate) on my server, maybe this package is having trouble validating it? Is there some option I can pass in that will make it work?

Eh, misconfigured server. I had not included the ca-bundle in the https.createServer options.


feature: update wallet name on create

no issue, update wallet name.
https://github.com/spacemeshos/smapp/assets/54288612/8f27ed5b-426d-4739-bfeb-7adcf9a93b5b

Hey, I've got 3 questions:
do we need to keep the "my_wallet" part? or could we just get rid of it once the User provides the custom name?

Why only 10 characters?

Once the custom name is set, and we go to the settings -> rename, then we can change the custom name of our wallet again. But in this case the file's name stays the same. What do you think about it? I'm a bit concerned... not sure but I think the Users might expect it to work the same as the naming during the wallet setup, but changing anything in the json file while this wallet is open in Smapp may require restarting SMAPP/relocating this file?

@monikasmolarek  will be fixed , only one moment, unfortunately for my_wallet , I have to left at least the wallet_NAME , to find all user wallets
about the 10 characters, the idea to show the whole name on the Wallet screen, I can limit it to 120 characters and add ... for the name or maybe place it on the different lines

Even better with this "wallet_" in the file name at the very beginning.
For the length of the wallet name - thanks! I didn’t think of displaying it on the Wallet screen, makes sense! and I would hate spoiling the layout there. So if you think it will be ok to have longer names, then I think dots at the end of the name should be better than wrapping. And maybe a small tooltip next to the wallet name input field (on the setup step) explaining that only the first 10 characters will be displayed?

LGTM👍


Domain for decimalValue property is too narrow

If there is ever a need to connect a number to something else it cannot be a literal, it has to have a URI (it might be called NumberValue).  It makes sense to use the same property, decimalValue to point to the number.  Currently, this falsely implies that the NumberValue is an instance of gist:Magnitude.
SUGGESTED FIX: remove the domain from gist:decimalValue.
This is a response to a current requirement for Platts, it is not a theoretical exercise.  It underscores the caution we need to take when using domain and range.
See also:  https://github.com/semanticarts/gist/issues/172

This just bit us again for the IBB Project.  Peter and I wanted to reuse decimalValue for things that are not magnitudes. New proposal:

deprecate gist:decimalValue which is misleadingly named in the first place (See https://github.com/semanticarts/gist/issues/172)
add new property called gist:numericalValue with no domain and whose range is the union of all the datatypes that are numbers i.e. (xsd:decimal or xsd:double or xsd:integer or owl:real or ...)
as explained in https://github.com/semanticarts/gist/issues/172, if there are special cases requiring a specific range, then a new subproperty can be created such as gist:doubleValue, gist:integerValue. This is a bit of an ant-pattern though, better to use SHACL. If we did create a decimalValue then it definitely should not have any domain. To have a separate property for use only with Magnitudes whose value is always double is an even worse anti-pattern (antier pattern?).

I like your suggestion. There may be cases where semantics rather than just expected usage requires a specific numeric type, in which case it might be appropriate to mint some of those more specific properties. Hypothetically, hasNumberOfChildren is an integer, for example. We may well not define those in gist but leave them to client ontologies.

@rjyounes Yes, exactly!

Address with #172 - may be a duplicate.

Any interest in addressing this for v10 release?
I am wondering because we are about to start baking the current definitions into new shapes for SA internal systems. Would be nice (for us) to make any changes now rather than later.
This might be a bigger change than just removing the range (see #172). There are several terms in gist that have owl:restriction onProperty gist:decimalValue. But that also makes it a good candidate to go into a major release like v10.

I'm interested!

Let's sort out whether the correct term is "numeric" or "numerical." I'm unclear on the difference, or whether there is a difference. The answers I get from a search do not help to clarify it.

@Jamie-SA I've put this into the June project so we can consider it for that release.

Let's sort out whether the correct term is "numeric" or "numerical." I'm unclear on the difference, or whether there is a difference. The answers I get from a search do not help to clarify it.

I think numericValue sounds better, the other one sounds al funny (so to speak).

DECISION:

deprecate gist:decimalValue which is misleadingly named in the first place (See https://github.com/semanticarts/gist/issues/172)
add new property called gist:numericValue with no domain and whose range is the union of all the datatypes that are numbers i.e. (xsd:decimal or xsd:double or xsd:integer or owl:real or ...)
as explained in https://github.com/semanticarts/gist/issues/172, if there are special cases requiring a specific range, then a new subproperty can be created such as gist:doubleValue, gist:integerValue. This is a bit of an ant-pattern though, better to use SHACL. If we did create a decimalValue then it definitely should not have any domain. To have a separate property for use only with Magnitudes whose value is always double is an even worse anti-pattern (antier pattern?).


Test Dataset

When I use mask2former_R101c_alltask_bs32_60k.yaml to get proposal classification, i got an error Dataset 'coco_2017_val_panoptic_with_sem_seg' is not registered! . Is the dataset wrong?

Sorry about that, you can download the file file for solving this problem.


Build Python project always in up-to-date state.

Environment

Steps to Reproduce

Create a new Black Django Web Project
Create a virtual environment for this project
In solution explorer, right click on project and click Build.

Expected behavior
The Django project build successfully.
Additional context and screenshots
In build output window show the project build in up-to-date state, can not finish.

Click button Run All Tests In Views from Test Explorer, then pop up the build window. And the build window cannot be completed.
Build of Visual Studio: 17.0.0 Preview 5.0 [31726.38.main]
Build of Python Package: 17.0.21264.5

closing at can't repo


AttributeError: module 'torch' has no attribute 'compile'

I did install it on a fresh machine with
!pip install -U torch
!pip install -U transformers
!pip install -U hqq

---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
Input In [1], in <cell line: 6>()
      4 model_id = 'mobiuslabsgmbh/Mixtral-8x7B-Instruct-v0.1-hf-attn-4bit-moe-2bit-metaoffload-HQQ'
      5 #Load the model
----> 6 from hqq.engine.hf import HQQModelForCausalLM, AutoTokenizer
      7 tokenizer = AutoTokenizer.from_pretrained(model_id)
      8 model     = HQQModelForCausalLM.from_quantized(model_id)

File /usr/local/lib/python3.9/dist-packages/hqq/engine/hf.py:6, in <module>
      2 from typing import Dict
      4 _HQQ_REGISTRY = {}
----> 6 from ..models.hf.llama import LlamaHQQ
      7 _HQQ_REGISTRY['LlamaForCausalLM'] = LlamaHQQ
      9 from hqq.models.hf.mixtral import MixtralHQQ

File /usr/local/lib/python3.9/dist-packages/hqq/models/hf/llama.py:1, in <module>
----> 1 from ..base import *
      2 from .base  import *
      4 #Patch LLama functions

File /usr/local/lib/python3.9/dist-packages/hqq/models/base.py:9, in <module>
      6 from abc import abstractmethod
      8 from huggingface_hub import snapshot_download
----> 9 from ..core.quantize import HQQLinear
     11 #Cleanup GPU vram
     12 def cleanup():

File /usr/local/lib/python3.9/dist-packages/hqq/core/quantize.py:246, in <module>
    243 		return grad_input, grad_weight, grad_bias
    245 #Main linear layer
--> 246 class HQQLinear(torch.nn.Module):
    247 	backend = HQQBackend.PYTORCH #Default
    249 	def __init__(self, linear_layer, quant_config, del_orig=True, compute_dtype=torch.float16, device_n=0):

File /usr/local/lib/python3.9/dist-packages/hqq/core/quantize.py:389, in HQQLinear()
    386 	weight = self.dequantize()
    387 	return torch.matmul(x, weight.t() if (transpose) else weight)
--> 389 @torch.compile()
    390 def matmul_compile(self, *args, **kwargs):
    391 	return self.matmul(*args, **kwargs)
    393 def forward_pytorch_backprop(self, x):

AttributeError: module 'torch' has no attribute 'compile'

this probably occurs because it needs the wrong pytorch version (1.X) which doesnt feature compile .
A hack to prevent this is to install pytorch 2.X after installing HQQ

Thank you for your comment!
The documentation explicitly says that you need to install Pytorch 2 (First, make sure you have a Pytorch 2 version that matches your CUDA version: https://pytorch.org/)
HQQ doesn't install Pytorch because it's integrated into other projects and automatically installing Pytorch was creating many issues, so we encourage the user to install their own version of Pytorch 2

You may need the pytorch nightly build too


fix: use of "tag" instead of "tags" in default rules

Signed-off-by: Vicente Herrera<EMAIL_ADDRESS>
What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

If contributing rules or changes to rules, please make sure to also uncomment one of the following line:

/kind rule-update

/kind rule-create

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area engine

/area examples

/area rules

/area integrations

/area tests

/area proposals

What this PR does / why we need it:
Fix rules that used wrong 'tag' keyword to use the right one, 'tags'.
Which issue(s) this PR fixes:
Some rules where using 'tag' keyword instead of valid 'tags' keyword. That prevented using tags to filter them.

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Yes

After this change, when using command line switches -T to disable rules by certain tag, or -t to only run rules with a certain tag, a different set with more rules will match as now they are more rules correctly tagged.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign kaizhe
You can assign the PR to them by writing /assign @kaizhe in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

rules/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/assign @kaizhe

LGTM label has been added.  Git tree hash: adf9b237cca91a14bfbcc8c597a5bbb588feffdf

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: leodido
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

rules/OWNERS [leodido]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign kaizhe
You can assign the PR to them by writing /assign @kaizhe in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

rules/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: leodido
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

rules/OWNERS [leodido]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/milestone 0.21.0

This fixed issue https://github.com/falcosecurity/falco/issues/1082


If user did not fill out profile during registration, cannot save profile later

User signs up with email+password+confirmed password. User logs out before filling in registration. Upon logging in again, going into settings, and filling in the information, the save button does not work. Therefore, the user does not exist in a hub and cannot see activities.
I have been able to reproduce this error on Firefox. Initially seen on Safari.

Needs testing to see if this is still an issue.


Add option to read sources from rustc --print sysroot

Standard library sources can now be installed via rustup and are available at the location shown by rustc --print sysroot. We should add an option to the Visual Rust general options page to automatically use this path (and maybe even make it the default).

I have made some work here. The main problem is: which rustc run to get sysroot? Maybe we need first aggregate ToolVersion and TargetTriple to "toolchain" class. And make toolchain option for project or solution.

The Cargo wrapper returned by Cargo.FindSupportedInstallation() already has a RustcExecutable property for this purpose. But there already is a GetSysrootAsync method here, which you can probably use. In a later step, we should centralize access to the toolchain, i.e. there should be only a single instance of the Cargo wrapper which handles the currently selected toolchain (related to #242). Toolchain selection will probably be delegated to rustup.

https://github.com/PistonDevelopers/VisualRust/pull/251


Fix typos

This PR fixes Typos

 extensions/vscode-api-tests/src/singlefolder-tests/webview.test.ts: sendRecieveMessage -> sendReceiveMessage
extensions/vscode-colorize-tests/test/colorize-fixtures/makefile: existance -> existence
extensions/vscode-colorize-tests/test/colorize-results/makefile.json:  existance -> existence
src/vs/base/common/buffer.ts: Unkown -> Unknown
src/vs/editor/contrib/suggest/browser/suggest.ts: unkown_provider -> unknown_provider
src/vs/editor/common/cursor/cursorWordOperations.ts: defintion -> definition
src/vs/editor/contrib/inlineCompletions/browser/ghostTextController.ts: neccessary -> necessary
src/vs/platform/configuration/common/configurationRegistry.ts: whenver -> whenever
src/vs/platform/notification/common/notification.ts: choosen -> chosen
src/vs/platform/theme/common/iconRegistry.ts: iconDefintion -> iconDefinition
src/vs/workbench/api/common/extHostTypes.ts: resolvedDefintion -> resolvedDefinition
src/vs/workbench/common/editor/editorGroupModel.ts: occured -> occurred
src/vs/workbench/contrib/files/test/browser/fileEditorInput.test.ts -> occuring -> occurring
src/vscode-dts/vscode.proposed.treeViewDragAndDrop.d.ts: occuring -> occurring
src/vs/workbench/contrib/debug/common/debug.ts: successfull -> successful, successfuly -> successfully
src/vs/workbench/contrib/files/browser/views/explorerViewer.ts: necessery -> necessary
src/vs/workbench/contrib/notebook/browser/diff/diffComponents.ts: getFormatedMetadataJSON -> getFormattedMetadataJSON, getFormatedOutputJSON -> getFormattedOutputJSON
src/vs/workbench/contrib/notebook/browser/diff/diffElementViewModel.ts: getFormatedMetadataJSON -> getFormattedMetadataJSON
src/vs/workbench/contrib/notebook/browser/docs/notebook.layout.md: defintion -> definition
src/vs/workbench/contrib/notebook/browser/notebook.contribution.ts: getFormatedMetadataJSON -> getFormattedMetadataJSON
src/vs/workbench/contrib/terminal/browser/terminalTypeAheadAddon.ts: appearence -> appearance
src/vs/workbench/services/search/browser/searchService.ts: _onDidRecieveTextSearchMatch -> _onDidReceiveTextSearchMatch, onDidRecieveTextSearchMatch -> onDidReceiveTextSearchMatch
src/vs/workbench/services/search/worker/localFileSearch.ts: proccessFile -> processFile

Thanks!


Update README.md

Added NVF2.4 example to README.md

@tal-rhino , @yuvalrhino , would you guys mind reviewing and approving the change? Just adding to readme

@antoni-at-rhino, 2.4 can be easier to use, but this example doesn't show that, yet.
From experience with previous releases, we shouldn't yet recommend this to users unless there are specific features new in 2.4 that they require. We should wait several more months until we have more of a successful track record with 2.4, first.


Game does not Pause

Fix bug with game not pausing under new rendering model.
This is because the canvas is rendering independently of the game state, and is no longer taking the pause/unpause state into account. Fixing this will also be challenging because there is not one centralized list of all sprites.
If this cannot be fixed, consider removing the pause button and state.

After consideration, I decided to remove the pause button. It wasn't providing any value to the game, and the remaining pause/unpause logic was not doing anything.
Commit: 39632a4f915703b3a37cf9707b4e16d4be06059d

Fixes bug with infinite recursion and re-rendering: 9d21222080b1e82d1b4181eb038d9e52f6c28b2e


Register and route other services

This updates the UA, TaskQueue, and blobstore service to behave like the datastore and search2 service in that they add a registration node in ZooKeeper and have requests routed to them based on those entries.

http://ocd.appscale.net:8080/job/Daily Build/6701/


Different results between original and transpiled circuits

Information

Qiskit Terra version:  0.11.0
Python version: 3.7.5
Operating system: MacOS Mojave 10.14.6

What is the current behavior?
Pulled from this stack exchange question: https://quantumcomputing.stackexchange.com/questions/9375/cannot-replicate-results-in-article-on-pricing-financial-derivatives-on-ibm-q
The original circuit is built in this way:
qc = QuantumCircuit(4, 4)
qc.h([0, 1, 2])
qc.ry(1.00, 3)
qc.rz(0.33, 3)
qc.cu3(1.6, -1.12, 2.03, 2, 3)
qc.cu3(2.23,0.51,3.65, 1, 3)
qc.cu3(0.8,-4.53,-1.39, 0, 3)
qc.h(0)
qc.cu1(np.pi/-2, 0, 1)
qc.cu1(np.pi/-4, 0, 2)
qc.h(1)
qc.cu1(-np.pi/2, 1, 2)
qc.h(2)
qc.measure(range(4), range(4))

drawn as such:

After executing the following code, I see that the circuit is transpiled and returns different results.
sim = prov.get_backend('ibmq_qasm_simulator')
job = execute(qc, sim)

Transpiled circuit:

The issue I have found is the same as the one the user asking the original stack exchange question had. The original circuit should return results similar to around 60%: 0111 and around 30%: 1111, based on the paper in the stack exchange and the measurement probabilities shown on IQX. However, after executing the circuit, we get results similar to around 55%: 0000 and 30%: 1000
Steps to reproduce the problem
Execute the original circuit above on the simulator.
What is the expected behavior?
Expected results should be similar to to the returned results.

How were you running the original circuit without transpiling it? The gates need to be unrolled to the basis set at least to run on aer (I'm testing it locally not using the online version but they should be the same). Running the input circuit with optimization level 0 (which will just unroll no other optimizations)

and with optimization level 1 (the default for execute()) returned similar results.
Level 0:
{'0000': 558, '0100': 29, '1010': 12, '0110': 16, '1101': 16, '0001': 2, '0101': 2, '1001': 37, '1110': 5, '1100': 15, '0111': 4, '1111': 26, '0010': 8, '1000': 294}
Level 1:
{'0000': 559, '0100': 27, '1010': 20, '0110': 14, '1101': 18, '0001': 7, '0101': 4, '1001': 32, '1110': 7, '1100': 10, '0111': 5, '1111': 19, '0010': 17, '1000': 285}

I ran the circuit by using execute(), so it would've transpiled the circuit at optimiation_level=1 if I understood it correctly. The measurement probability I was seeing for the original circuit before transpilation was what I saw through the IBM Q Experience Circuit Composer:

This probability also matched the probability found in the paper that the stack exchange poster had mentioned.
The results you posted match the results I received when I ran the circuit with execute() on the ibmq_qasm_simulator, but these results are different than the expected results I saw in IBM Q Experience and in the original stack exchange question.

I think all of those gates are in the Aer simulator basis so no unrolling will be done.
I'm guessing a phase issue with CU3, @chriseclectic can you check the definition of CU3 in terra and aer match? (related to https://github.com/Qiskit/qiskit-terra/pull/2755/files)

I think all of those gates are in the Aer simulator basis so no unrolling will be done.

In my local testing it needed to unroll Ry and Rz. With those in the circuit passed to Aer it raised an internal error caused by https://github.com/Qiskit/qiskit-aer/blob/master/src/simulators/densitymatrix/densitymatrix_state.hpp#L570-L573 (they're also not listed in the basis set: https://github.com/Qiskit/qiskit-aer/blob/master/qiskit/providers/aer/backends/qasm_simulator.py#L212-L217).
But, I was more asking to understand where/how the circuit was being run with the expected result, because without transpilation the results were the same locally. But, since the circuit composer doesn't use aer that makes sense.

After the discussion here, it seems that the answers on that StackOverflow post concluded that the circuit is not correct for the desired results / algorithm.  Closing now, but feel free to open a new issue if there's more to discuss.


Reverse the directories for the Openapi generation command

On this test run - the command that was used to generate the OpenAPI definitions is:
appmap openapi -d tmp/appmap --appmap-dir . --output-file openapi.yml

But the appmap CLI says:
appmap openapi --help
<snip>
  -d, --directory         program working directory                     [string]
      --appmap-dir        directory to recursively inspect for AppMaps

Given that the command likely should instead be:
appmap openapi -d . --appmap-dir tmp/appmap --output-file openapi.yml

This runner should have used this branch (if i configured it right)
https://github.com/getappmap/Misago/actions/runs/6053052555/job/16428070424#step:1:37
But the command it used didn't seem to have the right directory set per this code change so i'm not sure what's up here.
https://github.com/getappmap/Misago/actions/runs/6053052555/job/16428070424#step:5:104

Ok - at the very least the directory change works - testing on this workflow file
The runner uses the right dir names
appmap openapi -d . --appmap-dir tmp/appmap --output-file openapi.yml


]IJulia  1.23.2 with julia 1.6.2 under macOS 11.4 fails to open jupyter notebook

With IJulia and Conda added in the julia 1.6.2 REPL, I execute the following:
using IJulia, Conda
notebook()

This gives error:
ERROR: jupyter not found is not installed, cannot run notebook
Stacktrace:
 [1] error(s::String)
   @ Base ./error.jl:33
 [2] find_jupyter_subcommand(subcommand::String)
   @ IJulia ~/.julia/packages/IJulia/e8kqU/src/jupyter.jl:25
 [3] notebook(; dir::String, detached::Bool)
   @ IJulia ~/.julia/packages/IJulia/e8kqU/src/jupyter.jl:96
 [4] notebook()
   @ IJulia ~/.julia/packages/IJulia/e8kqU/src/jupyter.jl:95
 [5] top-level scope
   @ REPL[6]:1

So the jupyter server is not starting and a notebook is not opening in Safari.
I tried this as shown, expecting a prompt to install an internal jupyter, but that prompt never appeared.
I also tried starting jupyter under a separate conda installation and evaluating simply...
using IJulia
notebook()

...but get the same error.
Note that if I do start jupyter within my external conda environment, then I have no trouble directly browsing to, opening, and evaluating a notebook that connects to the julia kernel.

This can be closed.


feat: re-add Arbitrary for PooledTransactionsElement

This adds Arbitrary for BlobTransactionSidecar, which allows us to derive the same trait for BlobTransaction, which also allows us to derive Arbitrary with RLP tests, for PooledTransactionsElement.
This is refactored from the removed implementation in #4172

failing tests

Similar to TransactionSigned, blob tx has to implement arbitrary manually, because it needs to recalculate its transaction hash. Otherwise, it's using the randomly generated one.

ah right, will add then


Fix: undefined method split for an instance of Integer (NoMethodError)

I'm planing migrate from Puma to Falcon and during my tests I have found this issue.
Error:
    1m     warn: Async::Task: Reading HTTP/1.1 requests for Async::HTTP::Protocol::HTTP1::Server. [oid=0x456dc] [ec=0x449a8] [pid=9856] [2024-09-16 09:58:11 -0300]
               | Task may have ended with unhandled exception.
               |   NoMethodError: undefined method `split' for an instance of Integer (NoMethodError)
               |
               |                                                super(value.split(COMMA))
               |                                                           ^^^^^^
               |   → /Users/wagner/.rbenv/versions/3.3.5/lib/ruby/gems/3.3.0/gems/protocol-http-0.35.0/lib/protocol/http/header/split.rb:16 in `initialize'
               |     /Users/wagner/.rbenv/versions/3.3.5/lib/ruby/gems/3.3.0/gems/protocol-http-0.35.0/lib/protocol/http/headers.rb:281 in `new'
               |     /Users/wagner/.rbenv/versions/3.3.5/lib/ruby/gems/3.3.0/gems/protocol-http-0.35.0/lib/protocol/http/headers.rb:281 in `merge_into'
               |     /Users/wagner/.rbenv/versions/3.3.5/lib/ruby/gems/3.3.0/gems/protocol-http-0.35.0/lib/protocol/http/headers.rb:296 in `block in to_h'
               |     /Users/wagner/.rbenv/versions/3.3.5/lib/ruby/gems/3.3.0/gems/protocol-http-0.35.0/lib/protocol/http/headers.rb:295 in `each'
               |     /Users/wagner/.rbenv/versions/3.3.5/lib/ruby/gems/3.3.0/gems/protocol-http-0.35.0/lib/protocol/http/headers.rb:295 in `inject'
               |     /Users/wagner/.rbenv/versions/3.3.5/lib/ruby/gems/3.3.0/gems/protocol-http-0.35.0/lib/protocol/http/headers.rb:295 in `to_h'
               |     /Users/wagner/.rbenv/versions/3.3.5/lib/ruby/gems/3.3.0/gems/protocol-http-0.35.0/lib/protocol/http/headers.rb:290 in `[]'
               |     /Users/wagner/.rbenv/versions/3.3.5/lib/ruby/gems/3.3.0/gems/protocol-http-0.35.0/lib/protocol/http/content_encoding.rb:32 in `call'
               |     /Users/wagner/.rbenv/versions/3.3.5/lib/ruby/gems/3.3.0/gems/protocol-http-0.35.0/lib/protocol/http/middleware.rb:43 in `call'
               |     /Users/wagner/.rbenv/versions/3.3.5/lib/ruby/gems/3.3.0/gems/async-http-0.76.0/lib/async/http/server.rb:61 in `block in accept'
               |     /Users/wagner/.rbenv/versions/3.3.5/lib/ruby/gems/3.3.0/gems/async-http-0.76.0/lib/async/http/protocol/http1/server.rb:49 in `each'
               |     /Users/wagner/.rbenv/versions/3.3.5/lib/ruby/gems/3.3.0/gems/async-http-0.76.0/lib/async/http/server.rb:50 in `accept'
               |     /Users/wagner/.rbenv/versions/3.3.5/lib/ruby/gems/3.3.0/gems/io-endpoint-0.13.1/lib/io/endpoint/wrapper.rb:182 in `block (2 levels) in accept'
               |     /Users/wagner/.rbenv/versions/3.3.5/lib/ruby/gems/3.3.0/gems/async-2.17.0/lib/async/task.rb:197 in `block in run'
               |     /Users/wagner/.rbenv/versions/3.3.5/lib/ruby/gems/3.3.0/gems/async-2.17.0/lib/async/task.rb:422 in `block in schedule'

I don't know if was expected to Protocol::HTTP::Header::Split be able to handle Integers but I guess is safe to check if value can respond_to split. This solved the issue.
Types of Changes

Bug fix.

Contribution

[ ] I added tests for my changes.
[X] I tested my changes locally.
[X] I agree to the Developer's Certificate of Origin 1.1.

Headers should always be strings.
Do you know what is the value? e.g. how is response.headers['content-encoding'] becoming an integer?

After debugging it, I found that it's a custom header in my application. It always worked with Puma, and after my patch, it also worked with Falcon because super() was able to handle it.
I checked the RFCs, and you're right—it is expected to be text. However, I'm sure that NGINX and all browsers can handle an integer as the value type.
What should we do?

I checked the RFCs, and you're right—it is expected to be text. However, I'm sure that NGINX and all browsers can handle an integer as the value type.
What should we do?

There is no such thing as an integer value header, they must all be strings. Puma will be converting it to a string. This is required by Rack::Lint: https://github.com/rack/rack/blob/744f92d099653f873ced3380e425a6f82f0c6c6c/lib/rack/lint.rb#L719-L727

Ok. I'm closing this PR.

@ioquatix The actual Falcon behavior when a integer is used in the header is crash by a unhandled exception.
Do you think that unexpected errors like this one should be rescued to avoid a application restart ?

I don't have a strong opinion, but as a general rule I don't like introducing implicit conversions like to_s. Do you have any opinion about what we should do? This should only cause the request (and possibly connection) to fail, not the entire application.

I don't have a strong opinion, but as a general rule I don't like introducing implicit conversions like to_s. Do you have any opinion about what we should do? This should only cause the request (and possibly connection) to fail, not the entire application.

@ioquatix I strongly agree with you about to_s. I think only request should fail to make HTTP/1 and HTTP/2 suffer the same impact.
I was wondering the impact of a crafted request directly sent to the Falcon instance using a Integer value on the header. I didn't tried it yet, but It could lead to a DoS, I'm supposing that the same code is used to parse the requests.

@ioquatix I have tested  a crafted request using a integer in a header and only the request failed.
               | Task may have ended with unhandled exception.
               |   Protocol::HTTP1::BadHeader: Could not parse header: "X-Test-Integer-Header: \x00\x00\x00\x01"````

I guess this should be the same behavior when a server side violation happens.
Should this discussion move to Falcon repository?


chore: publish license_check workflow

Description
Since there is now a license_check workflow (#154) we should publish it and update documentation related to it.
Tasks

[x] Publish license_check workflow
[ ] Update license_check workflow documentation with an example of how to use the workflow

The license check workflow has now been published, see v1.15.0 release.

The licence check documentation can be seen in #164


Feature/Enable automatic payouts

This PR enables the automatic train developer payouts.
Merge once the just implemented developer specific DMs seem to work correctly.

Below PR is presumably the final fix before this PR can be merged:
https://github.com/guidojw/nsadmin-discord/pull/86


Add support for Rails 5.1

ActiveCotroller::TestCase.create needs controller class in Rails 5.1. See https://github.com/rails/rails/commit/496d744fa31665de810b404de968ba86ed87c319

Coverage increased (+0.2%) to 97.059% when pulling abbc97000e932efca83652b80a7293272f62cb32 on eitoball:rails-5.1 into 1fd20c4b92eaf26ec1f38eae9962cb8d3f8e859c on mizoR:master.

Released this change as v0.0.9, thanks a lot :)
https://rubygems.org/gems/active_decorator-rspec/versions/0.0.9


Get information about the Pos printer model

May I ask whether I have obtained information about the POS printer model in the current LAN through network scanning

I don’t understand the question. This library implements a subset of the ESC/POS spec. There aren’t currently any methods implemented that give you model information, but if that’s part of the spec we would gladly accept PRs that add that functionality. If you’re asking about port / ip address scanning to find devices, that’s out of scope for this library and there should be many .net tools that can do this.

What I mean is that ESC-POS.NET can scan the LAN printer and obtain the corresponding brand and model of the printer

I really want to get my reply. Now I want to find a solution. Thank you

Hi @jzeb, unfortunately, what you wish for doesn't have anything to do with the purpose of this library. You would need to accomplish that with another library and THEN use this one to communicate with the printer you found in your network

What I mean is that ESC-POS.NET can scan the LAN printer and obtain the corresponding brand and model of the printer

That’s out of scope for this library

Hi @jzeb, unfortunately, what you wish for doesn't have anything to do with the purpose of this library. You would need to accomplish that with another library and THEN use this one to communicate with the printer you found in your network

What I mean is that ESC-POS.NET can scan the LAN printer and obtain the corresponding brand and model of the printer

That’s out of scope for this library

So far, I have been looking for a long time, but I have not found a suitable library to use. Could you recommend it for me? Thank you

Unfortunately I've never had that need, so I wouldn't know which to recommend, but quick search in Google pointed a few already, not sure if you already went that path or not.

Currently can not find a solution, in distress


Cherry-picking cython fixes into stable branch

While building packages for our stable PPA, I'm getting these errors, which don't occur on daily builds:
https://launchpadlibrarian.net/227019225/buildlog_ubuntu-wily-amd64.kivy_1.9.0-3~stable0%2B201511191645~pkg77~ubuntu15.10.1_BUILDING.txt.gz
Could you please cherry-pick the commits, which fix these errors into stable branch?
Thanks

I think stable does not support that version of cython (0.23.3). Can't you downgrade cython to I think 0.23 which should fix that?

Well, if there is no way to fix it or it takes to much time, we can still
keep it like that. I'll just remove the broken packages. The latest Ubuntu
release already got kivy 1.9.0 in their repositories.
Finally, downgrading cython is no option (in my point of view a waste of
time - there are other more important tasks to be done). I'm happy that we
already got kivy compatible with cython shipped with Ubuntu and I don't
have to provide it in daily PPA anymore.

Well, https://github.com/kivy/kivy/pull/3283 is what fixed it. @akshayaurora wanne merge it into stable?


[Bug] Version 4.1.52 broke inline_create

Bug report
What I did
Defined a field to use inline_create with:
$this->crud->addField([
    'type' => 'relationship',
    'name' => 'customer_id',
    'label' => 'Customer',
    'ajax' => true,
    'inline_create' => true,
]);

What I expected to happen
The field was working normally before updating to Backpack version 4.1.53, showing the button to open the modal and create the related model.
What happened
In the "create operation", even though there is no value in the field, the file fetch_or_create tries to get a value from the database passing an empty string as the $current_value on line 37.
SQLSTATE[22P02]: Invalid text representation: 7 ERROR: invalid input syntax for type bigint: "" (SQL: select * from "customers" where "id" = ) (View: vendor/backpack/crud/src/resources/views/crud/fields/relationship/fetch_or_create.blade.php)

What I've already tried to fix it
Commenting the ajax and inline_create attributes stops the error.
I believe what caused this was a change from PR #3671 that changed to a strict comparison of $current_value and false.
When the field is empty, the previous line sets the empty string as the value for $current_value.
Before the change, since it was a loose comparison, the code would not try to access the database inside the if block.
PHP VERSION:
PHP 7.4.3 (cli) (built: Aug 13 2021 05:39:12) ( NTS )
Copyright (c) The PHP Group
Zend Engine v3.4.0, Copyright (c) Zend Technologies
with Zend OPcache v7.4.3, Copyright (c), by Zend Technologies
LARAVEL VERSION:
v8.61.0@3d528d3d3c8ecb444b50a266c212a52973a6669b
BACKPACK VERSION:
4.1.53@8698b8ed51e8b18e311f928f6f80a7161f1eb172
DATABASE VERSION:
PostgreSQL 12.7

Thank you so much for taking the time to write this thorough bug report @matheusb-comp ! We're on it.
@pxpm & @promatik - could you please both take a look too? This is URGENT.

Hello @matheusb-comp
Thanks for the report.
I can confirm that this happens ONLY in PostGres! MySQL would not complain from such query: select * from iconswhereid = '' this would just return empty result from MySQL. But in PG it would throw that error.
I am working on a fix for it, I should get back to you guys in a moment here. Just write it down so @promatik don't lose time here debugging!
Best,
Pedro

I've sent #3837 to address this.
Thanks again for such detailed report @matheusb-comp ! It was really helpfull!
I am going to close this, so we keep any discussion in the PR thread. Also, can you try to add that fix in your code and check if it really fixes it for you ? I tested in MySQL and PG, but an extra pair of eyes is always better.
Wish you the best,
Pedro

Also, can you try to add that fix in your code and check if it really fixes it for you ?

It is working now with the fix, thanks!

You are welcome and thanks for getting back with the feedback.
Sorry for introducing the bug, If you were not using PG I am sure I would not notice it in the near future!
Glad we could workout the solution. You are happy, we are happy, future users would be happy! Win-Win-Win!
Best,
Pedro


Added javadocs and internal docs to AUC.java and MetricsHelper.java

I have found that the best way for me to puzzle through this code is to add comments as I go. What would you think about incorporating this batch of my comments into your PR?

MetricsHelper -@param classIndex
The classIndex is an integer index into the first dimension of Cx.
What does this mean?

I have merged the changes, but look at my previous comment on dimension of Cx.

MetricsHelper -@param classIndex
The classIndex is an integer index into the first dimension of Cx.
What does this mean?

I defined Cx earlier in that same method javadoc:
   * @param labels the labels, will be cast to {@link TBool}
   *     shape (N, Cx, L1?) where N is the number of examples, Cx is zero or more
   *     class dimensions, and L1 is a potential extra dimension of size 1 that
   *     would be squeezed. If multiLabel or if
   *     labelWeights != null, then Cx must be a single dimension.


[WIP] Support DSTs

Currently, crossbeam-epoch doesn't support dynamically-sized types (DST): https://github.com/crossbeam-rs/rfcs/blob/master/text/2017-05-02-atomic-api.md#fat-pointers-and-dsts
This PR adds the support for DST by generalizing Box<T>, which was used as the underlying storage type for atomic pointers, to the Storage<T> trait.  For more details, see the comment on the Storage trait.  As an example, I added support for dynamically-sized arrays.  Other kinds of DSTs can be supported by implementing Storage<T>, even in the client code.
This PR was motivated by the fact that there's an unnecessary indirection in crossbeam-deque when accessing its underlying buffer.  As a proof of concept, I removed that indirection on top of PR in my local development: concurrent-circbuf.
This is a breaking change, but I tried to keep it as small as possible.  As far as I understand, the only breaking change is renaming Atomic::from(*const T) into Atomic::from_raw(*const T) and Shared::from(*const T) into Shared::from_raw(*const T).  (Question: I ended up changing the underlying types.  Is it a breaking change?)
This is a WIP.  Probably we want to discuss this PR's design and even write up an RFC.  I just share it for starting a discussion.  Thanks!

Closing as duplicate: https://github.com/crossbeam-rs/crossbeam/pull/209


Location Spammer?

Any ideas how to go about this?

https://github.com/AimTuxOfficial/AimTux/blob/9aa85f904dd465523296ae08437001bf4a3a150a/src/Hacks/spammer.cpp#L116 Aimtux got it c+p

oh sweet tysm

https://github.com/AimTuxOfficial/AimTux/blob/9aa85f904dd465523296ae08437001bf4a3a150a/src/Hacks/spammer.cpp#L116 Aimtux got it c+p

https://github.com/AimTuxOfficial/AimTux/blob/9aa85f904dd465523296ae08437001bf4a3a150a/src/Hacks/spammer.cpp#L116 Aimtux got it c+p

could you help me with this part
" return (const char*)((uintptr_t)this + offsets.DT_BasePlayer.m_szLastPlaceName);"
what do i do to replace the "offsets.DT_BasePlayer.m_szLastPlaceName"

NETVAR(idk, "CBasePlayer", "szLastPlaceName", char);

please learn what you are doing. with vs2019 you can literally hover over a variable and it will give you its value.
the offsets are certainly wrong anyway considering aimtux old and literally linux based

NETVAR(idk, "CBasePlayer", "szLastPlaceName", char);

looks correct, offset should be 0x000035B4 but may be outdated.

`   if (!config.misc.locationz)
return;
const auto localPlayer = interfaces.entityList->getEntity(interfaces.engine->getLocalPlayer());

for (int i = 1; i <= interfaces.engine->getMaxClients(); ++i) {
    const auto entity = interfaces.entityList->getEntity(i);
    std::string str = "say_team \"";
    str += entity->Location();
    str += "\"";

    interfaces.engine->clientCmdUnrestricted(str.c_str());

}`

crashing with this code
Location = NETVAR(Location, "CBasePlayer", "szLastPlaceName", char);
Any ideas? @xAkiraMiura @Kron1Q

void Misc::locationspam() noexcept
{
if (config.misc.locationz)
{
for (int i = 1; i <= interfaces.engine->getMaxClients(); ++i) {
const auto pentity = interfaces.entityList->getEntity(i);
const auto localPlayer = interfaces.entityList->getEntity(interfaces.engine->getLocalPlayer());
if (!pentity || !pentity->isAlive())
return;
interfaces.engine->clientCmdUnrestricted(std::string{ "say_team " }.append(pentity->GetLastPlaceName()).c_str());
}
}
}
ok so this works but it only prints my location??

have it working now, thanks guys


first observations

first of all, i wish this library much success.
http://oldman.readthedocs.org/en/latest/quickstart.html is a tad outdated. client_manager.use_all_store_models() is now client_manager.import_store_models()
earlier, if youre reading the pdf version, the cut off line should be
context_iri = "https://raw.githubusercontent.com/oldm/OldMan/master/examples/quickstart_context.jsonld"
even earlier, youre gonna run into something like this:
In [2]: from oldman import ClientResourceManager, parse_graph_safely, SPARQLDataStore
---------------------------------------------------------------------------
ImportError                               Traceback (most recent call last)
<ipython-input-2-3c41177edc7c> in <module>()
----> 1 from oldman import ClientResourceManager, parse_graph_safely, SPARQLDataStore

/home/kook/envs/oldman-2.7/build/bdist.linux-x86_64/egg/oldman/__init__.py in <module>()

/home/kook/envs/oldman-2.7/build/bdist.linux-x86_64/egg/oldman/resource/manager.py in <module>()

ImportError: No module named store.selector

im not sure what the solution was exactly, but i think removing the notion of oldman from site-packages and importing it from its directory directly.

Hi koo5,
Thanks a lot for your feedback!
I have committed your changes and I have tested the quick start, should be up-to-date now.
However, I have not been able to reproduce your problem on my GNU/Linux. From your log, I suppose that you have followed http://oldman.readthedocs.org/en/latest/installation.html .
Are you using Python 2.7?
Are you sure oldman is not installed in your global site-packages?

yes thats the procedure that i tried to follow, but who knows what i actually did:)
hope this helps:
(oldman-2.7)kook@kook-ThinkPad-R61e:~/envs/oldman-2.7/src/oldman$ git show -q HEAD
commit 79ef17bbdee22ec25f5eb76e7affacdcf8ae14d9
Author: Benjamin Cogrel<EMAIL_ADDRESS>Date:   Tue Feb 17 21:43:43 2015 +0100

    Typos found by koo5 (#41).
(oldman-2.7)kook@kook-ThinkPad-R61e:~/envs/oldman-2.7/src/oldman$ python setup.py install
running install
running bdist_egg
running egg_info
writing requirements to OldMan.egg-info/requires.txt
writing OldMan.egg-info/PKG-INFO
writing top-level names to OldMan.egg-info/top_level.txt
writing dependency_links to OldMan.egg-info/dependency_links.txt
reading manifest file 'OldMan.egg-info/SOURCES.txt'
writing manifest file 'OldMan.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-x86_64/egg
running install_lib
running build_py
creating build/bdist.linux-x86_64/egg
creating build/bdist.linux-x86_64/egg/oldman
copying build/lib.linux-x86_64-2.7/oldman/__init__.py -> build/bdist.linux-x86_64/egg/oldman
copying build/lib.linux-x86_64-2.7/oldman/common.py -> build/bdist.linux-x86_64/egg/oldman
copying build/lib.linux-x86_64-2.7/oldman/exception.py -> build/bdist.linux-x86_64/egg/oldman
copying build/lib.linux-x86_64-2.7/oldman/iri.py -> build/bdist.linux-x86_64/egg/oldman
copying build/lib.linux-x86_64-2.7/oldman/vocabulary.py -> build/bdist.linux-x86_64/egg/oldman
creating build/bdist.linux-x86_64/egg/oldman/model
copying build/lib.linux-x86_64-2.7/oldman/model/__init__.py -> build/bdist.linux-x86_64/egg/oldman/model
copying build/lib.linux-x86_64-2.7/oldman/model/ancestry.py -> build/bdist.linux-x86_64/egg/oldman/model
copying build/lib.linux-x86_64-2.7/oldman/model/attribute.py -> build/bdist.linux-x86_64/egg/oldman/model
copying build/lib.linux-x86_64-2.7/oldman/model/converter.py -> build/bdist.linux-x86_64/egg/oldman/model
copying build/lib.linux-x86_64-2.7/oldman/model/manager.py -> build/bdist.linux-x86_64/egg/oldman/model
copying build/lib.linux-x86_64-2.7/oldman/model/model.py -> build/bdist.linux-x86_64/egg/oldman/model
copying build/lib.linux-x86_64-2.7/oldman/model/operation.py -> build/bdist.linux-x86_64/egg/oldman/model
copying build/lib.linux-x86_64-2.7/oldman/model/property.py -> build/bdist.linux-x86_64/egg/oldman/model
copying build/lib.linux-x86_64-2.7/oldman/model/registry.py -> build/bdist.linux-x86_64/egg/oldman/model
creating build/bdist.linux-x86_64/egg/oldman/resource
copying build/lib.linux-x86_64-2.7/oldman/resource/__init__.py -> build/bdist.linux-x86_64/egg/oldman/resource
copying build/lib.linux-x86_64-2.7/oldman/resource/manager.py -> build/bdist.linux-x86_64/egg/oldman/resource
copying build/lib.linux-x86_64-2.7/oldman/resource/resource.py -> build/bdist.linux-x86_64/egg/oldman/resource
creating build/bdist.linux-x86_64/egg/oldman/parsing
copying build/lib.linux-x86_64-2.7/oldman/parsing/__init__.py -> build/bdist.linux-x86_64/egg/oldman/parsing
copying build/lib.linux-x86_64-2.7/oldman/parsing/operation.py -> build/bdist.linux-x86_64/egg/oldman/parsing
copying build/lib.linux-x86_64-2.7/oldman/parsing/value.py -> build/bdist.linux-x86_64/egg/oldman/parsing
creating build/bdist.linux-x86_64/egg/oldman/parsing/schema
copying build/lib.linux-x86_64-2.7/oldman/parsing/schema/__init__.py -> build/bdist.linux-x86_64/egg/oldman/parsing/schema
copying build/lib.linux-x86_64-2.7/oldman/parsing/schema/attribute.py -> build/bdist.linux-x86_64/egg/oldman/parsing/schema
copying build/lib.linux-x86_64-2.7/oldman/parsing/schema/context.py -> build/bdist.linux-x86_64/egg/oldman/parsing/schema
copying build/lib.linux-x86_64-2.7/oldman/parsing/schema/property.py -> build/bdist.linux-x86_64/egg/oldman/parsing/schema
creating build/bdist.linux-x86_64/egg/oldman/rest
copying build/lib.linux-x86_64-2.7/oldman/rest/__init__.py -> build/bdist.linux-x86_64/egg/oldman/rest
copying build/lib.linux-x86_64-2.7/oldman/rest/controller.py -> build/bdist.linux-x86_64/egg/oldman/rest
copying build/lib.linux-x86_64-2.7/oldman/rest/crud.py -> build/bdist.linux-x86_64/egg/oldman/rest
creating build/bdist.linux-x86_64/egg/oldman/utils
copying build/lib.linux-x86_64-2.7/oldman/utils/__init__.py -> build/bdist.linux-x86_64/egg/oldman/utils
copying build/lib.linux-x86_64-2.7/oldman/utils/crud.py -> build/bdist.linux-x86_64/egg/oldman/utils
copying build/lib.linux-x86_64-2.7/oldman/utils/sparql.py -> build/bdist.linux-x86_64/egg/oldman/utils
creating build/bdist.linux-x86_64/egg/oldman/validation
copying build/lib.linux-x86_64-2.7/oldman/validation/__init__.py -> build/bdist.linux-x86_64/egg/oldman/validation
copying build/lib.linux-x86_64-2.7/oldman/validation/value_format.py -> build/bdist.linux-x86_64/egg/oldman/validation
byte-compiling build/bdist.linux-x86_64/egg/oldman/__init__.py to __init__.pyc
byte-compiling build/bdist.linux-x86_64/egg/oldman/common.py to common.pyc
byte-compiling build/bdist.linux-x86_64/egg/oldman/exception.py to exception.pyc
byte-compiling build/bdist.linux-x86_64/egg/oldman/iri.py to iri.pyc
byte-compiling build/bdist.linux-x86_64/egg/oldman/vocabulary.py to vocabulary.pyc
byte-compiling build/bdist.linux-x86_64/egg/oldman/model/__init__.py to __init__.pyc
byte-compiling build/bdist.linux-x86_64/egg/oldman/model/ancestry.py to ancestry.pyc
byte-compiling build/bdist.linux-x86_64/egg/oldman/model/attribute.py to attribute.pyc
byte-compiling build/bdist.linux-x86_64/egg/oldman/model/converter.py to converter.pyc
byte-compiling build/bdist.linux-x86_64/egg/oldman/model/manager.py to manager.pyc
byte-compiling build/bdist.linux-x86_64/egg/oldman/model/model.py to model.pyc
byte-compiling build/bdist.linux-x86_64/egg/oldman/model/operation.py to operation.pyc
byte-compiling build/bdist.linux-x86_64/egg/oldman/model/property.py to property.pyc
byte-compiling build/bdist.linux-x86_64/egg/oldman/model/registry.py to registry.pyc
byte-compiling build/bdist.linux-x86_64/egg/oldman/resource/__init__.py to __init__.pyc
byte-compiling build/bdist.linux-x86_64/egg/oldman/resource/manager.py to manager.pyc
byte-compiling build/bdist.linux-x86_64/egg/oldman/resource/resource.py to resource.pyc
byte-compiling build/bdist.linux-x86_64/egg/oldman/parsing/__init__.py to __init__.pyc
byte-compiling build/bdist.linux-x86_64/egg/oldman/parsing/operation.py to operation.pyc
byte-compiling build/bdist.linux-x86_64/egg/oldman/parsing/value.py to value.pyc
byte-compiling build/bdist.linux-x86_64/egg/oldman/parsing/schema/__init__.py to __init__.pyc
byte-compiling build/bdist.linux-x86_64/egg/oldman/parsing/schema/attribute.py to attribute.pyc
byte-compiling build/bdist.linux-x86_64/egg/oldman/parsing/schema/context.py to context.pyc
byte-compiling build/bdist.linux-x86_64/egg/oldman/parsing/schema/property.py to property.pyc
byte-compiling build/bdist.linux-x86_64/egg/oldman/rest/__init__.py to __init__.pyc
byte-compiling build/bdist.linux-x86_64/egg/oldman/rest/controller.py to controller.pyc
byte-compiling build/bdist.linux-x86_64/egg/oldman/rest/crud.py to crud.pyc
byte-compiling build/bdist.linux-x86_64/egg/oldman/utils/__init__.py to __init__.pyc
byte-compiling build/bdist.linux-x86_64/egg/oldman/utils/crud.py to crud.pyc
byte-compiling build/bdist.linux-x86_64/egg/oldman/utils/sparql.py to sparql.pyc
byte-compiling build/bdist.linux-x86_64/egg/oldman/validation/__init__.py to __init__.pyc
byte-compiling build/bdist.linux-x86_64/egg/oldman/validation/value_format.py to value_format.pyc
creating build/bdist.linux-x86_64/egg/EGG-INFO
copying OldMan.egg-info/PKG-INFO -> build/bdist.linux-x86_64/egg/EGG-INFO
copying OldMan.egg-info/SOURCES.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying OldMan.egg-info/dependency_links.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying OldMan.egg-info/requires.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying OldMan.egg-info/top_level.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
zip_safe flag not set; analyzing archive contents...
creating 'dist/OldMan-0.2-py2.7.egg' and adding 'build/bdist.linux-x86_64/egg' to it
removing 'build/bdist.linux-x86_64/egg' (and everything under it)
Processing OldMan-0.2-py2.7.egg
Copying OldMan-0.2-py2.7.egg to /home/kook/envs/oldman-2.7/lib/python2.7/site-packages
Adding OldMan 0.2 to easy-install.pth file

Installed /home/kook/envs/oldman-2.7/lib/python2.7/site-packages/OldMan-0.2-py2.7.egg
Processing dependencies for OldMan==0.2
Searching for negotiator==1.0.0
Best match: negotiator 1.0.0
Adding negotiator 1.0.0 to easy-install.pth file

Using /home/kook/envs/oldman-2.7/lib/python2.7/site-packages
Searching for requests==2.5.1
Best match: requests 2.5.1
Adding requests 2.5.1 to easy-install.pth file

Using /home/kook/envs/oldman-2.7/lib/python2.7/site-packages
Searching for dogpile.cache==0.5.6
Best match: dogpile.cache 0.5.6
Adding dogpile.cache 0.5.6 to easy-install.pth file

Using /home/kook/envs/oldman-2.7/lib/python2.7/site-packages
Searching for validate-email==1.2
Best match: validate-email 1.2
Adding validate-email 1.2 to easy-install.pth file

Using /home/kook/envs/oldman-2.7/lib/python2.7/site-packages
Searching for SPARQLWrapper==1.6.4
Best match: SPARQLWrapper 1.6.4
Adding SPARQLWrapper 1.6.4 to easy-install.pth file

Using /home/kook/envs/oldman-2.7/lib/python2.7/site-packages
Searching for rdflib-jsonld==0.2
Best match: rdflib-jsonld 0.2
Adding rdflib-jsonld 0.2 to easy-install.pth file

Using /home/kook/envs/oldman-2.7/lib/python2.7/site-packages
Searching for rdflib==4.2.0.dev0
Best match: rdflib 4.2.0.dev0
rdflib 4.2.0.dev0 is already the active version in easy-install.pth
Installing rdf2dot script to /home/kook/envs/oldman-2.7/bin
Installing csv2rdf script to /home/kook/envs/oldman-2.7/bin
Installing rdfpipe script to /home/kook/envs/oldman-2.7/bin
Installing rdfs2dot script to /home/kook/envs/oldman-2.7/bin
Installing rdfgraphisomorphism script to /home/kook/envs/oldman-2.7/bin

Using /home/kook/envs/oldman-2.7/src/rdflib
Searching for dogpile.core==0.4.1
Best match: dogpile.core 0.4.1
Adding dogpile.core 0.4.1 to easy-install.pth file

Using /home/kook/envs/oldman-2.7/lib/python2.7/site-packages
Searching for html5lib==0.999
Best match: html5lib 0.999
Adding html5lib 0.999 to easy-install.pth file

Using /home/kook/envs/oldman-2.7/lib/python2.7/site-packages
Searching for pyparsing==2.0.3
Best match: pyparsing 2.0.3
Adding pyparsing 2.0.3 to easy-install.pth file

Using /home/kook/envs/oldman-2.7/lib/python2.7/site-packages
Searching for isodate==0.5.1
Best match: isodate 0.5.1
Adding isodate 0.5.1 to easy-install.pth file

Using /home/kook/envs/oldman-2.7/lib/python2.7/site-packages
Searching for six==1.9.0
Best match: six 1.9.0
Adding six 1.9.0 to easy-install.pth file

Using /home/kook/envs/oldman-2.7/lib/python2.7/site-packages
Finished processing dependencies for OldMan==0.2
(oldman-2.7)kook@kook-ThinkPad-R61e:~/envs/oldman-2.7/src/oldman$ ipython
WARNING: Attempting to work in a virtualenv. If you encounter problems, please install IPython inside the virtualenv.
Python 2.7.8 (default, Oct 20 2014, 15:05:19)
Type "copyright", "credits" or "license" for more information.

IPython 2.3.0 -- An enhanced Interactive Python.
?         -> Introduction and overview of IPython's features.
%quickref -> Quick reference.
help      -> Python's own help system.
object?   -> Details about 'object', use 'object??' for extra details.

In [1]: import oldman
INFO:rdflib:RDFLib Version: 4.2.0-dev
---------------------------------------------------------------------------
ImportError                               Traceback (most recent call last)
<ipython-input-1-962c9add6f3c> in <module>()
----> 1 import oldman

/home/kook/envs/oldman-2.7/src/oldman/build/bdist.linux-x86_64/egg/oldman/__init__.py in <module>()

/home/kook/envs/oldman-2.7/src/oldman/build/bdist.linux-x86_64/egg/oldman/resource/manager.py in <module>()

ImportError: No module named store.selector

In [2]:
Do you really want to exit ([y]/n)?
(oldman-2.7)kook@kook-ThinkPad-R61e:~/envs/oldman-2.7/src/oldman$ rm ~/envs/oldman-2.7/local/lib/python2.7/site-packages/OldMan-0.2-py2.7.egg
(oldman-2.7)kook@kook-ThinkPad-R61e:~/envs/oldman-2.7/src/oldman$ ipython
WARNING: Attempting to work in a virtualenv. If you encounter problems, please install IPython inside the virtualenv.
Python 2.7.8 (default, Oct 20 2014, 15:05:19)
Type "copyright", "credits" or "license" for more information.

IPython 2.3.0 -- An enhanced Interactive Python.
?         -> Introduction and overview of IPython's features.
%quickref -> Quick reference.
help      -> Python's own help system.
object?   -> Details about 'object', use 'object??' for extra details.

In [1]: import oldman
INFO:rdflib:RDFLib Version: 4.2.0-dev

In [2]:
Do you really want to exit ([y]/n)?
(oldman-2.7)kook@kook-ThinkPad-R61e:~/envs/oldman-2.7/src/oldman$ cd examples/
(oldman-2.7)kook@kook-ThinkPad-R61e:~/envs/oldman-2.7/src/oldman/examples$ ipython
WARNING: Attempting to work in a virtualenv. If you encounter problems, please install IPython inside the virtualenv.
Python 2.7.8 (default, Oct 20 2014, 15:05:19)
Type "copyright", "credits" or "license" for more information.

IPython 2.3.0 -- An enhanced Interactive Python.
?         -> Introduction and overview of IPython's features.
%quickref -> Quick reference.
help      -> Python's own help system.
object?   -> Details about 'object', use 'object??' for extra details.

In [1]: import oldman
---------------------------------------------------------------------------
ImportError                               Traceback (most recent call last)
<ipython-input-1-962c9add6f3c> in <module>()
----> 1 import oldman

ImportError: No module named oldman

In [2]:

Have you try to open python instead of ipython?
Apparently, ipython has not been installed in your virtualenv:
WARNING: Attempting to work in a virtualenv. If you encounter problems, please install IPython inside the virtualenv.

If you prefer IPython, you can try to install it in your virtualenv:
pip install ipython

I tried to install it on another machine and I have been able to reproduce this problem:
ImportError: No module named store.selector

The problem is that the sub-package oldman.store was not declared in setup.py. Now, it should be fixed.
Thanks again for reporting it!

:)
On Sat, Feb 21, 2015 at 11:43 AM, Benjamin Cogrel<EMAIL_ADDRESS>wrote:

I tried to install it on another machine and I have been able to reproduce
this problem:
ImportError: No module named store.selector
The problem is that the sub-package oldman.store was not declared in
setup.py. Now, it should be fixed.
Thanks again for reporting it!
—
Reply to this email directly or view it on GitHub
https://github.com/oldm/OldMan/issues/41#issuecomment-75366212.


WIP Release 0.8.0 alpha

WIP

Codecov Report

Merging #2861 (26fc947) into master (1a21018) will decrease coverage by 13.47%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master    #2861       +/-   ##
===========================================
- Coverage   36.08%   22.61%   -13.48%
===========================================
  Files         104       50       -54
  Lines        6460     1110     -5350
  Branches      197      197
===========================================
- Hits         2331      251     -2080
+ Misses       3821      832     -2989
+ Partials      308       27      -281

Flag
Coverage Δ

moduleA
22.61% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...ouse-service/event_handler/evaluate_sli_handler.go

shipyard-controller/api/project.go

helm-service/controller/delete_handler.go

.../configurationchanger/canary_weight_manipulator.go

...nfiguration-service/common/mongodb_project_repo.go

shipyard-controller/api/api_base.go

...-service/event_handler/start_evaluation_handler.go

shipyard-controller/common/pagination.go

configuration-service/common/files.go

helm-service/pkg/helm/test_util.go

... and 44 more

Continue to review full report at Codecov.

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


Getting "Illegal instruction" error when running sharp.js in Docker / Node container.

When running node.js in Docker, with sharp.js lib I am getting invalid instruction error and it exits
Same code works without error outside of container.
Here are the steps to reproduce, as well as work-around by using older version of sharp.js (0.27.2)
https://stackoverflow.com/questions/70488206/how-to-fix-invalid-instruction-error-when-running-node-js-in-docker-with-shar/

What is the output of running npx envinfo --binaries --system? Please answer this for inside and outside the container.
What is the output of running cat /proc/cpuinfo inside the container?
(My best guess is that you're running Docker via a virtualisation layer such as QEMU and creating an emulated CPU.)

  System:
    OS: Linux 5.10 Debian GNU/Linux 10 (buster) 10 (buster)
    CPU: (6) x64 AMD Phenom(tm) II X6 1090T Processor
    Memory: 2.44 GB / 12.42 GB
    Container: Yes
    Shell: 5.0.3 - /bin/bash
  Binaries:
    Node: 16.13.1 - /usr/local/bin/node
    Yarn: 1.22.15 - /usr/local/bin/yarn
    npm: 8.1.2 - /usr/local/bin/npm

processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 16
model           : 10
model name      : AMD Phenom(tm) II X6 1090T Processor
stepping        : 0
microcode       : 0xffffffff
cpu MHz         : 3210.791
cache size      : 512 KB
physical id     : 0
siblings        : 6
core id         : 0
cpu cores       : 6
apicid          : 0
initial apicid  : 0
fpu             : yes
fpu_exception   : yes
cpuid level     : 6
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow rep_good nopl cpuid extd_apicid pni cx16 popcnt hypervisor lahf_lm cmp_legacy cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw topoext vmmcall
bugs            : tlb_mmatch fxsave_leak sysret_ss_attrs null_seg amd_e400 spectre_v1 spectre_v2
bogomips        : 6421.58
TLB size        : 1024 4K pages
clflush size    : 64
cache_alignment : 64
address sizes   : 48 bits physical, 48 bits virtual
power management:

processor       : 1
vendor_id       : AuthenticAMD
cpu family      : 16
model           : 10
model name      : AMD Phenom(tm) II X6 1090T Processor
stepping        : 0
microcode       : 0xffffffff
cpu MHz         : 3210.791
cache size      : 512 KB
physical id     : 0
siblings        : 6
core id         : 1
cpu cores       : 6
apicid          : 1
initial apicid  : 1
fpu             : yes
fpu_exception   : yes
cpuid level     : 6
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow rep_good nopl cpuid extd_apicid pni cx16 popcnt hypervisor lahf_lm cmp_legacy cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw topoext vmmcall
bugs            : tlb_mmatch fxsave_leak sysret_ss_attrs null_seg amd_e400 spectre_v1 spectre_v2
bogomips        : 6443.86
TLB size        : 1024 4K pages
clflush size    : 64
cache_alignment : 64
address sizes   : 48 bits physical, 48 bits virtual
power management:

processor       : 2
vendor_id       : AuthenticAMD
cpu family      : 16
model           : 10
model name      : AMD Phenom(tm) II X6 1090T Processor
stepping        : 0
microcode       : 0xffffffff
cpu MHz         : 3210.791
cache size      : 512 KB
physical id     : 0
siblings        : 6
core id         : 2
cpu cores       : 6
apicid          : 2
initial apicid  : 2
fpu             : yes
fpu_exception   : yes
cpuid level     : 6
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow rep_good nopl cpuid extd_apicid pni cx16 popcnt hypervisor lahf_lm cmp_legacy cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw topoext vmmcall
bugs            : tlb_mmatch fxsave_leak sysret_ss_attrs null_seg amd_e400 spectre_v1 spectre_v2
bogomips        : 6437.95
TLB size        : 1024 4K pages
clflush size    : 64
cache_alignment : 64
address sizes   : 48 bits physical, 48 bits virtual
power management:

processor       : 3
vendor_id       : AuthenticAMD
cpu family      : 16
model           : 10
model name      : AMD Phenom(tm) II X6 1090T Processor
stepping        : 0
microcode       : 0xffffffff
cpu MHz         : 3210.791
cache size      : 512 KB
physical id     : 0
siblings        : 6
core id         : 3
cpu cores       : 6
apicid          : 3
initial apicid  : 3
fpu             : yes
fpu_exception   : yes
cpuid level     : 6
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow rep_good nopl cpuid extd_apicid pni cx16 popcnt hypervisor lahf_lm cmp_legacy cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw topoext vmmcall
bugs            : tlb_mmatch fxsave_leak sysret_ss_attrs null_seg amd_e400 spectre_v1 spectre_v2
bogomips        : 6432.10
TLB size        : 1024 4K pages
clflush size    : 64
cache_alignment : 64
address sizes   : 48 bits physical, 48 bits virtual
power management:

processor       : 4
vendor_id       : AuthenticAMD
cpu family      : 16
model           : 10
model name      : AMD Phenom(tm) II X6 1090T Processor
stepping        : 0
microcode       : 0xffffffff
cpu MHz         : 3210.791
cache size      : 512 KB
physical id     : 0
siblings        : 6
core id         : 4
cpu cores       : 6
apicid          : 4
initial apicid  : 4
fpu             : yes
fpu_exception   : yes
cpuid level     : 6
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow rep_good nopl cpuid extd_apicid pni cx16 popcnt hypervisor lahf_lm cmp_legacy cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw topoext vmmcall
bugs            : tlb_mmatch fxsave_leak sysret_ss_attrs null_seg amd_e400 spectre_v1 spectre_v2
bogomips        : 6432.69
TLB size        : 1024 4K pages
clflush size    : 64
cache_alignment : 64
address sizes   : 48 bits physical, 48 bits virtual
power management:

processor       : 5
vendor_id       : AuthenticAMD
cpu family      : 16
model           : 10
model name      : AMD Phenom(tm) II X6 1090T Processor
stepping        : 0
microcode       : 0xffffffff
cpu MHz         : 3210.791
cache size      : 512 KB
physical id     : 0
siblings        : 6
core id         : 5
cpu cores       : 6
apicid          : 5
initial apicid  : 5
fpu             : yes
fpu_exception   : yes
cpuid level     : 6
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow rep_good nopl cpuid extd_apicid pni cx16 popcnt hypervisor lahf_lm cmp_legacy cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw topoext vmmcall
bugs            : tlb_mmatch fxsave_leak sysret_ss_attrs null_seg amd_e400 spectre_v1 spectre_v2
bogomips        : 6448.26
TLB size        : 1024 4K pages
clflush size    : 64
cache_alignment : 64
address sizes   : 48 bits physical, 48 bits virtual
power management:

Please see #2723
The Phenom II 1090T is from 2010 and the Linux binaries require very slightly newer CPUs.

correct :)

Since it works with older version of the sharp.js 0.27.2 maybe we could call this a "feature" since it is likely faster by expecting improved CPU instruction set. May it be possible to conditionally use new(er) CPU instructions when available?
Would be helpful that it does not "crash" the whole app and instead throw an catchable error to help debugging as needed?
Just curious when running containers in the "cloud" could we always expect new(er) instruction set, or compatible instruction set, in particular now that ARM based CPUs are becoming available and popular?
Another related consideration: would compiling to WASM reduce performance significantly?
In not, that may be a practical solution to reduce complexity and dependencies on hardware features.

The minimum CPU requirement applies only to Linux x64. I'm not aware of a cloud provider that doesn't work with the prebuilt binaries provided by the latest version of sharp. Budget VPS companies might still offer older CPUs that don't, but the energy consumption of those things will be pretty terrible, and that will rapidly become the primary cost factor.
For Linux, almost all ARM Cortex-A CPUs from ARMv6 onwards are supported.
WASM is significantly slower - please see #1476 etc.


[DO NOT MERGE] Auto PR to update dependencies of mixer

This PR will be merged automatically once checks are successful.
none

This change is

@istio-testing: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/mixer-presubmit.sh
efa187ffed2db68b40bf8bf75e424ec6159db8a4
link
/test mixer-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


 The point of this driver is to allow synchronous, software-based transfers using the DMA interface. Its main usage is in SOF, but its design shouldn't limit its usage in other applications.

Naming this dummy dma was a dummy decision at that moment. What do you think of calling this simple-dma?

This is such a weird artifact of using DMA as an interface in SoF, I mean I'm not going to block it... but having to create a faked out DMA controller in software because i.MX uses shared memory to communicate to the big arm cores running linux is... awkward to say the least in my mind.
Things I'd like to see I suppose... renaming dummy DMA to maybe nxp sof-host-dma or something, as this is very specific to how sof works with this particular part no? Like this isn't trying to be a general purpose DMA controller in software is it?

Your PR description is not detailed enough to justify something as questionable as this. Please elaborate

Your PR description is not detailed enough to justify something as questionable as this. Please elaborate on why you think this is needed

I'm guessing the host SOF component was designed with the idea of performing the data transfer between Linux and firmware using a DMA engine, therefore it uses the Zephyr DMA interface. In our case (at least at the moment), we don't need a DMA to perform this transfer so we can use a simple memcpy(). Between trying to change the design such that on our platforms we don't use the DMA interface for the transfer and introducing a dummy DMA driver I prefer this as long as it doesn't affect anyone else or someone strongly opposes to its introduction. Also, I believe it's much simpler for the design to just not care about how the transfer is performed behind the scenes (either via memcpy() or an actual DMA engine) and use the DMA interface for all cases.

Things I'd like to see I suppose... renaming dummy DMA to maybe nxp sof-host-dma or something, as this is very specific to how sof works with this particular part no? Like this isn't trying to be a general purpose DMA controller in software is it? The name should match the intent here, and dummy DMA doesn't do that well enough I don't think

Yeah, just as @dbaluta pointed out, the naming isn't really the greatest. Was going to change to dma_nxp_software_dma to emphasise the fact that it's software-based, but if the naming is still misleading then what about something like dma_nxp_host_dma? In theory you can use this driver in any application that requires performing software-based transfers with the Zephyr DMA interface.

Your PR description is not detailed enough to justify something as questionable as this. Please elaborate on why you think this is needed

I'm guessing the host SOF component was designed with the idea of performing the data transfer between Linux and firmware using a DMA engine, therefore it uses the Zephyr DMA interface. In our case (at least at the moment), we don't need a DMA to perform this transfer so we can use a simple memcpy(). Between trying to change the design such that on our platforms we don't use the DMA interface for the transfer and introducing a dummy DMA driver I prefer this as long as it doesn't affect anyone else or someone strongly opposes to its introduction. Also, I believe it's much simpler for the design to just not care about how the transfer is performed behind the scenes (either via memcpy() or an actual DMA engine) and use the DMA interface for all cases.

Yeah I understand the issue, and as I mentioned I'm not planning on blocking this because I understand the difficulties here. That doesn't mean I think its pretty solution to the problem.

Yeah, just as @dbaluta pointed out, the naming isn't really the greatest. Was going to change to dma_nxp_software_dma to emphasise the fact that it's software-based, but if the naming is still misleading then what about something like dma_nxp_host_dma? In theory you can use this driver in any application that requires performing software-based transfers with the Zephyr DMA interface.

Well not entirely? This is a synchronous API that only actually does the copy once reload is called. This is a bit awkward as well. If we were to describe the behavior of every other DMA driver its more like...
dma_start() (asynchronously work through the transfer(s))
dma_reload() (append transfer work todo)
In this implementation...
dma_start() do nothing
dma_reload() do memcpy of the given buffer
How does this work given an initial set of transfers?
Behaviorally these are entirely different things. It happens to work because SOF works this way not because the DMA API behaviorally works this way across the board. To make it more general the transfers would need to be done asynchronously to the call path, and the initial transfer list would need to be worked through. The emulated DMA @cfriedt has in #57129 is probably closer in that regard as it uses a work queue to asynchronously work through transfers from what I recall.

Should be relatively trivial to extend dma_emul to do any custom tasks if that is necessary.
Technically, dma_emul could go in as-is if there are API consumers lined-uo @PiotrZierhoffer would probably appreciate that as well.

Should be relatively trivial to extend dma_emul to do any custom tasks if that is necessary.
Technically, dma_emul could go in as-is if there are API consumers lined-uo @PiotrZierhoffer would probably appreciate that as well.

Unfortunately I don't think dma emul would play well in the context of SoF where context swaps in the audio pipe are very costly. And dma_reload I believe is in the low latency audio pipe, so the memcpy in reload is the right answer and how it was done previously, but this can't be named in a way that implies its a general purpose software dma driver in my humble opinion.

@teburd tyvm for your comments, now I see how quirky this is. Will rename to reflect this fact.
As for the emulated DMA driver: for now, I'd like to avoid having to introduce another thread in the equation as it may introduce more problems especially if we can use the memcpy() approach.

@teburd tyvm for your comments, now I see how quirky this is. Will rename to reflect this fact.
As for the emulated DMA driver: for now, I'd like to avoid having to introduce another thread in the equation as it may introduce more problems especially if we can use the memcpy() approach.

yeah I completely understand! No need to have a work queue thread in this case

This is such a weird artifact of using DMA as an interface in SoF, I mean I'm not going to block it... but having to create a faked out DMA controller in software because i.MX uses shared memory to communicate to the big arm cores running linux is... awkward to say the least in my mind

Thanks for the comments @teburd . Indeed, this is not the ideal situation here. We were forced to "fake" a DMA because this is how SOF was designed. Intel actually has a real DMA between Host and DSP. I hope that we can merge this as it is (modulo all the review comments addressed) and than as an optimization we could think in the future of other possibilities.

V2 updates:

Changed the name of the driver to dma_nxp_sof_host_dma as per @teburd's suggestion.
Integrated the cache invalidation/flush operations in the driver. Comments in the reload() operation should describe why they're needed.


Suggestion: Upgrade to latest Swagger UI to fix Inline Model problem

As per these issues in AspnetCore repro, is there a possibility we can get an updrade to Swagger UI:
Any plans on updating to latest swagger ui 3.x
Use of actual model name instead of Inline Model

See my comment in #1064


Monitoring support

Is your feature request related to a problem? Please describe.
I want to monitor Quickwit's metrics and health checks. And I want to do it with a standard for the industry tooling like Prometheus, Grafana, etc.
Describe the solution you'd like

Integrate Prometheus metrics into Quickwit
Provide ready to use Grafana dashboards
Add notes about alerting setup (possibly via alert-manager or something similar)
Update documentation how to use it

Describe alternatives you've considered
Just do not introduce monitoring

Hello @zamazan4ik ,
We haven't document it much, but we do a set of prometheus metrics. You can access them on /metrics

We just added the metrics in the docs: https://github.com/quickwit-oss/quickwit/blob/main/docs/reference/metrics.md

@fmassot Thanks! For the users would be much easier to read it the information (at least some general info) directly from the documentation on the site. And there you can add a link to the metrics.md page.

Unfortunately, publishing the docs from our main repo to our website repo is not automated (yet). The metrics page will eventually be available on quickwit.io/docs, probably when we release 0.4 in a few weeks.

Unfortunately, publishing the docs from our main repo to our website repo is not automated (yet)

It is... but it was broken as one page had a broken link. It's fixed now: https://quickwit.io/docs/main-branch/reference/metrics

@zamazan4ik I opened a dedicated issue for the indexer monitoring #2160

@fmassot @fulmicoton is there an official Prometheus write API endpoint in quickwit?
Since the stream of logs is covered and the persisting of trace information throught he dedicated gRPC OTEL endpoint I was wandering if quickwit already (or will) support persisting of (e.g. Prometheus) metric information as well through a dedicated API ingest endpoint?

@ppaulweber support for metrics is planned for next year. We planned to work on two topics: storage optimized for time series + write/read API compatible with standards (like Prometheus). We don't have yet an accurate roadmap on this.

@fmassot thanks for this quick update and info.


Get genres in concept pages

Add genres to the concept page
https://github.com/wellcomecollection/catalogue-api/issues/615

mega detail but I think we've lost some spacing under the image gallery?
local

prod


renode-unstable: 1.14.0+20240106git1b3952c2c -> 1.14.0+20240119git1a0826937

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for renode-unstable is: Virtual development framework for complex embedded systems
meta.homepage for renode-unstable is: https://renode.org
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.14.0+20240119git1a0826937 in filename of file in /nix/store/smdspdpvy0sqp8d68izyzr70gfw58j80-renode-unstable-1.14.0+20240119git1a0826937

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
renode-unstable

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/smdspdpvy0sqp8d68izyzr70gfw58j80-renode-unstable-1.14.0+20240119git1a0826937 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A renode-unstable https://github.com/r-ryantm/nixpkgs/archive/7487b88f646cde3a27f8779b3fe1e7873def02da.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/7487b88f646cde3a27f8779b3fe1e7873def02da#renode-unstable

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/smdspdpvy0sqp8d68izyzr70gfw58j80-renode-unstable-1.14.0+20240119git1a0826937
ls -la /nix/store/smdspdpvy0sqp8d68izyzr70gfw58j80-renode-unstable-1.14.0+20240119git1a0826937/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

renode-unstable

Maintainer pings
cc @otavio for testing.

@otavio homepage for this package seems to need a small refresher, as renode.org is dead.


testing: publish test log to Build Cop Bot

This will automatically open/close issues for failing/passing tests (example). See https://github.com/googleapis/repo-automation-bots/tree/master/packages/buildcop.

cc @bcoe @sofisl @JustinBeckwith

@tbpg awesome work, I'm excited to see this work end to end.


new download page doesn't show any version numbers in the overview

The new download page looks nice, but you have to click on https://owncloud.org/install/#instructions-server and https://owncloud.org/install/#install-clients to see the current versions.
If you don't want to put the version numbers in the download/install overview, maybe you can create a separate overview page that shows all current versions.
What do you think?

Good point. Fixing...

This kind of works but isn't super - and doesn't work for the client. @tessus any suggestions on how else to show this? one of the @owncloud/designers might have an idea...

@jospoortvliet unfortunately I don't.

how was it done before the change?

@tessus the old install page simply had way more text in a vertical rather than horizontal layoud and showed it behind the name, like I have done now. But the page was much more colorful so it looked quite ok.
I can make it blue, but not dark blue so it won't fit color-wise in this page. I think it just doesn't fit - the extra click, I'm sure, won't chase anybody away so I think I'll drop this. But let's give the designers some time to come up with a creative solution...

I rather meant how the version numbers were retrieved. You said, you couldn't get the version for the Sync clients. I don't really care about design issues. Whether it's blue, green, pink, or just plain text, it's all the same to me. I only care about the information.
Thanks for looking into this.

@tessus well, sure, I can get the version the same way - but where do I put it on the page? That's the problem ;-)

I don't understand. Why not next to it?

Works for the server - but 'sync 1.8.0' is only true for the desktop client - the mobile clients (both!) have a different release cycle. So 1.8.0 is only correct for 1/3rd of the clients...
I am slightly inclined to put 1.8.0 there anyway, as you mocked up- this looks quite nice and the mobile clients take care of their own updates anyway.

Let's see what the designers think. I'm still not entirely sure about this...

Let's discuss it in #481 ;-)


Copilot can't see my code in open files

Copilot could see functions in my currently open file in VS Code for the past 6+ months.  Every day I just referred to the functions by name and Copilot knew exactly what I was talking about.  Suddenly after upgrading VS Code it can't see any code blocks unless I highlight them.  This is a 50% reduction in utility.

VS Code Version: 1.86.1
OS Version: Ubuntu 20
Logs:

Steps to Reproduce:

Ask Copilot about a method in the currently open file.
Copilot responds with:

"As an AI developed by OpenAI, I don't have the ability to see your screen, your open files, or any other part of your system..."

Maybe related to 861 (?)

Exact same issue on codesapces!

This is expected behaviour according to the release notes. I agree this is a massive reduction in utility. I'm having to select the entire file in order to give it the correct context.

This change in functionality caught me off guard too. I would highly recommend improving Copilot's response, because it's incorrect and misleading. Right now, asking the chatbot to reference your code through natural language results in a message that says it cannot look at your code. It can, but you need to use the "#file" or "#editor" commands. Copilot's reply should contain that information.
Also, it took me a while to find the release notes referenced in the previous comment. Here's a link for anyone else looking for more information:
https://github.blog/changelog/2024-02-12-vs-code-copilot-chat-january-2024-version-0-12/
This is a massive change in functionality that wasn't gracefully rolled out. Hope the next update improves the user experience across the entire spectrum.

That's an awful change and a significant step away from the idea that Copilot is like pair programming with a brilliant human. It's also a bit weird how the release notes make it sound like the #file function is new.

@cjkaminski Thank you for the answer.
This should be added to the extension settings obviously.  Something like editor_default: true

This change has severely degraded the usability of copilot imo.  If you don't use @workspaces or another command the response is almost always :
I'm sorry, but your message seems to be incomplete. Could you please provide more details or clarify what you need help with...
And my personal experience is that the results when using @workspaces/etc seem less useful/coherent. Not to mention it being an extra step each time you query.

Is downgrading VSCode to version 1.85 the only solution to restore the auto-reference feature?

Experiencing the same issue any solutions to revert this?

Sorry for the churn here. We were trying to push people towards the #editor variable, as the release notes describe https://code.visualstudio.com/updates/v1_86#_default-context-in-chat, but we see that hasn't been working out. So we are reverting the change until we have a better UX story for this, and you should now get the visible code as context.

Sorry for the churn here. We were trying to push people towards the #editor variable, as the release notes describe https://code.visualstudio.com/updates/v1_86#_default-context-in-chat, but we see that hasn't been working out. So we are reverting the change until we have a better UX story for this, and you should now get the visible code as context.

Did you recently re-implement that?? All of sudden, the current file is not auto-used and I have to add #editor on every question. Exactly WHY did you think this was a good idea to begin with, without offering a way to set it as default?


Update laravel/prompts

Allow newer versions of laravel/prompts. I am not aware of any breaking changes between V0.1 and V0.3.

Danke!


Localization support

Not everyone knows someone named Dave. In fact, outside of the
United States of Armenia, surprisingly few people are called that.
So let's remedy that so people can override Dave with their own
culturally relevant subject of ridicule. For instance, by calling:
$ ASFLAGS=-DSUBJECT=\"Ola\" make test
I can now get a localized version of fart-os that is culturally
relevant to Norway.
An alternative approach would be to start a "Get to know Dave"-program,
perhaps organize local events around the world where someone named
Dave will be introduced to people of different cultures. Thougths?

Not only is this culturally relevant, the example you gave is personally relevant. I feel very inspired and motivated to accept this.
However, I feel some documentation in the readme would be necessary before I can accept. Can you add that as well?

Good point. Here's a new version that does just that.

The perfect contribution to the perfect OS!


Secret variable cannot be used in PowerShell task if it contains an ampersand

Define a secret variable that contains an ampersand, e.g. a&b
Secret variables have to be passed into scripts as a parameter and it will fail at the point of passing the variable in, i.e. just having Param($inputVariableWhichIsSecret) in the script is sufficient.
Because VSTS seems to execute PowerShell block by block it tries to evaluate the secret variable and returns a PowerShell error:

The ampersand (&) character is not allowed. The & operator is reserved for future use; wrap an ampersand in double
quotation marks ("&") to pass it as part of a string.
At line:1 char:237

... Clear() } ; Invoke-Expression -Command ([System.Text.Encoding]::UTF8. ...

            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : ParserError: (:) [Invoke-Expression], ParseException
FullyQualifiedErrorId : AmpersandNotAllowed,Microsoft.PowerShell.Commands.InvokeExpressionCommand

The params are passed on a powershell command line so you need to escape (e.g. wrap in double or single quotes).
Note, passing on a ps command line enables things like arrays and hashtables. So passing on the ps command line is intentional and correct.

@ericsciple Thanks. Yes, that works, thanks. Would it make sense to document that the arguments to PowerShell actually get evaluated (e.g. in the help-markdown of the task)? I had a look at the documentation here which used to say that secret variables have to be passed in as $(mysecret), which seems to have changed by now as I can pass them in now as $env:mysecret as well. We as users rely on documentation and given that the behaviour of VSTS changes very quickly, it gets very confusing. Is there at least some sort of log to see the subtle changes of behaviour as you improve VSTS (which is appreciated btw)?

@ChristophB125 Secret variables do not get passed to ad hoc scripts. That has not changed.
Are you sure it's a secret?
I can't repro any issue with that behavior. Here is what I tried:

Create a definition with two variables
MySecretVariable = MySecretValue // this one is secret
MyPublicVariable = MyPublicValue

Add a PowerShell task with inline script:

"secret is: $env:MySecretVariable"
"public is: $env:MyPublicVariable"

Output of the script is:

secret is:
public is: MyPublicVariable

I know that I am late into this thread, but I am kind of stuck. And this thread is the closest to the issue I have. So, I have a SAS token which is set in previous Release task and then the Create Resource Group Task uses that SAS token to create the resource group. However, when I try to use the same SAS Token in a powershell task, if I just use in the parameters section of the PowerShell Task
-SecretArgument '$(SASToken)'
And then print it in the powershell script I get: ***
If I use , in the parameters section of the PowerShell Task
-SecretArgument $(SASToken)
And then print it out in the script, it errors out saying it contains"&" (the special characters that SAS token has), but I can see the half truncated value of $SASToken in the failed release log in clear text.
I have also used single quotes but that also masks it as ***. Is there a way to get this value in the powershell script?
Strangely , this SAS token works (without quotes) in the "Deploy Resource Group Task" when it's passed in the override parameter section (as many tutorials show).
I have run out of ideas to use it in the PowerShell task. Is this a bug in VSTS Release pipeline that secrets with special characters can't be used?


python/task/plus-one.py

Complete the task here:-
https://leetcode.com/problems/plus-one/
and provide the screenshot of the code and output on the path referenced to by the title of the issue.

Assign this to me

Please assign this issue!


Added translation for anvils

Looking good so far. I am still adding more items, so please check back later once I manage to push those commits

Looking good so far. I am still adding more items, so please check back later once I manage to push those commits

I like how you had the manganese and kyber anvil added, even though I have not committed them until now 😄
Just gonna add some missing textures and will probably merge.

I like how you had the manganese and kyber anvil added, even though I have not committed them until now 😄
Just gonna add some missing textures and will probably merge.

Oupsie, i've only copied these strings from the former version of the en_us lang, in which they already were added by DeatHunter👀

Oupsie, i've only copied these strings from the former version of the en_us lang, in which they already were added by DeatHunter👀

If anything, i just checked this version of ru_ru lang, bc was afraid of syntaxis issues, and it works fine

If anything, i just checked this version of ru_ru lang, bc was afraid of syntaxis issues, and it works fine


Incorrect display projects per page after selecting a number greater than 30

Describe the bug
If we have more than 30 projects and we choose in the tool to display more than 30 projects per page, only 30 are displayed. However, the number of pages will decrease and some projects will not be displayed.
To Reproduce
Steps to reproduce the behavior:
Add more than 100 projects
Choose 50 or 100 projects per page in projects list view
Count the number of projects (quantity is wrong)
Change to next page (you can see that the sum of the number of projects is less than 100)

Expected behavior
The page should display the same number of projects as selected per page. The number of projects on all pages should be the same as the number of all projects.
Screenshots
n/a -- can provide if really needed
Environment
OS: Mint
Label Studio Version Release 1.7.1

Additional context
In this line page_size should be passed as parameter.
https://github.com/heartexlabs/label-studio/blob/9308125b3633997d2546a26a7855804c850cc32a/label_studio/frontend/src/pages/Projects/Projects.js#L70
I found the error together with @mikbuch

The same issue applies to macOS Big Sur 11.7.2

The fix is in develop.

Great, thank you!