Using a tuple for modes= argument gives ValueError

Before posting a bug report

[X] I have searched exisisting GitHub issues to make sure the issue does not already exist.

Expected behavior
I generally use tuples for immutable structures, and so expected that modes could be given as such.  But it seems to be only working for lists.
Actual behavior
Shouldn't give a value error and should work just as if the modes= argument were a list.
Reproduces how often
Always.
System information
Mr Mustard: a differentiable bridge between phase space and Fock space.

Copyright 2021 Xanadu Quantum Technologies Inc.

Python version:            3.9.5

Platform info:             Linux-6.2.2-arch1-1-x86_64-with-glibc2.31

Installation path:         /usr/local/lib/python3.9/dist-packages/mrmustard

Mr Mustard version:        0.4.0

Numpy version:             1.23.5

Numba version:             0.56.4

Scipy version:             1.8.0

The Walrus version:        0.19.0

TensorFlow version:        2.10.1

Source code
from mrmustard.lab import BSgate
gate_tuple = BSgate(modes=(1,2)) >> BSgate(modes=(0,1))
gate_list = BSgate(modes=[1,2]) >> BSgate(modes=[0,1])
unitary = gate_list.U(cutoffs=(3,3,3)) # works
unitary = gate_tuple.U(cutoffs=(3,3,3))

Tracebacks
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
Cell In[19], line 1
----> 1 unitary = gate_tuple.U(cutoffs=(3,3,3))

File /usr/local/lib/python3.9/dist-packages/mrmustard/lab/abstract/transformation.py:218, in Transformation.U(self, cutoffs)
    216 if not self.is_unitary:
    217     return None
--> 218 X, _, d = self.XYd
    219 return fock.wigner_to_fock_U(
    220     X if X is not None else math.eye(2 * self.num_modes),
    221     d if d is not None else math.zeros((2 * self.num_modes,)),
    222     shape=cutoffs * 2 if len(cutoffs) == self.num_modes else cutoffs,
    223 )

File /usr/local/lib/python3.9/dist-packages/mrmustard/lab/circuit.py:76, in Circuit.XYd(self)
     74 for op in self._ops:
     75     opx, opy, opd = op.XYd
---> 76     opX = XPMatrix.from_xxpp(opx, modes=(op.modes, op.modes), like_1=True)
     77     opY = XPMatrix.from_xxpp(opy, modes=(op.modes, op.modes), like_0=True)
     78     opd = XPVector.from_xxpp(opd, modes=op.modes)

File /usr/local/lib/python3.9/dist-packages/mrmustard/utils/xptensor.py:561, in XPMatrix.from_xxpp(cls, tensor, like_0, like_1, modes)
    559     tensor = math.reshape(tensor, [_ for n in tensor.shape for _ in (2, n // 2)])
    560     tensor = math.transpose(tensor, (1, 3, 0, 2))
--> 561 return XPMatrix(tensor, like_0, like_1, modes)

File /usr/local/lib/python3.9/dist-packages/mrmustard/utils/xptensor.py:538, in XPMatrix.__init__(self, tensor, like_0, like_1, modes)
    534     raise ValueError(f"like_0 and like_1 can't both be {like_0}")
    535 if not (
    536     isinstance(modes, tuple) and len(modes) == 2 and all(isinstance(m, list) for m in modes)
    537 ):
--> 538     raise ValueError("modes should be a tuple containing two lists (outmodes and inmodes)")
    539 if len(modes[0]) == 0 and len(modes[1]) == 0 and tensor is not None:
    540     if (
    541         tensor.shape[0] != tensor.shape[1] and like_0
    542     ):  # NOTE: we can't catch square coherences if no modes are specified

ValueError: modes should be a tuple containing two lists (outmodes and inmodes)

Additional information
This is actually on the develop branch at 1abad670dc76a83efd73f8189f3875bd7915c234.  But I see the same behaviour using v0.4.0.

closing, feel free to reopen if needed


Suggestions for code modifications

In evaluate.py :  The parameter type can be modified to support the scenario where a sample contains multiple locality prompts for calculation.
The origin code is as following:
def compute_locality_quality(
    model,
    model_name,
    hparams: HyperParams,
    tok: AutoTokenizer,
    locality_key: str,
    prompt:  str,
    locality_ground_truth: str,
    device,
) -> typing.Dict:

Here's the updated code：
def compute_locality_quality(
    model,
    model_name,
    hparams: HyperParams,
    tok: AutoTokenizer,
    locality_key: str,
    prompt: typing.Union[str, List[str]], # str,
    locality_ground_truth: typing.Union[str, List[str]], #str,
    device,
) -> typing.Dict:

and as well as portability_evaluate.py:
def compute_portability_quality(
    model,
    model_name,
    hparams: HyperParams,
    tok: AutoTokenizer,
    portability_key: str,
    prompt: typing.Union[str, List[str]], # str,
    ground_truth: typing.Union[str, List[str]], # str,
    device,
) -> typing.Dict:

Thank you for your suggestion, I will update the corresponding code as soon as possible to support multiple locality inputs. 😊

Hi, we have updated the code. You can pass in parameters in the form of list or str. Single edit can correspond to multiple locality_inputs and portability_inputs. Please update to the latest version of the code and welcome to try it.
The input form for single editing is as follows:
locality_inputs = {
    'neighborhood':{
        'prompt': [['loc_input_1_for_editing_1', 'loc_input_2_for_editing_1']],
        'ground_truth': [['loc_input_1_ans', 'loc_input_2_ans']]
    }
}

If it helps you solve the related problem, please help close this issue. 😊

Yes it works! Thanks! 😄


assign early folding

prereq for CONST -> VALID rewrite.

if it's a flat CONST it must be the src of a BUFFER op. I found correctness problems with UPCAST otherwise.

couldn't repro the generate_dataset stuff despite many tries ended up just graph_rewriting the ASTs. I propose we make this a benchmark and download artifact.


[bp/1.26] Backport stack (2)

Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

tools/ci changes may not be thoroughly tested, and so we may introduce some breaks with prior releases, but I believe we'll be able to fix them if needed.

yep - im testing quite a bit here and will test further in downstream mirror when this lands
its a tradeoff previously i didnt keep ci in sync and that made backporting/fixing more difficult - its been a lot easier since doing it this way as the branches work ~the same
currently 1.26+ is kept in sync, and 1.24/5 were previously but are not now - but at least work ~the same

fwiw it works perfectly locally

i think we can fish the binary out of the docker image or similar

i figured a better way - update the build image and install the missing cmake/ninja as that was why it was breaking

/retest

@adisuissa i think this should be passing finally - would you mind giving it a last review


Use separate UniqueVector to track constants

Avoid polluting the main ValueMap until we actually
generate the SPIR-V constants.  It's less confusing
this way, and matches how we track and generate types.

Tested on Release and Debug build.
I like this code cleanup.
LGTM


[object] Store package version in object

Soon it will no longer be the case that a package's version is always 1, because:

Framework Upgrades will write new versions of the framework at increasing versions in the store.
Package Upgrades will pun the package's version in storage with its version in the chain of upgrades (Even though subsequent versions will exist at distinct ObjectIDs).

This PR retires PACKAGE_VERSION and stores the package version in MovePackage instead (although initially, it will still always be 1).
This change also means that it is no longer possible to ascertain a package's version, when it is passed in as an input object.
Breaking Changes

Call transactions that reference a non-existent package will produce a "Missing Input Object" error.  Because the query for the package is not fixed to a particular version, VersionNumber::MAX is returned as a sentinel value for the version it is missing at.

Test Plan
$ cargo nextest run

Stack

#7597

(Note, this is a stacked PR, so to review, just look at commits from [object] Store package version in object onwards, or wait to review until the bottom of the stack has landed.)

Test failure is probably legit, so let me move this back into draft mode.

I'm no longer sure that the issue with fullnode tests is due to this change.  @mystenmark, is this a known flaky test?  When run outside of simtest, I am seeing it sometimes succeeding, and sometimes not.

Thanks to @mystenmark I now know what's going on with the failing tests and they are legitimate after all.  Back to draft-mode to fix.

Just curious about the background, is there a doc discussing what guarantees that a transaction will not be executed with different input package versions, and why it is necessary to support creating a package at an initial version other than 1?

@mwtian,

Just curious about the background, is there a doc discussing what guarantees that a transaction will not be executed with different input package versions, and why it is necessary to support creating a package at an initial version other than 1?

This change is to support two kinds of upgrades:

Framework Upgrades, where there might be multiple versions under the same Object ID (0x1 or 0x2), but new versions are only added on epoch boundaries.
Third party package upgrades, where each new version of the package will exist at a fresh Object ID, but its version will be one greater than the previous version of the package, so there is only one version per object ID, but not necessarily version 1.

Do we need to include package object ref in the effects, now that we cannot tell its version based on the transaction data?

Interesting question. This doesn't seem entirely necessary as a state commitment, because there can only exist one version of each unique package id (except for frameworks).

Interesting question. This doesn't seem entirely necessary as a state commitment, because there can only exist one version of each unique package id (except for frameworks).

Same argument applies to the shared_object_ids in the effects. So the question is whether we need it for other things, such as pruner, snapshot hash and etc..

Let me kick off a thread on the question of package refs in effects -- I also think it probably won't be necessary, but I'm missing context on ancillary uses for effects.  I don't think that will affect the substance of this PR though, so let me land this to unblock the protocol upgrade work building on top of it.


[kineticscroll] Sometimes missing red back button, especially w/o widgets

Affected hardware version
Bangle 2
Your firmware version
2v21.107
The bug
@halemmerich
The red back button will sometimes be missing when using kineticscroll, especially when no widgets are loaded or shown.
This problem seems similar to https://github.com/espruino/BangleApps/issues/2168 so I reused/updated the debug code I made there, see below. Maybe the fix Gordon did there can be applied here as well.
/*
Test code for trying menu system with/without widget field present.

Use Web IDE and upload to ram.

Test 1:
1. Make sure to use the builtin scroller, uninstalling `kineticscroll` or similar.
2. upload this script to ram.
3. notice the red back button is present.
4. end test

Test 2:
1. Install `kineticscroll`
2. upload this script to ram.
3. notice the widget field and red back button is missing.
4. enter submenu and notice there is now a double heading.
5. exit submenu by pressing in the top left corner where the red back button would have been.
6. end test

Test 3:
1. Have `kineticscroll` installed.
2. Uncomment //Bangle.loadWidgets() down below.
3. Upload to ram.
4. notice the red back button is present.
5. end test

Test 4:
1. Have `kineticscroll` installed.
2. Uncomment //Bangle.loadWidgets() as well as //require("widget_utils").hide(); down below.
3. upload this script to ram.
4. enter submenu and notice there is now a double heading.
5. exit submenu by pressing in the top left corner where the red back button would have been.
6. end test

*/

print("\n\nBefore code is run:");
print(Bangle.appRect);

var mainMenu = {
  "" : {title : "Main menu",
        back : ()=>{
          print("\n\nBefore calling E.showMenu():");
          print(Bangle.appRect);
          E.showMenu();
          print("After calling E.showMenu():");
          print(Bangle.appRect);
        }
       },
  "1 Submenu" : ()=>{
    print("\n\nBefore calling E.showMenu(subMenu):");
    print(Bangle.appRect);
    E.showMenu(subMenu);
    print("After calling E.showMenu(subMenu):");
    print(Bangle.appRect);
  },
  "2 appRect" : ()=>{
    print("\nOn main menu:");
    print(Bangle.appRect);
  },
  "3" : ()=>{},
  "4" : ()=>{},
  "5" : ()=>{},
  "6" : ()=>{},
  "7" : ()=>{},
  "8" : ()=>{},
};

var subMenu = {
  "" : {title : "Submenu",
        back : ()=>{
          print("\n\nBefore calling E.showMenu(mainMenu):");
          print(Bangle.appRect);
          E.showMenu(mainMenu);
          print("After calling E.showMenu(mainMenu):");
          print(Bangle.appRect);
        }
       },
  "1" : ()=>{},
  "2 appRect" : ()=>{
    print("\n\nOn submenu:");
    print(Bangle.appRect);
  },
  "3" : ()=>{},
  "4" : ()=>{},
  "5" : ()=>{},
  "6" : ()=>{},
  "7" : ()=>{},
  "8" : ()=>{},
};

//Bangle.loadWidgets();
//require("widget_utils").hide();

E.showMenu(mainMenu);

I also wondered if it's just that some of the newest code from the standard scroller wasn't included in kineticscroll?
 The description of the fix seems to match the current code of kineticscroll since it gets the appRect while defining the new scroller function so definitely before calling setUI. Will have a look at that.


create employee request BE

create and sign employee request
change config for NHS LE

conf
apiary example create employee request v2

add validation for rest

[ ] error 500 in case duplicated phones types
ValidationError{description: "No duplicate values.", params: ["LAND_LINE"]

[ ] Where do we save signed content?


Semaphore timeout during long insert

Environment

Python: 3.7 64bit
pyodbc: 4.0.26
OS: Windows 10 64bit
DB: SQL Server 2012 Enterprise
driver: SQL Server Native Client 11.0

Connection Setup
Connection string: DSN=XXX;DATABASE=DB;Uid=USER;Pwd=PWD;MultipleActiveResultSets=True
In python:
CONN_TIMEOUT = 0	# i.e., no timeout
cxn = pyodbc.connect(conn_str, autocommit=True)
cxn.setencoding('utf-8')
cxn.timeout = CONN_TIMEOUT
...
def test_insert():
    # this is actually in a class
    x = [(i,) for i in range(10000000)]
    with cxn.cursor() as cur:
        cur.fast_executemany = True
        cur.execute('create table #tmp (unique_id int)')
        cur.commit()
        logging.info(1)
        cur.executemany('insert into #tmp values (?)', x)
        cur.commit()
        logging.info(2)
        cur.execute('create unique index tmp_pk on #tmp (unique_id)')
        cur.commit()
        logging.info(3)
        cur.execute('drop table #tmp')
        cur.commit()
    return 'done'

Expected behavior
Multiple calls to test_insert works as expected.
Observed behavior
Multiple large inserts will time out and it doesn't seem be related to connection timeout. This error is can be consistently replicated by running the above.
In [1]: test_insert()
[2019-04-16 11:26:31,383] [INFO] 1
[2019-04-16 11:34:46,561] [INFO] 2
[2019-04-16 11:34:48,338] [INFO] 3
Out[1]: done

In [2]: test_insert()
[2019-04-16 11:35:02,416] [INFO] 1
---------------------------------------------------------------------------
OperationalError                          Traceback (most recent call last)
<ipython-input-2-2bc7e3c2dfe0> in <module>
----> 1 test_insert()

~\Documents\project\database_int.py in test_insert(self)
   2379                         cur.commit()
   2380                         logging.info(1)
-> 2381                         cur.executemany('insert into #tmp values (?)', x)
   2382                         cur.commit()
   2383                         logging.info(2)

OperationalError: ('08S01', '[08S01] [Microsoft][SQL Server Native Client 11.0]TCP Provider: The semaphore timeout period has expired.\r\n (121) (SQLExecute); [08S01] [Microsoft][SQL Server Native Client 11.0]Communication link failure (121)')

Ok, taking out MultipleActiveResultSets=True seems to have solved the issue.


test: function for general crosswalk wrapper

Using a set of Carolyn's prioritized datasets as an input, test general_crosswalk.R function and identity any errors.

scrapped


Add patch for sscanf on libc

This PR adds a patch for a function imported from libc, which is not available on WASM. Currently I've just created a stub, which does not actually perform a function, but in the future we can patch this with a proper replacement if need be. Right now it seems to be unused.

Looks perfect


Spurious error related to "note commitment missing"

See: https://discord.com/channels/824484045370818580/981304070444814367/1248691717322838118
The basic failure mode involves doing transactions in pcli, such as contributing to the ceremony, and failing to send a transaction because of the error Note commitment missing. This seems spurious, in that it doesn't reproduce easily.
We should look into this more, as we've seen several reports about this.
Also, it seems like Galileo was having these errors back in November as well.

this looks like the same error observed in https://github.com/penumbra-zone/penumbra/issues/4574#issuecomment-2155251849

This is reproducibly happening for me on the current testnet

there are a collection of errors, all filed around the same time, that relate
to inconsistent behavior when viewing transactions. i took some time to gather
these, and write up my understanding of the current state of affairs:
#4452 reports that the view service's response streams terminate when an error
is encountered. #4465 reports that the view service misses some tx's when
scanning. #4577 describes the view service being corrupted with invalid
anchors.
#4584, #4574, and #4238 all describe issues with pcli failing to collect
various information. #4584 reports that pcli fails to
query dex all-positions, #4574 reports that pcli fails to sweep, and #4238
reports that pcli fails to detect delegator votes.
#4601 describes "note commitment missing" errors when making transactions
with pcli, which is the underlying issue behind #4574 in particular.
in response to this, we have already shipped a few changes to address this:

#4453 avoids recording invalid Metadata.
#4578 adds height checks to the view service.
#4586 adds height checks to the compact-block server.

these have all shipped in v0.77.3.
#4605 added test coverage for pcli sweep, and #4617 made additional changes
to facilitate exercising pcli in mock consensus tests. #4517 tracks an issue
that soft blocks us from adding more test coverage of the view service, which
caused us to disable that test coverage in #4633.
at this point i believe that #4601 and #4574 can also be closed via #4578
and #4586. these added defensive checks to the compact-block RPC and the
view service to help keep syncing deterministic and reliable, which is a
common thread between all of these issues. going forward, we can build out
more assurance of this system by addressing #4517 next.


undefined subject on using onFlow

Describe the bug
The subject parameter in the menuSuggestionFlow function (using onFlow) is consistently coming as undefined, even though valid input is provided in the request payload. This blocks the function's ability to dynamically generate menu suggestions based on the input theme.

To Reproduce
Steps to reproduce the behavior:

Deploy the menuSuggestionFlow function.  This code was generated while creating project via command line.export const menuSuggestionFlow = onFlow(
 ai,
 {
     name: "menuSuggestionFlow",
     inputSchema: z.string(),
     outputSchema: z.string(),
     authPolicy: firebaseAuth((user) => {}),
 },
 async (subject) => {
     const prompt = `Suggest an item for the menu of a ${subject} themed restaurant`;
     const llmResponse = await ai.generate({
         model: gemini15Flash,
         prompt: prompt,
         config: {
             temperature: 1,
         },
     });
     return llmResponse.text;
   }
 );

Use Postman or cURL to make a POST request to the deployed function with the following payload:{
    "subject": "Italian"
}

Check the logs for the value of the subject parameter.

Expected behavior
The subject parameter should capture the value from the payload (e.g., "Italian") and use it to generate the prompt for menu suggestions.

What We Tried
Validating Input Schema:
The inputSchema was defined as z.string() to ensure subject was a non-empty string. No schema errors were thrown, indicating that the input was passing validation.
Testing with Postman and cURL:
Sent a POST request with the following payload:
{
  "subject": "Italian"
}

Despite providing valid input, the subject remained undefined when logged in the function.
Logging the subject Parameter:
Added a console.log statement to log the subject value:
async (subject) => {
    console.log("Received subject:", subject); // Always logs "undefined"

}

The log consistently showed undefined.
Defaulted to a Hardcoded String:
Replaced subject with a hardcoded string to bypass the issue:
const prompt = Suggest an item for the menu of a French-themed restaurant;
This worked, but it is not a sustainable solution as the function is meant to dynamically generate responses based on the input.
Verified the Request Payload:
Confirmed the payload and headers were correct in Postman. The Authorization: Bearer token was included, and the JSON structure was validated.
Tested Alternative Schema:
Updated the inputSchema to z.object({ subject: z.string() }) to explicitly expect an object, but the issue persisted.
Tried Debugging onFlow:
Suspected a mapping issue in onFlow. Reviewed its internal behavior but found no immediate resolution.
Observation
The subject parameter is not being mapped correctly by onFlow. The issue may lie in how onFlow parses or maps the input payload.

Screenshots
N/A

Desktop (please complete the following information):

OS: Windows 11
Browser: Chrome
Version: 119

Additional context

Input validation through z.string() schema did not throw any errors.
Logs show subject consistently as undefined.
We tested using a hardcoded value instead of subject, and the function worked as expected.
Using onRequest resolved the issue, suggesting the problem lies in onFlow's handling of the input payload.
The issue persists despite verifying the payload structure and headers in the request.

This bug prevents the function from dynamically responding to user input, significantly hindering the expected functionality.

You need to wrap flow input in the request data object when making the request:
{
  "data": {
    "subject": "Italian"
  }
}

Thanks it worked.
Any suggestion for resource where we can see how to train a model for repeated task like transforming data to structured object so that we don't need to send the long prompt every time and also it can train itself.


Is it mandatory to restart yaws to see change in callback dirs?

In setting up some simple websocket examples i noticed
after changing a beam callback file  only by restarting yaws
changes will be visible.
Can we avoid that?
Maybe it's a cache thing and we could clear cache so yaws pulls new code?

Hi,
You can reload a module using Yaws script:
 $> yaws --load my_module

Another solution is to use src_dir in the global part of your config file. Yaws will compile all erlang modules found, recursively, in source directories. The compilation occurs when the configuration is loaded or reloaded.

Sorry for the late response.
#yaws --load module or # yaws --status etc all give me :
No yaws system responds

This is probably because you set a specific id to your Yaws instance. Check the id value in your configuration (It is default when unset). Then use it when you call Yaws script:
$> yaws --id {MYNAME} --load module

You can also get name of your Yaws instance using following Erlang snippet:
{ok, GC, _} = yaws_server:getconf(),
ID = yaws:gconf_id(GC),
...

That worked finaly (but if i execute it as root i'get also many messages.
sudo -H -u yaws bash -c 'yaws --status --id debian_yaws'
chomwitt@enous3:/$ id
uid=1000(chomwitt) gid=1000(chomwitt) ομάδες=1000(chomwitt),24(cdrom),25(floppy),27(sudo),29(audio),30(dip),33(www-data),44(video),46(plugdev),108(netdev),110(lpadmin),113(scanner)
chomwitt@enous3:/$ sudo -H -u yaws bash -c 'yaws --status --id debian_yaws'
IP Port Connections Sessions Requests
<IP_ADDRESS> 8443 0 1 0
<IP_ADDRESS> 8080 0 1 0
Uptime: 1 Days, 2 Hours, 4 Minutes
chomwitt@enous3:/
root@enous3:~# id
uid=0(root) gid=0(root) ομάδες=0(root)
root@enous3:~#  sudo -H -u yaws bash -c 'yaws --status --id debian_yaws'
{error_logger,{{2016,12,3},{16,46,38}},std_error,"File operation error: eacces. Target: .. Function: read_file_info. Process: code_server."}
{error_logger,{{2016,12,3},{16,46,38}},std_error,"File operation error: eacces. Target: ./standard_error.beam. Function: get_file. Process: code_server."}
{error_logger,{{2016,12,3},{16,46,38}},std_error,"File operation error: eacces. Target: ./supervisor_bridge.beam. Function: get_file. Process: code_server."}
{error_logger,{{2016,12,3},{16,46,38}},std_error,"File operation error: eacces. Target: ./user_sup.beam. Function: get_file. Process: code_server."}
{error_logger,{{2016,12,3},{16,46,38}},std_error,"File operation error: eacces. Target: ./user.beam. Function: get_file. Process: code_server."}
{error_logger,{{2016,12,3},{16,46,38}},std_error,"File operation error: eacces. Target: ./kernel_config.beam. Function: get_file. Process: code_server."}
{error_logger,{{2016,12,3},{16,46,38}},std_error,"File operation error: eacces. Target: ./queue.beam. Function: get_file. Process: code_server."}
=ERROR REPORT==== 3-Dec-2016::18:46:38 ===
File operation error: eacces. Target: .. Function: read_file_info. Process: code_server.
=ERROR REPORT==== 3-Dec-2016::18:46:38 ===
File operation error: eacces. Target: ./standard_error.beam. Function: get_file. Process: code_server.
=ERROR REPORT==== 3-Dec-2016::18:46:38 ===
File operation error: eacces. Target: ./supervisor_bridge.beam. Function: get_file. Process: code_server.
=ERROR REPORT==== 3-Dec-2016::18:46:38 ===
File operation error: eacces. Target: ./user_sup.beam. Function: get_file. Process: code_server.
=ERROR REPORT==== 3-Dec-2016::18:46:38 ===
File operation error: eacces. Target: ./user.beam. Function: get_file. Process: code_server.
=ERROR REPORT==== 3-Dec-2016::18:46:38 ===
File operation error: eacces. Target: ./kernel_config.beam. Function: get_file. Process: code_server.
=ERROR REPORT==== 3-Dec-2016::18:46:38 ===
File operation error: eacces. Target: ./queue.beam. Function: get_file. Process: code_server.


Uplift theia dependencies from v1.34.2 to 1.37.2

Do a yarn upgrade prior.

This upgrade is necessary so the following Theia version uplift still works with yarn start:electron.
This resulting yarn.lock is then based on going from clean to having run yarn locally a few times.

Base this uplifted-to Theia version on community's latest.
Cap the fontawesome-svg-core version to less than 1.3.0.

Without this change, the hereby upgrade leads to a broken yarn build.
This is despite requesting for a version that remains compatible with 1.2.17.
So a yarn upgrade without this adjustment lends the use of v1.3.0, which breaks the build.
Below [1] flags that breaking version as deprecated, and the later versions are way more major uplifts (6.x.y).

[1]https://www.npmjs.com/package/@fortawesome/fontawesome-svg-core?activeTab=versions
Signed-off-by: Marco Miller<EMAIL_ADDRESS>

Could you please upgrade to the latest community release [1] done May 05, 2023, i.e. 1.37.x? This will be the baseline used in the next CDT cloud blueprint community release as well. Thanks.
[1] https://theia-ide.org/releases/

The latest that I saw flying by is 1.38.0, publicised on Twitter IIRC. Maybe [1] above wasn't updated yet accordingly? But I might be misunderstanding this process.
A note, I'm working on fixing a rebuild issue with electron, pertaining to node-abi not being up-to-date it seems. So I'll amend some of these commits soon as well for that.

The latest that I saw flying by is 1.38.0, publicised on Twitter IIRC. Maybe [1] above wasn't updated yet accordingly?

The reference [1] is about community releases (every 3 month) and the content is correct. It has a cross-reference to the monthly releases on top if the page.

As previously mentioned, I get the below error upon testing this PR with electron. @vince-fugnitto, would you know why, by any chance? Not sure if I should upgrade anything or not, as I think the dependency versions already match with Theia's currently. But WDYT?
~/git/theia-trace-extension$ yarn start:electron
yarn run v1.22.19
$ yarn rebuild:electron && yarn --cwd examples/electron start
$ yarn --cwd examples/electron theia rebuild:electron --cacheRoot ../..
$ /home/(...)/git/theia-trace-extension/node_modules/.bin/theia rebuild:electron --cacheRoot ../..
Module not found: find-git-repositories
Processed "node-pty"
Processed "nsfw"
Processed "drivelist"
Processed "native-keymap"
✖ Rebuild Failed

An unhandled error occurred inside electron-rebuild
Could not detect abi for version 23.3.5 and runtime electron.  Updating "node-abi" might help solve this issue if it is a new release of electron

@marco-miller it may be time to perform a general yarn upgrade to update the lockfile, after doing so the yarn rebuild:electron command passed. Please note that there might  be other changes necessary after performing the upgrade (ex: fortawesome).

@bhufmann it works well for me, can you try with a compatible node version as I don't believe node 18 is supported by the framework according to the prerequisites.

Now, trying to start the browser example after packaging electron fails with a similar issue. But it works after cleaning and rebuilding without packaging electron prior. And I just noticed other versions under examples/electron which I might have to bump too, accordingly (e.g., electronVersion); WIP.

Now, trying to start the browser example after packaging electron fails with a similar issue. But it works after cleaning and rebuilding without packaging electron prior. And I just noticed other versions under examples/electron which I might have to bump too, accordingly (e.g., electronVersion); WIP.

-Done; pushed by now. I also added a related note in the README.

I'm using v16.20.0 as well. I did git clean -xdf, and I still get the issue. Deleting the node_modules directory doesn't help for me. Any suggestions?

Are you using the latest PR update with the now aligned electronVersion? If so, maybe share your exact sequence of terminal commands, so I can try to reproduce it. Thanks.

I'm using v16.20.0 as well. I did git clean -xdf, and I still get the issue. Deleting the node_modules directory doesn't help for me. Any suggestions?

Are you using the latest PR update with the now aligned electronVersion? If so, maybe share your exact sequence of terminal commands, so I can try to reproduce it. Thanks.

I had to clean my environment and now it's working with both the executable and yarn start:electron. Btw, I didn't have to delete the node-modules directory after yarn package and it still works for both.

I'm using v16.20.0 as well. I did git clean -xdf, and I still get the issue. Deleting the node_modules directory doesn't help for me. Any suggestions?

Are you using the latest PR update with the now aligned electronVersion? If so, maybe share your exact sequence of terminal commands, so I can try to reproduce it. Thanks.

I had to clean my environment and now it's working with both the executable and yarn start:electron. Btw, I didn't have to delete the node-modules directory after yarn package and it still works for both.
I had to delete the node-modules directory for yarn start:browser. It would be good to have that fixed too.

The latter is what I mentioned in the README, yes. I don't know how to fix this further, thus that note I added up in there.

When running yarn package I get the error print-out below. However, the executable still works. Do you get the same error?
    Error: Could not detect abi for version 23.3.6 and runtime electron.  Updating "node-abi" might help solve this issue if it is a new release of electron
        at getAbi (/home/eedbhu/git/theia-training/theia-trace-extension/node_modules/node-abi/index.js:36:9)
        at module.exports (/home/eedbhu/git/theia-training/theia-trace-extension/node_modules/prebuild-install/rc.js:73:57)
        at Object.<anonymous> (/home/eedbhu/git/theia-training/theia-trace-extension/node_modules/prebuild-install/bin.js:9:25)
        at Module._compile (node:internal/modules/cjs/loader:1196:14)
        at Object.Module._extensions..js (node:internal/modules/cjs/loader:1250:10)
        at Module.load (node:internal/modules/cjs/loader:1074:32)
        at Function.Module._load (node:internal/modules/cjs/loader:909:12)
        at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
        at node:internal/main/run_main_module:22:47

This was previously fixed for me locally when I updated this PR with that other commit, about the clean yarn (re)upgrade &co.

When running yarn package I get the error print-out below. However, the executable still works. Do you get the same error?
    Error: Could not detect abi for version 23.3.6 and runtime electron.  Updating "node-abi" might help solve this issue if it is a new release of electron
        at getAbi (/home/eedbhu/git/theia-training/theia-trace-extension/node_modules/node-abi/index.js:36:9)
        at module.exports (/home/eedbhu/git/theia-training/theia-trace-extension/node_modules/prebuild-install/rc.js:73:57)
        at Object.<anonymous> (/home/eedbhu/git/theia-training/theia-trace-extension/node_modules/prebuild-install/bin.js:9:25)
        at Module._compile (node:internal/modules/cjs/loader:1196:14)
        at Object.Module._extensions..js (node:internal/modules/cjs/loader:1250:10)
        at Module.load (node:internal/modules/cjs/loader:1074:32)
        at Function.Module._load (node:internal/modules/cjs/loader:909:12)
        at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
        at node:internal/main/run_main_module:22:47

This was previously fixed for me locally when I updated this PR with that other commit, about the clean yarn (re)upgrade &co.

That doesn't fix it for me.

When running yarn package I get the error print-out below. However, the executable still works. Do you get the same error?
    Error: Could not detect abi for version 23.3.6 and runtime electron.  Updating "node-abi" might help solve this issue if it is a new release of electron
        at getAbi (/home/eedbhu/git/theia-training/theia-trace-extension/node_modules/node-abi/index.js:36:9)
        at module.exports (/home/eedbhu/git/theia-training/theia-trace-extension/node_modules/prebuild-install/rc.js:73:57)
        at Object.<anonymous> (/home/eedbhu/git/theia-training/theia-trace-extension/node_modules/prebuild-install/bin.js:9:25)
        at Module._compile (node:internal/modules/cjs/loader:1196:14)
        at Object.Module._extensions..js (node:internal/modules/cjs/loader:1250:10)
        at Module.load (node:internal/modules/cjs/loader:1074:32)
        at Function.Module._load (node:internal/modules/cjs/loader:909:12)
        at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
        at node:internal/main/run_main_module:22:47

This was previously fixed for me locally when I updated this PR with that other commit, about the clean yarn (re)upgrade &co.

That doesn't fix it for me.

@vince-fugnitto, would you be able to also review this (updated) PR again at this stage? So we may confirm issues with it if any left. I'm able to build it locally but @bhufmann cannot. I'd need your help if any (issues), or from someone in your team please, to progress on this -if anything more. Thanks.

@marco-miller @bhufmann I followed some configurations and dependencies used in theia-blueprint (as it is the main example the project has for using and packaging electron) and it seems to work better.

I am able to start the browser example, start the electron example, package electron and there are no longer errors about the node-abi:
$ (cd examples/electron/ && yarn package)
/home/vince/workspaces/theia-trace-extension/examples/electron
yarn run v1.22.19
$ electron-builder
  • electron-builder  version=23.6.0 os=5.15.0-69-generic
  • loaded configuration  file=/home/vince/workspaces/theia-trace-extension/examples/electron/electron-builder.yml
  • description is missed in the package.json  appPackageFile=/home/vince/workspaces/theia-trace-extension/examples/electron/package.json
  • writing effective config  file=dist/builder-effective-config.yaml
  • skipped dependencies rebuild  reason=npmRebuild is set to false
  • packaging       platform=linux arch=x64 electron=23.3.6 appOutDir=dist/linux-unpacked
  • copying Electron  source=/home/vince/workspaces/theia-trace-extension/node_modules/electron/dist destination=/home/vince/workspaces/theia-trace-extension/examples/electron/dist/linux-unpacked
  • asar usage is disabled — this is strongly not recommended  solution=enable asar and use asarUnpack to unpack files that must be externally available
  • file source doesn't exist  from=/home/vince/workspaces/theia-trace-extension/examples/electron/plugins
  • file source doesn't exist  from=/home/vince/workspaces/theia-trace-extension/trace-compass-server
  • asar usage is disabled — this is strongly not recommended  solution=enable asar and use asarUnpack to unpack files that must be externally available
  • building        target=AppImage arch=x64 file=dist/Theia Trace Example Application-0.1.0.AppImage
  • default Electron icon is used  reason=application icon is not set
  • building        target=deb arch=x64 file=dist/electron-theia-trace-example-app_0.1.0_amd64.deb
Done in 131.66s.

For reference this is their electron-builder.yml.

@marco-miller @bhufmann I followed some configurations and dependencies used in theia-blueprint (as it is the main example the project has for using and packaging electron) and it seems to work better.

I am able to start the browser example, start the electron example, package electron and there are no longer errors about the node-abi:
$ (cd examples/electron/ && yarn package)
/home/vince/workspaces/theia-trace-extension/examples/electron
yarn run v1.22.19
$ electron-builder
  • electron-builder  version=23.6.0 os=5.15.0-69-generic
  • loaded configuration  file=/home/vince/workspaces/theia-trace-extension/examples/electron/electron-builder.yml
  • description is missed in the package.json  appPackageFile=/home/vince/workspaces/theia-trace-extension/examples/electron/package.json
  • writing effective config  file=dist/builder-effective-config.yaml
  • skipped dependencies rebuild  reason=npmRebuild is set to false
  • packaging       platform=linux arch=x64 electron=23.3.6 appOutDir=dist/linux-unpacked
  • copying Electron  source=/home/vince/workspaces/theia-trace-extension/node_modules/electron/dist destination=/home/vince/workspaces/theia-trace-extension/examples/electron/dist/linux-unpacked
  • asar usage is disabled — this is strongly not recommended  solution=enable asar and use asarUnpack to unpack files that must be externally available
  • file source doesn't exist  from=/home/vince/workspaces/theia-trace-extension/examples/electron/plugins
  • file source doesn't exist  from=/home/vince/workspaces/theia-trace-extension/trace-compass-server
  • asar usage is disabled — this is strongly not recommended  solution=enable asar and use asarUnpack to unpack files that must be externally available
  • building        target=AppImage arch=x64 file=dist/Theia Trace Example Application-0.1.0.AppImage
  • default Electron icon is used  reason=application icon is not set
  • building        target=deb arch=x64 file=dist/electron-theia-trace-example-app_0.1.0_amd64.deb
Done in 131.66s.

For reference this is their electron-builder.yml.

Many thanks for having checked this and the tips. I'll look into these and likely push an update soon.

The errors during build are gone with these suggested changes. However, I get the error about ERR_DLOPEN_FAILED from above. I did the following steps:
git clean -xdf
yarn
cd examples/electron/
yarn package
cd dist/
./Theia\ Trace\ Example\ Application-0.1.0.AppImage

Then I noticed if I do yarn start:electron first before yarn package I don't get the error. @vince-fugnitto, yarn start:browser does rebuild:electron (yarn --cwd examples/electron theia rebuild:electron --cacheRoot ../..). Should that be done as well before package?

@bhufmann these are the steps I do generally:

git clean -ffdx
yarn
cd examples/electron
yarn theia rebuild:electron
yarn package
cd dist/
./Theia\ Trace\ Example\ Application-0.1.0.AppImage

@bhufmann these are the steps I do generally (when packaging):

git clean -ffdx
yarn
cd examples/electron
yarn theia rebuild:electron
yarn package
cd dist/
./Theia\ Trace\ Example\ Application-0.1.0.AppImage

Thanks for the steps. I've never had to do step yarn theia rebuild:electron. Maybe this should be added to the package step, so that user don't forget and run into the same issue?

I get ERR_DLOPEN_FAILED when using yarn start:browser after having used the electron yarn commands above. It works after git-cleaning again along with yarn. I mean, all this after having applied the previous fixes locally. Anyway, I'll push them now while updating the README so it mentions git-cleaning where necessary, AFAIK that is. This PR will then be ready for review again.

@marco-miller @bhufmann so you are aware the current yarn theia rebuild:electron and yarn rebuild:browser scripts that you have in the repository rebuilds native modules, and you call them at the moment when performing yarn start:browser and yarn start:electron:
https://github.com/eclipse-cdt-cloud/theia-trace-extension/blob/45432b4055d63022aa68676b30aa61e07b2c28b6/package.json#L13-L14
It is important when switching from the browser application to the electron application (and vice-versa) to rebuild for the target, no need to git clean -ffdx and so on.
For packaging this will also be required which is why I mentioned it in https://github.com/eclipse-cdt-cloud/theia-trace-extension/pull/984#issuecomment-1587744405.

@marco-miller @bhufmann so you are aware the current yarn theia rebuild:electron and yarn rebuild:browser scripts that you have in the repository rebuilds native modules, and you call them at the moment when performing yarn start:browser and yarn start:electron:
https://github.com/eclipse-cdt-cloud/theia-trace-extension/blob/45432b4055d63022aa68676b30aa61e07b2c28b6/package.json#L13-L14
It is important when switching from the browser application to the electron application (and vice-versa) to rebuild for the target, no need to git clean -ffdx and so on.
For packaging this will also be required which is why I mentioned it in #984 (comment).

Ah, ok; thanks for having clarified that even further. I'll update this accordingly. I'd have this question please: is it normal that the rebuild:browser script doesn't --cdw to examples/browser first, as rebuild:electron does for its own? As for the --cacheRoot difference though, it looks genuine to me.

@marco-miller @bhufmann so you are aware the current yarn theia rebuild:electron and yarn rebuild:browser scripts that you have in the repository rebuilds native modules, and you call them at the moment when performing yarn start:browser and yarn start:electron:
https://github.com/eclipse-cdt-cloud/theia-trace-extension/blob/45432b4055d63022aa68676b30aa61e07b2c28b6/package.json#L13-L14
It is important when switching from the browser application to the electron application (and vice-versa) to rebuild for the target, no need to git clean -ffdx and so on.
For packaging this will also be required which is why I mentioned it in #984 (comment).

Ah, ok; thanks for having clarified that even further. I'll update this accordingly. I'd have this question please: is it normal that the rebuild:browser script doesn't --cdw to examples/browser first, as rebuild:electron does for its own? As for the --cacheRoot difference though, it looks genuine to me.

I think that is the issue for the :browser case. So I'm currently looking into aligning the rebuild:browser script.

I'm done pushing my latest fixes/update, ready for review again. Thanks for all the hints that led to this so far.

Thanks. It also works following the steps in the README.md for packaging. You could do the rebuilding of electron as part of the script yarn package.

Yes; pushed as a follow-up commit herein. Thanks.


[MMCA-4303] Adding missing unit tests

As per the ticket the current statement coverage is 83.57% and after adding this test it is still the same. Could you please increase it to at least 85% as this is our minimum target for test coverage? Once done, please update the minimum coverage to  85.


Feature iso date format with non english language

Fixes iso datestamp format parsing issue.
parse('2015-05-02T10:20:19+0000', languages=['fr'])
is not parsed, while
parse('2015-05-02T10:20:19+0000', languages=['en']) has good result.
Fixes #45

@Allactaga please take a look again.


returns  a single message at a time

How can I returns the first message for a vue-validator field. Useful when trying to display a single message at a time.

Thank you for your feedback!!

Useful when trying to display a single message at a time.

Sorry, I could understand.
Can you provide the minimum example code please ?

I have two forms, for example, if the first check is not passed, only to return to the first error information, the second form doesn't need to check again until the first check passed

I've ran into the same need. My use case was a field that is required and needs to be a number. When left empty I want just the required message displayed. If the field is filled out but not a number I want to display a error that a number needs to be entered.

Yes I have the same use-case like this.

I don't want to show two error messages a time.

I've ran into the same need too!

Echoing everything everyone else has already said on this thread. This would be a nice feature if it's not already supported.

a workaround:

hope the single-error-msg feature to be added.

Second this feature.


ctranslate2: 3.18.0 -> 3.20.0; python310Packages.ctranslate2: unblock by using tensorflow-bin

Unfortunately our tensorflow source build is behind and broken, so
migrating to the binary distribution for the time being to unbreak
ctranslate2.
Also take the opportunity to bring ctranslate2 up to the latest version.
https://github.com/OpenNMT/CTranslate2/blob/v3.20.0/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

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

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

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

(Some what releated, would you like to take a look at https://github.com/NixOS/nixpkgs/pull/255998)

jax (dependency of tensorflow-bin) is broken on nixos-unstable: https://hydra.nixos.org/build/236085123/nixlog/1

Worked last night on master for me on x86_64-linux. Just seems to be very brittle.


Dropzone with FileTrigger doesn't work in Safari

Provide a general summary of the issue here
If I drop any file into DropZone using Safari browser, It simply do nothing.
import {FileTrigger, Button} from 'react-aria-components';

function Example() {
  let [file, setFile] = React.useState(null);

  return(
    <DropZone>
      <FileTrigger
        onSelect={(e) => {
          let files = Array.from(e);
          let urls = files.map((file) => file.name);
          setFile(urls);
        }}>
        <Button>Select a file</Button>
      </FileTrigger>
      {file && file}
    </DropZone>
  );
}

🤔 Expected Behavior?
DropZone works as expected in combination with FileTrigger. File name is presented under FileTrigger.
😯 Current Behavior
File name of dropped file is not presented in GUI.
💁 Possible Solution
No response
🔦 Context
No response
🖥 Steps to Reproduce

Open this page in Safari browser.
Go to the following example:

import {FileTrigger, Button} from 'react-aria-components';

function Example() {
  let [file, setFile] = React.useState(null);

  return(
    <DropZone>
      <FileTrigger
        onSelect={(e) => {
          let files = Array.from(e);
          let urls = files.map((file) => file.name);
          setFile(urls);
        }}>
        <Button>Select a file</Button>
      </FileTrigger>
      {file && file}
    </DropZone>
  );
}

Drop any file into the Dropzone.

Version
"react-aria-components": "^1.0.0-beta.1"
What browsers are you seeing the problem on?
Safari
If other, please specify.
No response
What operating system are you using?
macos
🧢 Your Company/Team
No response
🕷 Tracking Issue
No response

Hi thanks for reporting this! Seems like we forgot to add onDrop to the example which is why the file name is not appearing when you drop a file.


Title: Add Flappy Bird Game

Is your feature request related to a problem? Please describe.

Implement a functional Flappy Bird game for our website.
This game will serve as a fun and engaging feature for our users, showcasing our capability to develop interactive web applications.
The game should include the core mechanics, a scoring system, and a user-friendly interface.

Describe the solution you'd like.

Initial Setup: Create repository and project structure.
Bird Mechanics: Implement bird rendering, gravity, and flapping.
Environment: Develop scrolling background and pipes.
Collision Detection: Implement collision detection.
Scoring: Set up scoring system and display.
User Interface: Design start and game over screens.
Sound Effects: Add optional sound effects.
Testing: Test on different devices and browsers.
Deployment: Deploy game on website.

Describe alternatives you've considered.
.
Add any other context or screenshots about the feature request here.

I would like to work on this issue. Please assign me this task for GSSoC'24.

Is your feature request related to a problem? Please describe.

Implement a functional Flappy Bird game for our website.
This game will serve as a fun and engaging feature for our users, showcasing our capability to develop interactive web applications.
The game should include the core mechanics, a scoring system, and a user-friendly interface.

Describe the solution you'd like.

Initial Setup: Create repository and project structure.
Bird Mechanics: Implement bird rendering, gravity, and flapping.
Environment: Develop scrolling background and pipes.
Collision Detection: Implement collision detection.
Scoring: Set up scoring system and display.
User Interface: Design start and game over screens.
Sound Effects: Add optional sound effects.
Testing: Test on different devices and browsers.
Deployment: Deploy game on website.

Describe alternatives you've considered.
.
Add any other context or screenshots about the feature request here.

Using HTML, CSS, JS

@AsmitaMishra24 All the best 👍🏻 and make sure to use only HTML, CSS and JS with proper all screens responsiveness

@swapnilsparsh Please assign me this task under gssoc , I want to work on this isssue.


More unit tests

Copy some of the C++ to the new pytest suite to improve coverage and catch PGC regressions

Exposes a bug in the yield operation that I'm trying to track down. Merging because this completes the task


[BEAM-10989] Add @SchemaCaseFormat annotation

Adds an @SchemaCaseFormat annotation that can be used to control the case format used in schema field names. For example:
@DefaultSchema(JavaFieldSchema.class)
@SchemaCaseFormat(CaseFormat.LOWER_UNDERSCORE)
class MyClass {
   public String user;
   public int ageInYears;
   @SchemaCaseFormat(CaseFormat.UPPER_CAMEL)
   public boolean knowsJavascript;
}

Will produce a schema with fields "user", "age_in_years", and "KnowsJavascript".
I think the primary application of this will be using lower_underscore for schemas that will be used across languages (e.g. in LogicalType base types, and cross-language transform configuration objects), but I figured a general purpose solution based on CaseFormat would be more valuable.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @kennknowles
CC: @reuvenlax @lukecwik

retest this please

Run Java PreCommit

Run Java_Examples_Dataflow PreCommit


(maint) Include hours and minutes in duration display

Previously, we displayed durations as only seconds. That meant that
lengthy operations would be reported as, for instance, 123 seconds. We
now break these times down into hours and minutes where applicable,
written as:
1 hr, 2 min, 3 sec
2 min, 3 sec
3.76 sec
When the duration is under a minute, we include two decimal places for
the seconds display. Otherwise, we strip the sub-second duration and
round to the nearest second.

This matches the behavior of puppet job / puppet task.


cmd/go: hang in 'exec powershell' in TestScript/build_acl_windows on windows/arm64

greplogs --dashboard -md -l -e 'FAIL: TestScript/build_acl_windows .*(?:\n    .*)*\> exec powershell.*(?:\n    .*)*: test timed out while running command' --since=2019-03-08
2022-02-12T05:44:16-f14ad78/windows-arm64-11
2022-02-11T22:01:05-badba35/windows-arm64-10

It's curious that the only two failures occurred within a few hours of each other — close enough that the coordinator could have been running them concurrently. It kind of makes me wonder whether something in the PowerShell executable is non-hermetic. 🤔
This test was converted to a script test in CL 165752, so the test itself is fairly old. Since these are the first time we've seen this failure mode, I'm going to leave this test enabled to see whether any future failures are also time-correlated.

It kind of makes me wonder whether something in the PowerShell executable is non-hermetic.

Looking at the logs, I think the hand happens while running go build -o $TMP\main.exe main.go, so before powershell is executed.
Still no clue.


Update CODEOWNERS

Please check if the PR fulfills these requirements

[x] The commit message follows the conventional commits guidelines
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce?

Code ownership changes.

What is the current behavior?

The code ownership is limited to the existing declaration.

What is the new behavior (if this is a feature change)?

The code ownership has been expanded.

Does this PR introduce a breaking change?

No.

Other information:

Not applicable.

Thanks team! :tada:


Omnibus fixes to IRGen for variadic generic type metadata

This PR takes over @slavapestov's #64163 and adds a number of fixes around the local type data and fulfillment subsystems.

@swift-ci Please test

My new test worked on my machine because I have the dead-stripping pass disabled locally for bootstrapping reasons.  I rewrote the test to force the metadata to be emitted.

@swift-ci Please test

@swift-ci Please test Linux

@swift-ci Please test


(Code Could not connect) via TCP???

I've created the API and it works fine if i open it in a separate browser window - however if i use the Tester part of FRAPI Admin I get an error saying:
Error: Unable to connect to
tcp://api.WEBSITEURL.co.uk:80. Error
#10060: A connection attempt failed because
the connected party did not properly respond
after a period of time, or established
connection failed because connected host has
failed to respond.
I get a similar message if I add my database credentials to the config. If i manually add mysql_connect('host', 'user', 'pass') to my code file it works fine.
Is this error caused by my setup or FRAPI?

I am having the exact same problem when using the tester. I cloned the latest version from Github and settings are default.
Error: Unable to connect to tcp://api.frapi:8080.
Error: php_network_getaddresses: getaddrinfo
failed: Name or service not known

Also, I don't understand why this has been closed w/o a solution?

My issue was that I was using a development box at home with a fake url and
the box didn't resolve the fake url in it's own /etc/hosts file. Once I put
the fake url in the /etc/hosts file it worked fine.
Thank you,

Bruce Gemberling          Web Developer
Sugar Land, TX<PHONE_NUMBER>
On Sun, Dec 4, 2011 at 8:36 AM, Dominik Jungowski <
<EMAIL_ADDRESS>
wrote:

Also, I don't understand why this has been closed w/o a solution?

Reply to this email directly or view it on GitHub:
https://github.com/frapi/frapi/issues/60#issuecomment-3006746

Nice, I just wanted to write the same thing :D
My Frapi is running on a virtual machine an api.frapi is in my /etc/hosts directing to the virtual machine. Once I modified the hosts file of the virtual machine aswell, adding <IP_ADDRESS> api.frapi, it worked fine.


resume support

We should send the corresponding token.

Receive should always use '-s' in order to enable this - when sending, we should check the value of the receive_resume_token if there is a remote dataset and send a resume stream accordingly.  We must check for the "extensible_dataset' feature, which is a prerequisite of using the "-s" flag.

The token shall be received (881f9ac) but sending doesn't check for or use tokens at this point.


Learning Pathways Pnp Provisioning Template failed

Provisioning status: Unfortunately your site provisioning at least partially failed!
correlation ID: b4eb2350-f9dc-4da8-998a-b3876dbe7aca

Hi,
Thanks for using the Look Book site. This seems to be a random hiccup on the SharePoint side which would imply that the template should work properly if you try it one more time. Seems that the provisioning did succeed partially. Can you test this one more time and, in case of any failure, share the updated Correlation ID (by creating a new issue) for us to double-check the flow. Thanks.


dingo installation problem

hi, I get this error when I try to install dingo on fresh laravel 5.8

Duplicate of #1624.


Request a shard version of LRU implementation.

This LRU implementation is very impressive, and I believe its performance should be one of the top, thanks for this brilliant job!
But we really need a sharded version instead of synced version to perform well in a high parallelism.
For example, a "shardedlru.go" like
type ShardedLRU[K comparable, V any] struct {
	mu  []sync.RWMutex
	lru []*LRU[K, V]
}

Background:
I happen to be currently implementing a simple lru cache as well, and would like to know how its performance compares to popular libraries. Here is my results on
const (
	keysize     = 16
	cachesize   = 16384
	parallelism = 1000
)

goos: linux
goarch: amd64
cpu: Intel(R) Xeon(R) Silver 4216 CPU @ 2.10GHz
BenchmarkCloudflareGet
BenchmarkCloudflareGet-8   	100000000	        60.48 ns/op	      16 B/op	       1 allocs/op
BenchmarkElasticGet
BenchmarkElasticGet-8      	15093165	       424.4 ns/op	       0 B/op	       0 allocs/op
BenchmarkHashicorpGet
BenchmarkHashicorpGet-8    	27390493	       349.8 ns/op	       0 B/op	       0 allocs/op
BenchmarkPhusluGet
BenchmarkPhusluGet-8       	199958748	        30.45 ns/op	       0 B/op	       0 allocs/op
PASS
ok  	command-line-arguments	32.350s

Obviously freelru (and hashicorp) does not perform as well as it should (I think it should be top-notch) due to the use of a single lock.
Please refer to https://github.com/phuslu/lru?tab=readme-ov-file#benchmarks for the code, thanks.

By the way, my latest version also use similar idioms to offload GC, thank you for your ideas!
see https://github.com/phuslu/lru/blob/master/rhh.go and https://github.com/phuslu/lru/blob/master/list.go
Could please add my lru lib to this bench?

@phuslu Thanks for your feedback!
Yes to a sharded version. I recently made a parallel benchmark and ran into the slowness issue of SyncedLRU. A quick hack to add partitions / shards - similar to what you suggest - made it faster by a factor of 20x when using 1024 shards (tested with 20 cores locally). I'd let the user apply the number of shards.
Not to forget: the benchmarks create an extreme situation that you normally won't run into in production... A more realistic benchmark would just do e.g. 100 or 1000 of Get/Add calls per second and thus won't run into heavy lock contention. I think we need to keep this in mind when answering the question what we are optimizing for.
The good speed of FreeLRU was more of a "side-effect" - the priority was to optimize GC overhead with relatively small key/value types.

Could please add my lru lib to this bench?

Would be a pleasure. You can also just make a PR :)

looking forward~

ShardedLRU is in main. I added a few parallel benchmarks (more to come).
Currently, the code is wrapped around LRU. But I'd like to reduce the number of allocs on creation. And the logic to determine the number of shards needs more thoughts.
Comments / reviews / tests are appreciated :)

Benchmark results for Get():

Congrats! Can I say that this is meet my expectation? 😆 Now freelru is a good alternative for fastcache.

Congrats! Can I say that this is meet my expectation? 😆 Now freelru is a good alternative for fastcache.

😃 I guess so. Fastcache isn't an LRU, no eviction occurs, but likely ShardedLRU is faster (adding that to their benchmarks would possibly not please them !?).

I mean although []struct{K,V} still have GC overhead comparing with fastcache, but fastcache(and its friends) has their own overhead - marshaling/unmarshaling between []byte and go objects.

Yes, for pointer objects or structs that contain pointer objects, you should have your own memory "flattening" code (e.g. use slicing inside a large memory block) and store indices or pointers inside the LRU/cache.


ci(test.yml): updated matrix

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add GenerateSecurityAudit to Get-DbaPrivilege

Type of Change

[ ] Bug fix (non-breaking change, fixes # )
[x] New feature (non-breaking change, adds functionality, fixes # )
[ ] Breaking change (effects multiple commands or functionality, fixes # )
[ ] Ran manual Pester test and has passed (`.\tests\manual.pester.ps1)
[ ] Adding code coverage to existing functionality
[ ] Pester test is included
[ ] If new file reference added for test, has is been added to github.com/sqlcollaborative/appveyor-lab ?
[ ] Nunit test is included
[ ] Documentation
[ ] Build system

Purpose

Add functionality to Get-DbaPrivilege to check for SeAuditPrivilege ('Generate security audits') in the Local Security Policy
Approach

Simple copy/paste/adapt of existing code from the same function.
Commands to test

Get-DbaPrivilege
Screenshots

Learning

How does this setting also pertain to SQL Server...what issue/feature request is being resolved by this addition?

This permission is required in order to allow SQL Audit to log to the
Windows security log.
--
Ben
On Fri, Nov 1, 2019, 05:18 Shawn Melton<EMAIL_ADDRESS>wrote:

How does this setting also pertain to SQL Server...what issue/feature
request is being resolved by this addition?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/sqlcollaborative/dbatools/pull/6171?email_source=notifications&email_token=ADHQE2LCL6WEOLF4GWPUO5LQRQM7RA5CNFSM4JHENIO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEC2YUHI#issuecomment-548768285,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADHQE2P7DTFT55HF6BLV2C3QRQM7RANCNFSM4JHENIOQ
.

Ah, ok...never log to security log so was not aware of that one 👍


Wish:Feature or example on how to use paching of LicenseFile setting in *.config

In Sitecore.FakeDb's configuration that is applied there is a setting called "LicenseFile", which tells Sitecore.FakeDb where the licensefile for Sitecore is located. It would be great if the ConfigReader of Sitecore.FakeDb supported a way to patch this setting, making it easier to upgrade Sitecore.FakeDb in a big solution with many test projects that is using Sitecore.FakeDb (Habitat).
If this is already supported, please add something to the wiki where it is shown how to do it, because I have not been able to make it work so far.

Thanks for reporting this, @michaelthyregod.
I'd expect the regular Sitecore patching to work here, but IIRC, there might be some issues with that. Needs to be investigated.

I've figured out how to make it work - so closing this ticket.


Websocket Reconnection Failes

Hi @bennyn I am still having a reconnection issue though I changed connect() parameters.
So, at some point websocket establishes connection and then closes, and this run as a loop. On ON_OPEN it shows that it establishes connect and just after that ON_CLOSE it says convection closed and repeats the same. I have to manually stop and run program in order to make it work.
Any recommendation and/or suggestion? should I subscribe every time when it reconnects again?

Hey, can you show me your code? I will try to reproduce this problem on my machine.

Please have look at the source code.
Thanks for helping me out.

Ok, I already see some issues here:

You cannot use this.client.ws.unsubscribe when receiving a WebSocketEvent.ON_CLOSE event because the WebSocket is closed so the unsubscribe message cannot be send through the WebSocket anymore
You still do await this.client.ws.connect but connect is not a Promise anymore since v1.6.0
You don't have to call client.ws.subscribe([this.channel]) after this.client.ws.connect because you are doing this already in your WebSocketEvent.ON_OPEN handler
I am not sure if this.client.ws.subscribe is necessary on every WebSocketEvent.ON_OPEN, I would guess you only need to do it for the very first ON_OPEN, can you confirm?

I had the issue even before adding 1. , 3. and 4. One commit before the latest commit.

I updated the code based on 2. and cleaned up 1., 3. and 4.. Let me run again and see how it goes. I also want to do some debugging so I can give you reason(s) why it happens.

Hey @baloian, thanks for your intensive testing. You can test against the official coinbase-pro library. It is deprecated but should still be able to connect to the WebSocket. If the problem also shows up with their library, then it tends to be a server issue.

That is a good idea. I will come back to testing in 2 weeks probably as I have some deadlines on my work.

Great. Good luck with your deadlines. 🍀


Fix #52, #21 and #35

@mreinstein correctly calls that #54 fixes #52, #21 and partially #35. What this does is use alexa-app's express method instead of cooking our own, plus a test that right now would hang on master and no longer hangs in this branch.
Replaces https://github.com/alexa-js/alexa-app-server/pull/56 on top of #60.
This is dependent on https://github.com/alexa-js/alexa-app/pull/150, I didn't find a better way to get ?utterances, ?schema and preRequest and postRequest support without moving this logic upstream to alexa-app.

Thanks for checking it out @rickwargo. I'll wait for @tejashah88 to do a code review of this and the upstream PR and merge. We should get things sorted out with a release next. Do you have anything blocking and not working after this?

@dblock on the surface it appears all good, but haven't had the time to dig under the covers. i'll have more time tomorrow.

I've updated this with a fix for #35. Now that we're mounting body-parser inside alexa-app, we can just remove it from alexa-app-server. See https://github.com/alexa-js/alexa-app/pull/155 for details.
@tejashah88 this is ready for you to merge

Sorry, @tejashah88, didn't get a chance to review today. I will have time in the morning.

Looks good, however bodyParser.urlencoded() is now removed via alexa-app#152 - found this testing a form post hosted in alexa-app-server. I believe this was previously handled - does it need to be handled or should it be called out in the README?

One (simple) formatting suggestion is to remove trailing slashes from the normalizedRoot in self.loadapps(). The comments have an example where the server root ends with a slash and if included, the message says, "loaded app [hello_world] at endpoint: /alexa//hello_world."

I think the urlencoded bodyparser is not the business of these libraries. I've added a note to UPGRADING in https://github.com/alexa-js/alexa-app/pull/158.
Opened https://github.com/alexa-js/alexa-app-server/issues/68 for the slashes thing, it's cosmetic unless I'm missing something.

Looks like everyone is happy with this, merging. Thanks for your help!

@dblock cosmetic only. I'm fine either way on the urlencoded bodyparser - #64 breaks functionality so it needs to be noted. Could be I was the only one using that.

Yep @rickwargo, I documented this change in UPGRADING, both here (https://github.com/alexa-js/alexa-app-server/pull/69) and alexa-app (https://github.com/alexa-js/alexa-app/pull/158).


Update deps

For some reason I hit this error:
error: the lock file /build/source/Cargo.lock needs to be updated but --frozen was passed to prevent this

so update the deps, first

Confirmed that it successfully builds with this update for https://github.com/NixOS/nixpkgs/pull/214300


requests.exceptions.HTTPError: 403 Client Error: Forbidden for url: https://botometer-pro.p.rapidapi.com/2/check_account

I used to use BotOrNot API when it was with Mashape but now my code does not work. SO I created an app with RapidAPI and obtained the rapidapi_key. I also did a new twitter app. I installed all the dependencies and my code still does not work! So I decided to run the example provided to make sure the API works but still no luck when I run it. I keep on getting this error
Traceback (most recent call last):   File "BotOrNot.py", line 16, in <module>     result = bom.check_account('@ACCOUNTNAME')   File "~/pythonEnvs/Google_Env/lib/python3.7/site-packages/botometer/__init__.py", line 132, in check_account     bom_resp.raise_for_status()   File "~/pythonEnvs/Google_Env/lib/python3.7/site-packages/requests/models.py", line 941, in raise_for_status     raise HTTPError(http_error_msg, response=self) requests.exceptions.HTTPError: 403 Client Error: Forbidden for url: https://botometer-pro.p.rapidapi.com/2/check_account
which does not seems to be in the list of possible error provided here  I would really appreciate anyhelp on why I am getting this error!

Without further information on the environment and the content of your script, it's really hard to determine the cause of the error.
My guess would be that the RapidAPI key is not correct.

To build off of @yangkcatiu, Make sure you're providing the RapidApi key in the X-RapidApi-Key request header. It's easy to forget and would lead to this error.

@yangkcatiu @clayadavis thank you both for helping out. I am using python virtual environment with Mac OS. Here it the test code I am trying to get to work
import botometer

rapidapi_key = "myKeyHere" # now it's called rapidapi key
twitter_app_auth = {
    'consumer_key': 'myKeyHere',
    'consumer_secret': 'myKeyHere',
    'access_token': 'myKeyHere',
    'access_token_secret': 'myKeyHere',
  }
bom = botometer.Botometer(wait_on_ratelimit=True,
                          rapidapi_key=rapidapi_key,
                          **twitter_app_auth)

# Check a single account by screen name
result = bom.check_account('@username')
print(result)

am I missing any key? in the code I put my the correct key instead of "myKeyHere" and I put an actual twitter username instead of "@username"

@clayadavis @yangkcatiu thank you both. I just solved the issue.  I had to click on the "Subscribe to Test Endpoint" button, once I clicked it my API become active and was able to make a request and get results.

Good to hear that!


I'm trying to use

I'm trying to use this library. I copied the example but i can't make it works.
I'm using Fedora Linux.
This is the error:
lua: /usr/share/lua/5.3/rs232.lua:252: attempt to index a nil value (field '_p')
stack traceback:
/usr/share/lua/5.3/rs232.lua:252: in method 'read'
ejemplocom.lua:14: in main chunk
[C]: in ?
Another error.
lua: /usr/share/lua/5.3/rs232.lua:265: attempt to index a nil value (field '_p')
stack traceback:
/usr/share/lua/5.3/rs232.lua:265: in method 'write'
ejemplocom.lua:14: in main chunk
[C]: in ?

This means that port didnt open. https://github.com/moteus/librs232/blob/master/bindings/lua/rs232.lua#L184
Test result of open method.

Thanks. I supossed that but ... why?
The port is ok. I tried with minicom and works fine.
Is something about rights, permissions etc... ?
I'm trying to connect with an Arduino board.

Checkout error returned by  port:open() method

The program is :
local rs232 = require "rs232"
local msg
local p, e = rs232.port('ttyUSB0',{
baud         = '57600';
data_bits    = '8';
parity       = 'NONE';
stop_bits    = '1';
flow_control = 'OFF';
rts          = 'ON';
})
print (p:open())
x,msg = p:write('AT\r\n')
And the result is:
nil    [RS232][OPEN] open error (2)
lua: /usr/share/lua/5.3/rs232.lua:265: attempt to index a nil value (field
'_p')
stack traceback:
/usr/share/lua/5.3/rs232.lua:265: in method 'write'
ejemplocom.lua:13: in main chunk
[C]: in ?
2017-11-06 6:39 GMT+01:00 Alexey Melnichuk<EMAIL_ADDRESS>
Checkout error returned by port:open() method
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/moteus/librs232/issues/5#issuecomment-342051475, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAuj9OTpZHaOWuZJYvz5JoVPNNKEHu7ks5szpuPgaJpZM4QSedf
.

--
José María
@itubalibre
http://itubal.github.io/ http://itubalstyle.blogspot.com

So reason of this error because you do not open port.
May be you need use "/dev/ttyUSB0" as port name,

Ok! It's working!!
Please, update the example code.
2017-11-06 20:32 GMT+01:00 Alexey Melnichuk<EMAIL_ADDRESS>
So reason of this error because you do not open port.
May be you need use "/dev/ttyUSB0" as port name,
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/moteus/librs232/issues/5#issuecomment-342260027, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAuj0M1MgAzMCHpSoIA7qLg9yOBqTojks5sz17FgaJpZM4QSedf
.

--
José María
@itubalibre
http://itubal.github.io/ http://itubalstyle.blogspot.com


The double sidebar issue

When "Add New Test Case" clicked. Should appear only one.

Resolved in linked PR.


SvelteKit simple example

With updated types & renderGraphiql ✅

Real fail? Flickering fail? 😳

Real fail? Flickering fail? 😳

Probably flickering 😞

Real fail? Flickering fail? 😳

Probably flickering 😞

Can we retrigger?

Thanks! 🎉


setEnabled not working

setEnabled to false not working on phone field

Actually you can do that by setEnabled false to the Spinner and the EditText
phoneField.getEditText.setEnabled(false);
phoneFieald.getSpinner.setEnabled(false);

so please add a function to the phone field that does that .
Thanks


feat: enable caching for CLI tooling

Summary

Creates the Git-ignored .caches/ directory to store all cache-related data.
Enables caching for all CLI tools that support the --cache flag (ESLint, Jest, and Prettier).

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add shortcut for index

Add an extension method for all optics (Lens, Iso, ...) and apply optics (ApplyLens, ApplyIso) for index so that we can do:
optic.index(10)

instead of
optic composeOptional index(10)

This should be very similar to what we have done for each:
https://github.com/optics-dev/Monocle/blob/master/core/shared/src/main/scala/monocle/Lens.scala#L284
https://github.com/optics-dev/Monocle/pull/908/files (but we moved it to implicit class)
Please write tests to check type inference is working fine (see https://github.com/optics-dev/Monocle/blob/master/test/shared/src/test/scala/monocle/LensSpec.scala#L121-L129)

started working on this

Thanks @asjad02, don't hesitate to ask if you have any questions. Here or on gitter.

@asjad02 It seems @sapizhak worked on this issue and #956 together. I hope you didn't invest too much time on it.


Wrong interface

Method persistSession() from this library is not able to work with session objects implementing Zend\Expressive\Session\SessionInterface.
There is calling method getId() on session object:
https://github.com/zendframework/zend-expressive-session-cache/blob/master/src/CacheSessionPersistence.php#L175
But getId() method is not part of SessionInterface so it is calling undefined method on session object.
Code to reproduce the issue
final class MySession implements Zend\Expressive\Session\SessionInterface
{
...
}

$mySession = new MySession(...); // OK
$sessionStorage = new CacheSessionPersistence(...); // OK
$sessionStorage->persistSession($mySession, $response); // Error - calling undefined method on session object.

I think it's coming from this: https://github.com/zendframework/zend-expressive-session/blob/master/src/SessionIdentifierAwareInterface.php#L25
There might be missing some interface reference somewhere.

Yes, Session class
https://github.com/zendframework/zend-expressive-session/blob/develop/src/Session.php
is implementing both SessionInterface and SessionIdentifierAwareInterface interfaces so it will work with this Session class. Because of this, there should be different method signature. Not:
public function persistSession(SessionInterface $session, ResponseInterface $response) : ResponseInterface

but this:
public function persistSession(Zend\Expressive\Session\Session $session, ResponseInterface $response) : ResponseInterface

now, we are sure persistSession() method consumes Session object which has getId(). But:

now, we can pass to method only this one specific Session object not our custom implementation based on some interface
actually, we can not change method to this because it is method from SessionPersistenceInterface an we must follow method signature from interface...

I think this can not be solved with interfaces how are now defined in
https://github.com/zendframework/zend-expressive-session
library...

This repository has been closed and moved to mezzio/mezzio-session-cache; a new issue has been opened at https://github.com/mezzio/mezzio-session-cache/issues/2.


Update to plonk 0.8.2

Changes

[x] dusk-plonk updated to 0.8.2 as a dependency. We are using the tag v0.8.2-polygon-1.
[x] Fix dependency issues with rand & libp2p (snow conflict).
[x] Fix indentation & UTs.
[x] Fix crates.io.path

Key files to review

Cargo.toml uses patch section to override the plonk dep.
Crate kate

It uses allocate feature to integrate with plonk on std.
New testnet::public_params fn to set the public params up from a seed.

Changes look good and nothing breaking. Let's go ahead with the merge.


Create our own openjdk7 builds for use as boot JDKs

Java 8 can be built using JDK8 as the boot JDK but in general the preferred approach is to use the version one level back i.e. Java7.
This leaves us with the problem of sourceing a boot JDK, but for newer operating systems and distributions, a version of openjdk7 is not easily available from the distribution's repositories (e.g. RHEL8, Ubuntu 20.04, Debian10).
Since we try to encourae (or at least make it easy for) people to use our scripts to build their own JDK by providing the openjdk-infrastructure ansible scripts, docker files, and the scripts in openjdk-build we should also make it easy to source JDK7 on the operating systems/distrubutions that people are using.
To this end, we should look at building openjdk7. Even if it is not something we're ever going to properly support it would be useful to have it available for use in the playbooks when the distribution does not provide a JDK7. The alternate option would be to source it elsewhere e.g. [azul's Zulu](https://www.azul.com/downloads/zulu-community/?version=java-7-lts&package=jdk. Neither bellsoft Liberica nor SAPMachine have JDK7 available.
This was triggered by discovering that on the AIX build machines we seem to have a version of openjdk7 used for bootstrapping JDK8 and the new machine I was setting up for build appeared not to have that installed via the playbooks (from discussions it appears it may have been built by us from source at some point). The machine does have a version of IBM Java 7 but that did not appear suitable for bootstrapping openjdk8.

I'm not sure we'll be able to build these ourselves for all of the platforms.
I'm comfortable with standardizing on Zulu for this.  Azul is a supporter/sponsor and they are the lead maintainers for 7.

I'm currently in the process of build JDK7 on CentOS6. I've tracked the process I've gone through , and will update as I go.

Run the playbook on the CentOS6 machine (skip the ant install if it makes the next step easier, but I didn't bother)

(Remove Ant 1.10.5 from /usr/local and) Download Ant 1.7.1 from here and extract to /usr/local

Retrieve some of the source code that doesn't come from the openjdk-jdk7 mercurial clone, and place into a folder (i.e. DROP_DIR), still in it's zipped state

mkdir -p DROP_DIR && cd DROP_DIR
wget https://sourceforge.net/projects/jdk7src/files/input-archives/jdk7-jaf-2010_08_19.zip/download -o jdk7-jaf-2010_08_19.zip
wget https://sourceforge.net/projects/jdk7src/files/input-archives/jaxp145_01.zip/download -o jaxp145_01.zip
wget https://sourceforge.net/projects/jdk7src/files/input-archives/jdk7-jaxws2_2_4-b03-2011_05_27.zip/download -o jdk7-jaxws2_2_4-b03-2011_05_27.zip

Clone the JDK7 source code:

hg clone http://hg.openjdk.java.net/jdk7/jdk7 JDK7_BUILD
cd JDK7_BUILD
sh ./get_sources.sh

Change some of the source code to disable-warnings-as-errors when compiling :

In hotspot/make/linux/makefiles/adlc.make , comment out

CFLAGS_WARN = -Werror
CFLAGS += $(CFLAGS_WARN)

In hotspot/make/linux/makefiles/gcc.make, comment out

WARNINGS_ARE_ERRORS = -Werror`

In jdk/make/common/Defs-linux.gmk, comment out

ifeq ($(COMPILER_WARNINGS_FATAL),true)
  GCC_WARNINGS += -Werror
endif

Run gmake sanity (which from what I can gather, is like configure) and then run gmake DISABLE_HOTSPOT_OS_VERSION_CHECK=ok. Setting that variable stops the build throwing an error about building on CentOS6 (as it thinks CentOS6 is too old, when it's actually too new)

Other help: https://hg.openjdk.java.net/jdk7u/jdk7u/raw-file/tip/README-builds.html
Current error:
java full version "1.7.0_261-mockbuild_2020_04_27_15_15-b00"
Using java runtime at: /usr/lib/jvm/java-1.7.0/jre
Error occurred during initialization of VM
Unable to load native library: /usr/lib/jvm/java-1.7.0-openjdk-<IP_ADDRESS>1.x86_64/jre/lib/amd64/libjava.so: symbol JVM_SetNativeThreadName, version SUNWprivate_1.1 not defined in file libjvm.so with link time reference
/home/vagrant/JDK7_build/hotspot/make/linux/Makefile:289: recipe for target 'product' failed
gmake[4]: *** [product] Error 1

@karianna They don't do AIX, and as per original comment I'm struggling to get any Java 7 that works on the AIX 7.1SP5 machine I'm trying to build the OpenJ9 JDK8 on at the moment.
For most of the bulid machines (earlier distributions) we're bootstrapping with the 7 that comes with them. We could certainly set up the playbooks with a zulu again (although we removed most of the references to the zulu repos) for the later distros which aren't supplied with a JDK7 from their repositories as an alternative

Given the problems Will has been having I'm good with using zulu on the newer Linux distributions although I believe it would be useful to be able to reproduce building our own on AIX

In fact zulu isn't available on any Linux architectures other than x64, so arm32, aarch64, s390x, ppc64le can't be sourced that way on modern distributions.

In fact zulu isn't available on any Linux architectures other than x64, so arm32, aarch64, s390x, ppc64le can't be sourced that way on modern distributions.

It looks like Zulu is now available for other Linux architectures (I've seen arm32 and aarch64), but not in version 7 I'm afraid.


[Create New Issue]:

Description
Description
Domain
Android Dev (Flutter)
Type of Contribution
Video
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign


Toolkit Stats Block

Extremely similar to #45 and #54. Should be coded to guard against styling problems when this block appears within other contexts.
Design mockups:

Closed via #75


isError.test.js added

https://playbook.learnersguild.org/Learning_Guide/Review.html
Should follow this guide for submitting review branches


Not found dll error when trying to generate via console

Nswagstudio worked fine, but when I tried generate openapi with a following command:
"nswag aspnetcore2openapi /assembly:CT.DistanceCalculator /output:openapi.json"

I had an error:
System.IO.FileNotFoundException: Could not load file or assembly 'file:///C:\src\CT\CT.DistanceCalculator\source\CT.DistanceCalculator\CT.DistanceCalculator' or one of its dependencies. The system cannot find the file specified.
File name: 'file:///C:\src\CT\CT.DistanceCalculator\source\CT.DistanceCalculator\CT.DistanceCalculator'

Then I tried to publish an assembly with the following command:
dotnet publish --self-contained --runtime win-x64 .\source\CT.DistanceCalculator\CT.DistanceCalculator.csproj

And then I had such error:
System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.AspNetCore.Mvc.Abstractions, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=adb9793829ddae60' or one of its dependencies. The system cannot find the file specified.
File name: 'Microsoft.AspNetCore.Mvc.Abstractions, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=adb9793829ddae60'

How to solve this issue?
Thanks in advance.

Maybe this page helps:
https://github.com/RicoSuter/NSwag/wiki/Assembly-loading
Otherwise /assembly is not the recommended way anymore but you should use /project:

When I specified the project, I got the error:
System.InvalidOperationException: Unsupported target framework '.NETCoreApp'.

you need to specify the correct runtime with eg /runtime:NetCore31

You may need to update your documentation for command line: https://github.com/RicoSuter/NSwag/wiki/AspNetCoreToOpenApiCommand
Also, when I put /assembly:bin/Forecasts.dll I get a FileNotFoundException with a reported path C:\<path to project folder>\bin\bin\Forecasts.dll  Note the duplicated intermediate path.


Add scheduler extension for actions

This will allow to pass state to a scheduled action to avoid closure allocation and allow for delegate caching.
Note this is based on changes from https://github.com/dotnet/reactive/pull/515 which should be merged before this PR.

In all of my projects (private and in the company) I also add a "MinimalSchedule" extension method which even dismisses the state parameter competely (as generic parameter for the action and parameter for the extension method) and uses Unit.Default instead. Its handy in all cases where the state isn't relevant and isn't used.

Could you post it?

@danielcweber yeah, sure. I made a gist for you: https://gist.github.com/Yeah69/41f6c3bcfcfde7cbe53ae178a58bfbbc
A little bonus is the async version ;)
I see that you declare the extension method internal. That way no one outside of this project can benefit of this extension methods.

Yes, the signature is up to debate because of possible ambiguity, therefore it is declared internal.


Create exploration of geocomputation

Explores Geocomputation with R from Lovelace et al to see if we can incorporate anything I learn into this project

linking issue #39, starting edits to rerun appropriate parts of repo to take into account changes in station key

take a look at leafgl package for faster geomcomputation on map view/leaflet. Also grapher but this isn't yet on CRAN

ok so now we have a somewhat working leafgl map with desire lines a la Lovelace et al. Here's what's next:

Clean up the branches/PRs
Incorporate the most recent Bikeshare data and rerun the project
Use the demo shiny and .rmd files to build cleaner, more user-friendly apps to actually deploy
solve major issues, such as #25 (dockless bikes) and #40 (time units) along the way.


Fixed cpp multi-topic consumer when topics are not partitioned

Motivation
The multi-topics consumer in C++ client is not correctly handling the case where topics are not partitioned.

SUCCESS
--none--


chore(renovate): Use shared configuration

Same as https://github.com/cloudquery/terraform-azure-cloudquery/pull/9

This PR is included in version 0.13.1 :tada:


Problem with Database Migration

Hi, I want to update my Application and therefore i need to update the existing database in my App. I know I can handle that with Database Migration, but for me it doesnt work actually. Steps I done so far:

Changed in Android Manifest the Version of my Database
Added the diretory assets/sugar_upgrades and created .sql with content.
I write in the file a couple of lines like these:
alter table 'DAY' add ATTRIBUTE_NAME INTEGER;
...
Write the new attributes which i want to implement for my objects in the class:
For ATTRIBUTE_NAME i write private int attribute_name in the Day class e.g.

Now when i start my App it crashes. Have anybody any tips on how to implement Database Migration or know, what i have done wrong?
Lasse

Okay, didnt solve this with Sugar ORM now. I used now a SQL Helper class which handles now the upgrade of the tables in the database. Works for me fine.


fail to insert under relationship @ManyToOne

I have 2 table DeviceLostRecord and Device which is in @ManyToOne relationship:
`
@Entity
public interface Device extends Observable, Parcelable, Persistable {
@Key
@Generated
int getId();

@Bindable
String getName();

}
@Entity
public interface DeviceLostRecord  extends Observable, Parcelable, Persistable {
@Key
@Generated
int getId();

@Column(value = "CURRENT_TIMESTAMP")
Date getCreateTime();

@Bindable
Location getLocation();

@ManyToOne(cascade = {CascadeAction.NONE})
Device getDevice();

}
`
when I attempt to insert a new record of DeviceLostRecord by:
`
public Observable addDeviceLostRecord(final Device device,final Location location) {
    DeviceLostRecordEntity newLost = new DeviceLostRecordEntity();

    newLost.getDevice().add(device);
    newLost.setLocation(location);
    return dataStore.insert(newLost).toObservable();
}

`
It throws exception like this:

java.lang.IllegalStateException: Exception thrown on Scheduler.Worker thread. Add onError handling.
Caused by: rx.exceptions.OnErrorNotImplementedException: table DeviceLostRecord has no column named device (code 1): , while compiling: insert into DeviceLostRecord (createTime, device, location) values (?, ?, ?)

I have no idea about the solution after googled for one and half day...

Sounds like you generated the tables originally without the device column. You should clear the app data and redeploy the application which will cause the tables to be regenerated

I see. It seems the problem of
    newLost.getDevice().add(device);
after changing it to
        newLost.setDevice(device);
It works now, though another problem comes out. While I am inserting DeviceLostRecord
dataStore.insert(newLost).toObservable();
a unwanted insert to Device happened
(or should I ask in a new issue?)
Anyway, I guess this issue can be closed. Thank you very much.

Hi you should be able to do both, when adding to collection you should update the source object to persist the change.
When you do dataStore.insert(newLost).toObservable(); what's the unexpected insert that occurs? This action should insert the newLost object.

Yes it inserted the newLost object. Also, it did an insert to the device table.... , which is unwanted.
For instance, initial I have
Device table :

device 1

NewLost table :
after doing  dataStore.insert(newLost).toObservable(); :
Device table :

device 1
device 1

NewLost table :

NewLost

If device1 is already existing in the table you should do something like:
device = dataStore.findById(deviceId);
newLost.getDevice().add(device);
dataStore.insert(newLost);

in your original snippet looks like you create a new DeviceLostRecordEntity each time.

super helpful!!!!!!
Thank you very much


Mobile / Fix LHS Menu Button

Github Issue #631
Removed the sphinx-generated top navigation bar from the mobile view entirely.  It only provided access to the table of contents, which on a mobile view, was not responsive.  In the mobile view, relying on the use of the TOC tree and use of the breadcrumbs for navigation.  Will need to enable a means to access the search box w/in the mobile view from any page in a later PR....

Thanks Jared! @asaadmahmood please take a look when you have a chance?

+1, looks fine to me.


⚠ Bofrost.be has degraded performance

In 9ef1d7a, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1986 ms

Resolved: Bofrost.be performance has improved in 932dc22 after 34 minutes.


Add file watcher for the config

It would be nice if a change to the configuration automatically reloads the service.

Not planned to do that as of now.


Use react-roi for image zoom and pan

closes #76

When we load multiple images, they all share the same zoom level. Each image should have a separate zoom level. It's currently not possible to set the initial zoom level with react-roi, so it will not really work as we want yet, but until then you can still already have one react-roi instance per image.

I'm having a look at the TS issue


Expose the global default metrics

This should make it easier to test code that uses go-metrics. In tests the code can be passed a different instance of Metrics, and in production code paths it can use the global Metrics returned from Default().
Without this change patching the global can cause flaky tests when other tests attempt to emit metrics to the global metrics instance.
An example of this can be see in https://github.com/hashicorp/consul/pull/8679 which uses this change to fix a flaky test.
Prior art: https://pkg.go.dev/github.com/hashicorp/go-hclog?tab=doc#Default
cc @armon @banks

CI ran on my branch, but did not appear to run on this PR: https://app.circleci.com/pipelines/github/dnephin/go-metrics/6/workflows/63f98684-a0aa-4510-ad00-8739c361d07d
I think the "run on fork PRs" config needs to be enabled, along with third-party orbs (https://github.com/armon/go-metrics/pull/116#issuecomment-690354747).


ci: add license scan workflow

What this PR does / why we need it:

Added license scan workflow for project dependencies which is aligned with CNCF guidelines.
osv-scanner experimental license scanning is used as agreed here.
The license scan is running in non-blocking mode since it is currently failing. Once all issues are resolved we can configure it to fail the build. See more details here.
The license scan is running together with vulnerability scan. I opened an issue to add support for running only license scan. See more details here.

Which issue(s) this PR fixes:

Fixes #2917

/retest


Add eleventy-favicon plugin

This is a plugin I created to auto generate all the favicon and the HTML declarations that go with (https://www.npmjs.com/package/eleventy-favicon).
Thanks 🚀

Thank you!


power-profiles-daemon 0.13 -> 0.20

Description of changes
Changelog:
The project has moved under the freedesktop 'Upower' group. The service is
now advertised as 'org.freedesktop.UPower.PowerProfiles' in addition to the
previous 'net.hadess.PowerProfiles' for compatibility reasons.
This release adds support for:

Multiple power-profiles-daemon drivers to load simultaneously.  This notably
allows both CPU based control with amd-pstate or intel-pstate as well as
ACPI platform profile based control.

amdgpu panel power savings which uses dedicated hardware in systems with
integrated Radeon graphics to decrease panel power consumption when the
system is on battery.

This release also enables the test suite by default, so distribution vendors
should update packaging accordingly.
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Closes #289019

Add a :+1: reaction to pull requests you find important.

Duplicate of https://github.com/NixOS/nixpkgs/pull/289748